Payrails website screenshot

Payrails

Payrails is a modular payment and financial infrastructure platform — "the operating system for profitable growth" — that gives merchants unified control over payments, tokenization, and financial data. Its API and SDKs orchestrate payments across many payment service providers (Adyen, Stripe, Checkout.com, Braintree, Klarna, and 100+ local methods), with a PCI-certified token vault, network tokenization, 3D Secure, a no-code Workflow Studio for routing and decisioning, automated reconciliation, chargeback/dispute management, fraud screening, and unified analytics. Authentication is OAuth 2.0 client-credentials (plus optional mTLS); events are delivered as HMAC-signed webhooks. Used by Eneba, PUMA, Vinted, Preply, inDrive, Just Eat, and Careem.

Payrails is listed with 1 API on the APIs.io network. Tagged areas include Company, Payments, Payment Orchestration, Fintech, and Tokenization.

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

Payrails’ developer surface includes documentation, API reference, getting-started guide, engineering blog, support, authentication, changelog, and 28 more developer resources.

52.9/100 developing ▬ flat Agent 27/100 agent aware Front door AI 4/6 moderate Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessSelf serve
1 API 4 Agent Skills
CompanyPaymentsPayment OrchestrationFintechTokenizationFraud PreventionDisputesReconciliationCheckoutFinancial Infrastructure

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.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/.
Show this score on your site. Kin Score badge preview for Payrails It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/payrails/"><img src="https://apis.io/badge/payrails/card.svg" alt="Payrails 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
7 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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/payrails/apis.yml: open an issue on github.com/api-evangelist/payrails 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.

MarketPositionDepthRegistered MCP serverDeclares compatibility
Stripe App Marketplace and Partner Ecosystem (builders on Stripe) standard 44.1 - -

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.

Payrails API

Payrails' REST API for payment orchestration — executions and payment actions (authorize, confirm, capture, cancel, refund, payout), instruments and tokens, the PCI vault, provi...

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

Defend a dispute

AGENT SKILL

Refund a payment

AGENT SKILL

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Event Specifications 1

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

Security Posture 4

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

Payrails Authentication

oauth2/mutualTLS · 3 schemes

SECURITY

Payrails Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Payrails Vulnerability Disclosure

no policy recorded

SECURITY

Payrails Trust Center

PCI DSS, GDPR

SECURITY

Resources

Get Started 3

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 for all 8

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 6

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: payrails
name: Payrails
description: Payrails is a modular payment and financial infrastructure platform — "the operating system for profitable growth"
  — that gives merchants unified control over payments, tokenization, and financial data. Its API and SDKs orchestrate payments
  across many payment service providers (Adyen, Stripe, Checkout.com, Braintree, Klarna, and 100+ local methods), with a PCI-certified
  token vault, network tokenization, 3D Secure, a no-code Workflow Studio for routing and decisioning, automated reconciliation,
  chargeback/dispute management, fraud screening, and unified analytics. Authentication is OAuth 2.0 client-credentials (plus
  optional mTLS); events are delivered as HMAC-signed webhooks. Used by Eneba, PUMA, Vinted, Preply, inDrive, Just Eat, and
  Careem.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://www.payrails.com/favicon.ico
url: https://raw.githubusercontent.com/api-evangelist/payrails/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
- eqt-ventures
- general-catalyst
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-04
tags:
- Company
- Payments
- Payment Orchestration
- Fintech
- Tokenization
- Fraud Prevention
- Disputes
- Reconciliation
- Checkout
- Financial Infrastructure
tags_raw:
- Company
- Payments
- Payment Orchestration
- Fintech
- Tokenization
- Fraud
- Disputes
- Reconciliation
- Checkout
- Financial Infrastructure
apis:
- name: Payrails API
  description: Payrails' REST API for payment orchestration — executions and payment actions (authorize, confirm, capture,
    cancel, refund, payout), instruments and tokens, the PCI vault, providers and workflow configuration, disputes, fraud,
    3DS, reports, SSO, and workspaces.
  humanURL: https://docs.payrails.com/reference
  baseURL: https://api.payrails.io
  properties:
  - type: Documentation
    url: https://docs.payrails.com/docs
  - type: APIReference
    url: https://docs.payrails.com/reference
  - type: Authentication
    url: authentication/payrails-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.payrails.com/
- type: DeveloperPortal
  url: https://docs.payrails.com/docs
- type: Documentation
  url: https://docs.payrails.com/docs
- type: APIReference
  url: https://docs.payrails.com/reference
- type: GettingStarted
  url: https://docs.payrails.com/docs/set-up-your-payrails-account-and-environment
- type: Blog
  url: https://www.payrails.com/blog
- type: Support
  url: https://www.payrails.com/contact
- type: GitHubOrganization
  url: https://github.com/payrails
- type: TermsOfService
  url: https://www.payrails.com/terms-and-conditions
- type: PrivacyPolicy
  url: https://www.payrails.com/privacy-policy
- type: StatusPage
  url: https://status.payrails.com
- type: Authentication
  url: authentication/payrails-authentication.yml
- type: Idempotency
  url: conventions/payrails-conventions.yml
- type: Conventions
  url: conventions/payrails-conventions.yml
- type: ErrorCatalog
  url: errors/payrails-problem-types.yml
- type: DeclineCodes
  url: errors/payrails-decline-codes.yml
- type: Lifecycle
  url: lifecycle/payrails-lifecycle.yml
- type: Deprecation
  url: https://docs.payrails.com/docs/v6-migration-guide
- type: ChangeLog
  url: https://docs.payrails.com/docs/v6-migration-guide
- type: Sandbox
  url: sandbox/payrails-sandbox.yml
- type: Webhooks
  url: asyncapi/payrails-notifications-webhooks.yml
- type: Packages
  url: packages/payrails-packages.yml
- type: SDKs
  url: packages/payrails-packages.yml
- type: Components
  url: components/payrails-components.yml
- type: X-MCPServerCandidate
  url: mcp/payrails-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: AgentSkill
  url: skills/_index.yml
- type: DataModel
  url: data-model/payrails-data-model.yml
- type: Conformance
  url: conformance/payrails-conformance.yml
- type: Compliance
  url: https://www.payrails.com/security
- type: WellKnown
  url: well-known/payrails-well-known.yml
- type: DomainSecurity
  url: security/payrails-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/payrails-vulnerability-disclosure.yml
- type: Security
  url: https://www.payrails.com/security
- type: TrustCenter
  url: security/payrails-trust-center.yml
- type: LLMsTxt
  url: llms/payrails-llms.txt
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 22
  pass: local-v1

Payrails API — frequently asked questions

Does Payrails have an API?

Yes. APIs.io lists 1 API from Payrails, including Payrails API.

How do I authenticate with the Payrails API?

Payrails uses bearer-token authentication (oauth2/mutualTLS · 3 schemes). The details are profiled on APIs.io as Payrails Authentication.

Is the Payrails API ready for AI agents?

Payrails has a Kin Score of 52.9 out of 100 (developing) and an Agent Readiness score of 26.8 (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/payrails"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/payrails/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/payrails/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.

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