Payment Gateways

Overview

RevKeen uses a gateway-agnostic architecture to process payments. Rather than locking you into a single payment processor, RevKeen abstracts the gateway layer so you can connect to your preferred processor and switch between them without re-engineering your billing workflows. All transaction data, margin tracking, and reporting work identically regardless of which gateway is processing the payment.

Supported Gateways

NMI (Network Merchants Inc.)

NMI is RevKeen's primary supported gateway. It provides a full-featured payment processing API with support for:

• Card-present and card-not-present transactions
• Recurring billing and tokenized payment storage (Customer Vault)
• ACH / eCheck payments
• Refunds, voids, and partial refunds
• Level 2 and Level 3 processing data for B2B transactions
• 3D Secure authentication

NMI connects to multiple acquiring banks, giving you flexibility in choosing your merchant account provider. Most RevKeen merchants use NMI with their existing or new merchant account.

Elavon

Elavon is RevKeen's payment processing partner and one of the world's largest payment processors, owned by US Bancorp. RevKeen's payment processing is powered by Elavon, providing:

• Direct acquiring relationships (no intermediary)
• Support for Visa, Mastercard, American Express, Discover, and international card brands
• Multi-currency processing
• PCI-compliant hosted payment fields
• Card-present support via PAX terminals

Gateway-Agnostic Architecture

RevKeen's billing engine treats gateways as interchangeable connectors. This means:

• Unified transaction model -- Whether a payment is processed through NMI, Elavon, or a future gateway, it is stored in the same transaction table with the same data structure. Your dashboard, reports, and analytics work the same way regardless of processor.

• Gateway-specific adapters -- Each gateway has its own adapter that translates RevKeen's internal payment requests into the gateway's API format. This handles differences in API structure, authentication, and response codes transparently.

• Credential isolation -- Gateway credentials are stored securely per merchant in encrypted vault storage (Infisical). Each merchant's credentials are isolated and never shared.

• Processing account mapping -- Merchants can have multiple processing accounts (e.g., different merchant accounts for different currencies or business entities). RevKeen routes transactions to the correct processing account based on configuration.

How to Configure Your Gateway

During Onboarding

When you sign up for RevKeen, your account manager will help you:

1. Choose a payment gateway (NMI is recommended for most merchants)
2. Set up your merchant account with the gateway or connect an existing one
3. Provide your gateway API credentials to RevKeen (Security Key for NMI)
4. Test a transaction to verify the connection
5. Go live

Adding a Gateway

If you need to add or change your gateway configuration:

1. Navigate to Settings > Payment Processing in your RevKeen dashboard
2. Click Add Processing Account
3. Select your gateway type
4. Enter your API credentials
5. Run a test transaction to validate the connection
6. Set the new account as active

Required Credentials

Transaction Flow

Regardless of which gateway you use, every transaction follows the same flow:

1. Checkout -- Customer enters payment details on your RevKeen-hosted checkout page or payment link
2. Tokenization -- Card details are tokenized by the gateway (never stored by RevKeen)
3. Authorization -- RevKeen sends the payment request through the gateway adapter
4. Capture -- The gateway processes the transaction with the acquiring bank
5. Recording -- RevKeen records the transaction with full cost data (processing fees, interchange, etc.)
6. Notification -- Webhook events fire, dashboard updates, and any integrations are triggered

Cost Tracking

One of RevKeen's key differentiators is tracking the actual cost of each transaction. When a payment is processed:

• Processing fees from your gateway are captured and recorded
• Interchange and assessment fees are tracked (where available from the gateway)
• Net revenue is calculated automatically
• Margin per transaction is visible in your dashboard

This gives you a true picture of what each payment costs, not just what you earned.

Frequently Asked Questions

Can I use multiple gateways?

Yes. You can configure multiple processing accounts and route transactions based on currency, business entity, or other criteria. Contact support for multi-gateway configuration.

What happens if my gateway goes down?

RevKeen monitors gateway health. If a transaction fails due to a gateway outage, the error is logged and you will be notified. Automatic failover between gateways is on the roadmap.

Are card details stored by RevKeen?

No. Card details are tokenized by the payment gateway. RevKeen stores only the token and last four digits for reference. Full card numbers never touch RevKeen's servers.

Can I switch gateways without losing data?

Yes. Because of the gateway-agnostic architecture, all your transaction history, customer data, and subscriptions remain intact when you switch gateways. Only new transactions will route through the new gateway.