Paymentsense

Paymentsense is a United Kingdom payment processing company that provides card payment acceptance to small and medium-sized businesses through card machines (PDQ terminals), online payment gateways, and EPOS integrations. Now part of Dojo, its developer-facing surface centers on the Connect platform, a cloud-hosted integration layer that gives each merchant an isolated host so point-of-sale and hospitality software can drive card terminals without touching card data. Paymentsense publishes a genuine public developer portal at docs.connect.paymentsense.cloud with interactive Swagger reference docs and downloadable OpenAPI/Swagger specifications for the Connect REST API (Pay-At-Counter and Pay-At-Table terminal integration, versions v0/v1/v2) and the Connect-E REST API for online/e-commerce card payments, plus a documented WebSockets interface. Authentication is HTTP Basic using a per-merchant API key supplied by Paymentsense. A separate merchant/software-house management portal at developers.paymentsense.com sits behind Google sign-in.

Paymentsense publishes 18 API contracts indexed on the APIs.io network, including Access Token API, Cross Reference Payment API, Hospitality Reports API, and 15 more. Tagged areas include Payments, United Kingdom, Payment Gateway, Payment Processing, and Card Payments.

The Paymentsense catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Paymentsense’s developer surface includes authentication, sandbox, changelog, documentation, API reference, getting-started guide, pricing, and 29 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

65.2/100 strong ▬ flat Agent 27/100 agent aware Front door AI 1/6 silent Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaid

4 published contracts 3 Agent Skills

Payments United Kingdom Payment Gateway Payment Processing Card Payments Acquiring Point-of-Sale In-Person Payments

Kin Score

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

Composite quality — 65.2/100 · strong

Contract Quality 11.6 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 12.8 / 15

Operational Transparency 4.1 / 10

Contract Governance 2.9 / 9

Discoverability 5.9 / 8

Regulatory Posture 5.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 27/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 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 0 / 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/paymentsense/"><img src="https://apis.io/badge/paymentsense/card.svg" alt="Paymentsense 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
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)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

