The following properties can be configured to control various aspects of the Broadleaf Customer Service
Property | Description |
---|---|
|
JPA Configuration Properties. See |
|
Datasource Configuration Properties. See |
|
Liquibase Configuration Properties. See |
|
Delegating Schema Configuration Properties for running in a composed mode along side other Broadleaf microservices. See |
Property | Description |
---|---|
|
Indicates that the customer’s username should always be set from their email Defaults to |
|
Declares the service that is responsible for storing saved payment methods Options: Default value: IMPORTANT: Even though storing and managing saved payment methods via CustomerServices is still supported, it is deprecated and PaymentTransactionServices should be used instead |
|
Determines whether the legacy permissions ( Defaults |
During checkout, a registered user can select to have their new payment saved.
This creates an event handled by CreatePaymentAccountEventListener
.
The following properties are used to configure that listener.
Property | Description |
---|---|
|
Determines whether the Due to the updated pattern of producing saved payments just after the successful execution of Authorize or AuthorizeAndCapture transactions in PaymentTransactionServices 1.0.2, this listener should only be needed for the transitional period after upgrading PaymentTransactionServices to 1.0.2. Once all the remaining Defaults to true |
|
The name of the display attribute where the credit card type is stored. Defaults to |
|
The name of the display attribute where the credit card number is stored, which should be masked. Defaults to |
|
The name of the display attribute where the credit card expiration month is stored. Defaults to |
|
The name of the display attribute where the credit card expiration year is stored. Defaults to |