Finscale documentation
Finscale is a payment orchestration gateway. You integrate one REST API; behind it, Finscale routes every transaction across multiple payment providers — picking the one most likely to approve it, and failing over automatically when one declines or times out. 40+ payment methods, one integration, one unified model for errors, refunds, and reconciliation.
Your first request
Everything runs through https://api.finscale.dev/v1. The test sandbox is live — any sk_test_ key authenticates. One call creates a payment; Finscale picks the provider:
curl https://api.finscale.dev/v1/payments \
-H "Authorization: Bearer sk_test_51FinscaleDemo…" \
-H "Idempotency-Key: idem_ord_9f21_0716" \
-H "Content-Type: application/json" \
-d '{
"amount": 4900,
"currency": "EUR",
"payment_method": "ideal",
"reference": "ord_9f21_0716",
"customer": { "email": "anna@example.com" },
"return_url": "https://shop.example.com/checkout/return"
}'
The response carries the routed provider as an opaque id ("provider": "prov_eu_acq_01") and, for redirect methods like iDEAL, a next_action URL to send your customer to. The quickstart walks the whole story, and the API playground lets you fire these calls from the browser.
Explore the docs
The docs follow the sidebar: eight groups, from first payment to going live.
Get started
How Finscale works · Quickstart · Go-live checklist
The architecture in one diagram, your first test payment in three calls, and everything to tick off before live traffic.
Accept payments
Hosted checkout · API integration · Payment lifecycle · Authorization flows · Multicurrency · Refunds · Disputes
The two integration paths, the payment state machine, and what happens after the sale — refunds and chargebacks.
Payment methods
Overview · Cards & 3DS · Wallets · Bank redirects · Real-time payments · Direct debit · Buy now pay later · Vouchers · Crypto
All 40+ methods by family — how each one authenticates, confirms, and settles.
Routing & risk
Smart routing · Routing rules · Provider health & failover · Risk engine
How every transaction finds its provider, how you steer it, and what screens it before authorization.
Money movement
Settlement & payouts · Ledger · Reconciliation · Balance
From captured amount to bank payout: the ledger behind it, and how to reconcile to the cent.
Merchants
Onboarding & KYB · Merchant API
The merchant lifecycle from created to active, and the object model behind it — for platforms onboarding sub-merchants.
Developer
API playground · Authentication · Errors · Idempotency · Pagination · Webhooks · Versioning · Rate limits · SDKs · Testing
The cross-cutting mechanics every integration shares — plus a live console to try the API from the browser.
Platform
Security & PCI · API reference ↗
How card data stays off your servers, and the full endpoint-by-endpoint reference on its own host.
Money is always integer minor units plus an ISO 4217 currency — "amount": 4900, "currency": "EUR" is €49.00. Providers are opaque ids like prov_eu_acq_01. One worked example order, ord_9f21_0716, recurs across every page so you can follow a single payment end to end.