Announced on March 24, 2026, support for the legacy configuration with the Payment Methods data model disabled will end on March 24, 2027. See the information and resources below to learn about the impact and transition to the new data model before the deadline.
What’s Changing #
The legacy Chargent configuration is a data model in which the Chargent Payment Methods feature is disabled. We are ending support for the legacy setup and standardizing on the updated Payment Methods model moving forward.
Why We’re Making This Change #
This transition helps ensure:
- Stronger long-term reliability and performance
- Improved security/compliance alignment
- A more consistent, supportable foundation for future enhancements
- More intuitive and convenient user experience
Key Dates #
- Initial notice: March 24, 2026
- End-of-Support (EOS): March 24, 2027
Starting March 24, 2027, we will no longer provide support for the legacy configuration.
Who is Impacted #
Your org is impacted if it is configured with Payment Methods disabled and thus relies on legacy objects/behaviors. To verify whether or not you are using the legacy model, follow these steps:
- Click the App Launcher icon at the top-left of your screen and choose Chargent.
- Select the Chargent Settings tab and Payment Methods subtab.
- If you see a button labeled [Activate Payment Methods], your org is still operating under the legacy model.
Alternatively, if the newer Payment Methods model is active in your org, you will see the complete Payment Methods Settings.
Moving to the New Data Model #
To transition to the new data model, you’ll first want to review dependencies in your configuration and identify items that may be affected, such as integrations, automations, payment collection flows, reconciliation processes, and reporting.
Once you’ve reviewed dependencies and planned the necessary configuration updates, you can begin transitioning to the new data model with Payment Methods activated.
As always, we recommend validating the transition in your sandbox first before deploying to production.
For detailed instructions, see Setting Up Payment Methods.
Resources #
- Setting Up Payment Methods
- Payment Methods Architecture
- Payment Methods Duplication Management
- Contacting Support
FAQs #
What happens at End-of-Support?
We will no longer provide support for the legacy configuration. We strongly recommend transitioning before March 24, 2027.
Will anything stop working on the EOS date?
EOS is a support milestone. Any product/runtime changes will be communicated separately if applicable.
How do I confirm whether I’m impacted?
Review the “Who is impacted” steps above or contact support with your org details.
How long will the transition take?
It depends on your dependencies (integrations/automations). Most teams plan sandbox testing plus a controlled production rollout at least two weeks prior to the EOS date.
