Feature/Notable Change | Impacted Services | Links |
---|---|---|
Introduced YugabyteDB Support |
||
Moved the storage of saved payment methods to PaymentTransactionServices |
PaymentTransactionServices |
|
Enhanced identification & storage of display attributes for PaymentAccounts |
PaymentTransactionServices |
Path | Description |
---|---|
|
Add PaymentAccount to Customer |
|
Update PaymentAccount’s Last Transaction Data |
Path | Description of Changes |
---|---|
|
Permission roots were changed to To continue using the legacy permission roots of |
|
|
|
|
|
|
|
broadleaf.customer.saved-payment-method.storage-location
How and where saved payment methods are stored.
See Saved Payment Method Storage Location Configuration for more details
broadleaf.customer.messaging.payment-account.create.enabled
Description: Declares if the CreatePaymentAccountEventListener is responsible for creating customer payment accounts based on the checkout completion event.
See Saved Payment Method Storage Location Configuration for more details
Default value: true
broadleaf.customer.messaging.payment-account.create.display-attributes.card-type-attribute
Description: The name of the display attribute where the credit card type is stored.
Default value: "creditCardType"
broadleaf.customer.messaging.payment-account.create.display-attributes.card-number-attribute
Description: The name of the display attribute where the credit card number is stored, which should be masked.
Default value: "creditCardNumber"
broadleaf.customer.messaging.payment-account.create.display-attributes.card-expiration-month-attribute
Description: The name of the display attribute where the credit card expiration month is stored.
Default value: "creditCardExpDateMonth"
broadleaf.customer.messaging.payment-account.create.display-attributes.card-expiration-year-attribute
Description: The name of the display attribute where the credit card expiration year is stored.
Default value: "creditCardExpDateYear"
broadleaf.customer.web.saved-payment-method.legacy-permission-enabled
Description: If set to true, then the legacy permission roots of CUSTOMER_SAVED_PAYMENT_MANAGEMENT, CUSTOMER, & CUSTOMER_PROFILE can be used for CustomerPaymentAccountEndpoint interactions.
Default value: false
There are new permissions and scopes for some service OAuth2 clients. Permissions and scopes can be added via admin or sql script.
See AuthServices release notes for more details.