The three integration routes
Every eCom Pay integration takes one of three routes, and choosing between them is the first conversation with the integration team.
Hosted payment pages
The fastest route live. The customer completes payment on a secure page served from the gateway’s infrastructure, styled with your branding, and returns to your site with the result. Card data never touches your systems, which keeps your PCI DSS workload at its smallest, and the integration effort is minimal, which is why it suits most businesses most of the time.
Platform plugins and modules
For stores on WooCommerce, Shopify, PrestaShop, Zen Cart and the other major platforms, a dedicated plugin embeds hosted payment fields inside your own checkout. Our team installs and configures it, tokenisation and 3D Secure 2 included, and tests every path before go live. The payment gateways index covers the platforms in full.
Direct API integration
For bespoke checkouts, marketplaces, booking engines and products of your own design, the payment API exposes card capture through hosted fields, tokenisation, 3D Secure 2 flows and recurring charges as building blocks. The custom API page covers what you can build, and the full technical reference arrives at onboarding.
What you receive at onboarding
Once your account is approved, your team receives the complete integration pack, the technical documentation for your chosen route, sandbox credentials for testing, your live credentials handled securely, and a named contact on the integration team. The documentation covers request formats, response handling, token workflows, authentication flows and error cases, everything a developer needs to build without guessing.
How the integration team works with you
The pattern is scoping, then sandbox, then verification, then live. Scoping agrees the route and the flows before anyone writes code. The sandbox phase runs your integration against test infrastructure with the team on hand for questions. Verification walks every payment path together, payments, saved cards, refunds, declines and authentication flows, before real customers arrive. And going live is deliberately the boring part, because everything interesting was settled earlier. Support does not end at launch, integration questions route through the same team for the life of the account.
Security expectations, both directions
The architecture keeps card data inside secure payment infrastructure, hosted fields and tokens mean your systems handle references, never raw card numbers. In return, credentials must be treated as secrets, kept out of source control and front-end code, and requests must come from your servers or through the hosted components as documented. The PCI compliance page explains how this architecture keeps your compliance workload small.
Before you apply
Integration questions before an application are welcome, and often save time. Tell us what you are building and your platform or stack, and the integration team will confirm the cleanest route and a realistic timeline, usually the same working day. Then the application itself takes minutes, and approval takes 24 hours once your documents are in.