Broadleaf Microservices
  • v1.0.0-latest-prod

Payment Transaction Release Notes for 1.1.12-GA


  • JDK 11 is required for Broadleaf release trains 1.7.0-GA, and beyond.

  • JDK 17 is supported for Broadleaf release trains 1.8.1-GA, and beyond.

New Features & Notable Changes

  • Introduced new SavedPaymentMethodStatus enums to better represent the status that aligns with the payment transaction execution result, and update the payment method status based on PaymentResponse#recommendedSavedPaymentMethodStatus

    • SavedPaymentMethodStatus.AWAITING_ASYNC_RESULTS - The saved payment method is created for the payment transaction, but the transaction results will be communicated asynchronously. This payment method cannot be used unless the transaction status is unknown.

    • SavedPaymentMethodStatus.INVALID_PAYMENT_METHOD - The payment transaction is failed and the failure type is INVALID_PAYMENT_METHOD.

  • Introduced the PaymentCustomerNotificationService, which was created to handle sending custom branded ACH mandate approval emails for Stripe payment transactions, instead of Stripe’s default emails

  • Improved messaging about archival by including transaction identifier type and making identifier labels in the message more distinct

Schema Changes


Bug Fixes

  • Fixed "Currency Mismatch" error by adding the transactions to the TransactionSummary before execution of any calculation

  • Fixed payment request’s hydration of customer details by using the name and phone values from the billing address if they are blank

  • Fixed issue with the creation time versus update time audit information on payment transactions and the transaction reversal job

  • Fixed issue with recording webhook transactions results if the payment or transaction is archived