Gateway Capability Reference¶
ChargeOn connects 20 payment gateways. Every gateway except GoCardless takes card payments, and all 20 support instant payments, scheduled payments, installment plans and subscriptions.
Use these tables to choose gateways that match your payment types, billing tasks and reporting needs before you connect them.
How to read these tables: choose a gateway marked Yes for the capability you need. Cells with additional text explain the setup or payment type to use.
Some capabilities are marked "With extra setup". That means the gateway can do it, but the gateway record has to be configured a particular way first. That configuration is not something you change from the guide: talk to whoever implemented ChargeOn for you, because it affects how card details are handled and it may affect your PCI obligations.
Payment Types¶
| Gateway | Card | Bank | SEPA |
|---|---|---|---|
| Adyen | Yes | Yes | Yes |
| Authorize.Net | Yes | Yes | No |
| Braintree | Yes | Yes | No |
| Checkout.com | Yes | Yes | Yes |
| CyberSource | Yes | Yes | No |
| Elavon | Yes | Yes (ACH) | No |
| FatZebra | Yes | Yes | No |
| Forte | Yes | Yes (ACH) | No |
| Global Payment | Yes | No | No |
| GoCardless | No | Yes, by mandate | Handled within the same mandate |
| Linked2Pay | Yes | Yes | No |
| NMI | Yes | Yes | No |
| PayPal | Yes | No | No |
| PayTrace | Yes | Yes (ACH) | No |
| RazorPay | Yes | No | No |
| Shift4 | Yes | No | No |
| Sola | Yes | Yes | No |
| Stax | Yes | Yes | No |
| Stripe | Yes | Yes | Yes |
| USAePay | Yes | Yes (ACH) | No |
Bank covers direct bank debits: ACH and e-cheque in the United States, and BECS in Australia. On an Australian-dollar payment the screen says "BECS" rather than "Bank" (see terminology). SEPA has a column of its own because only four gateways handle it, and one of those handles it differently from the rest.
GoCardless is the one gateway whose bank support works by mandate rather than by debiting an account afresh each time. The customer authorises a mandate once, and ChargeOn then charges against that mandate for every payment afterwards, including installments and subscriptions. The mandate itself is GoCardless’s stored payment method.
Operations¶
| Gateway | Authorise then capture | Void | Refund | Partial capture | Saved payment methods | Installments and subscriptions |
|---|---|---|---|---|---|---|
| Adyen | With extra setup | With extra setup | Yes | Yes | Yes | Yes |
| Authorize.Net | Yes | Yes | Yes | Yes | Yes | Yes |
| Braintree | Yes | Yes | Yes | Yes | Yes | Yes |
| Checkout.com | Yes | Yes | Yes | Yes | Yes | Yes |
| CyberSource | Yes | Yes | Yes | Yes | Yes | Yes |
| Elavon | Yes | Yes | Yes | No | Yes | Yes |
| FatZebra | Yes | Yes | Card only | Yes | Yes | Yes |
| Forte | Yes | Yes | Yes | Yes | Yes | Yes |
| Global Payment | Yes | Yes | Yes | Yes | Yes | Yes |
| GoCardless | No | No | Yes | No | The mandate is the stored payment method | Yes |
| Linked2Pay | Yes | Yes | Yes | No | Yes | Yes |
| NMI | Yes | Yes | Yes | No | Yes | Yes |
| PayPal | With extra setup | With extra setup | Yes | Yes | Yes | Yes |
| PayTrace | Yes | Yes | Yes | Yes | Yes | Yes |
| RazorPay | No | No | Yes | No | No | Yes, through its own checkout flow |
| Shift4 | Yes | Yes | Yes | Yes | Yes | Yes |
| Sola | Yes | Yes, including a bank payment before it settles | Yes | Yes | Yes | Yes |
| Stax | Yes | Yes, including a bank payment before it settles | Yes | Yes | Yes | Yes |
| Stripe | With extra setup | With extra setup | Yes | Yes | Yes | Yes |
| USAePay | Yes | Yes | Yes | Yes | Yes | Yes |
Use the Refund column to choose a gateway for card or bank refunds. FatZebra provides full and partial refunds for card payments.
Partial capture takes less than the amount originally authorised on a card. Choose a gateway marked Yes in that column for this task. On Elavon, Linked2Pay and NMI, capture the full authorised amount or void the hold.
Payment Links work on all 20 gateways. The address the customer receives varies: most gateways issue a link to a page ChargeOn hosts on your own Salesforce Site, while a few send the customer to the gateway's own checkout page instead.
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 is extra detail, such as tax amount and purchase order number, sent with a business card transaction to reduce processing costs. Twelve of the twenty transmit it.
| Gateway | Reconciliation | Level 2 commercial card data |
|---|---|---|
| Adyen | No | Yes |
| Authorize.Net | Yes | Yes |
| Braintree | Yes | Yes |
| Checkout.com | No | Yes |
| CyberSource | Yes | No |
| Elavon | No | No |
| FatZebra | Yes | Yes |
| Forte | Yes | Yes |
| Global Payment | No | No |
| GoCardless | Yes | No |
| Linked2Pay | No | No |
| NMI | Yes | Yes |
| PayPal | Yes | No |
| PayTrace | No | Yes |
| RazorPay | Yes | No |
| Shift4 | Yes | No |
| Sola | Yes | Yes |
| Stax | Yes | Yes |
| Stripe | Yes | Yes, in two levels of detail. See the note below |
| USAePay | Yes | Yes |
How much Level 2 data Stripe sends depends on your setup
In its standard configuration Stripe sends a purchase order, an invoice number and a customer code as reference information. The full Level 2 set, which adds the tax amount, the order reference, the customer reference and the shipping postcode, needs the Stripe gateway record configured differently.
If Level 2 interchange savings on Stripe matter to your business, raise it with whoever implemented ChargeOn before you go live, because the change is easier to make then than afterwards.
Gateway Fallback¶
Gateway fallback automatically retries a declined card payment on a backup gateway, so one gateway's problem does not cost you the sale (see terminology).
Set up fallback for card payments using eligible primary and backup gateways from the table below. Ask your implementation team to confirm each gateway record’s configuration.
| Gateway | Can act as a backup |
|---|---|
| Adyen | With extra setup |
| Authorize.Net | Yes, in its standard configuration |
| Braintree | Yes, in its standard configuration |
| Checkout.com | Yes, in its standard configuration |
| CyberSource | Yes, in its standard configuration |
| Elavon | Yes, in its standard configuration |
| FatZebra | Yes, in its standard configuration |
| Forte | Yes, in its standard configuration |
| Global Payment | Yes, in its standard configuration |
| GoCardless | No |
| Linked2Pay | Yes, in its standard configuration |
| NMI | Yes, in its standard configuration |
| PayPal | With extra setup |
| PayTrace | Yes, in its standard configuration |
| RazorPay | No |
| Shift4 | Yes, in its standard configuration |
| Sola | Yes, in its standard configuration |
| Stax | Yes, in its standard configuration |
| Stripe | With extra setup |
| USAePay | Yes, in its standard configuration |
A gateway marked Yes, in its standard configuration can act as a backup with its standard setup. Confirm the configuration of each gateway record with your implementation team. With extra setup applies to a gateway used as either the primary or a backup. See route payments and set up fallback.
How ChargeOn Learns a Payment's Outcome¶
ChargeOn receives status updates from GoCardless and RazorPay by webhook. For the 17 gateways listed below as scheduled checks, the transaction status job keeps outcomes up to date. Review Linked2Pay outcomes in your Linked2Pay dashboard.
| Gateway | How to review the outcome |
|---|---|
| GoCardless, RazorPay | Webhook updates in ChargeOn |
| Linked2Pay | Linked2Pay dashboard |
| Adyen, Authorize.Net, Braintree, Checkout.com, CyberSource, Elavon, FatZebra, Forte, Global Payment, NMI, PayPal, PayTrace, Shift4, Sola, Stax, Stripe, USAePay | Scheduled checks update ChargeOn |
Gateways That Behave Differently¶
Most of the twenty behave the way the tables above suggest. A handful are worth reading about before you choose one, so nothing surprises you later.
NMI¶
Confirm NMI’s connection by taking a test payment with test credentials, then check the result in Transaction History and the NMI dashboard. Scheduled status checks query NMI for each transaction.
Linked2pay¶
Confirm Linked2Pay’s connection with a test payment using test credentials. Review its outcome in the Linked2Pay dashboard. You can charge, refund, void and capture Linked2Pay payments.
Gocardless¶
GoCardless takes bank payments using a mandate the customer authorises once. That mandate is the stored payment method for future charges, and webhook updates keep payment outcomes current.
Razorpay¶
RazorPay takes card payments immediately and supports refunds. Use its checkout flow for installments and subscriptions. Webhooks update ChargeOn with payment outcomes.
Adyen, PayPal and Stripe¶
Customers complete payment on these gateways’ checkout pages, and ChargeOn records the outcome. To use capture, void or gateway fallback, ask your implementation team to complete the additional setup on the gateway record.
Sola and Stax¶
Sola and Stax can void a bank payment before it settles, as well as a card authorisation.
Fatzebra¶
Use FatZebra for card and bank payments and saved payment methods. Card payments support full and partial refunds.
Related Reading¶
- ChargeOn terminology covers Payment Type, payment modes, saved payment methods and the rest of the vocabulary this page assumes.
- Quick start guide walks through connecting a gateway.