1. Non-sensitive summary
Send the business model, markets, game category, payment journey and requested methods without attaching identity documents.
Contact us · Email directory
We do not use a generic contact form. Choose the team that matches your question and include enough context for a useful first response.
Before you email
For merchant enquiries, include your legal entity, game category, target countries, website or app, expected payment methods and whether your flow includes payouts.
Company information, partnerships and questions that do not fit another team.
New gaming business assessments, method availability and commercial discussions.
API, hosted checkout, webhooks, testing, status design and reconciliation requirements.
Production incidents and payment operations. Include your merchant reference, not sensitive payment data.
Merchant due diligence, game-category information, regulatory requests and responsible-use controls.
Access, correction, deletion and other privacy-related enquiries.
Report a suspected vulnerability with steps to reproduce and potential impact.
Merchant enquiry flow
Send the business model, markets, game category, payment journey and requested methods without attaching identity documents.
The proposed flow is reviewed for legal category, merchant information, integration needs and gateway configuration.
Before activation, request pricing, settlement arrangements, fund-handling institutions, privacy roles and support commitments in writing.
Share due-diligence material only after the receiving party and an appropriate transfer method have been confirmed.
Player payment question?
If you see a charge from a game or need help with an in-game purchase, the game operator has the order, account and fulfilment context. Contact its support team using the information in the game or receipt. Do not send payment credentials to us by email.