Cashflows website screenshot

Cashflows

Cashflows is a United Kingdom payment gateway and card acquirer, headquartered in London and a principal member of Visa and Mastercard, that helps businesses accept, process, and manage card payments across online, in-app, and in-person channels. Its product family spans a REST Cashflows Gateway (payment jobs, captures, refunds, tokenisation, recurring payments, and webhooks), hosted and embedded checkout, a cardholder-not-present Payments API with 3-D Secure, a Remote Authentication API for connecting to the acquiring network, and an In-Person Payments API served locally from Kinetic PCI-PTS terminals. Cashflows ships a genuine self-serve developer portal at developer.cashflows.com with reference documentation, a dedicated integration/sandbox environment, and webhook-based payment notifications, but it does not publish a downloadable OpenAPI/Swagger definition or a public Postman collection; its API reference is hand-authored HTML. Authentication is header-based (ConfigurationId plus a SHA-512 request hash for the Gateway, and auth_id/auth_pass for Remote Authentication) rather than OAuth.

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

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

Cashflows’ developer surface includes documentation, API reference, getting-started guide, pricing, engineering blog, support, authentication, and 24 more developer resources.

46.5/100 developing ▬ flat Agent 23/100 agent aware Front door AI 1/6 silent Heartbeat 50/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessEnterprise
4 APIs
PaymentsUnited KingdomPayment GatewayPayment ProcessingAcquiringCard PaymentsIn-Person Payments3D SecureRecurring PaymentsWebhook

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.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/.
Show this score on your site. Kin Score badge preview for Cashflows It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/cashflows/"><img src="https://apis.io/badge/cashflows/card.svg" alt="Cashflows 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
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • 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
9 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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/cashflows/apis.yml: open an issue on github.com/api-evangelist/cashflows 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.

