BUILD · OPERATE · UNDERSTAND
A gateway.
A complete reference.
Practical integration guides, operational playbooks and clear service policies. Everything has a place.
Developers
Your first payment connection ↗
A practical route from an isolated test account to your first live direct-payment integration.
DEVELOPERSTest without moving money ↗
Isolated developer accounts, test credentials and a lifecycle simulator.
DEVELOPERSCredentials with clear boundaries ↗
Understand which key belongs on which server, and how to replace it safely.
DEVELOPERSEvents your integration can trust ↗
Design payment handling around verified events and repeat delivery.
DEVELOPERSOne request. One intended outcome. ↗
Prevent retries from creating extra test purchases or duplicate activations.
DEVELOPERSFailures with a next step ↗
Handle validation, authentication and uncertain outcomes deliberately.
DEVELOPERSA deliberate move to live payments ↗
Complete the operational checks that a simulator cannot cover.
Product
Choose how payments reach you ↗
Direct payment is available now. Provider API connections are a future channel.
PRODUCTFrom receipt to accounted-for payment ↗
Make unresolved payments visible and compare them with the source of funds.
PRODUCTOperate the connection day to day ↗
Clear responsibilities for the phone, gateway and billing system.
Company
Discuss the right commercial setup ↗
Get a clear agreement for your market, volume and deployment.
COMPANYService and incident information ↗
Where to look when a payment or connection needs attention.
COMPANYWhat is available. What comes next. ↗
A transparent view of the current gateway and areas still under development.
Policies
Acceptable use ↗
Use the gateway for legitimate payment reconciliation and authorised integrations.
POLICIESRefunds, reversals and disputes ↗
Know who received the money and who can return it.
POLICIESData processing arrangements ↗
Set out the responsibilities for payment-related personal data before production use.
POLICIESRetention and account closure ↗
Keep evidence deliberately and remove data through a controlled process.
POLICIESCookies and browser storage ↗
A clear account of what the website keeps in your browser.
POLICIESReport a security concern ↗
Help us understand a vulnerability without exposing other customers.
POLICIESDeveloper and sandbox terms ↗
Rules for using the test environment and building integrations.