Nopan

Nopan is a specialized Payment Service Provider (PSP), built by former merchants and Netflix payments leaders, focused exclusively on European account and wallet payment methods (Wero, BLIK, Bizum, Satispay, IRIS). It exposes a single standardized API for account-to-account (A2A) and wallet payments with conversion-optimized flows, PSP-agnostic tokenization for recurring and merchant-initiated payments, a multi-currency settlement and reconciliation engine, normalized transaction data, and a real-time monitoring Portal. Authentication is OAuth2 client_credentials over mutual TLS with JWS request signing. Nopan is licensed as a Payment Institution by De Nederlandsche Bank (DNB) and is PSD2/SCA compliant. Backed by Newion, Crane, and Seedcamp.

Nopan publishes 5 APIs on the APIs.io network, including Authentication APIs API, Payment Processing APIs API, Reporting APIs API, and 2 more. Tagged areas include Payments, Payment Service Provider, Account-to-Account, Wallet Payments, and Open Banking.

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

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

🌐 Visit website 📡 Source on GitHub

48.9/100 developing ▬ flat Agent 35/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessSelf serve

1 APIs

Payments Payment Service Provider Account-to-AccountWallet PaymentsOpen Banking PSD2 Fintech Europe Tokenization Recurring Payments

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 48.9/100 · developing

Contract Quality 10.7 / 19

Developer Ergonomics 10.6 / 15

Access Clarity 4.3 / 15

Operational Transparency 0.8 / 10

Contract Governance 0.4 / 9

Discoverability 5.7 / 8

Regulatory Posture 10.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 35/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 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

Regulatory Posture applies to this provider. Its tags matched the Banking & Open Finance 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/nopan: 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 5

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

Nopan Authentication APIs API

This section covers the endpoints required for securely obtaining OAuth 2.0 access tokens to interact with the Nopan API. These APIs support machine-to-machine (M2M) authenticat...

Nopan Payment Processing APIs API

This section provides a set of operations for initiating and managing payments through the Nopan API. These endpoints enable clients to request payments, handle SCA, and track t...

Nopan Reporting APIs API

This section provides endpoints for accessing and downloading financial reports generated by the Nopan platform. Reports are available for a range of types including transaction...

Nopan Testing APIs API

The Nopan API includes a sandbox environment and test endpoints to help developers safely simulate, mock and validate payment flows without processing real transactions. These t...

Nopan Webhooks API

API of the webhooks notifications Nopan will send if configured in the portal.

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Nopan Authentication APIs API

OPEN COLLECTION

Nopan Authentication APIs Payment Processing APIs API

OPEN COLLECTION

Nopan Authentication APIs Reporting APIs API

OPEN COLLECTION

Nopan Authentication APIs Testing APIs API

OPEN COLLECTION

Nopan Authentication APIs Webhooks API

OPEN COLLECTION

Arazzo Workflows 2

Multi-step API workflows described with the Arazzo specification.

Nopan — accept and capture a payment

Authenticate, initiate a payment for SCA, finalize it, and capture funds.

ARAZZO

Nopan — refund a captured payment

Authenticate, refund a previously captured payment, and confirm via events.

ARAZZO

Event Specifications 1

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

Nopan Webhooks

ASYNCAPI

Security Posture 2

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

Nopan Authentication

oauth2/mutualTLS/http-bearer/jws-signing · 4 schemes

SECURITY

Nopan Domain Security

TLSv1.3 · HSTS · DNSSEC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Nopan Scopes

2 scopes · clientCredentials

2 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Nopan Agentic Access

16 operations · 12 acting

AGENTIC

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 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

AgenticAccess

AgenticAccess

Design & Contract 9

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

Webhooks

Conformance

Lifecycle

DataModel

Arazzo

Arazzo

Scroll for all 9

Build 1

SDKs, sample code, and the tooling you integrate with

Postman

Postman

Access & Security 4

Authentication, authorization, and security posture

Authentication

OAuthScopes

Compliance

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Blog

Blog

