Route by approval rate, cost or capacity
The platform
The routing layer between your checkout and the rails.
Payou sits above your acquiring relationships and decides, per transaction, which route has the best chance of an authorisation. Rules are configuration, not engineering work.
Incorporated in England & Wales
BLOCK 01
Routing engine
Every request is scored against your active rules before it leaves the layer: payer country, card brand and issuer, amount band, currency, method and historical provider performance.
Weighted split-testing between providers
Per-BIN and per-issuer overrides
Rule changes take effect without a deployment
- Europe
- United States
- Latin America
- Africa
- CIS
BLOCK 02
Cascade and retry logic
A soft decline is not the end of a payment. The layer replays the transaction on the next eligible route using the logic you defined, while the payer sees a single attempt.
Decline-code aware — hard declines are never retried
Configurable attempt limits and backoff
Retry on a different provider, currency or method
Every attempt recorded against one payment object
BLOCK 03
Unified checkout
One hosted or embedded checkout renders the method set a payer in that market expects. Cards, bank transfers and local wallets sit behind the same object model.
Hosted page, embedded fields or server-to-server
Method set resolved from payer geography
Localised copy and currency presentation
3-D Secure 2 handled by the layer
BLOCK 04
One reconciliation model
Providers disagree about field names, timestamps and settlement windows. The layer normalises all of it into a single ledger you can reconcile once.
Normalised transaction and settlement records
Per-provider fees mapped to one schema
Chargeback and refund events in the same stream
Exports and reporting API over one data model
Get started
See the request that does all of this.
Country and method are parameters of the same signed call. Read the reference and build against the live endpoints.