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

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