Trust Payments

Trust Payments is a London-headquartered payment gateway and processor (formerly Secure Trading / SecureTrading) operating across the United Kingdom, Europe, and the United States. It offers online, in-store point-of-sale, unattended, and mobile card acceptance, acquiring, alternative and local payment methods, tokenisation, recurring billing, payouts, and 3-D Secure authentication through its TRU Connect gateway. The developer surface centres on the Secure Trading Payment Platform (STPP) - a server-to-server JSON Webservices API for processing (AUTH, ACCOUNTCHECK, REFUND, SUBSCRIPTION, TRANSACTIONUPDATE, and TRANSACTIONQUERY), a JWT-authenticated client-side JavaScript Library for PCI-reduced hosted card fields, and mobile SDKs, all documented as reference articles in the Trust Payments help centre with Python, PHP, ReactJS, and Swift libraries published under the SecureTrading GitHub organisation. Trust Payments does not publish a downloadable OpenAPI/Swagger definition; production Webservices access requires PCI certification, account approval, and credential (key) exchange, so the surface is documentation-and-SDK driven rather than open self-serve.

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

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

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

🌐 Visit website 📡 Profile data on GitHub

49.1/100 developing ▬ flat Agent 23/100 agent aware Front door AI 1/6 silent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessEnterprise

2 APIs

Payments United Kingdom Payment Gateway Payment Processing Acquiring Card Payments Tokenization Subscription 3D Secure Point-of-Sale Webhook Payouts

Kin Score

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

Composite quality — 49.1/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 12.1 / 17

Access Clarity 7.8 / 17

Operational Transparency 2.9 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 5.9 / 15

Agent readiness — 23/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 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 0 / 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 3 / 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 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.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/trust-payments/"><img src="https://apis.io/badge/trust-payments/card.svg" alt="Trust Payments 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):

Contract Quality scores 39.0 — up to +15.3 composite points
Access Clarity scores 46.1 — up to +10.8 composite points
Contract Governance scores 18.2 — up to +9.8 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/trust-payments/apis.yml: open an issue on github.com/api-evangelist/trust-payments 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
MACH & Headless Commerce	builds-on	45.0	-	-
EU/EEA Payment and E-Money Institutions (PSD2 passports)	builds-on	45.0	-	-
E-commerce Extension Marketplaces (Adobe Commerce / Magento, Shopware)	builds-on	45.0	-	-

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.

3-D Secure

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

APIs 2

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

Trust Payments Webservices API

Server-to-server JSON API (the Secure Trading Payment Platform / STPP) for card processing and management on the TRU Connect gateway. Supports request types including AUTH, ACCO...

Trust Payments Payouts API

Payout / disbursement capability exposed through the Webservices API, used to send funds out (for example refunds beyond original transactions and supported payout flows) via th...

Trust Payments API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Trust Payments Plans Pricing

0 plans

PLANS

FinOps 1

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

Trust Payments Finops

FINOPS

Event Specifications 1

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

Trust Payments Webhooks

ASYNCAPI

Security Posture 2

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

Trust Payments Authentication

credentials/jwt · 2 schemes

SECURITY

Trust Payments Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

Login

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

Webhooks

Components

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

DeclineCodes

Packages

SDKs

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Compliance

Compliance

Operate 3

Status, limits, changes, and where to get help

StatusPage

StatusPage

HelpCenter

HelpCenter

Support

Support

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: trust-payments
url: https://raw.githubusercontent.com/api-evangelist/trust-payments/refs/heads/main/apis.yml
name: Trust Payments
kind: company
description: Trust Payments is a London-headquartered payment gateway and processor (formerly Secure Trading / SecureTrading)
  operating across the United Kingdom, Europe, and the United States. It offers online, in-store point-of-sale, unattended,
  and mobile card acceptance, acquiring, alternative and local payment methods, tokenisation, recurring billing, payouts,
  and 3-D Secure authentication through its TRU Connect gateway. The developer surface centres on the Secure Trading Payment
  Platform (STPP) - a server-to-server JSON Webservices API for processing (AUTH, ACCOUNTCHECK, REFUND, SUBSCRIPTION, TRANSACTIONUPDATE,
  and TRANSACTIONQUERY), a JWT-authenticated client-side JavaScript Library for PCI-reduced hosted card fields, and mobile
  SDKs, all documented as reference articles in the Trust Payments help centre with Python, PHP, ReactJS, and Swift libraries
  published under the SecureTrading GitHub organisation. Trust Payments does not publish a downloadable OpenAPI/Swagger definition;
  production Webservices access requires PCI certification, account approval, and credential (key) exchange, so the surface
  is documentation-and-SDK driven 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: 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
