No contact form · direct team inboxes

Contact the team that can answer.

Choose the email that matches your question. A clear subject line and a little context help the right team respond without a handoff chain.

MERCHANT / SALES

New payment setup

For gateway availability, commercial terms, payment methods, settlement needs, onboarding, or a new merchant application.

INTEGRATION / TECHNICAL

API and checkout

For integration architecture, hosted checkout, test flows, callbacks, webhooks, payment states, or implementation questions.

EXISTING MERCHANT

Operational support

For transaction references, payment-status questions, refunds, settlement records, access, or an existing merchant issue.

BUSINESS DEVELOPMENT

Partnerships

For banks, payment-route partners, commerce platforms, technology providers, and considered go-to-market opportunities.

RISK / COMPLIANCE

Policy and review

For merchant-review questions, policy notices, legal requests, data-protection enquiries, or responsible disclosure routing.

WHAT TO INCLUDE

Help us start well

New merchants should include the business name, website, product or service, expected payment methods, estimated monthly volume, average transaction value, and preferred settlement account country.

Protect payment data.

Do not sendFull card numbers, security codes, passwords, secret API keys, one-time codes, or unnecessary identity documents by email.
Transaction questionsUse the merchant reference or gateway transaction ID. Mask customer details and card information.
UrgencyDescribe the business impact and affected payment state. Do not place sensitive information in the subject line.