Tribe Payments
Tribe Payments is a London, United Kingdom-based payments technology company and issuer/acquirer processor that gives banks, acquirers, and fintechs a modular, API-driven platform to launch card and payment products without building core processing in-house. Built around its ISAAC processing engine, Tribe spans card issuing (issuer processing), merchant acquiring and a payment gateway, POS/SoftPOS terminal management, tokenization, fraud and risk monitoring, 3D Secure, digital wallets, Open Banking (PSD2 account-to-account payment initiation and account information), and Bank Connect / Banking-as-a-Service. Tribe positions itself as developer-led, publishing an extensive public API reference at doc.tribepayments.com; sandbox access is granted on request rather than through fully open self-service signup. Its home market is the United Kingdom, where PSD2/Open Banking and the Faster Payments and Bacs rails operated by Pay.UK anchor a dense cluster of API-native payment providers.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Tribe Payments the way a machine reads it — 20 machine-readable artifacts across 15 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 — Tribe Payments scores 51.0/100 (developing), with a separate agent-readiness read of 80/100 (agent native). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Tribe Payments
Each block below is one kind of artifact we hold for Tribe Payments. 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 15
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.
Payment Gateway - Credit Card API
Tribe Payments Gateway Credit Card API (v3) for merchants processing credit and debit card e-commerce (ECOM) transactions - sale, authorization, capture, refund, and void - orga...
Payment Gateway - Hosted Payments API (HPP)
Tribe Payments Gateway Hosted Payments Page API (v3) that lets merchants collect card payments through a Tribe-hosted checkout, offloading PCI scope, plus a webhook interface fo...
Payment Gateway - Credit Card Token API
Tribe Payments Gateway Credit Card Token API (v3) for tokenizing card credentials so merchants can store and reuse cards for recurring and card-on-file payments without holding ...
Payment Gateway - Reports API
Tribe Payments Gateway Reports API (v3) providing merchants programmatic access to transaction reporting and reconciliation data over REST, with a report callback interface for ...
Point of Sale - Device Directory API
Tribe Payments Point of Sale Device Directory API (v3) for registering, managing, and querying the estate of physical and SoftPOS payment terminals (devices) connected to Tribe'...
Risk Monitor - Client API
Tribe Payments Risk Monitor Client API (v1.1) for real-time fraud and transaction-risk monitoring, letting clients submit and query risk decisions, with a webhooks interface for...
Open Banking - Bank API
Tribe Payments Open Banking Bank API (v2) - the bank/ASPSP-facing side of Tribe's Open Banking product, exposing account information and payment-initiation capabilities to permi...
Open Banking - Third-Party Providers API (TPP)
Tribe Payments Open Banking Third-Party Providers (TPP) API (v2) - the TPP-facing side of Tribe's Open Banking product for initiating account-to-account payments (PIS) and retri...
Issuer Processor - Program Manager API (PM API)
Program Manager API (v1.2) for card issuers to interact with Tribe's ISAAC issuer-processing platform - issuing cards, managing programs and cardholders, and processing card tra...
Issuer Processor - Transaction Authorization Interface (TAI API)
Transaction Authorization Interface (v1.2) that sends webhook messages to issuers with the latest information about card-transaction status changes and system events on Tribe's ...
Acquiring Processor - Acquirer API (ACAPI)
Acquirer API (ACAPI, v1) for Tribe's acquiring-processor platform, covering acquirer-side transaction processing and settlement. Documented in the Tribe developer portal; no dow...
Acquiring Processor - Merchant API (MAPI)
Merchant API (MAPI, v1) for onboarding and managing merchants on Tribe's acquiring-processor platform. Documented in the Tribe developer portal as Markdown; no downloadable Open...
Acquiring Processor - Terminal API (TAPI)
Terminal API (TAPI, v2) for integrating physical payment terminals with Tribe's acquiring-processor platform. Documented in the Tribe developer portal; no downloadable OpenAPI i...
Acquiring Processor - Tokenization API (TOKAPI)
Tokenization API (TOKAPI, v1) for tokenizing card data within Tribe's acquiring-processor platform. Documented in the Tribe developer portal; no downloadable OpenAPI is publishe...
Bank Connect - Payment Services API
Payment Services API (v1) for Tribe's Bank Connect / Banking-as-a-Service product, enabling fintechs to embed banking and payment services. Documented in the Tribe developer por...
Scroll within the panel for all 15 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
tribe-payments-mcp.yml
MCP SERVEREvent 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.
Tribe Payments Webhooks
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 Tribe Payments — 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 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Access & Security 3
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/tribe-payments · machine-readable index on apis.io