MarketPositionDepthRegistered MCP serverDeclares compatibility
EU/EEA Payment and E-Money Institutions (PSD2 passports) regulated 9.6 (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.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 4

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

Cashflows Gateway API

REST API for creating and managing payment jobs and payments — create, retrieve, and cancel payment jobs; capture, refund, and cancel individual payments; card tokenisation; and...

Cashflows Payments API

REST/JSON API for cardholder-not-present card payments with 3-D Secure support — authorisation, capture, void, refund, credit, IIN lookup, and 3-D Secure version 2 authenticatio...

Cashflows Remote Authentication API

API for connecting directly to the Cashflows acquiring network to authorise card transactions, authenticated with auth_id (Profile/Merchant ID) and auth_pass credential headers.

Cashflows In-Person Payments API

Standalone REST API for PCI-PTS secure Kinetic payment devices, served locally from the terminal (default http://127.0.0.1:8080) under /api/v2 — device info, ping/status, settin...

Cashflows API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

FinOps 1

Cost, billing, and metering signals for API financial operations.

Event Specifications 1

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

Security Posture 2

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

Cashflows Authentication

apiKey/http-hash-signature/credential-pair · 3 schemes

SECURITY

Cashflows Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 4

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 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: cashflows
url: https://raw.githubusercontent.com/api-evangelist/cashflows/refs/heads/main/apis.yml
name: Cashflows
kind: company
description: Cashflows is a United Kingdom payment gateway and card acquirer, headquartered in London and a principal member
  of Visa and Mastercard, that helps businesses accept, process, and manage card payments across online, in-app, and in-person
  channels. Its product family spans a REST Cashflows Gateway (payment jobs, captures, refunds, tokenisation, recurring payments,
  and webhooks), hosted and embedded checkout, a cardholder-not-present Payments API with 3-D Secure, a Remote Authentication
  API for connecting to the acquiring network, and an In-Person Payments API served locally from Kinetic PCI-PTS terminals.
  Cashflows ships a genuine self-serve developer portal at developer.cashflows.com with reference documentation, a dedicated
  integration/sandbox environment, and webhook-based payment notifications, but it does not publish a downloadable OpenAPI/Swagger
  definition or a public Postman collection; its API reference is hand-authored HTML. Authentication is header-based (ConfigurationId
  plus a SHA-512 request hash for the Gateway, and auth_id/auth_pass for Remote Authentication) rather than OAuth.
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: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: medium
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
x-docs-platform: sphinx
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-21
tags:
- Payments
- United Kingdom
- Payment Gateway
- Payment Processing
- Acquiring
- Card Payments
- In-Person Payments
- 3D Secure
- Recurring Payments
- Webhook
tags_raw:
- Payments
- United Kingdom
- Payment Gateway
- Payment Processing
- Acquiring
- Card Payments
- In-Person Payments
- 3-D Secure
- Recurring Payments
- Webhooks
created: '2026-07-24'
modified: '2026-10-06'
specificationVersion: '0.23'
apis:
- aid: cashflows:cashflows-gateway-api
  name: Cashflows Gateway API
  description: REST API for creating and managing payment jobs and payments — create, retrieve, and cancel payment jobs; capture,
    refund, and cancel individual payments; card tokenisation; and recurring payments. Payment status changes are delivered
    asynchronously via webhook notifications (retried for up to a month) sent from Cashflows notification IPs.
  humanURL: https://developer.cashflows.com/api_reference/cashflows_gateway.html
  baseURL: https://gateway.cashflows.com/api/gateway
  tags:
  - Payments
  - Gateways
  - Webhook
  - Recurring Payments
  tags_raw:
  - Payments
  - Gateway
  - Webhooks
  - Recurring Payments
  properties:
  - type: Documentation
    url: https://developer.cashflows.com/gateway/cashflows_gateway.html
  - type: APIReference
    url: https://developer.cashflows.com/api_reference/cashflows_gateway.html
- aid: cashflows:cashflows-payments-api
  name: Cashflows Payments API
  description: REST/JSON API for cardholder-not-present card payments with 3-D Secure support — authorisation, capture, void,
    refund, credit, IIN lookup, and 3-D Secure version 2 authentication and verification flows.
  humanURL: https://developer.cashflows.com/api_reference/payments.html
  tags:
  - Payments
  - 3D Secure
  - Card Payments
  tags_raw:
  - Payments
  - 3-D Secure
  - Card Payments
  properties:
  - type: Documentation
    url: https://developer.cashflows.com/onlinepayments
  - type: APIReference
    url: https://developer.cashflows.com/api_reference/payments.html
- aid: cashflows:cashflows-remote-authentication-api
  name: Cashflows Remote Authentication API
  description: API for connecting directly to the Cashflows acquiring network to authorise card transactions, authenticated
    with auth_id (Profile/Merchant ID) and auth_pass credential headers.
  humanURL: https://developer.cashflows.com/api_reference/remote_auth_api.html
  baseURL: https://secure.cashflows.com/gateway/remote_auth
  tags:
  - Payments
  - Acquiring
  - Authorization
  properties:
  - type: APIReference
    url: https://developer.cashflows.com/api_reference/remote_auth_api.html
- aid: cashflows:cashflows-in-person-payments-api
  name: Cashflows In-Person Payments API
  description: Standalone REST API for PCI-PTS secure Kinetic payment devices, served locally from the terminal (default http://127.0.0.1:8080)
    under /api/v2 — device info, ping/status, settings, transactions, screens, receipts, and printing.
  humanURL: https://developer.cashflows.com/api_reference/ipp.html
  baseURL: http://127.0.0.1:8080/api/v2
  tags:
  - Payments
  - In-Person Payments
  - Terminal
  properties:
  - type: APIReference
    url: https://developer.cashflows.com/api_reference/ipp.html
common:
- type: Plans
  url: plans/cashflows-plans-pricing.yml
- url: https://www.cashflows.com/blog/rss.xml
  type: BlogRSS
- type: DomainSecurity
  url: security/cashflows-domain-security.yml
- type: Website
  url: https://www.cashflows.com/
- type: DeveloperPortal
  url: https://developer.cashflows.com/
- type: Documentation
  url: https://developer.cashflows.com/
- type: APIReference
  url: https://developer.cashflows.com/api_reference/api_reference_overview.html
- type: GettingStarted
  url: https://developer.cashflows.com/getting_started/getting_started.html
- type: StatusPage
  url: https://status.cashflows.com/
- type: Pricing
  url: https://www.cashflows.com/pricing
- type: Blog
  url: https://www.cashflows.com/blog
- type: Support
  url: https://www.cashflows.com/contact/support
- type: TermsOfService
  url: https://www.cashflows.com/legal/terms-and-conditions
- type: PrivacyPolicy
  url: https://www.cashflows.com/legal/privacy-policy
- type: Login
  url: https://portal.cashflows.com/
- type: GitHubOrganization
  url: https://github.com/cashflows
- type: Authentication
  url: authentication/cashflows-authentication.yml
- type: Conventions
  url: conventions/cashflows-conventions.yml
- type: ErrorCatalog
  url: errors/cashflows-problem-types.yml
- type: DeclineCodes
  url: errors/cashflows-decline-codes.yml
- type: Webhooks
  url: asyncapi/cashflows-gateway-webhooks.yml
- type: Packages
  url: packages/cashflows-packages.yml
- type: SDKs
  url: packages/cashflows-packages.yml
- type: Lifecycle
  url: lifecycle/cashflows-lifecycle.yml
- type: Sandbox
  url: sandbox/cashflows-sandbox.yml
- type: Components
  url: components/cashflows-components.yml
- type: Conformance
  url: conformance/cashflows-conformance.yml
- type: DataModel
  url: data-model/cashflows-data-model.yml
- type: WellKnown
  url: well-known/cashflows-well-known.yml
- type: X-MCPServerCandidate
  url: mcp/cashflows-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/cashflows-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Cashflows API — frequently asked questions

Does Cashflows have an API?

Yes. APIs.io lists 4 APIs from Cashflows, including Cashflows Gateway API, Cashflows Payments API and Cashflows Remote Authentication API, and 1 more.

How do I authenticate with the Cashflows API?

Cashflows uses bearer-token authentication (apiKey/http-hash-signature/credential-pair · 3 schemes). The details are profiled on APIs.io as Cashflows Authentication.

Is the Cashflows API ready for AI agents?

Cashflows has a Kin Score of 46.5 out of 100 (developing) and an Agent Readiness score of 22.7 (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/cashflows"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/cashflows/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/cashflows/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.

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