Approve more payments on your Stripe 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.
Stripe + PaymentKit
What you can do with Stripe
Stripe processes the payment. PaymentKit vaults the card, decides where each charge goes, and runs billing and recovery above it.
Stripe processes the payment
Charges run through your own Stripe account, using a restricted API key you create for PaymentKit.
PaymentKit runs the layer above
Subscription billing, routing, and failed-payment recovery across every Stripe account.
Your accounts stay yours
Keep your Stripe account, Dashboard, and payouts. Cards live in PaymentKit's vault instead of being locked to Stripe.
One view of everything
Approvals, recovery, and revenue across your whole setup in one dashboard.
Payment path: Checkout, then PaymentKit, then Stripe account, then Acquiring bank.
- Connection type
- Payment processor, connected with API keys
- Payment methods
- Cards, Apple Pay, Google Pay, Stripe Link, Klarna, Afterpay, and Affirm
- Transaction types
- Charges, refunds, and subscription renewals
- Merchant accounts
- Multiple Stripe accounts, each connected as its own route
- Markets and currencies
- Follows your Stripe account's countries and currencies
- Account requirements
- Stripe account with raw card data API access enabled
How it works
Connect Stripe in three steps
From your Stripe account to live payments. Stripe's raw card API approval is the only wait, and it usually takes a few days.
Step 1: Request raw card access
Ask Stripe to enable its raw card data APIs. We give you the PCI documents and the message to send.
Step 2: Connect Stripe
Create a restricted API key for PaymentKit, then add it and your publishable key in PaymentKit under Payment processors.
Step 3: Turn on methods and test
Choose cards, wallets, Link, and buy now, pay later, then run a test charge, refund, and renewal before going live.
AI dunning
Recover failed Stripe renewals
When a renewal fails on Stripe, 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 Stripe 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.

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