Skip to content

Connect a payment gateway

A gateway is how ChargeOn actually moves money. Nothing in ChargeOn can take a payment until at least one gateway is connected, active, and verified — repeat this page for every gateway you want to use.

Before you start

  • You need the ChargeOn Admin permission set.
  • Your gateway account already exists, with API credentials ready — or, for GoCardless and RazorPay, an existing merchant account you can authorise ChargeOn against.
  • Decide the Checkout Experience before you start if you can — see Choose a checkout experience. You set it in step 4 below, and it is the single most consequential choice on this page.

Steps

  1. Open the ChargeOn app, go to the Payment Gateway tab (or Settings Hub → Gateways), and click New.
  2. Give it a descriptive Payment Gateway Name — this is what your team sees when choosing a gateway, for example "Production Stripe" rather than just "Stripe".
  3. Choose the Gateway from the list of 20 providers.
  4. Choose the Checkout Experience. See Choose a checkout experience if you have not already decided.
  5. If you are switching Adyen, PayPal or Stripe to Direct API, tick Direct Card Mode Confirmed. ChargeOn blocks the save without it — these three gateways normally avoid raw card data, and this box exists so you consciously accept the extra compliance scope of collecting it yourself.
  6. Enter the Base URI (sandbox) and Live Base URI (production), and set Environment.
  7. Set the Default Currency and Minimum Charge Amount.
  8. Select every Payment Mode (Instant, Schedule, Recurring) and Payment Type this gateway genuinely supports. Leaving one out makes it unavailable later with no explanation on screen — see the gateway reference for what a given gateway actually offers.
  9. Under Credentials, click Add Row for each key-value pair your gateway issued you. ChargeOn encrypts these automatically on save.
  10. Tick Active.
  11. Click Save.

GoCardless and RazorPay connect differently. Instead of entering credentials, create the record and click Connect — this takes you to the provider's own site to authorise ChargeOn against your merchant account, then brings you back automatically. Once connected, also ask your gateway provider to send webhook notifications to the address ChargeOn shows on the gateway record — these are the only two gateways ChargeOn receives that kind of notification from.

Now authorise Salesforce to actually reach the gateway:

  1. Go to Setup → Remote Site Settings and click New Remote Site.
  2. Give it the gateway's name and web address, leave Active ticked, and click Save.

What you should see

The gateway record saved and listed as Active, with your credentials or OAuth connection in place. Next, verify gateway credentials before relying on it.

If it does not work

Symptom Likely cause What to do
Save is blocked with a message about Direct Card Mode You switched Adyen, PayPal or Stripe to Direct API without ticking Direct Card Mode Confirmed Tick it and save again
The Payment Type or Payment Mode you expect is not offered Not every combination is available for every gateway Check the gateway reference for what this gateway actually supports
Payments fail with a connection error even though the credentials look right No Remote Site Setting exists for the gateway's address Add one — steps 12–13
The GoCardless or RazorPay Connect flow does not complete The OAuth redirect did not land back in Salesforce Retry, and confirm My Domain is fully deployed for all users