Payment orchestration that routes for outcomes.

Connect every provider you work with, define routing logic that reflects how your business actually operates, and let Paytone retry, fall back, and recover transactions in real time — without rewriting your integration.

How it works

From integration to recovery, in four steps.

Orchestration is more than routing — it's the complete loop from connecting providers to learning from every outcome.

01

Connect

Plug in your existing provider contracts and merchant accounts. Paytone speaks to every major acquirer, PSP, and local processor through a single integration layer.

02

Define rules

Build routing logic in plain conditions — cost, region, BIN, currency, method, historical approval rate. Edit rules in the dashboard; deploy without a release.

03

Route in real time

Every transaction passes through the rule engine and is sent to the provider best suited for it — with provider health, latency, and recent decline rates evaluated live.

04

Recover & optimize

Soft declines retry on cascaded fallbacks, network errors reroute automatically, and outcome data feeds back into the routing model so next month's mix improves on today's.

Features

A routing engine that respects your business logic.

Rules and strategies you can compose, tune, and observe — not a black box you have to trust.

Cost-optimized routing

Send each transaction to the cheapest viable provider given currency, method, region, and merchant configuration — without sacrificing approval rate.

Approval-rate routing

Score providers on rolling historical approval and steer traffic toward whoever is performing best right now for that specific BIN, country, or currency combination.

BIN-based logic

Route at the issuer level — premium cards, co-branded portfolios, regulated regions — each handled by the processor with the strongest performance on that bin range.

Cascading retries

Soft declines automatically retry on the next provider in your waterfall. Retry windows, fallback order, and stop conditions are yours to configure.

Real-time observability

Every routing decision is visible, traceable, and explainable. Inspect which rule matched, which provider was tried, and why — for every individual transaction.

Provider waterfalls

Build ordered fallback chains by method, country, or merchant. When the primary provider declines or times out, the next link picks up automatically.

Code & integration

A single create() call. Infinite routing logic.

Routing rules live in configuration, not in your application code. Your engineers ship a single integration and your payment operators iterate on strategy independently.

One API for every provider

Create a payment with a strategy name. Paytone evaluates the active rule set, selects the best provider, and falls back through your waterfall until the transaction is captured or definitively declined.

Strategies are first-class

Define strategies like best_approval, lowest_cost, or your own named policies. Reference them by name from any integration point.

Webhook events, all the way down

Every routing decision, retry, fallback, and final outcome emits a signed webhook. Your downstream systems stay in sync without polling — and your audit log writes itself.

Start orchestrating payments.

Connect your providers, define a routing strategy, and start moving live traffic — most teams are in production within a week.