Adyen
Adyen’s own card component takes the card, with native 3-D Secure 2.
- Currencies
- Any your account supports
Payment processors
Charge with the account each business already has.
A charging shop connects its own account with one of the 10 payment processors below. We decide which shop takes each payment — that processor’s own card form takes the card, and the money settles straight to that shop.
Card numbers and processor keys never reach us
Missing yours? Suggest itSupported
Connect any of these today.
Every one works in the WooCommerce and Magento 2 plugins; the PrestaShop, OpenCart and Zen Cart plugins, still in build, carry the same list.
Each can charge at once, or authorise now and capture later.
Airwallex
Airwallex card elements take the card. Authorise, partial capture, void and partial refunds are all supported.
- Currencies
- Any your account supports
Leave Airwallex’s separate merchant-of-record product switched off on this account.
Authorize.net
Authorize.net’s own payment lightbox takes the card, so the number goes straight to Authorize.net.
- Currencies
- AUD, CAD, DKK, EUR, GBP, NOK, NZD, PLN, SEK, USD
No 3-D Secure on this gateway — keep EEA and UK payments on another account.
Braintree
Braintree Hosted Fields take the card, so the number goes straight from the browser to Braintree.
- Currencies
- Any your account supports
Checkout.com
Checkout.com takes the card, with authorise, capture, cancel and partial refunds.
- Currencies
- Any your account supports
The card form opens as its own page — Checkout.com does not allow its card fields inside a frame.
Mollie
Mollie Components take the card inside the payment window.
- Currencies
-
23 currencies
AED, AUD, CAD, CHF, CZK, DKK, EUR, GBP, HKD, HUF, ILS, ISK, JPY, NOK, NZD, PHP, PLN, RON, RUB, SEK, SGD, USD, ZAR
3-D Secure always happens on Mollie’s own page, which opens in a small window.
PayPal
PayPal’s card fields, the PayPal button, or both — with the shop’s own PayPal business account.
- Currencies
-
25 currencies
AUD, BRL, CAD, CHF, CNY, CZK, DKK, EUR, GBP, HKD, HUF, ILS, JPY, MXN, MYR, NOK, NZD, PHP, PLN, RUB, SEK, SGD, THB, TWD, USD
Square
The Square Web Payments form takes the card, so the number goes straight to Square.
- Currencies
- USD, CAD, GBP, EUR, AUD, JPY
One Square account settles in exactly one currency — route each currency to the right account.
Stripe
Stripe’s own card form takes the card, with the shop’s own Stripe account.
- Currencies
- Any your account supports
Worldpay
Access Worldpay’s Checkout card fields take the card, so the number goes straight to Worldpay.
- Currencies
- Any your account supports
No self-serve sandbox: credentials come from your Worldpay account manager or dashboard.
Plus a built-in test processor
Free on every plan and no account needed: its test cards approve and decline on cue, so you can route test payments before any real processor is connected.
Not supported yet
Looked at, and not ready yet.
We only switch a processor on once real orders run through it end to end. These are the ones we have already studied, and what stands in the way.
Amazon Pay
Not yetA wallet that cannot open inside a payment window, so it needs a full-page redirect option at checkout first.
Cybersource
Not yetPlanned on its newer request-signing scheme. Test credentials are only issued after onboarding.
Klarna
Not yetBuy now, pay later. It needs the exact order lines, so it waits for cross-shop product matching and its own option at checkout.
Nuvei
Not yetNeeds extra server-side checks around its browser flow, and test credentials are only issued after onboarding.
Paystack
Not yetNigeria, Ghana, South Africa, Kenya and Côte d’Ivoire. Waiting on a live test of West African CFA franc amounts before real money goes through it.
PayU (Europe)
Not yetPoland, Czechia, Romania and Hungary. It confirms payments asynchronously, which needs handling we have not built yet.
Razorpay
Not yetIndia. Razorpay approves every website by hand, and we are still confirming how that works when one shop charges for another.
FastSpring, Paddle and Whop cannot work with GatewayChanger
They are merchants of record: they sell the product themselves and pay the shop out later. The charging business has no payment account of its own with them, so there is nothing for a payment to be routed to.
Missing one?
Can’t find your payment processor?
Tell us its name and where its API documentation lives. We read every suggestion — it is how we decide what to build next.
What a processor needs to work here
- The charging business has its own account with it — not a merchant of record that resells the product.
- It takes the card on its own form: embedded card fields or its own payment page.
- It can charge an exact amount in a currency we name, and refund it later.