Approve more payments on your Inovio 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.
Inovio + PaymentKit
What you can do with Inovio
Inovio is your gateway: it connects your business to acquiring banks and moves the transaction. PaymentKit is the layer above it.
Inovio processes the payment
It connects you to acquiring banks and runs eligible charges through your merchant accounts.
PaymentKit runs the layer above
Subscription billing, routing, and failed-payment recovery across every Inovio MID.
Your accounts stay yours
Keep your Inovio account, your MIDs, 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 Inovio MID, then Acquiring bank.
- Connection type
- Payment gateway
- Payment methods
- Credit and debit cards
- Transaction types
- Charges, refunds, and subscription renewals
- Merchant accounts
- Multiple MIDs, each connected as its own route
- Markets and currencies
- Follows your Inovio merchant account setup
- Account requirements
- Active Inovio gateway account with API access; MIDs approved for recurring billing
How it works
Set up Inovio with PaymentKit
Three steps from your existing Inovio account to live payments, with a full test run before any customer is charged.
Step 1: Check your account
Confirm you have an active Inovio gateway account with API access, and that the merchant accounts you want to use are approved for recurring billing.
Step 2: Connect Inovio
Add your Inovio API credentials in PaymentKit under Processors. Each merchant 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 through Inovio's test environment before sending live customer payments.
AI dunning
Automatically recover failed Inovio renewals
When a renewal fails on Inovio, 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 Inovio MID 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.

Inovio vs. Inovio + PaymentKit
Inovio alone vs. Inovio with PaymentKit
You keep your Inovio account and your banking relationships. PaymentKit makes them work harder.
| Inovio alone | With PaymentKit | |
|---|---|---|
| Checkout | Inovio aloneOne checkout per Inovio integration | With PaymentKitOne checkout in front of every Inovio merchant account and any other processor |
| A soft decline | Inovio aloneThe sale is usually lost | With PaymentKitCascades to your next merchant account in the same session |
| Stored cards | Inovio aloneTokens tied to one processor | With PaymentKitVaulted independently and portable across processors |
| Failed renewals | Inovio aloneRetries on a fixed timer | With PaymentKitAI dunning timed by decline code and billing cycle |
| Processor outage | Inovio aloneCheckout goes down with it | With PaymentKitTraffic fails over to a healthy route automatically |
| Expired or reissued cards | Inovio aloneRenewal declines, customer has to act | With PaymentKitNetwork tokens and account updater refresh them |
| Reporting | Inovio aloneOne dashboard per processor | With PaymentKitApprovals, recovery, and revenue across every route in one view |
Unified checkout
One checkout for every Inovio MID
Customers enter their card once. PaymentKit vaults it and can charge it through any Inovio merchant account or other processor you connect.
Every Inovio MID behind one checkout
Each Inovio 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 Inovio MID.
Add other processors anytime
Run Inovio next to Stripe, Adyen, Authorize.net, or any supported gateway, all through one API.
Payment orchestration
Route every payment to its best Inovio MID
PaymentKit picks the right Inovio account for each transaction by card type, currency, region, ticket size, 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 Inovio MID 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
