Access requirements
Platform access is issued to authorised merchants and partners under separate commercial and technical arrangements. Public visitors can review conceptual documentation; credentials and environment URLs are not published on this site.
- Confirmed commercial agreement with AQPAY LTD or an authorised partner
- Designated technical contact for credential delivery
- Approved domains, callback URLs and IP ranges where controls apply
- Secure credential storage and environment separation
Integration preparation
- Identify whether your integration will use server-to-server, hosted payment pages, webhooks, or a combination.
- Prepare sandbox-capable systems that can receive redirects and webhook callbacks.
- Confirm TLS, logging and secret-management practices for your environment.
- Review security, acceptable-use and support guidance on this site.
- Wait for provider-verified API documentation before implementing production traffic.
What to expect next
Once the white-label gateway provider configuration is confirmed, authorised teams will receive:
- Sandbox and production environment details
- Authentication method and credential handling instructions
- Verified API reference and webhook guidance
- Portal access and operational contacts
Important constraints
- Do not invent or assume endpoint paths, signatures or status models.
- Do not process live cardholder data outside approved environments.
- Do not share credentials across environments or teams without need.
- Do not submit sensitive payment data through support channels.
Return to the documentation overview or review support guidance if you already have an authorised contact path.