takepayments website screenshot

takepayments

takepayments (a trading name of Payzone UK Limited) is a United Kingdom payment gateway and merchant-services provider that lets businesses accept card payments online, in person, and over the phone. Its online payment gateway offers Hosted (redirect) and Direct (server-to-server) integrations for e-commerce checkouts, delivered as SOAP v1.1 XML and HTTPS form-POST requests authenticated with a merchant ID and a pre-shared-key signature hash, alongside ready-made shopping-cart plugins and backend SDK code packs. Its newer Terminal API is a modern REST/JSON surface hosted on Azure API Management, secured with OAuth 2.0 client-credentials via Microsoft Azure AD, that pairs and drives card machines (Move5000, PAX A920 Pro) for Start-Transaction, Pairing, Split Bill & Gratuity, and Pay at Table flows. takepayments runs a real public developer portal at developer.takepayments.com but does not publish a downloadable OpenAPI/Swagger definition; its API reference is documentation-only, and merchant onboarding is sales-led rather than open self-serve.

takepayments publishes 1 API on the APIs.io network. Tagged areas include Payments, United Kingdom, Payment Gateway, Payment Processing, and Card Payments.

takepayments’ developer surface includes documentation, API reference, SDKs, engineering blog, support, pricing, authentication, and 20 more developer resources.

33.9/100 thin ▬ flat Agent 9/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessSelf serve
1 APIs
PaymentsUnited KingdomPayment GatewayPayment ProcessingCard PaymentsCard MachinesIn-Person PaymentsE-CommercePSPAcquiring

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
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/.
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 github.com/api-evangelist/takepayments: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

takepayments Terminal API

A REST/JSON API hosted on Azure API Management for pairing and driving takepayments card machines (Move5000, PAX A920 Pro) from an integrated app or POS. Documented operations i...

Security Posture 2

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

Takepayments Authentication

oauth2/apiKey · 2 schemes

SECURITY

Takepayments Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 5

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: takepayments
url: https://raw.githubusercontent.com/api-evangelist/takepayments/refs/heads/main/apis.yml
name: takepayments
kind: company
description: takepayments (a trading name of Payzone UK Limited) is a United Kingdom payment gateway and merchant-services
  provider that lets businesses accept card payments online, in person, and over the phone. Its online payment gateway offers
  Hosted (redirect) and Direct (server-to-server) integrations for e-commerce checkouts, delivered as SOAP v1.1 XML and HTTPS
  form-POST requests authenticated with a merchant ID and a pre-shared-key signature hash, alongside ready-made shopping-cart
  plugins and backend SDK code packs. Its newer Terminal API is a modern REST/JSON surface hosted on Azure API Management,
  secured with OAuth 2.0 client-credentials via Microsoft Azure AD, that pairs and drives card machines (Move5000, PAX A920
  Pro) for Start-Transaction, Pairing, Split Bill & Gratuity, and Pay at Table flows. takepayments runs a real public developer
  portal at developer.takepayments.com but does not publish a downloadable OpenAPI/Swagger definition; its API reference is
  documentation-only, and merchant onboarding is sales-led rather than open self-serve.
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: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-02'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Payments
- United Kingdom
- Payment Gateway
- Payment Processing
- Card Payments
- Card Machines
- In-Person Payments
- E-Commerce
- PSP
- Acquiring
tags_raw:
- Payments
- United Kingdom
- Payment Gateway
- Payment Processing
- Card Payments
- Card Machines
- In-Person Payments
- Ecommerce
- PSP
- Acquiring
created: '2026-07-24'
modified: '2026-07-25'
specificationVersion: '0.23'
apis:
- aid: takepayments:takepayments-terminal-api
  name: takepayments Terminal API
  description: A REST/JSON API hosted on Azure API Management for pairing and driving takepayments card machines (Move5000,
    PAX A920 Pro) from an integrated app or POS. Documented operations include Authentication, Start a Transaction, Pairing
    a Terminal, Split Bill & Gratuity, and Pay at Table. Authentication is OAuth 2.0 client-credentials issued by Microsoft
    Azure AD, with the JWT passed as an Authorization Bearer header. Sandbox and production base URLs are published on the
    developer portal; no downloadable OpenAPI/Swagger is provided.
  humanURL: https://developer.takepayments.com/apis
  baseURL: https://takepayments-integrated-prod-apim.azure-api.net/
  tags:
  - Terminal API
  - In-Person Payments
  - Card Machines
  - Pay at Table
  - REST
  properties:
  - type: Documentation
    url: https://developer.takepayments.com/
  - type: APIReference
    url: https://developer.takepayments.com/apis
  - type: Authentication
    url: https://developer.takepayments.com/documentation/authentication
  - type: Documentation
    url: https://developer.takepayments.com/documentation/Start-Transaction
  - type: SDK
    url: https://developer.takepayments.com/online-sdk
common:
- type: DomainSecurity
  url: security/takepayments-domain-security.yml
- type: Website
  url: https://www.takepayments.com/
- type: DeveloperPortal
  url: https://developer.takepayments.com/
- type: Documentation
  url: https://www.takepayments.com/developer-support/
- type: APIReference
  url: https://developer.takepayments.com/apis
- type: SDK
  url: https://developer.takepayments.com/online-sdk
- type: Plugins
  url: https://www.takepayments.com/developer-support/shopping-carts/
- type: GitHubOrganization
  url: https://github.com/takepayments
- type: LinkedIn
  url: https://www.linkedin.com/company/takepayments-limited/
- type: Blog
  url: https://www.takepayments.com/blog/
- type: Support
  url: https://www.takepayments.com/partner-support/
- type: ContactUs
  url: https://www.takepayments.com/contact-us/
- type: TermsOfService
  url: https://www.takepayments.com/terms-and-conditions/
- type: PrivacyPolicy
  url: https://www.takepayments.com/privacy-policy/
- type: Pricing
  url: https://www.takepayments.com/card-machines/
- type: Authentication
  url: authentication/takepayments-authentication.yml
- type: WellKnown
  url: well-known/takepayments-well-known.yml
- type: Conventions
  url: conventions/takepayments-conventions.yml
- type: Sandbox
  url: sandbox/takepayments-sandbox.yml
- type: Packages
  url: packages/takepayments-packages.yml
- type: SDKs
  url: packages/takepayments-packages.yml
- type: Conformance
  url: conformance/takepayments-conformance.yml
- type: Compliance
  url: https://www.takepayments.com/pci-compliance/
- type: ErrorCatalog
  url: errors/takepayments-problem-types.yml
- type: Lifecycle
  url: lifecycle/takepayments-lifecycle.yml
- type: X-MCPServerCandidate
  url: mcp/takepayments-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/takepayments-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/takepayments"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/takepayments/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/takepayments/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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