tags:
- Payments
- United Kingdom
- Payment Gateway
- Payment Processing
- Acquiring
- Card Payments
- Tokenization
- Subscription
- 3D Secure
- Point-of-Sale
- Webhook
- Payouts
tags_raw:
- Payments
- United Kingdom
- Payment Gateway
- Payment Processing
- Acquiring
- Card Payments
- Tokenization
- Subscriptions
- 3-D Secure
- Point of Sale
- Webhooks
- Payouts
created: '2026-07-24'
modified: '2026-07-25'
specificationVersion: '0.23'
apis:
- aid: trust-payments:webservices-api
  name: Trust Payments Webservices API
  description: Server-to-server JSON API (the Secure Trading Payment Platform / STPP) for card processing and management on
    the TRU Connect gateway. Supports request types including AUTH, ACCOUNTCHECK, REFUND, SUBSCRIPTION, TRANSACTIONUPDATE,
    and TRANSACTIONQUERY. Authenticated with a Webservices API alias (username) and password scoped to a site reference; production
    use requires PCI certification and credential exchange. No downloadable OpenAPI is published.
  humanURL: https://help.trustpayments.com/hc/en-us/sections/360005821218-Webservices-API
  baseURL: https://webservices.securetrading.net/json/
  tags:
  - Payments
  - Card Payments
  - Processing
  - Acquiring
  properties:
  - type: Documentation
    url: https://help.trustpayments.com/hc/en-us/sections/360005821218-Webservices-API
  - type: APIReference
    url: https://help.trustpayments.com/hc/en-us/articles/11569681677713-Webservices-API-Guide-for-POS-developers
  - type: Documentation
    url: https://help.trustpayments.com/hc/en-us/articles/4402754655761--Install-our-library
- aid: trust-payments:payouts-api
  name: Trust Payments Payouts API
  description: Payout / disbursement capability exposed through the Webservices API, used to send funds out (for example refunds
    beyond original transactions and supported payout flows) via the STPP JSON interface on the TRU Connect gateway. Same
    alias/password + site reference authentication as the core Webservices API.
  humanURL: https://help.trustpayments.com/hc/en-us/articles/4402771924497-Payouts-with-Webservices-API
  baseURL: https://webservices.securetrading.net/json/
  tags:
  - Payouts
  - Disbursements
  - Payments
  properties:
  - type: Documentation
    url: https://help.trustpayments.com/hc/en-us/articles/4402771924497-Payouts-with-Webservices-API
  - type: APIReference
    url: https://help.trustpayments.com/hc/en-us/sections/360005821218-Webservices-API
common:
- type: Plans
  url: plans/trust-payments-plans-pricing.yml
- type: DomainSecurity
  url: security/trust-payments-domain-security.yml
- type: Website
  url: https://www.trustpayments.com/
- type: Documentation
  url: https://help.trustpayments.com/hc/en-us
- type: APIReference
  url: https://help.trustpayments.com/hc/en-us/sections/360005821218-Webservices-API
- type: GitHubOrganization
  url: https://github.com/SecureTrading
- type: StatusPage
  url: https://status.trustpayments.com/
- type: Pricing
  url: https://www.trustpayments.com/pricing/
- type: Blog
  url: https://www.trustpayments.com/blog/
- type: HelpCenter
  url: https://help.trustpayments.com/hc/en-us
- type: Login
  url: https://myst.trustpayments.com/
- type: TermsOfService
  url: https://www.trustpayments.com/terms-of-use/
- type: PrivacyPolicy
  url: https://www.trustpayments.com/privacy-policy/
- type: DeveloperPortal
  url: https://www.trustpayments.com/developers/
- type: GettingStarted
  url: https://www.trustpayments.com/get-started/
- type: Support
  url: https://www.trustpayments.com/contact-us/
- type: Authentication
  url: authentication/trust-payments-authentication.yml
- type: Conventions
  url: conventions/trust-payments-conventions.yml
- type: ErrorCatalog
  url: errors/trust-payments-error-codes.yml
- type: DeclineCodes
  url: errors/trust-payments-decline-codes.yml
- type: Sandbox
  url: sandbox/trust-payments-sandbox.yml
- type: Lifecycle
  url: lifecycle/trust-payments-lifecycle.yml
- type: Conformance
  url: conformance/trust-payments-conformance.yml
- type: Compliance
  url: https://www.trustpayments.com/security/
- type: Webhooks
  url: asyncapi/trust-payments-webhooks.yml
- type: Packages
  url: packages/trust-payments-packages.yml
- type: SDKs
  url: packages/trust-payments-packages.yml
- type: Components
  url: components/trust-payments-components.yml
- type: LLMsTxt
  url: llms/trust-payments-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Trust Payments API — frequently asked questions

Does Trust Payments have an API?

Yes. APIs.io lists 2 APIs from Trust Payments, including Trust Payments Webservices API and Trust Payments Payouts API.

How do I authenticate with the Trust Payments API?

Trust Payments uses bearer-token authentication (credentials/jwt · 2 schemes). The details are profiled on APIs.io as Trust Payments Authentication.

Is the Trust Payments API ready for AI agents?

Trust Payments has a Kin Score of 49.1 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/trust-payments"

All providers

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

Every operation they expose

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

How their score was established

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