Paysend website screenshot

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.

40.2/100 developing ▬ flat Agent 26/100 agent aware Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
1 APIs
PaymentsUnited KingdomCross-BorderMoney TransferPayoutsPayment ProcessingFXRemittanceFintech

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
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/.
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 github.com/api-evangelist/paysend: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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

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.'
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-09-03'
  method: derived
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.23'
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: X-MCPServerCandidate
  url: mcp/paysend-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/paysend-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/paysend"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/paysend/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/paysend/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.

A second provider on the same verified email joins the account you already have.