Payments
Payment API Integration
Behind every deposit button is a chain of API calls: create a payment request, hand the player to the provider's flow, receive a status webhook, credit the wallet. Payment API integration is about making that chain reliable under real-world conditions — retries, duplicates and late callbacks included.
- Payment request flows
- Webhook handling
- Idempotent processing
- Payout flows
- Reconciliation support
The core flows
The API workflows every iGaming payment integration implements.
- Payment request creation with unique references
- Hosted, embedded or redirect provider flows
- Status webhooks for success, failure and pending states
- Payout requests for withdrawals
- Reconciliation exports and reporting
Idempotency is not optional
Providers retry webhooks; players refresh pages; networks fail. Every transaction handler must be idempotent — processing the same callback twice must never credit a player twice.
Status handling
Payment states are not binary. Pending, authorized, failed, expired and chargebacked all need defined behaviour in the wallet and the admin panel.
Frequently Asked Questions
What happens if a provider webhook arrives twice?
Idempotent handling means the second delivery is recognised as a duplicate and ignored — the player is credited exactly once.
Can we use our own cashier UI?
Yes. The payment API layer can drive a fully custom cashier, or a standard cashier component can be provided.
Related pages & guides
Payment Gateway Integration
The business-level payments overview.
Learn moreIntegration Process
How payment projects are delivered.
Learn moreTechnical Documentation
Guides on callbacks, errors and testing.
Learn more GuideHow iGaming Payment Integration Works
Deposits, withdrawals, callbacks and the onboarding realities of gambling payments.
Learn moreBuild Your iGaming Platform With CasinoAPI
Tell us what you're building. We'll map the integrations, architecture and next steps with you.