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 2 APIs on the APIs.io network: Connect REST API and Connect-E REST API. 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.

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

56.7/100 developing ▬ flat Agent 71/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
3 APIs 1 MCP Servers
PaymentsUnited KingdomPayment GatewayPayment ProcessingCard PaymentsAcquiringPoint of SaleIn-Person Payments

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 56.7/100 · developing
Contract Quality 15.1 / 25
Developer Ergonomics 14.8 / 20
Commercial Clarity 10.5 / 20
Operational Transparency 4.8 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 71/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/paymentsense: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 3

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

Paymentsense Connect REST API

Cloud REST API for driving Paymentsense card terminals from EPOS software. Covers Pay-At-Counter (/pac) transactions and reports and Pay-At-Table (/pat) hospitality flows agains...

Paymentsense Connect-E REST API

OpenAPI 3.0 REST API for online / e-commerce card payments. Issues access-tokens, processes and resumes payments, runs cross-reference (repeat) payments, and lists supported pay...

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...

Arazzo Workflows 2

Multi-step API workflows described with the Arazzo specification.

_Index

ARAZZO

Paymentsense Pay-At-Counter — take a card payment

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

ARAZZO

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

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.

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

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

Source (apis.yml)

apis.yml Raw ↑
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.
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
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.19'
apis:
- aid: paymentsense:connect-rest-api
  name: Paymentsense Connect REST API
  description: Cloud REST API for driving Paymentsense card terminals from EPOS software. Covers Pay-At-Counter (/pac) transactions
    and reports and Pay-At-Table (/pat) hospitality flows against a per-merchant Connect host. Published in versions v0 (Swagger
    2.0, 3.0-beta), v1 (Swagger 2.0, 3.1) and v2 (OpenAPI 3.0, 3.2, current). Authenticates with HTTP Basic using the merchant
    API key as the password.
  humanURL: https://docs.connect.paymentsense.cloud/rest/api
  baseURL: https://your-host-here.connect.paymentsense.cloud
  tags:
  - Payments
  - Point of Sale
  - Card Payments
  - Pay At Table
  properties:
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/rest/getting-started
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/rest/api
  - type: OpenAPI
    url: openapi/paymentsense-connect-v2.json
  - type: OpenAPI
    url: openapi/paymentsense-connect-v1.json
  - type: OpenAPI
    url: openapi/paymentsense-connect-v0.json
  - 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: Arazzo
    name: Pay-At-Counter — take a card payment
    url: arazzo/paymentsense-pac-take-payment.yml
- aid: paymentsense:connect-e-rest-api
  name: Paymentsense Connect-E REST API
  description: OpenAPI 3.0 REST API for online / e-commerce card payments. Issues access-tokens, processes and resumes payments,
    runs cross-reference (repeat) payments, and lists supported payment methods against the Connect-E host (e.<host>.connect.paymentsense.cloud).
  humanURL: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  baseURL: https://e.test.connect.paymentsense.cloud
  tags:
  - Payments
  - Online Payments
  - Card Payments
  - E-Commerce
  properties:
  - type: Documentation
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: APIReference
    url: https://docs.connect.paymentsense.cloud/ConnectE/RestApi
  - type: OpenAPI
    url: openapi/paymentsense-connect-e-v0.json
  - type: Overlay
    url: overlays/paymentsense-connect-e-v0-overlay.yaml
  - type: Components
    url: components/paymentsense-components.yml
- 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
  - 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
common:
- 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: MCPServer
  url: mcp/paymentsense-mcp.yml
- 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