How Card Processing Is Set Up
What you provide and what RevKeen configures so you can accept card payments
- Who your card acquirer is and how payments reach it
- What you provide during onboarding
- What RevKeen configures on your behalf
- How card data is kept out of your systems
RevKeen card payments run over one path: the NMI payment gateway, routed to Elavon as your acquirer. You do not connect a gateway yourself. RevKeen configures card processing for you during onboarding, as described in Account Setup.
How the pieces fit
| Party | Role |
|---|---|
| Elavon | Your acquirer. You hold your own Elavon merchant agreement, which gives you a merchant ID (MID). Elavon performs its own underwriting and settles card funds to your bank account. |
| NMI | The payment gateway. It carries card transactions from RevKeen to Elavon and tokenises card details. |
| RevKeen | Configures an NMI gateway profile for your Elavon MID, and runs checkout, billing, and reporting on top of it. |
What you provide
- Your business details and onboarding application in the RevKeen dashboard
- Your Elavon merchant agreement, or the details needed for Elavon to set one up with you
- Any additional information Elavon asks for during its underwriting
You do not need to create NMI API keys, security keys, or tokenisation keys. RevKeen does not ask you to paste gateway credentials into the dashboard.
What RevKeen configures
- The NMI gateway account and the processor profile that routes your transactions to your Elavon MID
- Card tokenisation on RevKeen-hosted checkout and payment pages
- 3D Secure, and Apple Pay and Google Pay where enabled for your account
Once card processing is live, you can start taking card payments.
To add a further MID or trading entity, or to change how card processing is configured, contact support@revkeen.com. Extra MIDs and gateway work are priced on the Fees page.
How a card payment flows
- Customer enters card -- Card details are entered in RevKeen's hosted checkout form.
- Tokenisation -- Card details are tokenised by NMI in the browser. Raw card data never touches your servers, and RevKeen does not store full card numbers or CVV.
- Authorisation -- RevKeen sends the payment through NMI to Elavon.
- Result returned -- The approval or decline is recorded against the invoice or order, and the customer is redirected.
Taking payments through the API
Card processing is configured once for your account, and every API payment uses it automatically. To take payments programmatically, see the Developer Quickstart and the API reference.
Next Steps
- Checkout -- Choose between hosted checkout links and API-created sessions
- First payment -- Take your first payment end to end
- Payments Guide -- Learn about payment processing
- Webhooks -- Set up payment event notifications
Owner: david · Reviewed 30 Sep 2026 · Next review 30 Oct 2026