Payment Gateways
How RevKeen card processing works -- the NMI gateway routed to Elavon acquiring
Configured by RevKeen -- Card processing is set up for you during onboarding. Contact support@revkeen.com if you need to change your configuration or add a merchant ID.
Overview
RevKeen card payments run over one path: the NMI payment gateway, routed to Elavon as your acquirer. You hold your own Elavon merchant agreement and merchant ID (MID). RevKeen configures the NMI gateway profile for that MID, so you do not enter or manage gateway credentials yourself.
See How card processing is set up for what you provide and what RevKeen configures.
The card path
NMI
NMI is the payment gateway. It carries transactions from RevKeen to Elavon and supports:
- Card-not-present transactions on RevKeen-hosted checkout, payment links, and invoices
- Tokenised card storage for recurring billing and saved cards
- Refunds, voids, and partial refunds
- 3D Secure authentication
Elavon
Elavon is your acquirer, under your own merchant agreement with Elavon. Elavon performs its own underwriting and compliance checks, and settles card funds to your bank account.
How RevKeen stores your card processing
- Unified transaction model -- Every card payment, refund, and chargeback is stored in the same transaction record, so your dashboard, reports, and reconciliation work the same way for every payment.
- Credential isolation -- Gateway credentials for your account are held by RevKeen, encrypted per merchant, and never shared with another merchant. You never handle them.
- Processing account mapping -- A merchant can have more than one processing account, for example a separate MID for a different trading entity. RevKeen routes each transaction to the correct account based on your configuration.
Transaction flow
The card payment path, from RevKeen checkout through NMI to Elavon:
- Checkout -- Customer enters payment details on a RevKeen-hosted checkout page, payment link, or invoice
- Tokenisation -- Card details are tokenised by NMI (never stored in full by RevKeen)
- Authorisation -- RevKeen sends the payment through NMI to Elavon
- Capture -- Elavon processes the transaction
- Recording -- RevKeen records the transaction against the invoice or order it pays
- Notification -- Webhook events fire, the dashboard updates, and any integrations are triggered
Provider fees
Card processing fees -- interchange, scheme, acquirer, and gateway charges -- are set and billed by your own providers under your agreements with them. Your provider statements are the source for those amounts. RevKeen records each transaction, refund, and chargeback, and shows payout information for reporting and reconciliation. RevKeen's own platform fees are listed on the Fees page.
Frequently Asked Questions
Can I have more than one merchant ID?
Yes. Additional MIDs and trading entities can be configured. Contact support; extra MID setup is priced on the Fees page.
Are card details stored by RevKeen?
No. Card details are tokenised by the payment gateway. RevKeen stores only the token and the last four digits for reference. Full card numbers never touch RevKeen's servers.
Can I use a different gateway or acquirer?
Card processing on RevKeen runs through NMI to Elavon. If you need something different, contact support to discuss your requirements.
Owner: david · Reviewed 1 Oct 2026 · Next review 30 Dec 2026