TerraPay

TerraPay is a global cross-border payments and digital-wallet infrastructure company connecting banks, mobile wallets, money-transfer operators, merchants, and card networks into a single interoperable network for real-time international money movement. Its partner API Suite follows the GSMA Mobile Money API, exposing account validation, FX quotations, and multi-rail transactions (wallet, bank account, and card) across global remittance corridors, with compliance, monitoring, reconciliation, and reporting built into the platform. Partners authenticate with signed request headers over mutual TLS across Sandbox, UAT, and LIVE environments. Added to the API Evangelist network from the Partech portfolio and enriched from TerraPay's public developer portal.

TerraPay is listed with 1 API on the APIs.io network. Tagged areas include Company, Financial Services, Payments, Cross-Border Payments, and Remittances.

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

TerraPay’s developer surface includes documentation, API reference, getting-started guide, authentication, sandbox, and 12 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

27.5/100 thin ▬ flat Agent 26/100 agent aware Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

Company Financial Services Payments Cross-Border Payments Remittances Mobile Money Digital Wallet Money Transfer FintechGSMA Mobile Money API

Kin Score

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

Composite quality — 27.5/100 · thin

Contract Quality 8.3 / 21

Developer Ergonomics 8.1 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.9 / 11

Contract Governance 0.5 / 10

Discoverability 6.2 / 9

Regulatory Posture 2.3 / 15

Agent readiness — 26/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 9 / 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/terrapay/"><img src="https://apis.io/badge/terrapay/card.svg" alt="TerraPay 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
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
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 0.0 — up to +20.0 composite points
Contract Quality scores 39.0 — up to +15.3 composite points
Operational Transparency scores 7.9 — up to +12.0 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/terrapay/apis.yml: open an issue on github.com/api-evangelist/terrapay 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
African Payments (Nigeria, Kenya, South Africa, Ghana, WAEMU)	regulated	55.6	-	-
Canada RPAA Payment Service Providers (Bank of Canada registry + Payments Canada)	regulated	55.6	-	-

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.

APIs 1

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

TerraPay API Suite

GSMA Mobile Money API profile for account validation, FX quotations, and multi-rail money movement (wallet/bank/card) across international corridors.

Event Specifications 1

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

Terrapay Notifications Webhooks

ASYNCAPI

Security Posture 2

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

Terrapay Authentication

apiKey/custom-signed-headers/mutualTLS · 6 schemes

SECURITY

Terrapay Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

Conformance

Lifecycle

Webhooks

DataModel

Scroll for all 7

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: terrapay
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/terrapay.png
name: TerraPay
description: TerraPay is a global cross-border payments and digital-wallet infrastructure company connecting banks, mobile
  wallets, money-transfer operators, merchants, and card networks into a single interoperable network for real-time international
  money movement. Its partner API Suite follows the GSMA Mobile Money API, exposing account validation, FX quotations, and
  multi-rail transactions (wallet, bank account, and card) across global remittance corridors, with compliance, monitoring,
  reconciliation, and reporting built into the platform. Partners authenticate with signed request headers over mutual TLS
  across Sandbox, UAT, and LIVE environments. Added to the API Evangelist network from the Partech portfolio and enriched
  from TerraPay's public developer portal.
url: https://raw.githubusercontent.com/api-evangelist/terrapay/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- partech
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Financial Services
- Payments
- Cross-Border Payments
- Remittances
- Mobile Money
- Digital Wallet
- Money Transfer
- Fintech
- GSMA Mobile Money API
tags_raw:
- Company
- Financial Services
- Payments
- Cross-Border Payments
- Remittances
- Mobile Money
- Digital Wallets
- Money Transfer
- Fintech
- GSMA Mobile Money API
- Financial-Services
apis:
- name: TerraPay API Suite
  description: GSMA Mobile Money API profile for account validation, FX quotations, and multi-rail money movement (wallet/bank/card)
    across international corridors.
  humanURL: https://developers.terrapay.com/docs/
  baseURL: https://uat-connect.terrapay.com:21211
  tags:
  - Payments
  - Cross-Border Payments
  - Mobile Money
  properties:
  - type: Documentation
    url: https://developers.terrapay.com/docs/
  - type: APIReference
    url: https://developers.terrapay.com/apiReference.html
  - type: GettingStarted
    url: https://developers.terrapay.com/getStarted.html
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 11
  pass: local-v1
common:
- type: Website
  url: https://www.terrapay.com/
- type: DeveloperPortal
  url: https://developers.terrapay.com/
- type: Documentation
  url: https://developers.terrapay.com/docs/
- type: APIReference
  url: https://developers.terrapay.com/apiReference.html
- type: GettingStarted
  url: https://developers.terrapay.com/getStarted.html
- type: Authentication
  url: authentication/terrapay-authentication.yml
- type: Conventions
  url: conventions/terrapay-conventions.yml
- type: Idempotency
  url: conventions/terrapay-conventions.yml
- type: ErrorCatalog
  url: errors/terrapay-problem-types.yml
- type: Conformance
  url: conformance/terrapay-conformance.yml
- type: Lifecycle
  url: lifecycle/terrapay-lifecycle.yml
- type: X-MCPServerCandidate
  url: mcp/terrapay-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/terrapay-llms.txt
- type: Sandbox
  url: sandbox/terrapay-sandbox.yml
- type: Webhooks
  url: asyncapi/terrapay-notifications-webhooks.yml
- type: DataModel
  url: data-model/terrapay-data-model.yml
- type: DomainSecurity
  url: security/terrapay-domain-security.yml

TerraPay API — frequently asked questions

Does TerraPay have an API?

Yes. APIs.io lists 1 API from TerraPay, including TerraPay API Suite.

How do I authenticate with the TerraPay API?

TerraPay uses bearer-token authentication (apiKey/custom-signed-headers/mutualTLS · 6 schemes). The details are profiled on APIs.io as Terrapay Authentication.

Is the TerraPay API ready for AI agents?

TerraPay has a Kin Score of 27.5 out of 100 (thin) and an Agent Readiness score of 25.9 (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/terrapay"

All providers

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

Every operation they expose

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

How their score was established

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