ECOMMPAY review: products, technology and pricing (2026)

ECOMMPAY (written Ecommpay on its own site) is a payment service provider and direct card acquirer that gives merchants one integration for cards, wallets, open banking, buy now pay later and payouts. Its technology is built around a hosted Payment Page and a JSON API called Gate, backed by its own acquiring and a risk and analytics layer.

The company describes itself as a full-stack provider, meaning it runs the gateway, the acquiring relationship and the payment-method connections itself rather than reselling them. If those terms are unfamiliar, our guide to payment gateways, PSPs and acquirers explains the difference.

At a glance

How the platform works

A merchant integrates once, and Ecommpay handles the connections behind it. For cards, it acts as the acquirer, so authorisation requests go from its gateway to the card schemes and issuers without a separate acquiring contract. For everything else, such as wallets, bank-based methods and cash vouchers, the gateway connects to the local scheme or provider and returns a normalised result. The how card payments work guide shows where each party sits in a typical card flow.

There are two ways to take a payment. In the hosted route, the merchant builds a signed payment request and sends the customer to Ecommpay's Payment Page, which collects the details and returns the outcome by server-side callback. In the API route, the merchant calls Gate directly and builds its own checkout. The company lists tokenisation, encryption and Level 1 PCI DSS certification on its gateway page.

Gate's documentation describes two interaction styles. Synchronous requests, such as checking a payment's status, are answered inside the same HTTP session and normally return in under 100 ms. Asynchronous requests, such as starting a payment that needs the customer or an external scheme, are acknowledged first and finished later by a callback. Every request is a POST with a UTF-8 JSON body and a signature over TLS 1.2 or higher, and callbacks must be acknowledged with HTTP 200. Requests pass through three stages: acceptance, processing (including the signature check) and execution.

Risk tooling is described as real-time risk control plus retry logic and routing to reduce failed payments. For tokenised card data and 3-D Secure, see our explainers on network tokenisation and 3-D Secure.

Products

Payment gateway and acquiring

The core product is a gateway with direct acquiring in a single integration. Ecommpay says it supports more than 100 global and local payment methods and processes in more than 70 markets (company pages, accessed 3 November 2026).

Payouts

Payouts go to cards and to alternative methods in local currencies. The company lists use cases such as paying out winnings, loans and salaries, and funding transfers between accounts. It also appears in Visa's Direct partner directory as a provider offering instant or bulk payouts to cards.

Subscriptions, links and QR payments

Recurring billing, payment links, reusable QR codes and a virtual payment terminal sit alongside the gateway. Payment links and QR codes suit sellers who take orders by message or at events without a full website checkout.

Orchestration and optimisation

Ecommpay lists payment orchestration among its solutions and also sells to orchestration platforms, covered under recent launches. Its authorisation optimisation features include retry logic, intelligent routing, Currency Choice (customers pick their billing currency) and a dashboard for success-rate trends. See payment orchestration explained for the wider concept.

Merchant dashboard

The dashboard covers transaction search, refunds, reporting and payment strategy analytics. A separate carbon-offsetting checkout option is also listed.

Developer experience and integrations

The documentation portal (developers.ecommpay.com) is organised around onboarding, an overview, examples and support. Onboarding is a four-step process: application, set-up with a client manager, testing in a separate environment, and a move to live support.

Three integration routes are documented for Payment Page: a signed API request, a PHP SDK distributed through Composer, and a JavaScript SDK for Node.js. Each route covers creating the request, sending the customer to the page and reading the result by callback. The Gate section adds quickstarts with PHP and Go examples and covers one-step and two-step purchases, payment links, recurring payments on stored credentials, refunds, payouts and card verification with a zero or non-zero amount.

For apps, the mobile SDK embeds checkout inside the app so customers are not sent to a mobile browser. It supports card scanning, recurring billing, 3-D Secure, Apple Pay and Google Pay, with two UI options: one using Ecommpay's components and one where the merchant supplies its own. The company lists Android 5.0 and iOS 14 as minimum versions and also mentions Flutter. E-commerce plugins listed include WooCommerce, BigCommerce and Magento. The small-business page adds Xero for reconciliation and states there is no native Shopify integration.

Payment methods, currencies and coverage

Marketing pages cite more than 100 alternative payment methods. The developer reference is more granular: its method-code table, as opened on 3 November 2026, lists 70 entries, including cards, Apple Pay, Google Pay, China UnionPay, Alipay, WeChat, GCash, Skrill, SEPA Direct Debit, PIX, Bizum, Klarna and 21 country-specific open banking entries such as Germany and Spain. The two counts measure different things, so treat the documentation list as the integration-ready set and the marketing figure as the headline.

The platform's payment-method finder breaks coverage down by region (Africa, Asia, CIS, Europe, Latin America, Middle East, North America, Oceania and the Caribbean). Currencies are not stated on the gateway page. For background on local methods, see alternative payment methods explained.

Pricing model

Enterprise pricing is not published; the gateway page directs prospects to contact sales. The one public rate card is for UK micro-businesses (page accessed 3 November 2026):

Eligibility for that plan requires a UK-registered business that has traded for at least six months, has an active website, earns under €2m a year and has fewer than 10 employees. The company also states that fraud controls use in-house risk rules and graph analysis, with a claimed 97% detection and prevention rate, which is the company's own figure and not independently checked.

Recent launches

Regulation in brief

Ecommpay states on its About us page that it is authorised by the UK Financial Conduct Authority and holds PCI DSS Level 1 certification. Its timeline records an FCA licence in 2014 and Visa and Mastercard Principal Member status in 2015. We did not open a regulator register for this edition, and the page does not list its other entities; our guide on how to check a financial licence shows how to verify the entity that would contract with you.

Who it tends to suit

Ecommpay may suit merchants that want acquiring, local methods and payouts from a single provider, particularly in Europe and the UK, and platforms that need to add a PSP behind an orchestration layer. The published UK small-business plan is aimed at very small online sellers, while larger merchants negotiate pricing. Readers comparing it with a peer can see Ecommpay vs Emerchantpay, and the gateways hub lists related profiles.