ECOMMPAY

ECOMMPAY is a London-headquartered international payment service provider and direct card acquirer founded in 2012, authorised by the UK Financial Conduct Authority (FRN 607597), PCI DSS Level 1 certified, and holding Visa and Mastercard Principal Membership. It operates its own payment gateway, acquiring, and certified processing platform, serving e-commerce merchants across Europe, the UK, and global markets with card processing, 100+ alternative and local payment methods, open banking, payouts, multi-currency settlement, and fraud prevention. Its developer surface is API-native but signature-authenticated rather than token-based: merchants integrate through a hosted Payment Page API, a server-to-server Gate API for direct payment processing, a Data API for reporting and reconciliation, and a Dashboard for operational management, all documented on a public developer portal with callbacks/webhooks and multi-language SDKs. Its home market is the United Kingdom.

ECOMMPAY is listed with 4 APIs on the APIs.io network. Tagged areas include Payments, United Kingdom, Payment Gateway, Payment Processing, and Acquiring.

The ECOMMPAY catalog on APIs.io includes 1 event-driven AsyncAPI specification.

ECOMMPAY’s developer surface includes documentation, API reference, getting-started guide, pricing, engineering blog, support, signup flow, and 22 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

37.9/100 thin ▬ flat Agent 26/100 agent aware Heartbeat 70/100 slowing saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

4 APIs

Payments United Kingdom Payment Gateway Payment Processing Acquiring Card Payments Alternative Payment Methods Open Banking Payouts Cross-Border Fraud Prevention

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 37.9/100 · thin

Contract Quality 8.3 / 21

Developer Ergonomics 8.9 / 17

Access Clarity 3.1 / 17

Operational Transparency 2.0 / 11

Contract Governance 1.9 / 10

Discoverability 5.9 / 9

Regulatory Posture 5.4 / 15

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/ecommpay/"><img src="https://apis.io/badge/ecommpay/card.svg" alt="ECOMMPAY on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 18.4 — up to +16.3 composite points
Contract Quality scores 39.0 — up to +15.3 composite points
Operational Transparency scores 18.4 — up to +10.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/ecommpay/apis.yml: open an issue on github.com/api-evangelist/ecommpay to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
MACH & Headless Commerce	builds-on	34.5 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

ECOMMPAY Payment Page API

