GetPaid

Getpaid is a licensed European (EEA) embedded-payments platform that lets software platforms and marketplaces process payments while keeping the merchant relationship and capturing the transaction margin. It provides white-labeled hosted checkout across 30+ payment methods, atomic real-time split settlement that distributes a single transaction across sellers, the platform and agents, seller onboarding with KYC/KYB, subscriptions and invoicing with SEPA Direct Debit, and an AI-native agent-payments API with scoped authority tokens and spending limits. The v2 REST API uses OAuth 2.0 client-credentials auth, cursor pagination, RFC 7807 problem-details errors, an idempotency-key header, and 10 webhook events. Getpaid is a PCI-DSS Level 1, GDPR- and PSD2/SCA-aligned licensed payment institution with hubs in Germany, Spain and Finland.

GetPaid publishes 8 API contracts indexed on the APIs.io network, including Accounts API, Applications API, Authentication API, and 5 more. Tagged areas include Company, Payments, Embedded Payments, Split Settlement, and Checkout.

The GetPaid catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

GetPaid’s developer surface includes documentation, API reference, quickstart, signup flow, support, changelog, authentication, and 23 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

50.2/100 developing ▬ flat Agent 50/100 agent ready Front door AI 5/6 prominent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessEnterpriseSelf serve

1 published contract 3 Agent Skills

Company Payments Embedded PaymentsSplit SettlementCheckout Marketplace Onboarding Subscription Agentic Payments Europe

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Consumer Commerce

AE-140

CheckoutsPayments

POST /v2/checkouts POST /v2/payments POST /v2/payments/{payment_id}/refunds

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 50.2/100 · developing

Contract Quality 11.7 / 19

Developer Ergonomics 10.3 / 15

Access Clarity 2.8 / 15

Operational Transparency 2.3 / 10

Contract Governance 2.9 / 9

Discoverability 5.5 / 8

Regulatory Posture 6.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 50/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 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/getpaid/"><img src="https://apis.io/badge/getpaid/card.svg" alt="GetPaid 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
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)
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified)
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's
Dry-Run / Simulate Mode +4 pts — OpenAPI: destructive operations expose a dry_run / simulate / preview / validate_only parameter

2 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 18.4 — up to +16.3 composite points
Operational Transparency scores 23.7 — up to +9.9 composite points
Contract Quality scores 62.2 — up to +9.5 composite points

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/getpaid/apis.yml: open an issue on github.com/api-evangelist/getpaid 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.

Market	Position	Depth	Registered MCP server	Declares compatibility
x402 Micropayments & Agentic Pay-per-Call	undeclared	-	-	-

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.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 8

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

GetPaid Accounts API

Getpaid accounts created for sellers so they can start accepting payments and receiving payouts.

GetPaid Applications API

Onboarding applications to collect the necessary information from sellers to create their Getpaid accounts and start accepting payments.

GetPaid Authentication API

