The eCom Pay payment gateway API puts full card processing behind whatever you are building, a bespoke checkout, a marketplace, a booking engine or a product that does not exist yet. Hosted fields keep card data off your systems, tokenisation powers saved cards and repeat billing, and settlement lands the next working day, approved in 24 hours once your documents are in.
24 hrs
approval, once documents are in
150+
currencies processed
4.4
Trustpilot rating
2010
processing payments since
On this page Choosing a provider · The integration · Going live · See it working · Once you are live · FAQs
A payment API is a long-term dependency, so choose it like one. Three things separate an API your developers will thank you for from one they will curse.
Check your approval oddsThe right architecture captures cards through hosted fields served from the gateway’s secure infrastructure, so raw card data never touches your servers and your PCI DSS scope stays small however custom the build gets.
Documentation is the start, not the service. An integration goes live faster and safer when developers can talk to people who work with the API daily, which is exactly what our team provides through scoping, build and testing.
The API is half the product, the account behind it is the other half. Underwriting done properly, settlement the next working day and a personal account manager mean the business side keeps pace with the build.
Full card processing as building blocks, with the account and support behind them.
Take one-off payments inside any flow you design, with hosted fields dropping into your own front end so the experience stays entirely yours.
Vault cards as secure tokens on first use, then charge, re-charge or one-tap checkout against the token. Saved cards, subscriptions and repeat billing all build on the same block.
Strong customer authentication runs through the API with the gateway handling the challenge flows, keeping you aligned with SCA rules without building bank interactions yourself.
Schedule recurring charges against stored tokens for subscriptions, instalments and usage billing, with smart retries rescuing failed payments.
Price and charge in the currencies your customers think in, settle in yours from 25+, and reconcile everything on one account.
Clear transaction data with consistent references, so your own dashboards, ledgers and reconciliation jobs have something solid to stand on.
Fair. So here is what UK merchants say after switching to eCom Pay, in their own words.
It was such a pleasure working with eCom Pay for my company, very straightforward to set up and the team were so helpful. No hidden fees, cost efficient, and from using other platforms before I can say this has been the best so far.
Verified merchantvia Trustpilot
We found eCom Pay to be a simple, efficient payment system to integrate, with a lot of support behind it. Would recommend them over competitors who charge far too much.
Verified merchantvia Trustpilot
Great customer service from eCom Pay. Needed a card reader for my business, they had me set up fast and gave me better rates than the last company. Highly recommend.
Verified merchantvia Trustpilot
Super impressed with eCom Pay. The transaction fees are competitive, and I love that my customers have multiple payment options, which has noticeably improved my sales.
Verified merchantvia Trustpilot
Good service from eCom Pay. The card machines are reliable and easy to use. I like that there are no hidden fees and everything is explained upfront.
Verified merchantvia Trustpilot
Would highly recommend. Easy, simple, and always answers when I need help. The best payment gateway I have come across, with a wide variety of packages available.
Verified merchantvia Trustpilot
The application is the start, not the product. This is what running your payments with eCom Pay actually looks like, week to week.
Available 24/7 by phone, WhatsApp or email. Integration questions, rate reviews and new features all go through one person who knows your build.
The developer hub covers integration routes and how the pieces fit, and full technical documentation is provided at onboarding, walked through with your team.
Custom builds in specialist sectors run on accounts underwritten for them, the same API on acquiring that understands your industry.
Start with one payment flow and add saved cards, recurring billing or new currencies as the product evolves, all on the same account and integration.
Any flow that ends in a card payment. Bespoke checkouts, marketplaces, booking engines, SaaS billing, apps and internal tools all build on the same blocks, hosted card capture, tokenisation, 3D Secure 2 and recurring charges, with settlement the next working day.
No. Hosted payment fields capture card details directly into the gateway’s secure infrastructure and hand your systems a token, so your PCI DSS scope stays small no matter how custom the surrounding build is.
Both. The developer hub and full technical documentation cover the how, and our integration team works with your developers through scoping, sandbox, build and testing, which is usually the difference between a smooth fortnight and a stuck month.
Yes. Cards vault as secure tokens on first use, and scheduled or on-demand charges run against the token, with smart retries on failures. Subscriptions, instalments and usage billing all build on that primitive.
Processing runs in 150+ currencies with settlement in 25+, so international pricing is a product decision rather than a payments limitation, and everything reconciles on one account.
The account is approved in 24 hours once your documents are in, and build time depends on your scope, agreed honestly at the start. Simple hosted-field integrations go live in days, and our team supports the build for as long as it takes.
Written by the eCom Pay team. Reviewed August 2026. Last updated August 2026.
Direct API access with humans behind it, hosted card security and settlement the next working day, approved in 24 hours once your documents are in.
Start technical reading on the developer hub, or see all platform gateways if a plugin fits better.