Every processor you need, routed by rules you set.
Connect several payment processors, route each payment by country, card, amount, or currency, fall back on failure, and keep test and live money apart.
More than one processor, on purpose
Throttle connects to card processors, PayPal, wallets, and Stripe as connectors, and you can run several at once. Instead of choosing one processor for good, you decide which one handles each payment — and what happens when it says no.
Routing rules
Each application has an ordered cascade: a default list of connectors to try, plus conditional rules that take over when a payment matches. Rules can match on:
- the buyer’s country, or the card’s country, scheme, type, or source,
- the amount range and currency,
- the payment source and your own order metadata.
Card payments and redirect methods such as PayPal have separate routing, and decline rules can refuse a payment before it ever reaches a processor. A failure on one route can fall through to the next — set deliberately, so a hard decline isn’t retried just to add latency.
Authorize now, capture later
Take payment at checkout, or authorize at order time and capture when you ship. Capture less than you authorized and the remainder is released to the buyer. Payments can also be voided, refunded in full or in part, and left to expire, and every step lands on the order’s payment status.
Saved cards, without card data
Buyers can view, add, and remove their own saved cards with a buyer-scoped token, and those cards are what subscriptions renew against. Card fields are hosted by the processor, so raw card numbers never touch your site or Throttle.
Test and live never mix
Every workspace environment has its own connections and credentials: non-production environments use processor sandboxes, production uses live accounts. New applications start with card and PayPal simulators switched on, so a test checkout completes before you’ve connected anything real. If platform billing lapses, the production connection is frozen rather than deleted.
Good to know
- Live payments need a production-entitled workspace.
- PayPal connects by pasting API credentials; Stripe connects in one click.