Introduction
What SpicePay is and how the platform fits together.
SpicePay is a payment orchestration platform. You integrate once — against the SpicePay API and hosted checkout — and accept payments through every processor we support, fiat and crypto alike, with one dashboard for the whole fleet.
Why orchestration?
If you process meaningful volume, a single payment provider becomes a liability:
- Outages at one processor stop all revenue.
- Coverage — no single provider offers every payment method your customers want, from cards and wallets to crypto.
- Fees differ significantly between providers, and negotiating requires you to be able to shift volume.
- New markets often need a local provider or a payment method your current one lacks.
SpicePay solves this by sitting between your product and the processors. You keep one integration; we take care of the rest.
The platform at a glance
| Component | URL | What it does |
|---|---|---|
| Control Center | dashboard.spicepay.net |
Configure connectors, checkout, and teams; monitor payments |
| Hosted Checkout | checkout.spicepay.net |
PCI-scoped payment page your customers see |
| API | api.spicepay.net |
Programmatic access to payments, refunds, customers |
| Docs | spicepay.net/docs |
You are here |
Supported processors
SpicePay connects to Stripe, NowPayments, Cryptomus, Mollie, PayPal, EPayOuts, PaySepro, Klarna, and Creem — covering cards, wallets, bank payments, buy-now-pay-later, and cryptocurrency from one integration. See Connectors.
Core capabilities
- Connectors — connect processors with your own merchant accounts and credentials; SpicePay orchestrates between them.
- Payments — one payment API across all processors, with hosted checkout, iframe embedding, and payment links. See Payments.
- WordPress — a no-code plugin that adds SpicePay checkout to any WordPress site. See WordPress.
- Surcharging — pass payment costs to the customer where regulation permits, with rule-based surcharge logic. See Surcharges.
- Subscriptions — recurring billing with decline-aware retries and dunning. See Subscriptions.
- Disputes & refunds — a single queue for chargebacks and refunds across every processor. See Refunds & disputes.
- Analytics — approval rates, volumes, fees, and failure reasons across your whole fleet, not per-processor silos.
How a payment flows
- Your backend creates a payment via the API (or your storefront opens Hosted Checkout).
- The customer picks a payment method; SpicePay sends the payment to the connector configured for that method, currency, and region.
- Surcharge rules (if configured) adjust the amount presented to the customer before they confirm.
- The payment is processed on the connector; webhooks notify your systems and the transaction appears in the Control Center in real time.
Next steps
- Follow the Quickstart to take your first test payment.
- Tour the Control Center.
- Set up your first connector.