Approve more payments on your Pay by Pago 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.
Pay by Pago + PaymentKit
What you can do with Pay by Pago
Pay by Pago is your gateway: it moves the transaction. PaymentKit is the layer above it.
Pay by Pago 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 Pay by Pago account.
Your accounts stay yours
Keep your Pay by Pago 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 Pay by Pago 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 Pay by Pago account setup
- Account requirements
- Active Pay by Pago account with API access, approved for recurring billing
How it works
Connect Pay by Pago in three steps
From your existing Pay by Pago account to live payments, with a full test run before any customer is charged.
Step 1: Check your account
Confirm you have an active Pay by Pago account with API access, and that it is approved for recurring billing.
Step 2: Connect Pay by Pago
Add your Pay by Pago 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 Pay by Pago renewals
When a renewal fails on Pay by Pago, 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 Pay by Pago 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.

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