Approve more payments on your Electronic Payment Exchange gateway
Talk to our team
Tell us about your business
Leave your details and a real person will follow up with next steps. No pitch deck, just straight answers.
Electronic Payment Exchange + PaymentKit
What you can do with Electronic Payment Exchange
Electronic Payment Exchange is your gateway: it moves the transaction. PaymentKit is the layer above it.
Electronic Payment Exchange processes the payment
It moves the transaction and runs eligible charges through your merchant accounts.
PaymentKit runs the layer above
Subscription billing, routing, and failed-payment recovery across every Electronic Payment Exchange account.
Your accounts stay yours
Keep your Electronic Payment Exchange account and your banking relationships.
One view of everything
Approvals, recovery, and revenue across your whole setup in one dashboard.
Payment path: Checkout, then PaymentKit, then Electronic Payment Exchange account, then Acquiring bank.
- Connection type
- Payment gateway
- Payment methods
- Cards and the methods your account supports
- Transaction types
- Charges, refunds, and subscription renewals
- Merchant accounts
- Multiple accounts, each connected as its own route
- Markets and currencies
- Follows your Electronic Payment Exchange account setup
- Account requirements
- Active Electronic Payment Exchange account with API access, approved for recurring billing
How it works
Connect Electronic Payment Exchange in three steps
From your existing Electronic Payment Exchange account to live payments, with a full test run before any customer is charged.
Step 1: Check your account
Confirm you have an active Electronic Payment Exchange account with API access, and that it is approved for recurring billing.
Step 2: Connect Electronic Payment Exchange
Add your Electronic Payment Exchange API credentials in PaymentKit under Processors. Each account connects as its own route, so you can add more than one.
Step 3: Verify your workflow
Run a test charge, a refund, and a subscription renewal in test mode before sending live customer payments.
AI dunning
Recover failed Electronic Payment Exchange renewals
When a renewal fails on Electronic Payment Exchange, AI dunning reads the decline code, retries at the best moment, and only emails the customer when it has to.
Retries timed by decline reason
Soft declines get well-timed retries, hard declines skip wasted attempts, and a retry can move to another Electronic Payment Exchange account or processor.
Dunning emails that adapt
Branded sequences change tone and timing based on the type of failure.
Self-serve card updates
Customers fix their card in a secure portal, and the payment retries right away.

Electronic Payment Exchange vs. Electronic Payment Exchange + PaymentKit
Electronic Payment Exchange alone vs. Electronic Payment Exchange with PaymentKit
You keep your Electronic Payment Exchange account and your banking relationships. PaymentKit makes them work harder.
| Electronic Payment Exchange alone | With PaymentKit | |
|---|---|---|
| Checkout | Electronic Payment Exchange aloneOne checkout per Electronic Payment Exchange integration | With PaymentKitOne checkout in front of every Electronic Payment Exchange merchant account and any other processor |
| A soft decline | Electronic Payment Exchange aloneThe sale is usually lost | With PaymentKitCascades to your next merchant account in the same session |
| Stored cards | Electronic Payment Exchange aloneTokens tied to one processor | With PaymentKitVaulted independently and portable across processors |
| Failed renewals | Electronic Payment Exchange aloneRetries on a fixed timer | With PaymentKitAI dunning timed by decline code and billing cycle |
| Processor outage | Electronic Payment Exchange aloneCheckout goes down with it | With PaymentKitTraffic fails over to a healthy route automatically |
| Expired or reissued cards | Electronic Payment Exchange aloneRenewal declines, customer has to act | With PaymentKitNetwork tokens and account updater refresh them |
| Reporting | Electronic Payment Exchange aloneOne dashboard per processor | With PaymentKitApprovals, recovery, and revenue across every route in one view |
Unified checkout
One checkout for every Electronic Payment Exchange account
Customers enter their card once. PaymentKit vaults it and can charge it through any Electronic Payment Exchange merchant account or other processor you connect.
Every Electronic Payment Exchange account behind one checkout
Each Electronic Payment Exchange merchant account connects as its own route, so your checkout never has to change when you add or retire one.
Cards that belong to you
Cards live in PaymentKit's PCI Level 1 vault, so subscribers stay billable across every Electronic Payment Exchange account.
Add other processors anytime
Run Electronic Payment Exchange next to any other supported gateway, all through one API.
Payment orchestration
Route every payment to its best Electronic Payment Exchange account
PaymentKit picks the right Electronic Payment Exchange account for each payment by card, currency, region, and live performance, then cascades soft declines.
Rules you control
Route by card brand, BIN range, currency, country, or ticket size, and set the order accounts are tried.
Cascading on soft declines
A soft decline on one Electronic Payment Exchange account moves the same charge to your next account. The customer never re-enters a card.
Failover when a route goes down
If an account or processor stops responding, traffic moves to a healthy route automatically.
Integration directory
Find an integration
Search every gateway, processor, and payment method PaymentKit connects with, and see what's available today.
Loading integrations…
FAQ
