Cascading
A second channel, before the player notices.
Where a method has several partner channels, a declined or stalled deposit moves to the next in the same session. Status is checked first, to help prevent double payments.
A deposit, from the player's tap to the partner's settlement.
A withdrawal, from the player's request to the partner's payout.
When one partner channel fails, the next one gets the same request, in the same session.
Paysooper's software routes each request and reports its status. The payment partner processes each payment and payout, holds any prefunded balance and settles to you. Paysooper never receives, holds, controls or transfers funds.
What comes with it
More deposits in. Fewer problems out.
Dedicated support
A team that knows your business.
The people who set up your integration answer your messages, from onboarding to live traffic. When a partner channel slows down, we let you know.
Risk management
Risk checks before the deposit.
Trusted players can be whitelisted, and blacklist screening helps stop known bad actors before they deposit, reducing chargeback abuse and fraud.
Inside the router
Which channel goes first, and why.
Cascading is only as good as the order it tries things in. The router ranks every live partner channel for each payment request, and keeps re-ranking as results come back.
- Method
- UPI, QRIS, GCash: each has its own set of channels.
- Amount
- Some channels handle small tickets better, others large ones.
- Live success rate
- Recent results move a channel up or down the order.
- Channel health
- A channel that stops answering is taken out of rotation.
Integration
One API across every market
REST API and signed webhooks
The same request and the same callback format for UPI in India and QRIS in Indonesia. A new market uses the same endpoints.
Reconciliation data
Each transaction's status and the partner's reference come back through the API and webhooks, to help you reconcile each settlement.