# Tribe Payments

**Canonical:** https://apis.io/providers/tribe-payments/  
**Website:** https://www.tribepayments.com/  
**APIs profiled:** 15

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.

## Kin Score — 46.1 / 100 (developing)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 46.1).

| Facet | Score |
|---|---|
| Discoverability | 72.2 |
| Contract Quality | 54.9 |
| Governance | 30.3 |
| Contract Governance | 30.3 |
| Operational Transparency | 39.5 |
| Developer Ergonomics | 28.0 |
| Commercial Clarity | 31.6 |
| Access Clarity | 31.6 |

Regulatory layer — **Payments**: 62.5 (matched via tags).

## Agent readiness — 48.0 (agent-native)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | derived |
| Reversibility Documented | documented |
| MCP Server | no |
| Auth Clarity | yes |
| Idempotency | verified |
| Error Semantics | verified |
| OpenAPI Examples | partial |
| Rate Limit Signal | no |
| Event Surface Described | derived |
| Agent Skills | derived |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## APIs (15)

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

## MCP servers (1)

- **Tribe Payments MCP Server**

## Agentic access (1)

- **Tribe Payments Agentic Access** — 104 operations · 78 acting · 1 human-in-the-loop

## Security (2)

- **Tribe Payments Authentication** — apiKey/http · 8 schemes
- **Tribe Payments Domain Security** — TLSv1.3 · HSTS · DMARC

## Tags

Payments, United Kingdom, Issuer Processor, Card Issuing, Acquiring, Payment Gateway, Payment Processing, Open Banking, Account-to-Account, Banking as a Service, Fraud, Point-of-Sale

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/tribe-payments/). Scores are computed from the provider's own public artifacts under a published rubric.
