Open Payments
Open Payments provides a unified API platform that connects businesses to multiple banks, enabling payments, account data access, cross‑border transactions, and financial data aggregation. Their solution simplifies integration, reduces friction, and offers real‑time cash‑flow visibility, compliance with PSD2 and GDPR, and customizable branding for enterprises seeking to build modern financial services.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Open Payments the way a machine reads it — 23 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Open Payments scores 43.9/100 (developing), with a separate agent-readiness read of 31/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from Open Payments's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/openpayments-io/"
title="Open Payments on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/openpayments-io.svg"
alt="Open Payments Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/openpayments-io/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/openpayments-io/"
title="Open Payments on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/openpayments-io/card.svg"
alt="Open Payments Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Open Payments
Each block below is one kind of artifact we hold for Open Payments. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Open Payments Account Information Service (AIS) API
The Account Information Service (AIS) offers the following services: * Transaction reports for a given account or card account including balances if applicable * Balances of a g...
Open Payments ASPSP Information Service API
The ASPSP (Account Servicing Payment Service Providers) Information Service allows looking up information about banks and other account providers. The service offers the followi...
Open Payments Bankgiro Lookup API
Bankgiro Lookup APIs provide enhanced data and pre-payment validation on top of our core APIs. These services enable you to build more reliable, user-friendly payment experience...
Open Payments Consent Service API
The Consent Service offers the following services: * Create and authorize consents between the PSU and the TPP for use in the AIS services * Get status of consent and retrieve p...
Open Payments FX Connect API
FX Connect enables you to execute cross-border payments without integrating the Payment Initiation Service (PIS), operating seamlessly on top of your own existing bank integrati...
Open Payments ISO Payments API
ISO Payments offers a direct and intuitive interface to the banks ISO 20022 products. By leveraging ISO 20022, you can automate and streamline a wide range of payment processes,...
Open Payments KYC Service API
KYC Service offers the following services: * Initiation of a KYC process to access our KYC webform * KYC status of a corporation
Open Payments Payment Initiation Service (PIS) API
Payment Initiation Service (PIS) offers the following services: * Create and authorize payments * Status information of payments and authorizations * Create and authorize basket...
Open Payments Payout Service API
The Payout Service brings efficiency and security to a wide range of payment processes, including supplier invoices, payroll, refunds, and other forms of disbursement. The solut...
Open Payments SEPA Direct Debit API
The SEPA Direct Debit API allows you to initiate EUR-denominated collections directly from your customer's bank account in the Netherlands by submitting debit instructions in JS...
Open Payments Verification of Payee (VoP) API
The Verification of Payee (VoP) API allows you to instantly verify that a creditor's name matches the provided account details (IBAN) and display the result to your PSU, e.g. wh...
Scroll within the panel for all 11 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Openpayments Io Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Open Payments API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ConfirmIsoPaymentResponse
JSON SCHEMAConfirmPayoutResponse
JSON SCHEMACreatePayoutRequest
JSON SCHEMACreatePayoutResponse
JSON SCHEMAGetPayoutResponse
JSON SCHEMASEPA Direct Debit Payment
JSON SCHEMASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Open Payments — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/openpayments-io · machine-readable index on apis.io
This is an independent, third-party profile of Open Payments, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.