Gateway capability reference¶
ChargeOn connects 20 payment gateways. Every gateway except GoCardless supports card payments, and every one can take an instant, scheduled or recurring charge. Beyond that, each one is built differently, so the exact set of payment types, checkout experiences and operations it offers differs from the next one. That is not a scorecard — a gateway that supports fewer operations is not a lesser gateway, it is a different fit for a different business. Use these tables to see exactly what each gateway supports before you connect it.
How to read these tables: ✓ means yes. An em dash (—) means not supported. Where the answer needs more than yes or no, the cell says so directly.
Payment types¶
| Gateway | Card | Bank | SEPA |
|---|---|---|---|
| Adyen | ✓ | ✓ | ✓ |
| Authorize.Net | ✓ | ✓ | — |
| Braintree | ✓ | ✓ | — |
| Checkout.com | ✓ | ✓ | ✓ |
| CyberSource | ✓ | ✓ | — |
| Elavon | ✓ | ✓ (ACH) | — |
| FatZebra | ✓ | ✓ | — |
| Forte | ✓ | ✓ (ACH) | — |
| Global Payment | ✓ | — | — |
| GoCardless | — | ✓ — by mandate | Handled within the same mandate |
| Linked2Pay | ✓ | ✓ | — |
| NMI | ✓ | ✓ | — |
| PayPal | ✓ | — | — |
| PayTrace | ✓ | ✓ (ACH) | — |
| RazorPay | ✓ | — | — |
| Shift4 | ✓ | — | — |
| Sola | ✓ | ✓ | — |
| Stax | ✓ | ✓ | — |
| Stripe | ✓ | ✓ | ✓ |
| USAePay | ✓ | ✓ (ACH) | — |
Bank covers direct bank debits — ACH and e-cheque in the United States, and BECS in Australia, which appears on screen as "BECS" rather than "Bank" for an Australian-dollar payment (see terminology). SEPA is broken out on its own because only four gateways handle it, and one of them handles it differently from the rest.
GoCardless is the one gateway whose bank support works by mandate rather than by debiting an account fresh each time. The customer authorises a mandate once; ChargeOn then charges against that mandate for every payment afterwards, including recurring ones. The mandate itself is GoCardless's stored payment method — there is no separate saved-payment-method step. GoCardless has no card path at all.
Checkout experience¶
This is the single most consequential setting on a gateway, and the most misunderstood. Checkout Experience is chosen on each gateway record, not fixed to the gateway product. The same gateway can run Direct API on one record and Hosted Fields on another — it decides what your customer sees and who handles the card details (see terminology). Seventeen of the twenty gateways offer both a Direct API and a Hosted Fields path; which one actually runs for a given connection is up to whoever configures that record, not a property of the gateway's brand.
| Gateway | Direct API | Hosted Fields | Redirect |
|---|---|---|---|
| Adyen | ✓ — needs the Direct Card Mode confirmation | ✓ | ✓ (default) |
| Authorize.Net | ✓ (default) | ✓ | — |
| Braintree | ✓ (default) | ✓ | — |
| Checkout.com | ✓ (default) | ✓ | — |
| CyberSource | ✓ (default) | ✓ | — |
| Elavon | ✓ (default) | ✓ | — |
| FatZebra | ✓ (default) | ✓ | — |
| Forte | ✓ (default) | ✓ | — |
| Global Payment | ✓ (default) | ✓ | — |
| GoCardless | — | — | ✓ (only option) |
| Linked2Pay | ✓ (only option) | — | — |
| NMI | ✓ (default) | ✓ | — |
| PayPal | ✓ — needs the Direct Card Mode confirmation | ✓ | ✓ (default) |
| PayTrace | ✓ (default) | ✓ | — |
| RazorPay | — | — | ✓ (only option) |
| Shift4 | ✓ (default) | ✓ | — |
| Sola | ✓ (default) | ✓ | — |
| Stax | ✓ (default) | ✓ | — |
| Stripe | ✓ — needs the Direct Card Mode confirmation | ✓ | ✓ (default) |
| USAePay | ✓ (default) | ✓ | — |
Only three gateways offer a single experience each: Linked2Pay (Direct API only), RazorPay and GoCardless (Redirect only). Every other gateway can be switched between experiences, and — as the tables below show — that switch also changes which operations are available and whether the gateway can take part in gateway fallback.
For Adyen, PayPal and Stripe, Direct API is available but is not their default — it requires ticking the Direct Card Mode confirmation on the gateway record, because it means your Salesforce org handles the raw card number instead of the gateway's own checkout page.
Payment Links work on all 20 gateways. The address the customer receives just depends on the Checkout Experience: a Direct API or Hosted Fields gateway issues a link to a page ChargeOn hosts on your own Salesforce Site; a Redirect gateway issues a link to the gateway's own checkout page.
Operations¶
| Gateway | Authorise → capture | Void | Refund | Partial capture | Saved payment methods | Recurring |
|---|---|---|---|---|---|---|
| Adyen | ✓ — Hosted Fields or Direct API only | ✓ — Hosted Fields or Direct API only | ✓ | ✓ | ✓ | ✓ |
| Authorize.Net | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Braintree | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Checkout.com | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| CyberSource | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Elavon | ✓ | ✓ | ✓ | — | ✓ | ✓ |
| FatZebra | ✓ | ✓ | ✓ — card only; a bank payment cannot be refunded | ✓ | ✓ | ✓ |
| Forte | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Global Payment | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| GoCardless | — | — | ✓ | — | The mandate is the stored payment method | ✓ |
| Linked2Pay | ✓ | ✓ | ✓ | — | ✓ | ✓ |
| NMI | ✓ | ✓ | ✓ | — | ✓ | ✓ |
| PayPal | ✓ — Hosted Fields or Direct API only | ✓ — Hosted Fields or Direct API only | ✓ | ✓ | ✓ | ✓ |
| PayTrace | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| RazorPay | — | — | ✓ | — | — | ✓ — captured through its own checkout flow, not a saved payment method |
| Shift4 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Sola | ✓ | ✓ — including a bank payment before it settles | ✓ | ✓ | ✓ | ✓ |
| Stax | ✓ | ✓ — including a bank payment before it settles | ✓ | ✓ | ✓ | ✓ |
| Stripe | ✓ — Hosted Fields or Direct API only | ✓ — Hosted Fields or Direct API only | ✓ | ✓ | ✓ | ✓ |
| USAePay | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Every gateway supports refunds, in full or in part, with one payment-type exception: on FatZebra, card payments refund normally but bank payments cannot be refunded through ChargeOn. Check the Refund column above before promising a customer a refund on a bank payment. Partial capture is a narrower, separate capability: taking less than the amount originally authorised on a card, before the hold is released. Three of the gateways that support capture don't offer it — Elavon, Linked2Pay and NMI capture the full authorised amount or nothing. GoCardless and RazorPay show a dash only because they have no capture step at all.
Payment Links are supported by every gateway and are covered in Checkout experience above, since the link's web address depends on that setting rather than varying operation by operation.
Reconciliation and Level 2 data¶
Reconciliation compares what ChargeOn recorded against what the gateway actually processed (see terminology). Fourteen of the twenty gateways are wired into it. Level 2 commercial card data — extra detail such as tax amount and purchase order number, sent with a business card transaction to reduce processing costs — is transmitted by twelve of the twenty.
| Gateway | Reconciliation | Level 2 commercial card data |
|---|---|---|
| Adyen | — | ✓ |
| Authorize.Net | ✓ | ✓ |
| Braintree | ✓ | ✓ |
| Checkout.com | — | ✓ |
| CyberSource | ✓ | — |
| Elavon | — | — |
| FatZebra | ✓ | ✓ |
| Forte | ✓ | ✓ |
| Global Payment | — | — |
| GoCardless | ✓ | — |
| Linked2Pay | — | — |
| NMI | ✓ | ✓ |
| PayPal | ✓ | — |
| PayTrace | — | ✓ |
| RazorPay | ✓ | — |
| Shift4 | ✓ | — |
| Sola | ✓ | ✓ |
| Stax | ✓ | ✓ |
| Stripe | ✓ | ✓ — full set on Direct API or Hosted Fields; reference metadata only on Redirect (see note below) |
| USAePay | ✓ | ✓ |
On Stripe, Level 2 depends on your checkout experience
Stripe sends different data depending on how the gateway is configured. With Direct API or hosted fields, it sends the full Level 2 set — tax amount, order reference, customer reference and shipping postcode. With the redirect checkout experience, it sends only a purchase order, invoice number and customer code as reference information, without tax or shipping.
If Level 2 interchange savings matter to you on Stripe, that is a reason to choose Direct API or hosted fields over redirect. See Checkout experience above.
Being outside the reconciliation or Level 2 list isn't tied to how capable or widely used a gateway otherwise is — Adyen and Checkout.com, both full dual-mode gateways, sit outside reconciliation, for example.
Gateway fallback¶
Gateway fallback automatically retries a declined card payment on a backup gateway, so a single gateway problem does not cost you the sale (see terminology). Fallback is precise about what it covers: it applies to card payments, and only between gateways that are running Direct API at the moment of the charge. A gateway record running Hosted Fields or Redirect is never a fallback target, whatever the brand — the card details were entered somewhere ChargeOn cannot re-use them from.
| Gateway | Takes part in fallback | Condition |
|---|---|---|
| Adyen | ✓ | Only while its record runs Direct API, with the Direct Card Mode confirmation ticked |
| Authorize.Net | ✓ | Whenever its record runs Direct API |
| Braintree | ✓ | Whenever its record runs Direct API |
| Checkout.com | ✓ | Whenever its record runs Direct API |
| CyberSource | ✓ | Whenever its record runs Direct API |
| Elavon | ✓ | Whenever its record runs Direct API |
| FatZebra | ✓ | Whenever its record runs Direct API |
| Forte | ✓ | Whenever its record runs Direct API |
| Global Payment | ✓ | Whenever its record runs Direct API |
| GoCardless | Never | No card path exists to retry a card payment on |
| Linked2Pay | ✓ | Whenever its record runs Direct API |
| NMI | ✓ | Whenever its record runs Direct API |
| PayPal | ✓ | Only while its record runs Direct API, with the Direct Card Mode confirmation ticked |
| PayTrace | ✓ | Whenever its record runs Direct API |
| RazorPay | Never | Has no Direct API path able to take a raw card number |
| Shift4 | ✓ | Whenever its record runs Direct API |
| Sola | ✓ | Whenever its record runs Direct API |
| Stax | ✓ | Whenever its record runs Direct API |
| Stripe | ✓ | Only while its record runs Direct API, with the Direct Card Mode confirmation ticked |
| USAePay | ✓ | Whenever its record runs Direct API |
RazorPay and GoCardless can never take part in fallback, for structural reasons rather than as a gap. GoCardless has no card path of any kind — bank mandates are not something another gateway can retry. RazorPay has no Direct API implementation capable of taking a raw card number at all, even when its record is flagged Direct API, so there is nothing for the fallback mechanism to hand a card to.
Webhooks and status updates¶
GoCardless and RazorPay post a webhook back to ChargeOn the moment a payment's status changes. Every other gateway is polled: ChargeOn checks in with the gateway on a schedule to keep transaction status up to date, rather than being told immediately.
| Gateway | How ChargeOn learns the outcome |
|---|---|
| GoCardless | Posts a webhook |
| RazorPay | Posts a webhook |
| All other 18 gateways | Polled on a schedule |
Linked2Pay is the one exception within "polled." It has no status-polling of any kind, in addition to no webhook — see Linked2Pay below.
Gateways that behave differently¶
Most of the twenty behave the way the tables above would lead you to expect. A handful are worth knowing about specifically, so choosing one does not come with a surprise later.
NMI¶
Verify Credentials always reports failure
NMI has no credentials-verification endpoint to check against, so Verify Credentials reports failure for it no matter what you enter — this is expected, not a sign anything is wrong. Confirm NMI is working by taking a test payment instead. Status polling for NMI is unaffected — it is a live round trip that queries NMI directly for each transaction.
Linked2Pay¶
Linked2Pay has no credential verification and no status polling of any kind — it is the only gateway with neither. It still processes live charges and can be refunded, voided and captured normally; its transaction status is simply never checked automatically after the fact, so it is worth confirming outcomes through your own gateway dashboard for this one.
GoCardless¶
GoCardless supports bank payments only — there is no card path. The mandate the customer authorises once acts as GoCardless's stored payment method, so there is no separate tokenisation step to configure. It is one of only two gateways that post a webhook rather than being polled, and it never takes part in gateway fallback because there is no card transaction for another gateway to retry.
RazorPay¶
RazorPay does not offer an authorisation hold or a void. A RazorPay card charge takes the money immediately rather than reserving it first, so there is nothing to release before it settles. It does support refunds and recurring charges — recurring works through its own token-capture flow rather than through a saved payment method — and it posts a webhook rather than being polled.
Adyen, PayPal and Stripe¶
In their default Redirect experience, these three do not offer capture or void — the customer pays on the gateway's own checkout page, and ChargeOn only learns the result afterwards. Switching the Checkout Experience to Hosted Fields, or to Direct API with the Direct Card Mode confirmation ticked, adds capture and void for all three.
Sola and Stax¶
Sola and Stax can void a bank payment before it settles, in addition to a card authorisation — most gateways only support void on cards. Neither one's credential check is a straightforward pass/fail against the gateway in the way most others are: Sola's check contacts two separate hosts before reporting success, and Stax's check raises an error rather than a clean failure when credentials are wrong. Both gateways' status polling is a live round trip with the gateway.
FatZebra¶
A FatZebra bank payment can be taken and its saved payment method managed, but it cannot be refunded through ChargeOn. Card payments on FatZebra refund normally.
Related reading¶
- ChargeOn terminology — Payment Type, Payment Method, Checkout Experience and the other vocabulary this page assumes.
- Quick start guide — connect a gateway and choose its Checkout Experience.