Approve more payments on your Airwallex 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.
Airwallex + PaymentKit
What you can do with Airwallex
Airwallex is your processor: it moves the transaction for your Airwallex account. PaymentKit is the layer above it.
Airwallex processes the payment
Card and wallet payments run through your Airwallex account, connected with a restricted API key.
PaymentKit runs the layer above
Subscription billing, routing, and failed-payment recovery across every Airwallex account.
Your accounts stay yours
Keep your Airwallex 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 Airwallex account, then Acquiring bank.
- Connection type
- Payment processor, connected with a Client ID and restricted API key
- Payment methods
- Cards, Apple Pay, and Google Pay
- Transaction types
- Charges, refunds, and subscription renewals
- Merchant accounts
- Multiple Airwallex accounts, each connected as its own route
- Markets and currencies
- Follows your Airwallex account's currencies
- Account requirements
- Airwallex account with a restricted API key for payments
How it works
Connect Airwallex in three steps
From your existing Airwallex account to live payments, with a full test run before any customer is charged.
Step 1: Create a restricted key
In Airwallex, open Developer, then API Keys, and create a restricted key with access to payments resources.
Step 2: Connect Airwallex
Add your Client ID and API key in PaymentKit under Payment processors, and choose the environment.
Step 3: Add wallets and test
Turn on Apple Pay and Google Pay if you want them, then run a test charge, refund, and renewal before going live.
AI dunning
Recover failed Airwallex renewals
When a renewal fails on Airwallex, 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 Airwallex 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.

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