Release Title: Chargent Version 8.55
Release Installation URL: Chargent Installation & Updates
Release Date: August 18, 2026
Package Versions:
- 8.55 – Anywhere
- 8.55 – Base
- 8.55 – Orders
Release Overview #
Chargent v8.55 introduces Merchant-Initiated Transactions (MIT) and Card-on-File (COF) compliance updates for our Cybersource gateway integration. 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 #
MIT/COF Compliance
We’ve updated our Cybersource integration by adding fields, settings, and automation related to MIT/COF mandates set by major credit card brands (such as Visa and Mastercard).
What is MIT/COF 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)
This classification, along with whether it is the Initial or Subsequent use of a stored payment credential, must be sent to the payment gateway in every transaction request. Failure to comply can result in higher interchange rates, disputes, or card network penalties.
Why Cybersource?
To improve authorization success rates for recurring and tokenized transactions, Cybersource is actively enforcing VISA and Mastercard’s mandates for Merchant-Initiated Transactions (MIT) and Cardholder-Initiated Transactions (CIT). Customers using the Cybersource gateway integration on Chargent versions prior to 8.55 may experience transactions flagged as “out-of-compliance.” See Cybersource’s article Supporting Merchant-Initiated Transactions and Credential-on-File for Visa, Mastercard, and Discover for more information.
Additional gateway support is forthcoming. Please feel free to reach out if you have any questions.
What’s New?
The following updates were made to Chargent’s automation, settings, and fields as they relate to MIT/COF Compliance:
Automation
After updating to Chargent v8.55, the following data is automatically sent to supported gateways, and no manual entry is required. Chargent automatically classifies every charge and authorization using the following rules (in priority order):
- PAN present → always Customer Initiated (cardholder is actively entering their card)
- Stored payment method, first use → Customer Initiated (Initial credential use)
- Payment Request or Take Payment → always Customer Initiated
- Recurring batch → always Merchant Initiated
- API/explicit override → caller-declared value used
- Fallback → org-wide default setting (configurable — see the “Settings” section below)
Settings
A new setting controls the fallback classification when no rule applies (see the “Automation” section above). This setting defaults to “Customer Initiated Transaction” (the safe default). Most customers should not need to change this.
To modify this setting, follow these steps:
- In the AppLauncher, search for and select Chargent Settings.
- Click the Payment Methods subtab.
- In the dropdown to the right of Default Additional Charge Usage, select the option that best matches your use case based on the “Which option should I choose?” section below.
- Click Save Settings.
Which option should I choose?
To process payments compliantly, Chargent must determine whether your customers are actively involved when an Internal User makes a one-time charge using an existing Payment Method. Actively involved means they are on the phone or giving direct consent. For example, an agent is given express permission by the customer to process a payment, selects an existing Payment Method in the Payment Console, and charges the customer.
Select “Customer Initiated Transactions” if the customer is actively involved. Select ‘Merchant Initiated Transactions’ if the customer is not actively involved. As noted above, most merchants should leave this field set as “Customer Initiated Transactions”.
Fields
New fields were created to allow you to track the payment type (CIT or MIT) and origin (which Chargent feature was used to take payment). The following new fields were added to the Chargent Log and Transaction objects:
| Chargent Log | |
| Payment Initiator | Customer Initiated Transaction or Merchant Initiated Transaction |
| Payment Type | Initial or Subsequent (first vs. repeat use of the stored credential) |
| Transaction | |
| Origin | Where the transaction came from (e.g. Payment Console, Batch, API) |
| Payment Initiator | Customer or Merchant Initiated |
These fields are not automatically added to your page layouts. If you would like to monitor them, you can add them to your page layout manually.
Action Required
All customers who use the Cybersource gateway integration should ensure they update to Chargent v8.55 or later. 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.
Bug Fixes #
Resolved: Stripe: Missing required param: mandate_data[customer_acceptance][online][user_agent]
If your ACH Transactions are failing with Response Status: Declined and Response Message: Missing required param: mandate_data[customer_acceptance][online][user_agent], update to Chargent v8.55 or later via the Package Installation Manager (PIM).
If you continue to experience issues with recurring ACH transactions after updating Chargent, see Stripe: Missing required param: mandate_data[customer_acceptance][online][user_agent].