In order to authenticate with Getpaid API you need to request an OAuth 2.0 access token using your client ID and secret by calling the [Request access toke

GetPaid Checkouts API

Payment checkout sessions for one-time payments that the buyer can complete using Getpaid hosted checkout.

GetPaid Payments API

Create and manage payments initiated by the platform on behalf of the buyer. For recurring and unscheduled payments based on a previous standing instruction.

GetPaid Queries API

List resources filtering and sorting them as needed.

GetPaid Accept payments webhooks API

Webhooks related to accepting payment events.

GetPaid Onboard sellers webhooks API

Webhooks related to onboarding and accounts events.

Scroll for all 8

Open Collections 6

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

Getpaid Accounts API

OPEN COLLECTION

Getpaid Accounts Applications API

OPEN COLLECTION

Getpaid Accounts Authentication API

OPEN COLLECTION

Getpaid Accounts Checkouts API

OPEN COLLECTION

Getpaid Accounts Payments API

OPEN COLLECTION

Getpaid Accounts Queries API

OPEN COLLECTION

Agent Skills 3

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

Accept a payment with a hosted checkout

AGENT SKILL

Onboard a seller

AGENT SKILL

Refund a captured payment

AGENT SKILL

GetPaid API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Getpaid Plans Pricing

0 plans

PLANS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Getpaid Finops

FINOPS

Event Specifications 1

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

Getpaid Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

GetPaid API Rules

62 rules · 52 errors 7 warnings 3 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Getpaid Openapi Overlay

2 actions · update · getpaid-openapi-original.yml

DERIVED

Security Posture 2

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

Getpaid Authentication

oauth2 · 1 scheme

SECURITY

Getpaid Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Getpaid Scopes

4 scopes · clientCredentials

4 scopes

SCOPES

Agentic Access 1

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

Getpaid Agentic Access

16 operations · 7 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

Quickstart

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

Lifecycle

DataModel

Webhooks

Conformance

Scroll for all 7

Build 1

SDKs, sample code, and the tooling you integrate with

Postman

Postman

Access & Security 4

Authentication, authorization, and security posture

Authentication

OAuthScopes

DomainSecurity

Compliance

Operate 2

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

PrivacyPolicy

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: getpaid
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: enterprise
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Enterprise · Self-serve signup
  confidence: medium
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/getpaid.png
name: GetPaid
description: Getpaid is a licensed European (EEA) embedded-payments platform that lets software platforms and marketplaces
  process payments while keeping the merchant relationship and capturing the transaction margin. It provides white-labeled
  hosted checkout across 30+ payment methods, atomic real-time split settlement that distributes a single transaction across
  sellers, the platform and agents, seller onboarding with KYC/KYB, subscriptions and invoicing with SEPA Direct Debit, and
  an AI-native agent-payments API with scoped authority tokens and spending limits. The v2 REST API uses OAuth 2.0 client-credentials
  auth, cursor pagination, RFC 7807 problem-details errors, an idempotency-key header, and 10 webhook events. Getpaid is a
  PCI-DSS Level 1, GDPR- and PSD2/SCA-aligned licensed payment institution with hubs in Germany, Spain and Finland.
url: https://raw.githubusercontent.com/api-evangelist/getpaid/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- insight-partners
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
x-docs-platform: docusaurus
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
x-docs-hosting: azure-static
tags:
- Company
- Payments
- Embedded Payments
- Split Settlement
- Checkout
- Marketplace
- Onboarding
- Subscription
- Agentic Payments
- Europe
tags_raw:
- Company
- Payments
- Embedded Payments
- Split Settlement
- Checkout
- Marketplace
- Onboarding
- Subscriptions
- Agent Payments
- Europe
apis:
- aid: getpaid:getpaid-accounts-api
  name: GetPaid Accounts API
  description: Getpaid accounts created for sellers so they can start accepting payments and receiving payouts.
  humanURL: https://docs.getpaid.io/api
  baseURL: https://api.getpaid.io
  tags:
  - Account
  tags_raw:
  - Accounts
  properties:
  - type: OpenAPI
    url: openapi/getpaid-accounts-api-openapi.yml
  - type: APIReference
    url: https://docs.getpaid.io/api
- aid: getpaid:getpaid-applications-api
  name: GetPaid Applications API
  description: Onboarding applications to collect the necessary information from sellers to create their Getpaid accounts
    and start accepting payments.
  humanURL: https://docs.getpaid.io/api
  baseURL: https://api.getpaid.io
  tags:
  - Application
  tags_raw:
  - Applications
  properties:
  - type: OpenAPI
    url: openapi/getpaid-applications-api-openapi.yml
  - type: APIReference
    url: https://docs.getpaid.io/api
- aid: getpaid:getpaid-authentication-api
  name: GetPaid Authentication API
  description: '<!-- markdownlint-disable link-fragments -->

    In order to authenticate with Getpaid API you need to request an OAuth 2.0 access token using your client ID and secret

    by calling the [Request access token endpoint](#tag/Authentication/operation/request_access_token).

    <!-- markdownlint-enable link-fragments -->


    Check full details on [how API authentication and authorization works](/integration/api/authentication/) and [how to get

    your client credentials](/integration/api/authentication/client-credentials).


    <!-- ReDoc-Inject: <security-definitions> -->'
  humanURL: https://docs.getpaid.io/api
  baseURL: https://api.getpaid.io
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/getpaid-authentication-api-openapi.yml
  - type: APIReference
    url: https://docs.getpaid.io/api
- aid: getpaid:getpaid-checkouts-api
  name: GetPaid Checkouts API
  description: Payment checkout sessions for one-time payments that the buyer can complete using Getpaid hosted checkout.
  humanURL: https://docs.getpaid.io/api
  baseURL: https://api.getpaid.io
  tags:
  - Checkout
  tags_raw:
  - Checkouts
  properties:
  - type: OpenAPI
    url: openapi/getpaid-checkouts-api-openapi.yml
  - type: APIReference
    url: https://docs.getpaid.io/api
- aid: getpaid:getpaid-payments-api
  name: GetPaid Payments API
  description: 'Create and manage payments initiated by the platform on behalf of the buyer.


    For recurring and unscheduled payments based on a previous standing instruction.'
  humanURL: https://docs.getpaid.io/api
  baseURL: https://api.getpaid.io
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/getpaid-payments-api-openapi.yml
  - type: APIReference
    url: https://docs.getpaid.io/api
- aid: getpaid:getpaid-queries-api
  name: GetPaid Queries API
  description: List resources filtering and sorting them as needed.
  humanURL: https://docs.getpaid.io/api
  baseURL: https://api.getpaid.io
  tags:
  - Query
  tags_raw:
  - Queries
  properties:
  - type: OpenAPI
    url: openapi/getpaid-queries-api-openapi.yml
  - type: APIReference
    url: https://docs.getpaid.io/api
- aid: getpaid:getpaid-accept-payments-webhooks-api
  name: GetPaid Accept payments webhooks API
  description: Webhooks related to accepting payment events.
  humanURL: https://docs.getpaid.io/api
  baseURL: https://api.getpaid.io
  tags:
  - Accept payments webhooks
  properties:
  - type: OpenAPI
    url: openapi/getpaid-accept-payments-webhooks-api-openapi.yml
- aid: getpaid:getpaid-onboard-sellers-webhooks-api
  name: GetPaid Onboard sellers webhooks API
  description: Webhooks related to onboarding and accounts events.
  humanURL: https://docs.getpaid.io/api
  baseURL: https://api.getpaid.io
  tags:
  - Onboard sellers webhooks
  properties:
  - type: OpenAPI
    url: openapi/getpaid-onboard-sellers-webhooks-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/getpaid-capability-edges.yml
  name: GetPaid Business Capability Map
- type: Plans
  url: plans/getpaid-plans-pricing.yml
- type: Website
  url: https://www.getpaid.io/
- type: Overlay
  url: overlays/getpaid-openapi-overlay.yaml
- type: DeveloperPortal
  url: https://docs.getpaid.io
- type: Documentation
  url: https://docs.getpaid.io
- type: APIReference
  url: https://docs.getpaid.io/api
- type: Quickstart
  url: https://docs.getpaid.io/integration/api
- type: SignUp
  url: https://dashboard.getpaid.io
- type: Support
  url: mailto:support@getpaid.io
- type: PrivacyPolicy
  url: https://www.getpaid.io/privacy-policy
- type: Postman
  url: https://docs.getpaid.io/integration/api/postman
- type: ChangeLog
  url: changelog/getpaid-changelog.yml
- type: Authentication
  url: authentication/getpaid-authentication.yml
- type: OAuthScopes
  url: scopes/getpaid-scopes.yml
- type: AgenticAccess
  url: agentic-access/getpaid-agentic-access.yml
- type: DomainSecurity
  url: security/getpaid-domain-security.yml
- type: WellKnown
  url: well-known/getpaid-well-known.yml
- type: Conventions
  url: conventions/getpaid-conventions.yml
- type: Idempotency
  url: conventions/getpaid-conventions.yml
- type: ErrorCatalog
  url: errors/getpaid-problem-types.yml
- type: Lifecycle
  url: lifecycle/getpaid-lifecycle.yml
- type: Sandbox
  url: sandbox/getpaid-sandbox.yml
- type: DataModel
  url: data-model/getpaid-data-model.yml
- type: Webhooks
  url: asyncapi/getpaid-webhooks.yml
- type: X-MCPServerCandidate
  url: mcp/getpaid-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/getpaid-llms.txt
- type: Conformance
  url: conformance/getpaid-conformance.yml
- type: Compliance
  url: https://getpaid.io/compliance
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

GetPaid API — frequently asked questions

Does GetPaid have an API?

Yes. APIs.io lists 8 APIs from GetPaid, including GetPaid Accounts API, GetPaid Applications API and GetPaid Authentication API, and 5 more.

Is there an OpenAPI specification for the GetPaid API?

Yes. APIs.io indexes 8 OpenAPI specifications for GetPaid, each linked for download from this page.

How do I authenticate with the GetPaid API?

GetPaid documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Getpaid Authentication.

Is the GetPaid API ready for AI agents?

GetPaid has a Kin Score of 50.2 out of 100 (developing) and an Agent Readiness score of 50.1 (agent-ready), 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/getpaid"

All providers

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

Every operation they expose

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

How their score was established

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

GitHub Google LinkedIn

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