GetPaid website screenshot

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 6 APIs on the APIs.io network, including Accounts API, Applications API, Authentication API, and 3 more. Tagged areas include Company, Payments, Embedded Payments, Split Settlement, and Checkout.

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

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

🌐 Visit website 📡 Source on GitHub
56.6/100 developing ▬ flat Agent 84/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
6 APIs 1 MCP Servers
CompanyPaymentsEmbedded PaymentsSplit SettlementCheckoutMarketplaceOnboardingSubscriptionsAgent PaymentsEurope

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 56.6/100 · developing
Contract Quality 18.1 / 25
Developer Ergonomics 15.2 / 20
Commercial Clarity 6.3 / 20
Operational Transparency 3.1 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 84/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/getpaid: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 6

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

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.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

getpaid-mcp.yml

MCP SERVER

Event Specifications 1

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

Getpaid Webhooks

ASYNCAPI

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 · 12 acting

16 operations · 12 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 Quickstart
Quickstart
 SignUp
SignUp
 Sandbox
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
 MCPServer
MCPServer
 LLMsTxt
LLMsTxt
 AgentSkill
AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 Idempotency
Idempotency
 ErrorCatalog
ErrorCatalog
 Lifecycle
Lifecycle
 DataModel
DataModel
 Webhooks
Webhooks
 Conformance
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
Authentication
 OAuthScopes
OAuthScopes
 DomainSecurity
DomainSecurity
 Compliance
Compliance

Operate 2

Status, limits, changes, and where to get help

Support
Support
 ChangeLog
ChangeLog

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy
PrivacyPolicy

Source (apis.yml)

apis.yml Raw ↑ 
aid: getpaid
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/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.20'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- 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:
  - 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:
  - 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:
  - 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:
  - Queries
  properties:
  - type: OpenAPI
    url: openapi/getpaid-queries-api-openapi.yml
  - type: APIReference
    url: https://docs.getpaid.io/api
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- 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: MCPServer
  url: mcp/getpaid-mcp.yml
- 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