Release Title: Chargent Version 8.65
Release Installation URL: Chargent Installation & Updates
Release Date: November 10, 2026
Package Versions:
- 8.65 – Anywhere
- 8.65 – Base
- 8.65 – Orders
Release Overview #
Chargent v8.65 includes updates to the Worldpay (fka Vantiv) gateway integration, including MIT/CIT Compliance and Worldpay Account Updater service compatibility. This release also includes multiple bug fixes. See below for more details.
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 #
Worldpay (fka Vantiv) Gateway Integration Updates
Our goal is to be the premier integration between Worldpay and Salesforce. As such, we’ve significantly updated our Worldpay gateway integration by improving MIT/CIT compliance and adding support for Worldpay’s Account Updater service.
MIT/CIT Compliance
We’ve updated our Worldpay integration by adding fields, settings, and automation related to MIT/CIT mandates set by major credit card brands (such as Visa and Mastercard).
What is MIT/CIT Compliance?
Card networks (Visa, Mastercard, and others) require that every payment using a stored payment method be classified as either:
- Customer Initiated (CIT) — the customer is actively present and authorizing the payment (e.g., clicking “Pay Now” in a portal)
- Merchant Initiated (MIT) — the customer has previously authorized recurring or unattended charges and is not present at the time of payment (e.g., scheduled batch billing)
Action Required
Customers using the Worldpay gateway integration are encouraged to update to the latest version of Chargent. Once updated, classification is automatic, and the default setting (Customer Initiated) is correct for most customers. There are two use cases that require additional action:
- If you run recurring batch billing: Subsequent batch charges will automatically be sent as Merchant Initiated with the correct stored-credential network reference. Ensure your payment methods have completed at least one successful Initial transaction before batch charges run.
- If you use the Chargent REST API or ActionService: A new optional merchantInitiated boolean parameter is available. Set it to true to explicitly declare Merchant Initiated for custom recurring billing engines and false to explicitly declare Customer Initiated. If omitted, automatic classification applies.
Learn more by visiting our MIT/CIT Compliance documentation.
Worldpay Account Updater
Chargent v8.65 includes compatibility with Worldpay’s Account Updater. When a card is renewed, replaced, or reissued, Worldpay’s Account Updater returns the new card details inside the transaction response. Chargent now reads that data and keeps the stored card information current, so recurring and card-on-file charges continue to work without manual updates.
Action Required
If you would like to start using Worldpay’s Account Updater, ensure the following prerequisites are completed:
- Update to the latest version of Chargent PIM (Package Installation Manager).
- Ensure you are using Worldpay API version 12. Learn more by visiting Gateway Version Update.
- Enable Account Updater in Worldpay by visiting Get started with Account Updater.
Learn more by visiting Worldpay’s Account Updater documentation.
Note: This refers to Worldpay’s own Account Updater feature and is not related to Chargent’s Account Updater feature.
Bug Fixes #
The following bugs can be resolved by updating to Chargent v8.65 or later.
Resolved: Worldpay: New Response Code Errors
Customers using Worldpay were receiving errors due to Worldpay’s new Response Codes: 136 and 137. Resolved in Chargent v8.65, these response codes will no longer result in an error.
Resolved: Surcharging: Switching Payment Methods From Credit Card to Bank Account Display Issue
An error occurred when switching from credit card to bank account payment methods, causing the surcharge amount to display after switching when it should be removed. The issue has been resolved, and the surcharge is correctly removed when switching from Credit Card to Bank Account.
Resolved: Cybersource: Refunds With Surcharging Causing Errors
Partial refunds that included a surcharge amount caused CyberSource to reject the partial refund with reason code 203 (refund/credit exceeds original transaction amount). Additionally, full refunds including a surcharge amount could cause a null pointer exception. Both errors were resolved in Chargent v8.65.
Resolved: FatZebra: Tokenization Failure without CVV
When using the FatZebra gateway integration, credit cards with no CVV supplied failed to tokenize, returning the response “CVV is required”. This has been resolved in Chargent v8.65, and credit cards can now be tokenized successfully without the CVV using the FatZebra gateway integration.
Resolved: Unresolved Transactions Created on Payment Retry With Surcharging
When processing a payment with surcharging, a payment retry after an initial failure (such as a bad ZIP code or CVV, expired card, or gateway validation decline) was creating an Unresolved Transaction in Chargent instead of a Transaction record. This issue has been resolved, and surcharged retries will now correctly create a Transaction record in Chargent.
