Provider dependent
Payments
Payment and location interfaces are built in. Live providers are contracted and accepted per deployment.
The problem
Payments are where regulation, fraud and customer experience collide. A provider swap shouldn’t mean a rebuild.
What the platform does
Deposits and withdrawals run through payment interfaces that sit behind the wallet. The provider is a deployment choice; the wallet, limits and ledger stay the same.
How it works
Follow it through.
- Front end
- Platform API
- Wallet
- Payment provider
- 01
The player starts a deposit or withdrawal in any front end.
- 02
Limits and restrictions are checked by the platform first.
- 03
The configured provider handles the payment.
- 04
The wallet and ledger record the outcome.
Controls
- Deposit limits and affordability thresholds
- Withdrawal restrictions linked to AML cases
- Every movement recorded on the ledger
Operator experience
Withdrawals are handled in the back office alongside AML cases and fraud checks.
Integration points
- Payment providers, contracted per deployment
- Geolocation provider where required
Audit & reporting
Payment outcomes land on the ledger and in operator reporting.
Related capabilities
Let’s talk about what you’re building.
Tell us what you’re building. We’ll tell you plainly what the platform does today and what it would take.