The ChargeAfter API is exposed across three distinct environments: Sandbox, UAT, and Production. Each environment utilizes completely isolated data, independent user accounts, and dedicated base URLs.

To switch between environments, simply replace the base URL in your API requests and update your authentication credentials accordingly.

Environment Comparison

Guidelines: When to use each environment

1. UAT (User Acceptance Testing) Environment

Best for: Testing upcoming features, early integrations, and experimental workflows.

When to use: Use this environment when you want to preview and test new ChargeAfter capabilities before they are finalized. It is our bleeding-edge testing ground where new code is deployed as soon as it is ready for feedback.

Note: Because this environment is actively used to iterate on new features, it is less stable than Sandbox and is subject to periodic updates, configuration changes, or data refreshes.

2. Sandbox Environment (Staging)

Best for: Production-like testing, final QA, and continuous integration (CI/CD) pipelines.

When to use: Use this environment to test your software against a stable, reliable version of ChargeAfter that mirrors the live environment. Sandbox serves as your true Staging environment. Whenever our servers are updated in Production, our Sandbox is updated simultaneously to ensure total alignment.

Best Practice: This is the final gate for your QA team. If your integration works perfectly in Sandbox, it is ready for Production.

3. Production Environment

Best for: Live applications interacting with real consumers.

When to use: Switch to this environment only after your integration has passed full verification in your Sandbox/Staging setup.

Warning: Every request made to this endpoint triggers real-world actions, including legal credit applications, credit inquiries for consumers, and actual financial transactions.