Connectors
Connecting payment processors to SpicePay.
A connector is a configured link to a payment processor using your own merchant account and credentials. SpicePay orchestrates across connectors; the money and processor relationships stay yours.
Supported processors
| Processor | Coverage |
|---|---|
| Stripe | Cards, wallets, bank debits |
| PayPal | PayPal wallet, cards |
| Mollie | Cards, iDEAL, SEPA, and other European methods |
| Klarna | Buy now, pay later |
| NowPayments | Cryptocurrency payments |
| Cryptomus | Cryptocurrency payments |
| Creem | Digital products and SaaS billing |
| EPayOuts | Payouts and disbursements |
| PaySepro | Card acquiring |
Adding a connector
- Connectors → Add connector, pick the processor.
- Enter credentials from your processor dashboard (API key, merchant ID — fields vary per processor; the setup screen documents each one).
- Choose which payment methods this connector serves (cards, wallets, bank debits, crypto).
- Optionally restrict to specific currencies or regions.
- Save. The connector performs a live credential check and flips to Connected.
Test vs live: connectors are configured per environment. Wire up test credentials in your test project first; the checkout and API behave identically.
Webhook forwarding
During setup, SpicePay shows a processor-side webhook URL to register in the processor's dashboard. This is how asynchronous events (bank debits clearing, crypto confirmations, disputes) reach SpicePay. The setup screen marks this step as required for processors where it matters.
Managing connectors
- Edit credentials or method coverage at any time; changes apply to new payments immediately.
- Disable a connector to stop sending it new payments without deleting its history — in-flight payments and refunds on it still complete.
- Health — each connector card shows recent success rate and latency, so a degrading processor is visible before your customers tell you.
Native payment panes (Stripe)
Stripe renders Apple Pay, Google Pay and Link inside its own payment form, and only offers them when the top-level page's domain is registered as a payment method domain on your Stripe account. If your shop embeds the checkout in an iframe, that page is your shop — so Stripe hides those wallets with no error.
A native pane moves a method out of Stripe's form into a tile drawn by the checkout itself. Clicking the tile opens the hosted checkout in a new tab, at the top level, showing only that method — where the registered domain applies, so no per-shop registration is needed.
Configure it per Stripe connector under Connectors → your Stripe connector → Native payment panes. Per method you choose whether it renders as a pane, its label (with per-language overrides), an optional second line, its icon (a built-in glyph, or your own inline SVG — plain shapes only; it is rebuilt from a safe allowlist, and markup carrying scripts, external references or <style> blocks is rejected in favour of the built-in glyph), which section it appears under, and its order. A method promoted to a pane is removed from Stripe's payment form, so it never renders twice.
Independently of the visibility setting, a wallet tile is hidden from customers whose browser cannot use that wallet — a tile opening a wallet the browser cannot present would be a dead end. Apple Pay needs Safari on Apple hardware, so it never appears in Chrome or Firefox (including Chrome on macOS). Google Pay is treated more permissively: it is hidden only at the top level in a browser without the Payment Request API (Firefox). Inside an iframe the tile still shows even there, because a frame can hide that API by permission policy on a browser that does support the wallet — and the tile opens a top-level tab, where it would work. If you are checking your own shop and an Apple Pay tile is missing, open it in Safari before assuming the pane is misconfigured.
Available methods: apple_pay, google_pay, link, klarna, affirm, ideal, alipay, revolut_pay, amazon_pay. A non-wallet method must also be enabled on the connector — such a pane never reaches a customer otherwise, and the editor flags it. The three wallets ride the card rail, so their panes work without a separate toggle; only explicitly switching a wallet off on the connector disables its pane.
Before you turn this on: your embedding page must permit pop-ups (see Payments), and Apple and Google both have brand guidelines covering how their marks may be used and what a marked button may do — review them before shipping a tile that carries one.
Multiple accounts on one processor
You can add the same processor multiple times (e.g. two Stripe accounts for two legal entities, or separate accounts per region). Each is an independent connector serving the payment methods, currencies, and regions you assign it.