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 — 64 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 42.8/100 (developing), with a separate agent-readiness read of 36/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 Tribe Payments'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/tribe-payments/"
title="Tribe Payments on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tribe-payments.svg"
alt="Tribe Payments Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/tribe-payments/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tribe-payments/"
title="Tribe Payments on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tribe-payments/card.svg"
alt="Tribe Payments 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 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 45
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.
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...
Tribe Payments 3DS authentication required API
The 3DS authentication required API from Tribe Payments — 1 operation(s) for 3ds authentication required.
Tribe Payments Account API
Endpoints for confirming funds in the account.
Tribe Payments Accounts API
The Accounts API from Tribe Payments — 4 operation(s) for accounts.
Tribe Payments App API
The App API from Tribe Payments — 4 operation(s) for app.
Tribe Payments Authorization API
The Authorization API from Tribe Payments — 3 operation(s) for authorization.
Tribe Payments Authorize API
The Authorize API from Tribe Payments — 2 operation(s) for authorize.
Tribe Payments Bulk payments API
Endpoints for executing bulk payments.
Tribe Payments Cancel API
The Cancel API from Tribe Payments — 2 operation(s) for cancel.
Tribe Payments Cancel recurring API
The Cancel recurring API from Tribe Payments — 2 operation(s) for cancel recurring.
Tribe Payments Capture API
The Capture API from Tribe Payments — 2 operation(s) for capture.
Tribe Payments Credit API
The Credit API from Tribe Payments — 2 operation(s) for credit.
Tribe Payments Direct payments API
Some supported ASPSPs provide a more direct approach to some actions. Instead of retrieving prior user consent, actions can be executed directly, followed by an SCA confirmation...
Tribe Payments Direct payments without Bank API
Endpoints for executing direct payments (without acquiring previous consent).
Tribe Payments Disputes API
The Disputes API from Tribe Payments — 2 operation(s) for disputes.
Tribe Payments Event Data API
The Event Data API from Tribe Payments — 6 operation(s) for event data.
Tribe Payments Funds API
The Funds API from Tribe Payments — 1 operation(s) for funds.
Tribe Payments Funds confirmation API
Endpoints for confirming funds in the account.
Tribe Payments General API
Endpoints for interacting with the general data.
Tribe Payments Health Check API
The Health Check API from Tribe Payments — 1 operation(s) for health check.
Tribe Payments Host API
The Host API from Tribe Payments — 5 operation(s) for host.
Tribe Payments Incremental authorize API
The Incremental authorize API from Tribe Payments — 2 operation(s) for incremental authorize.
Tribe Payments Order status API
The Order status API from Tribe Payments — 2 operation(s) for order status.
Tribe Payments P2 P API
The P2P API from Tribe Payments — 2 operation(s) for p2p.
Tribe Payments Payment API
The Payment API from Tribe Payments — 4 operation(s) for payment.
Tribe Payments Payments API
The Payments API from Tribe Payments — 7 operation(s) for payments.
Tribe Payments Performance API
The Performance API from Tribe Payments — 1 operation(s) for performance.
Tribe Payments Pre authorize API
The Pre authorize API from Tribe Payments — 2 operation(s) for pre authorize.
Tribe Payments Prepare API
The Prepare API from Tribe Payments — 1 operation(s) for prepare.
Tribe Payments Prepare error API
The Prepare error API from Tribe Payments — 1 operation(s) for prepare error.
Tribe Payments Prepare success API
The Prepare success API from Tribe Payments — 1 operation(s) for prepare success.
Tribe Payments Process API
The Process API from Tribe Payments — 2 operation(s) for process.
Tribe Payments Processing accounts API
The Processing accounts API from Tribe Payments — 2 operation(s) for processing accounts.
Tribe Payments Processor API
The Processor API from Tribe Payments — 5 operation(s) for processor.
Tribe Payments Refund API
The Refund API from Tribe Payments — 2 operation(s) for refund.
Tribe Payments Sale API
The Sale API from Tribe Payments — 2 operation(s) for sale.
Tribe Payments Status API
The Status API from Tribe Payments — 1 operation(s) for status.
Tribe Payments Transactions API
The Transactions API from Tribe Payments — 2 operation(s) for transactions.
Tribe Payments User Actions Trigger API
The User Actions Trigger API from Tribe Payments — 1 operation(s) for user actions trigger.
Scroll within the panel for all 45 ·
Open Collections 15
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).
Bank Webhooks API
OPEN COLLECTIONOpen Banking: Bank API
OPEN COLLECTIONPayment Webhooks
OPEN COLLECTIONOpen Banking: TPP API v2
OPEN COLLECTIONMerchant API Credit Card Callback
OPEN COLLECTIONMerchant API Credit Card
OPEN COLLECTIONMerchant API Credit Card Token
OPEN COLLECTIONMerchant API Credit Card Token Webhook
OPEN COLLECTIONMerchant API HPP
OPEN COLLECTIONMerchant API HPP Webhook
OPEN COLLECTIONDevice Directory API
OPEN COLLECTIONMerchant API
OPEN COLLECTIONMerchant API Report
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONScroll within the panel for all 15 ·
Event 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 2
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
This is an independent, third-party profile of Tribe Payments, 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.