Paysend

Paysend is a London-headquartered global fintech, founded in 2017, building a cross-border digital payments network that moves money to bank accounts, cards, and wallets across 170+ countries in 40+ currencies for more than 11 million consumers and a growing base of enterprise clients. Alongside its consumer money-transfer app, Paysend operates Paysend Enterprise, a business-facing payments platform whose developer surface is a single Payout API: one integration disburses funds worldwide to cards and accounts, with FX rate lookups, bank and card tokenization utilities, partner statements, and balance queries. The API is a partner-provisioned, enterprise integration (United Kingdom home market) rather than a fully public self-serve product — authentication is API key plus HMAC digital signature (X-OPP-Signature), requests are idempotent via a request id and date, and payout status is delivered through configurable webhook notifications. Paysend documents this surface openly on a Docusaurus developer portal with a sandbox mock service, but does not publish a downloadable OpenAPI/Swagger definition or a public base URL.

Paysend publishes 1 API on the APIs.io network. Tagged areas include Payments, United Kingdom, Cross-Border, Money Transfer, and Payouts.

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

Paysend’s developer surface includes documentation, API reference, authentication, engineering blog, getting-started guide, support, sandbox, and 14 more developer resources.

36.1/100 thin ▬ flat Agent 43/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
1 APIs 1 MCP Servers
PaymentsUnited KingdomCross-BorderMoney TransferPayoutsPayment ProcessingFXRemittanceFintech

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 36.1/100 · thin
Contract Quality 5.7 / 25
Developer Ergonomics 13.5 / 20
Commercial Clarity 3.7 / 20
Operational Transparency 1.7 / 13
Governance 0.0 / 12
Discoverability 8.0 / 10
Agent readiness — 43/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/paysend: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

Paysend Enterprise Payout API

Paysend Enterprise's single Payout API disburses funds worldwide to cards and bank accounts through the Paysend payments network. A multi-task POST /processing endpoint carries ...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

paysend-mcp.yml

MCP SERVER

Event Specifications 1

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

Security Posture 2

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

Paysend Authentication

apiKey/hmac-signature · 2 schemes

SECURITY

Paysend Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: paysend
url: https://raw.githubusercontent.com/api-evangelist/paysend/refs/heads/main/apis.yml
name: Paysend
kind: company
description: 'Paysend is a London-headquartered global fintech, founded in 2017, building a cross-border digital payments
  network that moves money to bank accounts, cards, and wallets across 170+ countries in 40+ currencies for more than 11 million
  consumers and a growing base of enterprise clients. Alongside its consumer money-transfer app, Paysend operates Paysend
  Enterprise, a business-facing payments platform whose developer surface is a single Payout API: one integration disburses
  funds worldwide to cards and accounts, with FX rate lookups, bank and card tokenization utilities, partner statements, and
  balance queries. The API is a partner-provisioned, enterprise integration (United Kingdom home market) rather than a fully
  public self-serve product — authentication is API key plus HMAC digital signature (X-OPP-Signature), requests are idempotent
  via a request id and date, and payout status is delivered through configurable webhook notifications. Paysend documents
  this surface openly on a Docusaurus developer portal with a sandbox mock service, but does not publish a downloadable OpenAPI/Swagger
  definition or a public base URL.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Payments
- United Kingdom
- Cross-Border
- Money Transfer
- Payouts
- Payment Processing
- FX
- Remittance
- Fintech
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.19'
apis:
- aid: paysend:paysend-enterprise-payout-api
  name: Paysend Enterprise Payout API
  description: Paysend Enterprise's single Payout API disburses funds worldwide to cards and bank accounts through the Paysend
    payments network. A multi-task POST /processing endpoint carries operations including pay.toCard, pay.toAccount, fx.rateGet
    / fx.rateGet.p2a, bank.get / bank.search, card.createToken / card.infoGet, partner.statementGet, getBalance, and task.statusGet,
    with a companion GET /processing/status/ for status retrieval. Authentication is API key plus HMAC digital signature (X-OPP-Signature,
    SHA-256/512); requests are made idempotent via header.request.id and header.request.date, and payment outcomes are pushed
    to configurable webhook notification URLs. A sandbox mock service is provided. No downloadable OpenAPI specification or
    public base URL is published; the surface is partner-provisioned.
  humanURL: https://developer.paysend.com/product-overview/
  tags:
  - Payouts
  - Cross-Border
  - FX
  - Payments
  properties:
  - type: Documentation
    url: https://developer.paysend.com/product-overview/
  - type: APIReference
    url: https://developer.paysend.com/endpoints/get-processing-status/
  - type: Authentication
    url: https://developer.paysend.com/authentication-and-idempotency/
  - type: Webhooks
    url: https://developer.paysend.com/webhook-notification-service/
common:
- type: DomainSecurity
  url: security/paysend-domain-security.yml
- type: Website
  url: https://paysend.com/
- type: DeveloperPortal
  url: https://developer.paysend.com/
- type: Documentation
  url: https://developer.paysend.com/product-overview/
- type: APIReference
  url: https://developer.paysend.com/endpoints/get-processing-status/
- type: Authentication
  url: https://developer.paysend.com/authentication-and-idempotency/
- type: GitHubOrganization
  url: https://github.com/paysend
- type: Blog
  url: https://paysend.com/blog
- type: PrivacyPolicy
  url: https://cloud.paysend.com/web/docs/Global_Privacy_Policy_Paysend.pdf
- type: Product
  url: https://paysend.com/enterprise
- type: GettingStarted
  url: https://developer.paysend.com/
- type: Support
  url: https://help.paysend.com/hc/en-us
- type: Compliance
  url: https://paysend.com/en/blog/paysend-compliance-security-digital-money-transfers
- type: Conventions
  url: conventions/paysend-conventions.yml
- type: Idempotency
  url: conventions/paysend-conventions.yml
- type: ErrorCatalog
  url: errors/paysend-error-codes.yml
- type: Sandbox
  url: sandbox/paysend-sandbox.yml
- type: Webhooks
  url: asyncapi/paysend-webhooks.yml
- type: Conformance
  url: conformance/paysend-conformance.yml
- type: MCPServer
  url: mcp/paysend-mcp.yml
- type: LLMsTxt
  url: llms/paysend-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com