Release Title: Chargent version 7.96
Release Date: August 11, 2025
This version is no longer available to download via the Package Installation Manager (PIM). Customers may only install or update to the latest version of Chargent, which includes features, enhancements, and fixes from all previous versions. For more information about updating Chargent, see Chargent Installation & Updates.
For information about our latest release, please refer to Release Notes.
Release Overview #
Chargent version 7.96 focuses on bug fixes and security enhancements. Specifically, issues related to the Cybersource Gateway Integration, Experience Cloud payments, and our Legacy SOAP API were resolved. See the details below for more information. 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.
Enhancements #
Security Enhancements
We’re constantly working hard to ensure the utmost security of Chargent. This update includes several behind-the-scenes security enhancements. We’ve also updated the OAuth completion steps that appear when customers first access the Chargent Settings tab. Learn more by visiting our Chargent Settings Tab documentation.
Bug Fixes #
Resolved: Cybersource Update Token Error
Fixed a bug that began in Chargent v7.70, where some customers using the Cybersource gateway integration were unable to perform an update token call, receiving the error message “Not Approved. Reject”. This error surfaced due to an updated requirement for Cybersource callouts that requires a Grand Total in token operations. Please update to the latest version of Chargent to resolve the error.
Learn more about our Cybersource Integration.
Resolved: Experience Cloud User Flow Error
Fixed an issue that may occur when an Experience Cloud user attempts to process an ACH transaction via a custom-built flow, resulting in the following error: “Error completing bank payment sale. Please try again or contact support.”
You can verify the issue by using your browser’s developer console (in Chrome, click the three dots in the top right of your browser window, click More Tools, and click Developer Tools), where the following line will appear: “User does not have access to the following fields:ChargentBase__Gateway__c.ChargentBase__Allow_Unlinked_Refund__c.”
This error will not occur when a System Administrator attempts to make a payment, but it will occur when Experience Cloud users attempt to make a payment. When the error occurs, a Chargent Order record will be generated without a related Transaction record, and your gateway will successfully process the payment. To resolve the error, update to the latest version of Chargent.
Resolved: Legacy SOAP API Regression Error
Fixed an issue impacting customers using AppFrontier’s Legacy SOAP API, where the code would fail due to a null Transaction ID. We recommend all customers using our Legacy SOAP API update to the latest version of Chargent if they experience any issues related to their customization.
Alternatively, we recommend switching to our new REST API for additional functionality and ease of use.
Resolved: Scratch Org REST API Response Missing Payment Method Information
Resolved an issue related to transactions created with the REST API in Scratch Orgs, where the response may be missing information related to the following objects: Chargent Payment Methods, Chargent Logs, or Chargent Tokens. This issue surfaced in Chargent v7.95. Please update to the latest version of Chargent to apply the fix.
Learn more about Chargent’s REST API. Additionally, see Understanding Payment Methods Architecture to learn about our Payment Methods Objects.
Known Issue #
Cybersource XML Parsing Error
We are currently working hard to resolve an error that occurs when populating the PO Number while using the Cybersource gateway integration. In this case, when attempting to make a payment using the Cybersource gateway with the PO Number field populated, the following error occurs: “soap:Client – XML parse error.”
Workaround: Until the issue is resolved, do not populate the PO Number field on the Chargent Order record when using the Cybersource gateway integration. For the time being, customers can opt to populate another unused field with a value representing the PO Number or use Cybersource’s Custom Field Mapping.