LinkedIn

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: nopan
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/nopan.png
name: Nopan
description: Nopan is a specialized Payment Service Provider (PSP), built by former merchants and Netflix payments leaders,
  focused exclusively on European account and wallet payment methods (Wero, BLIK, Bizum, Satispay, IRIS). It exposes a single
  standardized API for account-to-account (A2A) and wallet payments with conversion-optimized flows, PSP-agnostic tokenization
  for recurring and merchant-initiated payments, a multi-currency settlement and reconciliation engine, normalized transaction
  data, and a real-time monitoring Portal. Authentication is OAuth2 client_credentials over mutual TLS with JWS request signing.
  Nopan is licensed as a Payment Institution by De Nederlandsche Bank (DNB) and is PSD2/SCA compliant. Backed by Newion, Crane,
  and Seedcamp.
url: https://raw.githubusercontent.com/api-evangelist/nopan/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- seedcamp
- newion
- crane
x-tier: profiled
x-tier-reason: enriched-from-public-api
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Payments
- Payment Service Provider
- Account-to-Account
- Wallet Payments
- Open Banking
- PSD2
- Fintech
- Europe
- Tokenization
- Recurring Payments
tags_raw:
- Payments
- Payment Service Provider
- Account to Account
- Wallet Payments
- Open Banking
- PSD2
- Fintech
- Europe
- Tokenization
- Recurring Payments
apis:
- aid: nopan:nopan-authentication-apis-api
  name: Nopan Authentication APIs API
  description: This section covers the endpoints required for securely obtaining OAuth 2.0 access tokens to interact with
    the Nopan API. These APIs support machine-to-machine (M2M) authentication using mutual TLS (mTLS) and client credentials.
    A valid access token is required to authorize all subsequent requests to protected resources.
  humanURL: https://docs.nopan.com/
  baseURL: https://api.nopan.io
  tags:
  - Authentication APIs
  properties:
  - type: OpenAPI
    url: openapi/nopan-authentication-apis-api-openapi.yml
  - type: Authentication
    url: authentication/nopan-authentication.yml
  - type: OAuthScopes
    url: scopes/nopan-scopes.yml
  - type: Conventions
    url: conventions/nopan-conventions.yml
  - type: ErrorCatalog
    url: errors/nopan-error-codes.yml
  - type: Webhooks
    url: asyncapi/nopan-webhooks.yml
  - type: Sandbox
    url: sandbox/nopan-sandbox.yml
  - type: DataModel
    url: data-model/nopan-data-model.yml
- aid: nopan:nopan-payment-processing-apis-api
  name: Nopan Payment Processing APIs API
  description: This section provides a set of operations for initiating and managing payments through the Nopan API. These
    endpoints enable clients to request payments, handle SCA, and track the status of transactions in real time. Designed
    for seamless integration, the APIs support secure and compliant payment workflows for a variety of use cases including
    e-commerce, invoicing, and in-app purchases.
  humanURL: https://docs.nopan.com/
  baseURL: https://api.nopan.io
  tags:
  - Payment Processing APIs
  properties:
  - type: OpenAPI
    url: openapi/nopan-payment-processing-apis-api-openapi.yml
  - type: Authentication
    url: authentication/nopan-authentication.yml
  - type: OAuthScopes
    url: scopes/nopan-scopes.yml
  - type: Conventions
    url: conventions/nopan-conventions.yml
  - type: ErrorCatalog
    url: errors/nopan-error-codes.yml
  - type: Webhooks
    url: asyncapi/nopan-webhooks.yml
  - type: Sandbox
    url: sandbox/nopan-sandbox.yml
  - type: DataModel
    url: data-model/nopan-data-model.yml
- aid: nopan:nopan-reporting-apis-api
  name: Nopan Reporting APIs API
  description: This section provides endpoints for accessing and downloading financial reports generated by the Nopan platform.
    Reports are available for a range of types including transaction details, fee breakdowns, bank addendum data, and settlement
    summaries. Reports can be searched by date range, organization, or processing account, and downloaded by ID.
  humanURL: https://docs.nopan.com/
  baseURL: https://api.nopan.io
  tags:
  - Reporting APIs
  properties:
  - type: OpenAPI
    url: openapi/nopan-reporting-apis-api-openapi.yml
  - type: Authentication
    url: authentication/nopan-authentication.yml
  - type: OAuthScopes
    url: scopes/nopan-scopes.yml
  - type: Conventions
    url: conventions/nopan-conventions.yml
  - type: ErrorCatalog
    url: errors/nopan-error-codes.yml
  - type: Webhooks
    url: asyncapi/nopan-webhooks.yml
  - type: Sandbox
    url: sandbox/nopan-sandbox.yml
  - type: DataModel
    url: data-model/nopan-data-model.yml
