SwitchFlow is a payment-orchestration layer for cross-border payments. You keep your own Stripe and Adyen merchant accounts; SwitchFlow decides which gateway each payment should try first, and when a retryable decline, timeout, or outage occurs, it transparently retries the same payment on your next-priority gateway — while your customer’s checkout keeps a single loading state.

​
Why merchants use it

  • Recovered revenue. Soft declines and gateway incidents no longer end the checkout — failover happens mid-request, in the same customer interaction.
  • One integration, many gateways. One server-side API call, one embeddable widget, one unified webhook schema — regardless of which gateway captured.
  • Your gateways, your money. Funds settle into your existing Stripe/Adyen accounts. SwitchFlow never touches settlement.
  • PCI kept out of your stack. Card data goes from the customer’s browser directly to a PCI-certified vault. Neither your servers nor SwitchFlow’s API ever see a PAN.

​
How a checkout flows

  1. Your backend creates a payment session with your secret API key.
  2. The checkout widget on your page collects the card and tokenizes it straight to the vault.
  3. SwitchFlow’s routing engine attempts capture on your priority-1 gateway and fails over per your rules if needed (total budget ≤ 2.5 s at p95).
  4. Your backend receives one signed, unified webhook with the outcome and the full per-gateway attempt trail.

​
Start here

Quickstart

Go from account to first test payment in about 15 minutes.

API reference

Payment sessions, authentication, errors — the full server-side contract.

Checkout widget

Embed the card form and handle success, decline, and fallback states.

Webhooks

Receive unified payment events and verify their signatures.