Connecting Klyme (Pay by Bank)

Klyme is a UK Open Banking provider. Shoppers pay by authorising a bank transfer in their banking app — no card details, no chargebacks, instant settlement. Swft collects a 2% platform fee, billed monthly.

When to use Klyme

Klyme is best for UK-only shoppers paying mid-to-high-ticket items. It works for any cart size but its main value is bypassing card-network fees (typically 1.5%+) for larger transactions where 2% Swft + Klyme’s own tariff is still cheaper than card processing.

Klyme is not available outside the UK. Swft auto-hides the Pay by Bank button for shoppers in non-UK billing countries.

Prerequisites

• A Klyme merchant account (klyme.io)
• Your Swft API key already saved in Settings → Swft Checkout

Get your Klyme credentials

Klyme issues three values per merchant:

• Merchant UUID — your unique identifier in Klyme’s system.
• Username — HTTP Basic auth username for API calls.
• Password — HTTP Basic auth password.

Find these in your Klyme merchant dashboard under Settings → API credentials. If you don’t see them, contact your Klyme account manager — they may need to enable API access for your merchant profile.

For testing, Klyme provides a separate sandbox dashboard at api-test.klyme.io with its own UUID and credentials.

Connect Klyme in Swft

1. Go to your Swft Dashboard → Settings → Payments.
2. Find the Klyme (Pay by Bank) card.
3. Paste your Merchant UUID, Username, and Password.
4. If you’re testing with sandbox credentials, leave Live mode OFF. Switch it ON for production.
5. Tick Enable Klyme.
6. Click Save.

The Pay by Bank button now appears above the card form for UK shoppers.

How payments work

When a UK shopper clicks Pay by Bank:

1. Swft’s API requests a payment authorisation from Klyme using your credentials.
2. Klyme returns a checkout URL; Swft redirects the shopper.
3. Shopper picks their bank, authenticates in their banking app, and approves the transfer.
4. Bank confirms to Klyme → Klyme confirms to Swft → Swft marks the session complete and creates a paid WooCommerce order with payment_method: 'klyme'.
5. Shopper sees the order confirmation page.

Funds settle directly to your nominated bank account under Klyme’s payout schedule (typically same-day for UK Faster Payments). Klyme’s own per-transaction fees apply — refer to your Klyme contract.

Pending payments

Some bank transfers are asynchronous — the shopper authorises in their app but the funds take seconds to minutes to clear. Swft handles this by marking the session “pending” on return; once Klyme confirms settlement, the session and WC order flip to complete.

If a shopper returns to your site before settlement, they see a “We’re confirming your payment with your bank” message and an email receipt arrives once cleared.

Platform fee

Swft’s 2% platform fee on Klyme transactions is billed monthly via Stripe Billing, against the card you have on file. Open Banking doesn’t support marketplace-style fee skims at the protocol layer.

You’ll see a single Swft invoice each month covering accumulated fees from all out-of-band gateways (PayPal, Klyme, NomuPay).

Refunds

Open Banking has no native refund mechanism — transactions are one-way bank transfers. To refund a Klyme order:

1. Issue a refund from your Klyme dashboard → the order. Klyme initiates a reverse Faster Payment to the customer’s bank.
2. Mark the WC order refunded manually in WooCommerce → Orders.

This is by design at the protocol level, not a Swft limitation.

Test mode

To test without real bank transfers:

1. Use sandbox Klyme credentials (provided when you sign up; if missing, request from Klyme support).
2. In Swft, paste them with Live mode OFF.
3. Run a checkout and pick Pay by Bank. Klyme’s sandbox bank picker shows mock banks you can authorise against without real funds moving.

Disconnecting Klyme

In Settings → Payments, uncheck Enable Klyme. The Pay by Bank button disappears for new shoppers. Existing pending transactions continue to settle.

To fully remove credentials, blank out the UUID, username, and password and save.