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.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Paymentsense the way a machine reads it — 27 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Paymentsense scores 58.1/100 (strong), with a separate agent-readiness read of 30/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Paymentsense's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/paymentsense/"
title="Paymentsense on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/paymentsense.svg"
alt="Paymentsense Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/paymentsense/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/paymentsense/"
title="Paymentsense on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/paymentsense/card.svg"
alt="Paymentsense Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Paymentsense
Each block below is one kind of artifact we hold for Paymentsense. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
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 within the panel for all 18 ·
Open Collections 4
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Connect-E Development Environment
OPEN COLLECTIONConnect REST API
OPEN COLLECTIONConnect REST API
OPEN COLLECTIONConnect REST API
OPEN COLLECTIONArazzo Workflows 1
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
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.
ARAZZOEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Paymentsense Connect Events
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Paymentsense — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 4
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
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/paymentsense · machine-readable index on apis.io
This is an independent, third-party profile of Paymentsense, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.