6 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 61.9 — up to +9.5 composite points
Contract Governance scores 31.8 — up to +8.2 composite points
Operational Transparency scores 42.1 — up to +7.5 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/paymentsense/apis.yml: open an issue on github.com/api-evangelist/paymentsense 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
UK G-Cloud Suppliers (UK public-sector cloud procurement)	regulated	18.3 (thin)	-	-
EU/EEA Payment and E-Money Institutions (PSD2 passports)	regulated	18.3 (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.

OpenAPI

measured — observed by APIs.io (published)

APIs 18

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

Paymentsense Connect WebSockets API

Documented WebSockets interface for the Connect platform, offering an event-driven alternative to the REST API for terminal integration. No downloadable OpenAPI/AsyncAPI specifi...

Paymentsense Access Token API

The Access Token API from Paymentsense — 1 operation(s) for access token.

Paymentsense Cross Reference Payment API

The Cross Reference Payment API from Paymentsense — 1 operation(s) for cross reference payment.

Paymentsense Hospitality Reports API

The Hospitality Reports API from Paymentsense — 2 operation(s) for hospitality reports.

Paymentsense Hospitality Tables API

The Hospitality Tables API from Paymentsense — 6 operation(s) for hospitality tables.

Paymentsense PAC Reports API

The PAC Reports API from Paymentsense — 2 operation(s) for pac reports.

Paymentsense PAC Reports (Ingenico Only) API

The PAC Reports (Ingenico Only) API from Paymentsense — 2 operation(s) for pac reports (ingenico only).

Paymentsense PAC Terminals API

The PAC Terminals API from Paymentsense — 3 operation(s) for pac terminals.

Paymentsense PAC Transactions API

The PAC Transactions API from Paymentsense — 6 operation(s) for pac transactions.

Paymentsense PAT Reports API

The PAT Reports API from Paymentsense — 2 operation(s) for pat reports.

Paymentsense PAT Tables API

The PAT Tables API from Paymentsense — 6 operation(s) for pat tables.

Paymentsense Payment Details API

The Payment Details API from Paymentsense — 1 operation(s) for payment details.

Paymentsense Payment Methods API

The Payment Methods API from Paymentsense — 1 operation(s) for payment methods.

Paymentsense Resume Payment API

The Resume Payment API from Paymentsense — 1 operation(s) for resume payment.

Paymentsense Retail Reports API

The Retail Reports API from Paymentsense — 2 operation(s) for retail reports.

Paymentsense Retail Terminals API

The Retail Terminals API from Paymentsense — 2 operation(s) for retail terminals.

Paymentsense Retail Transactions API

The Retail Transactions API from Paymentsense — 3 operation(s) for retail transactions.

Paymentsense Revoke Access Token API

The Revoke Access Token API from Paymentsense — 1 operation(s) for revoke access token.

Scroll for all 18

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Connect-E Development Environment

OPEN COLLECTION

Connect REST API

OPEN COLLECTION

Connect REST API

OPEN COLLECTION

Connect REST API

OPEN COLLECTION

Arazzo Workflows 1

Multi-step API workflows described with the Arazzo specification.

Paymentsense Pay-At-Counter — take a card payment

List a terminal, start a card transaction on it, and poll to the outcome.

ARAZZO

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Take an online card payment with Connect-E

AGENT SKILL

Run a Pay-At-Table hospitality flow

AGENT SKILL

Take a Pay-At-Counter card payment

AGENT SKILL

Paymentsense API pricing

Prices published by Paymentsense, read 2026-10-28 from www.paymentsense.com/uk/pricing/.

Plan	Price
MasterCard/Visa UK debit & credit – in person / online	1.40% per transaction
MasterCard/Visa UK business card – in person / online	1.99% per transaction
Phone – debit	1.40% + 50p per transaction
Phone – credit	1.90% per transaction
Phone – business	2.49% per transaction
Authorisation fee	5p per transaction
Chargeback fee	£28.00 per chargeback
Refund fee	50p per refund

All 15 plans, limits and sources →

Billed by: transaction · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

Paymentsense Plans Pricing

15 plans

PLANS

Paymentsense Price Estimates

0 plans

PLANS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Paymentsense

SLA

FinOps 1

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

Paymentsense Finops

FINOPS

Event Specifications 1

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

Paymentsense Connect Events

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Paymentsense API Rules

45 rules · 35 errors 9 warnings 1 info

SPECTRAL

OpenAPI Overlays 4

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Paymentsense Connect E V0 Overlay

1 action · update · paymentsense-connect-e-v0.json

DERIVED

Paymentsense Connect V0 Overlay

1 action · update · paymentsense-connect-v0.json

DERIVED

Paymentsense Connect V1 Overlay

1 action · update · paymentsense-connect-v1.json

DERIVED

Paymentsense Connect V2 Overlay

1 action · update · paymentsense-connect-v2.json

DERIVED

Security Posture 2

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

Paymentsense Authentication

apiKey/http · 3 schemes

SECURITY

Paymentsense Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Paymentsense Agentic Access

50 operations · 28 acting · 1 human-in-the-loop

50 operations · 28 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Sandbox

Sandbox

Login

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

DataModel

Conformance

Lifecycle

Build 3

SDKs, sample code, and the tooling you integrate with

Packages

Packages

ToolCrosswalk

ToolCrosswalk

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Compliance

Compliance

Operate 4

Status, limits, changes, and where to get help

StatusPage

ChangeLog

ChangeLog

HelpCenter

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Other 4

Properties that don't map to a standard resource type

Overlay

Overlay

Overlay

Overlay

Source (apis.yml)

aid: paymentsense
url: https://raw.githubusercontent.com/api-evangelist/paymentsense/refs/heads/main/apis.yml
name: Paymentsense
kind: company
description: Paymentsense is a United Kingdom payment processing company that provides card payment acceptance to small and
  medium-sized businesses through card machines (PDQ terminals), online payment gateways, and EPOS integrations. Now part
  of Dojo, its developer-facing surface centers on the Connect platform, a cloud-hosted integration layer that gives each
  merchant an isolated host so point-of-sale and hospitality software can drive card terminals without touching card data.
  Paymentsense publishes a genuine public developer portal at docs.connect.paymentsense.cloud with interactive Swagger reference
  docs and downloadable OpenAPI/Swagger specifications for the Connect REST API (Pay-At-Counter and Pay-At-Table terminal
  integration, versions v0/v1/v2) and the Connect-E REST API for online/e-commerce card payments, plus a documented WebSockets
  interface. Authentication is HTTP Basic using a per-merchant API key supplied by Paymentsense. A separate merchant/software-house
  management portal at developers.paymentsense.com sits behind Google sign-in.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: high
  source:
  - plans
  - 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
- Card Payments
- Acquiring
- Point-of-Sale
- In-Person Payments
tags_raw:
- Payments
- United Kingdom
- Payment Gateway
- Payment Processing
- Card Payments
- Acquiring
- Point of Sale
- In-Person Payments
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.23'
apis:
- aid: paymentsense:connect-websockets-api
  name: Paymentsense Connect WebSockets API
  description: Documented WebSockets interface for the Connect platform, offering an event-driven alternative to the REST
    API for terminal integration. No downloadable OpenAPI/AsyncAPI specification is published; only reference documentation
    is available.
  humanURL: https://docs.connect.paymentsense.cloud/websockets/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Payments
  - WebSocket
  - Point-of-Sale
  tags_raw:
  - Payments
  - WebSockets
  - Point of Sale
  properties:
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/websockets/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/websockets/api
  - type: Webhooks
    url: asyncapi/paymentsense-connect-events.yml
- aid: paymentsense:paymentsense-access-token-api
  name: Paymentsense Access Token API
  description: The Access Token API from Paymentsense — 1 operation(s) for access token.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Access Token
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-access-token-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-cross-reference-payment-api
  name: Paymentsense Cross Reference Payment API
  description: The Cross Reference Payment API from Paymentsense — 1 operation(s) for cross reference payment.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Cross Reference Payment
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-cross-reference-payment-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-hospitality-reports-api
  name: Paymentsense Hospitality Reports API
  description: The Hospitality Reports API from Paymentsense — 2 operation(s) for hospitality reports.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Hospitality Reports
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-hospitality-reports-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-hospitality-tables-api
  name: Paymentsense Hospitality Tables API
  description: The Hospitality Tables API from Paymentsense — 6 operation(s) for hospitality tables.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Hospitality Tables
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-hospitality-tables-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-pac-reports-api
  name: Paymentsense PAC Reports API
  description: The PAC Reports API from Paymentsense — 2 operation(s) for pac reports.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - PAC Reports
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-pac-reports-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-pac-reports-ingenico-only-api
  name: Paymentsense PAC Reports (Ingenico Only) API
  description: The PAC Reports (Ingenico Only) API from Paymentsense — 2 operation(s) for pac reports (ingenico only).
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - PAC Reports (Ingenico Only)
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-pac-reports-ingenico-only-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-pac-terminals-api
  name: Paymentsense PAC Terminals API
  description: The PAC Terminals API from Paymentsense — 3 operation(s) for pac terminals.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - PAC Terminals
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-pac-terminals-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-pac-transactions-api
  name: Paymentsense PAC Transactions API
  description: The PAC Transactions API from Paymentsense — 6 operation(s) for pac transactions.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - PAC Transactions
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-pac-transactions-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-pat-reports-api
  name: Paymentsense PAT Reports API
  description: The PAT Reports API from Paymentsense — 2 operation(s) for pat reports.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - PAT Reports
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-pat-reports-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-pat-tables-api
  name: Paymentsense PAT Tables API
  description: The PAT Tables API from Paymentsense — 6 operation(s) for pat tables.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - PAT Tables
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-pat-tables-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-payment-details-api
  name: Paymentsense Payment Details API
  description: The Payment Details API from Paymentsense — 1 operation(s) for payment details.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Payment Details
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-payment-details-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-payment-methods-api
  name: Paymentsense Payment Methods API
  description: The Payment Methods API from Paymentsense — 1 operation(s) for payment methods.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Payment Methods
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-payment-methods-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-resume-payment-api
  name: Paymentsense Resume Payment API
  description: The Resume Payment API from Paymentsense — 1 operation(s) for resume payment.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Resume Payment
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-resume-payment-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-retail-reports-api
  name: Paymentsense Retail Reports API
  description: The Retail Reports API from Paymentsense — 2 operation(s) for retail reports.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Retail Reports
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-retail-reports-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-retail-terminals-api
  name: Paymentsense Retail Terminals API
  description: The Retail Terminals API from Paymentsense — 2 operation(s) for retail terminals.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Retail Terminals
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-retail-terminals-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-retail-transactions-api
  name: Paymentsense Retail Transactions API
  description: The Retail Transactions API from Paymentsense — 3 operation(s) for retail transactions.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Retail Transactions
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-retail-transactions-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
- aid: paymentsense:paymentsense-revoke-access-token-api
  name: Paymentsense Revoke Access Token API
  description: The Revoke Access Token API from Paymentsense — 1 operation(s) for revoke access token.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Revoke Access Token
  properties:
  - type: OpenAPI
    url: openapi/paymentsense-revoke-access-token-api-openapi.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: Arazzo
    url: arazzo/paymentsense-pac-take-payment.yml
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: Components
    url: components/paymentsense-components.yml
common:
- type: Plans
  url: plans/paymentsense-plans-pricing.yml
- type: Overlay
  url: overlays/paymentsense-connect-v2-overlay.yaml
- type: Overlay
  url: overlays/paymentsense-connect-v1-overlay.yaml
- type: Overlay
  url: overlays/paymentsense-connect-v0-overlay.yaml
- type: Overlay
  url: overlays/paymentsense-connect-e-v0-overlay.yaml
- type: DomainSecurity
  url: security/paymentsense-domain-security.yml
- type: AgenticAccess
  url: agentic-access/paymentsense-agentic-access.yml
- type: Authentication
  url: authentication/paymentsense-authentication.yml
- type: Packages
  url: packages/paymentsense-packages.yml
- type: X-MCPServerCandidate
  url: mcp/paymentsense-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: ToolCrosswalk
  url: mcp/paymentsense-tool-crosswalk.yml
- type: LLMsTxt
  url: llms/paymentsense-llms.txt
- type: Conventions
  url: conventions/paymentsense-conventions.yml
- type: ErrorCatalog
  url: errors/paymentsense-problem-types.yml
- type: DataModel
  url: data-model/paymentsense-data-model.yml
- type: Conformance
  url: conformance/paymentsense-conformance.yml
- type: Compliance
  url: https://dojo.tech/articles/what-is-pci-compliance/
- type: Sandbox
  url: sandbox/paymentsense-sandbox.yml
- type: Lifecycle
  url: lifecycle/paymentsense-lifecycle.yml
- type: StatusPage
  url: https://status.paymentsense.com/
- type: ChangeLog
  url: changelog/paymentsense-changelog.yml
- type: ChangeLog
  url: https://docs.connect.paymentsense.cloud/rest/changelog
- type: AgentSkill
  url: skills/_index.yml
- type: Login
  url: https://developers.paymentsense.com
- type: Website
  url: https://www.paymentsense.com/uk/
- type: DeveloperPortal
  url: https://docs.connect.paymentsense.cloud/
- type: Documentation
  url: https://docs.connect.paymentsense.cloud/
- type: APIReference
  url: https://docs.connect.paymentsense.cloud/rest/api
- type: GettingStarted
  url: https://docs.connect.paymentsense.cloud/rest/getting-started
- type: GitHubOrganization
  url: https://github.com/Paymentsense-DevSupport
- type: Pricing
  url: https://www.paymentsense.com/uk/pricing/
- type: Blog
  url: https://www.paymentsense.com/uk/blog/
- type: HelpCenter
  url: https://support.paymentsense.com/hc/en-us
- type: TermsOfService
  url: https://www.paymentsense.com/uk/legal/terms/
- type: PrivacyPolicy
  url: https://www.paymentsense.com/uk/legal/privacy/
- type: LinkedIn
  url: https://www.linkedin.com/company/paymentsense/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Paymentsense API — frequently asked questions

Does Paymentsense have an API?

Yes. APIs.io lists 18 APIs from Paymentsense, including Paymentsense Connect WebSockets API, Paymentsense Access Token API and Paymentsense Cross Reference Payment API, and 15 more.

Is there an OpenAPI specification for the Paymentsense API?

Yes. APIs.io indexes 17 OpenAPI specifications for Paymentsense, each linked for download from this page.

How do I authenticate with the Paymentsense API?

Paymentsense uses bearer-token authentication (apiKey/http · 3 schemes). The details are profiled on APIs.io as Paymentsense Authentication.

How much does the Paymentsense API cost?

Paymentsense publishes its prices; its MasterCard/Visa UK debit & credit – in person / online plan is 1.40% per transaction as of 2026-10-28. APIs.io lists 15 pricing plans for Paymentsense, with each plan's price, limits and inclusions under Pricing on this page.

Is the Paymentsense API ready for AI agents?

Paymentsense has a Kin Score of 65.2 out of 100 (strong) and an Agent Readiness score of 26.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/paymentsense"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/paymentsense/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.