Hosted, highly customisable payment form for accepting payments across cards, alternative payment methods, and wallets. Merchants open the Payment Page with a signed request (HM...

ECOMMPAY Gate API

Server-to-server payment API for direct integration, giving merchants full control of the payment flow through their own interface. Supports one-time purchases, refunds, payouts...

ECOMMPAY Data API

Reporting and data-retrieval API for programmatic access to payment, operation, and reconciliation data on the ECOMMPAY platform. Requests are accepted over HTTP/1.1+ with TLS 1...

ECOMMPAY Dashboard

Merchant management interface providing tools for controlling, analysing, and managing payments, projects, and reporting across the ECOMMPAY platform.

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Ecommpay Callbacks Webhooks

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Ecommpay Authentication

signature-hmac · 1 scheme

SECURITY

Ecommpay Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

Webhooks

Conformance

Lifecycle

Components

Scroll for all 7

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

DeclineCodes

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Compliance

Compliance

Operate 2

Status, limits, changes, and where to get help

StatusPage

StatusPage

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Source (apis.yml)

aid: ecommpay
url: https://raw.githubusercontent.com/api-evangelist/ecommpay/refs/heads/main/apis.yml
name: ECOMMPAY
kind: company
description: 'ECOMMPAY is a London-headquartered international payment service provider and direct card acquirer founded in
  2012, authorised by the UK Financial Conduct Authority (FRN 607597), PCI DSS Level 1 certified, and holding Visa and Mastercard
  Principal Membership. It operates its own payment gateway, acquiring, and certified processing platform, serving e-commerce
  merchants across Europe, the UK, and global markets with card processing, 100+ alternative and local payment methods, open
  banking, payouts, multi-currency settlement, and fraud prevention. Its developer surface is API-native but signature-authenticated
  rather than token-based: merchants integrate through a hosted Payment Page API, a server-to-server Gate API for direct payment
  processing, a Data API for reporting and reconciliation, and a Dashboard for operational management, all documented on a
  public developer portal with callbacks/webhooks and multi-language SDKs. Its home market is the United Kingdom.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Payments
- United Kingdom
- Payment Gateway
- Payment Processing
- Acquiring
- Card Payments
- Alternative Payment Methods
- Open Banking
- Payouts
- Cross-Border
- Fraud Prevention
tags_raw:
- Payments
- United Kingdom
- Payment Gateway
- Payment Processing
- Acquiring
- Card Payments
- Alternative Payment Methods
- Open Banking
- Payouts
- Cross-Border
- Fraud
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.23'
apis:
- aid: ecommpay:ecommpay-payment-page-api
  name: ECOMMPAY Payment Page API
  description: Hosted, highly customisable payment form for accepting payments across cards, alternative payment methods,
    and wallets. Merchants open the Payment Page with a signed request (HMAC signature over the request parameters using the
    project secret key) and receive asynchronous callbacks with the payment result. Includes JavaScript and mobile SDKs.
  humanURL: https://developers.ecommpay.com/en/en_PP_about.html
  baseURL: https://paymentpage.ecommpay.com
  tags:
  - Payments
  - Hosted Payment Page
  - Checkout
  properties:
  - type: Documentation
    url: https://developers.ecommpay.com/en/en_PP_about.html
  - type: APIReference
    url: https://developers.ecommpay.com/en/en_PP_API.html
- aid: ecommpay:ecommpay-gate-api
  name: ECOMMPAY Gate API
  description: Server-to-server payment API for direct integration, giving merchants full control of the payment flow through
    their own interface. Supports one-time purchases, refunds, payouts, and credential-on-file transactions. Requests are
    authenticated with a project ID and an HMAC signature over the request payload; payment results are delivered via asynchronous
    callbacks. The API reference is rendered on a dedicated Stoplight-based reference host.
  humanURL: https://developers.ecommpay.com/en/en_Gate_Integration_About.html
  baseURL: https://api.ecommpay.com/v2
  tags:
  - Payments
  - Payouts
  - Refunds
  - Server-to-Server
  tags_raw:
  - Payments
  - Payouts
  - Refunds
  - Server to Server
  properties:
  - type: Documentation
    url: https://developers.ecommpay.com/en/en_Gate_Integration_About.html
  - type: APIReference
    url: https://api-developers.ecommpay.com/api.html
- aid: ecommpay:ecommpay-data-api
  name: ECOMMPAY Data API
  description: Reporting and data-retrieval API for programmatic access to payment, operation, and reconciliation data on
    the ECOMMPAY platform. Requests are accepted over HTTP/1.1+ with TLS 1.2+ at the documented endpoints and are signature-authenticated.
    The interface specification is published on a dedicated Stoplight-based reference host.
  humanURL: https://developers.ecommpay.com/en/en_dbl_api_overview.html
  baseURL: https://data.ecommpay.com/v1
  tags:
  - Data
  - Reporting
  - Reconciliation
  properties:
  - type: Documentation
    url: https://developers.ecommpay.com/en/en_dbl_api_overview.html
  - type: APIReference
    url: https://api-data.ecommpay.com/api.html
- aid: ecommpay:ecommpay-dashboard
  name: ECOMMPAY Dashboard
  description: Merchant management interface providing tools for controlling, analysing, and managing payments, projects,
    and reporting across the ECOMMPAY platform.
  humanURL: https://developers.ecommpay.com/en/en_dbl_about.html
  tags:
  - Dashboards
  - Management
  - Reporting
  tags_raw:
  - Dashboard
  - Management
  - Reporting
  properties:
  - type: Documentation
    url: https://developers.ecommpay.com/en/en_dbl_about.html
common:
- type: DomainSecurity
  url: security/ecommpay-domain-security.yml
- type: Website
  url: https://ecommpay.com/
- type: DeveloperPortal
  url: https://developers.ecommpay.com/
- type: Documentation
  url: https://developers.ecommpay.com/landing-en/
- type: APIReference
  url: https://api-developers.ecommpay.com/api.html
- type: GettingStarted
  url: https://developers.ecommpay.com/en/en_getting_started.html
- type: GitHubOrganization
  url: https://github.com/ITECOMMPAY
- type: StatusPage
  url: https://status.ecommpay.com/
- type: Pricing
  url: https://ecommpay.com/pricing/
- type: Blog
  url: https://ecommpay.com/blog/
- type: Support
  url: https://ecommpay.com/support/
- type: SignUp
  url: https://dashboard.ecommpay.com/
- type: TermsOfService
  url: https://ecommpay.com/terms-of-use/
- type: PrivacyPolicy
  url: https://ecommpay.com/privacy-policy/
- type: LinkedIn
  url: https://www.linkedin.com/company/ecommpay
- type: Authentication
  url: authentication/ecommpay-authentication.yml
- type: Conventions
  url: conventions/ecommpay-conventions.yml
- type: Idempotency
  url: conventions/ecommpay-conventions.yml
- type: Packages
  url: packages/ecommpay-packages.yml
- type: SDKs
  url: packages/ecommpay-packages.yml
- type: Sandbox
  url: sandbox/ecommpay-sandbox.yml
- type: ErrorCatalog
  url: errors/ecommpay-decline-codes.yml
- type: DeclineCodes
  url: errors/ecommpay-decline-codes.yml
- type: Webhooks
  url: asyncapi/ecommpay-callbacks-webhooks.yml
- type: Conformance
  url: conformance/ecommpay-conformance.yml
- type: Compliance
  url: https://ecommpay.com/
- type: Lifecycle
  url: lifecycle/ecommpay-lifecycle.yml
- type: Components
  url: components/ecommpay-components.yml
- type: LLMsTxt
  url: llms/ecommpay-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

ECOMMPAY API — frequently asked questions

Does ECOMMPAY have an API?

Yes. APIs.io lists 4 APIs from ECOMMPAY, including ECOMMPAY Payment Page API, ECOMMPAY Gate API and ECOMMPAY Data API, and 1 more.

How do I authenticate with the ECOMMPAY API?

ECOMMPAY uses bearer-token authentication (signature-hmac · 1 scheme). The details are profiled on APIs.io as Ecommpay Authentication.

Is the ECOMMPAY API ready for AI agents?

ECOMMPAY has a Kin Score of 37.9 out of 100 (thin) and an Agent Readiness score of 25.9 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/ecommpay"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/ecommpay/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/ecommpay/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.