- aid: nopan:nopan-testing-apis-api
  name: Nopan Testing APIs API
  description: The Nopan API includes a sandbox environment and test endpoints to help developers safely simulate, mock and
    validate payment flows without processing real transactions. These testing APIs mirror the behavior of the live endpoints,
    allowing you to initiate payments, trigger SCA flows, and verify callbacks using predefined test data. This environment
    is ideal for integration testing, QA workflows, and development staging before going live.
  humanURL: https://docs.nopan.com/
  baseURL: https://api.nopan.io
  tags:
  - Testing APIs
  properties:
  - type: OpenAPI
    url: openapi/nopan-testing-apis-api-openapi.yml
  - type: Authentication
    url: authentication/nopan-authentication.yml
  - type: OAuthScopes
    url: scopes/nopan-scopes.yml
  - type: Conventions
    url: conventions/nopan-conventions.yml
  - type: ErrorCatalog
    url: errors/nopan-error-codes.yml
  - type: Webhooks
    url: asyncapi/nopan-webhooks.yml
  - type: Sandbox
    url: sandbox/nopan-sandbox.yml
  - type: DataModel
    url: data-model/nopan-data-model.yml
- aid: nopan:nopan-webhooks-api
  name: Nopan Webhooks API
  description: API of the webhooks notifications Nopan will send if configured in the portal.
  humanURL: https://docs.nopan.com/
  baseURL: https://api.nopan.io
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/nopan-webhooks-api-openapi.yml
  - type: Authentication
    url: authentication/nopan-authentication.yml
  - type: OAuthScopes
    url: scopes/nopan-scopes.yml
  - type: Conventions
    url: conventions/nopan-conventions.yml
  - type: ErrorCatalog
    url: errors/nopan-error-codes.yml
  - type: Webhooks
    url: asyncapi/nopan-webhooks.yml
  - type: Sandbox
    url: sandbox/nopan-sandbox.yml
  - type: DataModel
    url: data-model/nopan-data-model.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/nopan-capability-edges.yml
  name: Nopan Business Capability Map
- type: DeveloperPortal
  url: https://docs.nopan.com/
- type: Documentation
  url: https://docs.nopan.com/
- type: APIReference
  url: https://docs.nopan.com/api
- type: GettingStarted
  url: https://docs.nopan.com/guides/integration-walkthrough
- type: Authentication
  url: authentication/nopan-authentication.yml
- type: OAuthScopes
  url: scopes/nopan-scopes.yml
- type: Conventions
  url: conventions/nopan-conventions.yml
- type: Idempotency
  url: conventions/nopan-conventions.yml
- type: ErrorCatalog
  url: errors/nopan-error-codes.yml
- type: Webhooks
  url: asyncapi/nopan-webhooks.yml
- type: Conformance
  url: conformance/nopan-conformance.yml
- type: Compliance
  url: conformance/nopan-conformance.yml
- type: Lifecycle
  url: lifecycle/nopan-lifecycle.yml
- type: Sandbox
  url: sandbox/nopan-sandbox.yml
- type: DataModel
  url: data-model/nopan-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/nopan-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: Overlay
  url: overlays/nopan-payments-overlay.yaml
- type: AgentSkill
  url: skills/_index.yml
- type: Arazzo
  name: Accept and capture a payment
  url: arazzo/nopan-accept-payment.yml
- type: Arazzo
  name: Refund a captured payment
  url: arazzo/nopan-refund-payment.yml
- type: AgenticAccess
  url: agentic-access/nopan-agentic-access.yml
- type: DomainSecurity
  url: security/nopan-domain-security.yml
- type: Postman
  url: https://docs.nopan.com/postman/nopan-api-collection.zip
- type: Blog
  url: https://nopan.com/blog
- type: Support
  url: mailto:support@nopan.com
- type: TermsOfService
  url: https://nopan.com/terms-of-use
- type: PrivacyPolicy
  url: https://nopan.com/privacy-policy
- type: LinkedIn
  url: https://www.linkedin.com/company/nopan/
- type: Website
  url: https://nopan.com
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 22
  pass: local-v1

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/nopan"

All providers

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

Every operation they expose

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

How their score was established

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

GitHub Google LinkedIn

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