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

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