Gateway Setup

Connect your payment processor to start accepting payments

RevKeen integrates with NMI (Network Merchants Inc.) as the primary payment gateway. This guide walks you through connecting your gateway and configuring it for both test and production environments.

Supported Payment Gateways

📄

NMI Gateway

Recommended. Full support including tokenization, recurring billing, 3DS verification, and ACH payments.

📄

Other Gateways

Additional gateway support coming soon. Contact us if you have specific requirements.

Prerequisites

An NMI merchant account (nmi.com)
Access to your NMI merchant portal
API Security Key from NMI settings
Collect.js tokenization key (for secure card collection)

NMI Gateway Setup

Get Your API Security Key

Log in to your NMI merchant portal
Navigate to Settings → Security Keys
Generate a new API Security Key or copy an existing one
Keep this key secure — it provides full API access

Never expose your API Security Key in client-side code. It should only be stored securely on your server or in RevKeen's encrypted settings.

Get Your Collect.js Tokenization Key

In the NMI portal, go to Settings → Collect.js
Create a new tokenization key
Set the allowed domains (your checkout URLs)
Copy the generated tokenization key

The tokenization key is safe to use in client-side code. It only allows card tokenization, not actual charges.

Configure Gateway in RevKeen

Go to Settings → Payment Gateway in your RevKeen dashboard
Select NMI as your gateway provider
Enter your API Security Key
Enter your Collect.js Tokenization Key
Click Save & Verify

Test Your Connection

RevKeen will verify your credentials by performing a zero-dollar authorization. If successful, your gateway status will show as Connected.

Run a test payment using one of the test cards below to verify the full flow.

Test Card Numbers

Use these test cards in sandbox/test mode to simulate various scenarios:

Card Number	Brand	Result
`4111111111111111`	Visa	✅ Approved
`5431111111111111`	Mastercard	✅ Approved
`341111111111111`	Amex	✅ Approved
`4000000000000002`	Visa	❌ Declined
`4000000000003220`	Visa	🔐 3DS Required

Use any future expiration date (e.g., 12/28) and any 3-digit CVV (or 4-digit for Amex) when testing.

Test vs Production Mode

Mode	Use Case	Real Charges
`Test`	Development, QA, demos	❌ No
`Production`	Live customer payments	✅ Yes

Toggle between modes in Settings → Payment Gateway → Environment.

Always thoroughly test in Test mode before switching to Production. Production transactions will charge real cards and cannot be easily undone.

How Payment Flow Works

Customer Enters Card

Card details entered in RevKeen's secure checkout form

Collect.js Tokenization

Card tokenized client-side — raw card data never touches your servers

RevKeen Processes Payment

Token sent to RevKeen API, which calls NMI to process the charge

Result Returned

Success or decline response, customer redirected appropriately

API Configuration (Optional)

If you're using the RevKeen API to process payments programmatically, ensure your gateway is configured before making charge requests:

// Gateway configuration is managed in the dashboard
// API calls automatically use your configured gateway

const payment = await client.payments.create({
  customerId: 'cus_xxxxxxxx',
  amount: 9900, // $99.00 in cents
  currency: 'USD',
  paymentMethodToken: 'tok_xxxxxxxx', // From Collect.js
  description: 'Pro Plan Subscription',
});

if (payment.data.status === 'succeeded') {
  console.log('Payment successful:', payment.data.transactionId);
}

Troubleshooting

"Invalid API Key" error

Verify you copied the complete API Security Key from NMI. Check there are no extra spaces or missing characters.

Collect.js not loading

Ensure your domain is added to the allowed domains in NMI's Collect.js settings. Include both your development and production URLs.

Test payments work but production fails

Check that your NMI account is fully activated for live processing. Some accounts require additional verification before going live.

Next Steps

📄