Payment Gateways

Swft Checkout supports multiple payment gateways side-by-side. Configure as many as you need; shoppers see only the methods you’ve enabled for their region and cart.

Cards globally via Stripe Connect. Swft's 2% fee is deducted in-flow. Native in-page PayPal button. Funds settle to your PayPal Business balance. UK Open Banking. Lower fees, instant settlement, no chargebacks. Cards plus Apple Pay and Google Pay for high-risk verticals like competitions and lotteries. Automatic above the contact form via Stripe's Express Checkout Element. Klarna, Clearpay, Affirm, Zip — toggled in your Stripe Dashboard. iDEAL, Bancontact, BLIK, SOFORT, EPS, MobilePay, Swish, Vipps, Bizum, MB WAY, Alma.

Fee model

Swft charges a flat 2% per successful transaction, regardless of gateway. How that fee is collected differs:

• In-flow (Stripe) — Stripe Connect’s application_fee_amount deducts the 2% before funds settle to your account. The fee shows up as a transfer deduction on your Stripe dashboard. No separate invoice.
• Out-of-band (everyone else) — PayPal, Klyme, and NomuPay don’t support marketplace-style fee skims at the gateway layer. Swft records each successful transaction in a platform-fee ledger and bills the accumulated fees once a month to the card you have on file in Stripe Billing.

Both models snapshot the fee rate at the time of the transaction, so a future rate change doesn’t retroactively re-bill historical orders.

Choosing what to enable

Most merchants enable Stripe plus one or two regional methods:

• UK consumer storefront — Stripe + Klyme (Open Banking is fast and cheap for shoppers) + BNPL.
• EU storefront — Stripe + Local Payments (iDEAL, Bancontact etc. surface automatically by billing country) + BNPL.
• Competition / lottery site on Total Processing — NomuPay alongside or instead of Stripe. PayPal as a secondary option.
• Global SaaS / digital goods — Stripe + PayPal + BNPL is usually enough.

You can run any number of gateways at once. The checkout’s payment section orders them by best-fit-for-the-shopper:

1. Express wallets first (Apple Pay / Google Pay)
2. Open Banking in the UK
3. Local methods in the EU
4. Card form
5. PayPal / NomuPay (where configured)
6. BNPL

Empty / unconfigured gateways are hidden — shoppers never see a broken button.

Test mode

Each gateway has its own concept of “test mode”:

Gateway	Test mode toggle	Test credentials
Stripe	Live/test on the connected account	Stripe test cards (4242 4242 4242 4242)
PayPal	paypal_live_mode in Swft	PayPal sandbox app + sandbox buyer account
Klyme	klyme_live_mode in Swft	Klyme sandbox credentials
NomuPay	nomupay_live_mode in Swft	OPPWA sandbox via [email protected]

If you mix live and test credentials across gateways, the checkout shows a banner warning the shopper that an order may be a test charge. This prevents real customers from being billed against a sandbox account.

Refunds

Refunds happen in WooCommerce, not Swft. Each WC payment gateway plugin handles its own refund flow:

Swft is not in the refund path for any gateway

You retain full control of money movement. Refund buttons in WooCommerce → Orders call the merchant’s gateway plugin directly.

• Stripe — refund button in WC → Orders, hits Stripe via the WooCommerce Stripe Gateway plugin.
• PayPal — same pattern, via the WooCommerce PayPal Payments plugin.
• NomuPay — same pattern, via the NomuPay Payment Gateway for WooCommerce plugin. Swft tags NomuPay orders with the meta that plugin’s refund handler expects, so refunds work out of the box.
• Klyme — Open Banking refunds go through the Klyme dashboard; WooCommerce will mark the order refunded but the actual fund transfer happens in Klyme.

What’s next

The most common starting point. Two-click OAuth, supports cards globally. Already on Stripe? Add PayPal in under five minutes. Connect your existing NomuPay account for cards, Apple Pay, and Google Pay.