Developers
Connect payments.
Keep the context.
Design the journey from your business application to an approved payment provider, with a clear path back to the record.
Payment gateways
Start with the right payment relationship.
Scope the service, provider account, country and currency before choosing an integration route.
Merchant-owned checkout
Explore a hosted payment journey using the merchant’s own approved acquiring arrangement.
Wallet funding
A distinct money flow with its own provider, account and operating requirements.
Card programmes
Issuing needs a suitable programme and eligibility model. It is not an extension of checkout.
A considered payment journey
From a customer action
to a reliable record.
Think beyond the checkout screen. A useful integration accounts for confirmation, incomplete journeys and the questions your operations team will need to answer.
- Define the requestConnect the merchant, sale and intended payment.
- Verify the outcomeProvider confirmation, not a browser return, determines payment status.
- Plan for exceptionsAgree how pending outcomes and follow-up work are handled.
- Keep business contextConnect the outcome to the appropriate record and reporting process.
Integration discovery
Fit the payment journey to your product.
Integration access and documentation are agreed through a scoped discussion, rather than self-service API registration.
Websites & apps
Connect the customer experience with payment status and a useful next step.
Platforms & marketplaces
Define who owns the transaction and receives funds before shaping the solution.
Programme portals
Align participant access, service eligibility and reporting needs with the operating model.
A useful integration brief
Start with what needs to connect.
- Your website, app, marketplace or programme
- Who pays, receives funds and provides support
- Country, currency and provider requirements
- Reporting and reconciliation needs
Share the journey, not the credentials.
Keep keys, customer records and card details out of your enquiry. Service availability and implementation commitments follow a separate assessment.
Send an integration brief