Request a demo

SATO · Payments

Payment routing based on what providers do, not what they announce

Provider health is measured from real attempts. The cashier switches away from a failing provider and back, and a preview shows exactly what a given player sees.

Decisions come from observation

The payments section decides which payment methods a player is shown, based on what providers actually do rather than on what they announce. It holds the provider registry, measures health continuously, routes traffic, switches away from a failing provider and back again, and previews the cashier for any player.

What is measured, and why

  • Pass rate over attempts. The window is counted in attempts, not hours. A provider with a handful of payments a day would never fill a two-hour window and would be filed as “not enough data” while it quietly failed.
  • Instant-decline share. A decline within a second of creation is the signature of a provider refusing on its own side. A decline hours later is a player who walked away. Ordinary reports mix the two; routing separates them.
  • Median time to result. A provider that still passes payments but takes a minute to do it is already losing players.
  • Hourly profile. A provider that is closed at night and healthy by day is not degraded. It should be hidden during its own closed hours and not switched off altogether, and its health sample must exclude those hours.

Declared schedules are shown, never trusted alone

A declared maintenance window is stored and displayed beside the observed state as a second, independent fact. When the two disagree, the operator sees the disagreement instead of a silent override.

The AI operator and routing

The AI reads the same measurements and speaks in consequences: which route degraded, how many attempts were affected, what the alternative is. It prepares the routing change with a preview; a person approves it. Changes to money flow are not made autonomously.

Questions and answers

Why not hide a payment method on the provider's announced schedule?

Announced maintenance windows and real closing hours often differ. A cashier that trusts the announcement hides a working channel. SATO stores the declared schedule and shows it, but decides from observed attempts.

What does the routing measure?

The pass rate over a sample of recent attempts, the share of declines that happen within one second of creation, the median time to a result, and an hourly profile from which a provider's observed closing hours are derived.

Can I see what a player sees?

Yes. The cashier preview renders the payment methods exactly as a given player would see them, so a routing change can be checked before and after.

Want to see it on your use case?

See it running on a live demo: a player-facing casino and a back office you can talk to.