Setup¶
Everything an administrator configures once. Most of it you will not touch again after go-live — with the exception of gateway credentials and email templates.
| Page | What it covers |
|---|---|
| Connect a payment gateway | Adding credentials so ChargeOn can reach a gateway |
| Verify gateway credentials | Confirming the connection works before you take live money |
| Choose a checkout experience | The three ways a customer can enter payment details, and how to pick |
| Route payments between gateways | Sending transactions to different gateways by rule, and falling back on failure |
| Map fields to your objects | Telling ChargeOn where to read customer and amount data from |
| Customise notification emails | Changing what customers receive for links, receipts and credit memos |
| Rotate the encryption key | Replacing the key that protects stored credentials |
| Set up multicurrency payments | Scoping gateways to currencies and understanding how ChargeOn picks one |
Connect a gateway before anything else
Every other page in this guide assumes at least one gateway is connected and verified. Nothing in ChargeOn can move money until that is true.
The order that actually matters¶
Most of this section can be read in any order once a gateway exists, but three pages build on each other:
- Connect a payment gateway — while creating the gateway record you choose its Checkout Experience. Read Choose a checkout experience first if you have not decided.
- Verify gateway credentials — do this immediately after connecting, before you rely on the gateway for anything else.
- Map fields to your objects — needs a connected, verified gateway to point at. This is also where you assign the notification email templates and, optionally, fallback gateways.
Rotate the encryption key and set up multicurrency payments are independent of the sequence above — come back to them whenever they apply to you.