Release Title: Chargent Version 8.45
Release Installation URL: Chargent Installation & Updates
Release Date: July 16, 2026
Package Versions:
- 8.45 – Base
- 8.46 – Orders
- 8.45 – Anywhere
Release Overview #
Chargent v8.45 introduces improvements for our Stripe gateway integration, in which automation surrounding the Customer Token field on the Chargent Order record has been updated. Additionally, we’ve resolved several bugs. For more information, see the details below.
If you have any questions, please contact our support team. We are always happy to help!
Not sure what version of Chargent you’re on? Click here to find out. We always recommend updating and testing in your sandbox org before deploying into production.
Release Details #
Improved Stripe Customer Token Field Automation
We’ve improved the Stripe gateway integration’s automation to automatically populate the Customer Token field on the Chargent Order record. Previously, when using the Stripe gateway integration, the Customer Token field did not populate automatically on the Chargent Order record during certain Payment Method reuse flows (such as reusing a Payment Method on a new order or on subsequent charges for the same order). The new behavior is outlined below:
- Scenario 1 (Reuse on New Order): A payment method is successfully created and saved on “Order A.” Now, when creating a completely separate “Order B” and selecting that existing Payment Method, the customer token is passed to the new order, resulting in a successful transaction.
- Scenario 2 (Multiple Charges on Same Order): The user successfully processes an initial charge on a single Chargent Order. When they attempt to run a second charge on the same record, the customer token is present, and the transaction is successful.
Bug Fixes #
Resolved: Stored Payment Method Mismatch on Experience Cloud Sites
Fixed an issue where, when an authenticated Experience Cloud user deletes an existing payment method and immediately enters a new one in the Take Payment component, the system mistakenly processed the transaction against the old, removed card instead of the new one.
The user interface incorrectly shows that the new card was accepted and confirms a successful transaction. However, the system continues to charge or authorize the transaction using the previously stored payment token.
This issue is strictly limited to the sequence of deleting a card and adding a new one in a single interaction via the Take Payment component. Adding a new card without deleting an existing one, or adding a card to a completely fresh order, works correctly.
Resolution
This issue has been fully resolved in Chargent v8.45. The update ensures that when a customer removes a payment method, the previous card data is cleared instantly from the order, allowing the new card to be registered and charged correctly.
Upgrade to the latest version of Chargent via the Package Installation Manager (PIM) to correct the payment component’s processing sequence.
Resolved: Cybersource Reason Code 101 (missingField: card/accountNumber) on Charges with Tokens
Fixed an issue where recurring billing requests may fail when using the Cybersource gateway integration. When using the Cybersource gateway integration, recurring billing requests may fail with Reason Code 101 (REJECT), resulting in the following error: missingField: card/accountNumber.
Resolution
This issue was partially resolved in v8.26 and is fully resolved in Chargent v8.45. If you encounter this error, update Chargent to v8.45 or later via the Package Installation Manager (PIM) and retry your transaction.
Resolved: Cybersource Reason Code 233 Decline on ACH Transactions when “Savings” is Selected
Fixed an issue where, when using the Cybersource gateway integration to process a bank account transaction with “Savings” selected as the ACH account type, Reason Code 233 (general decline) is returned and the transaction is declined.
Resolution
This issue has been fully resolved in Chargent v8.45. If you use the Cybersource gateway integration, ensure you update to the latest version of Chargent via the Package Installation Manager (PIM) to successfully process your ACH transactions with an ACH account type of “Savings”.
