Peach Payments website screenshot

Peach Payments

Peach Payments is a pan-African payment orchestration gateway founded in 2012 in Cape Town, South Africa, operating across South Africa, Kenya, and Mauritius. Its PCI DSS Level 1 platform exposes REST APIs for Checkout (Hosted, Embedded, Embedded Express), server-to-server Payments, Payment Links, Payouts, and Reconciliation, supporting cards plus local methods like PayShap, Capitec Pay, 1Voucher, Mobicred, M-PESA, and MauCAS in ZAR, KES, and MUR.

Peach Payments publishes 6 API contracts indexed on the APIs.io network, including Authentication API, Checkout API, Payment Links API, and 3 more. Tagged areas include Payments, Fintech, Africa, Payment Gateway, and Checkout.

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

Peach Payments’ developer surface includes authentication, sandbox, changelog, documentation, API reference, getting-started guide, support, and 36 more developer resources.

70.6/100 exemplar ▬ flat Agent 28/100 agent aware Front door AI 1/6 silent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessPaid
1 published contract 3 Agent Skills
PaymentsFintechAfricaPayment GatewayCheckoutPayouts

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
CheckoutPayments
POST /v2/checkout GET /v2/checkout/{checkoutId} POST /payments

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 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. Kin Score badge preview for Peach Payments It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/peachpayments/"><img src="https://apis.io/badge/peachpayments/card.svg" alt="Peach Payments 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
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • 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
  • Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
6 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/peachpayments/apis.yml: open an issue on github.com/api-evangelist/peachpayments 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
African Payments (Nigeria, Kenya, South Africa, Ghana, WAEMU) 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 1

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.

measured — observed by APIs.io (published)

APIs 6

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

Peach Payments Authentication API

OAuth 2.0 token generation for Checkout, Payouts, and Reconciliation.

Peach Payments Checkout API

Hosted, Embedded, and Embedded Express checkout sessions.

Peach Payments Payment Links API

Shareable, single-use and bulk payment links.

Peach Payments API

Server-to-server debit and refund transactions.

Peach Payments Payouts API

Merchant-initiated payouts and bank account verification.

Peach Payments Reconciliation API

Settlement and transaction reconciliation reporting.

Postman Collections 6

Ready-to-run Postman collections for exercising this provider's APIs.

Open Collections 6

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

Agent Skills 3

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

Peach Payments API pricing

Prices published by Peach Payments, read 2026-10-28 from www.peachpayments.com/fees/.

PlanPrice
Growth plan 2.95% +R1.50 per txn (ex VAT)
Includes: Easy plugins, 24/7 phone & email support, free automated daily settlements, local & international ca
Enterprise plan Custom volume-based rates
Includes: For businesses that transact over R500,000 per month; Dedicated Account Manager; API & SDK integrati
International Mastercard, Visa & Amex Cards (Growth) 3.50% + R1.50/transaction
Pay by Bank (incl all banks except Capitec) (Growth) 1.50% + R1.50/transaction
PayJustNow (Growth) 5.35% + R4.80 + R1.50/transaction + R199 monthly fee
Payflex (Growth) 5.25% + R4/transaction + R1.50/transaction
Float (Growth) 5.10% + R4/transaction
Happy Pay (Growth) 4.99% + R4/transaction + R1.50/transaction

All 10 plans, limits and sources →

Rate limits

Compiled by API Evangelist, not yet checked against Peach Payments's documentation. Rate-limit details →

Billed by: transaction · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Peachpayments Rate Limits

2 limits

RATE LIMITS

Service Levels 1

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

FinOps 1

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

Event Specifications 1

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

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Peach Payments API Rules

64 rules · 62 errors 1 warnings 1 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.

Peachpayments Openapi Overlay

5 actions · update · peachpayments-openapi.yml

DERIVED

Security Posture 4

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

Peachpayments Authentication

http/inline-credentials · 3 schemes

SECURITY

Peachpayments Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Peachpayments Vulnerability Disclosure

Hackerone · contact published

SECURITY

Peachpayments Trust Center

PCI DSS Level 1, PCI DSS v4.0

SECURITY

Agentic Access 1

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

Peachpayments Agentic Access

13 operations · 7 acting

13 operations · 7 acting

AGENTIC

Resources

Get Started 5

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 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 5

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 5

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: peachpayments
url: https://raw.githubusercontent.com/api-evangelist/peachpayments/refs/heads/main/apis.yml
name: Peach Payments
kind: company
description: Peach Payments is a pan-African payment orchestration gateway founded in 2012 in Cape Town, South Africa, operating
  across South Africa, Kenya, and Mauritius. Its PCI DSS Level 1 platform exposes REST APIs for Checkout (Hosted, Embedded,
  Embedded Express), server-to-server Payments, Payment Links, Payouts, and Reconciliation, supporting cards plus local methods
  like PayShap, Capitec Pay, 1Voucher, Mobicred, M-PESA, and MauCAS in ZAR, KES, and MUR.
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: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: high
  source:
  - plans
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/peachpayments.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
tags:
- Payments
- Fintech
- Africa
- Payment Gateway
- Checkout
- Payouts
created: '2026-07-17'
modified: '2026-09-16'
specificationVersion: '0.23'
apis:
- aid: peachpayments:peachpayments-authentication-api
  name: Peach Payments Authentication API
  description: OAuth 2.0 token generation for Checkout, Payouts, and Reconciliation.
  humanURL: https://developer.peachpayments.com/docs/checkout-embedded-authentication
  baseURL: https://dashboard.peachpayments.com
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/peachpayments-authentication-api-openapi.yml
  - type: Documentation
    url: https://developer.peachpayments.com/docs/checkout-embedded-authentication
  - type: Documentation
    url: https://developer.peachpayments.com/docs/checkout-overview
  - type: APIReference
    url: https://developer.peachpayments.com/reference/payment
  - type: PostmanCollection
    url: collections/peachpayments.postman_collection.json
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payments-api-flows
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payment-links-overview
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payouts-api-1
  - type: Documentation
    url: https://developer.peachpayments.com/docs/bus-ops-recon-api
- aid: peachpayments:peachpayments-checkout-api
  name: Peach Payments Checkout API
  description: Hosted, Embedded, and Embedded Express checkout sessions.
  humanURL: https://developer.peachpayments.com/docs/checkout-embedded-authentication
  baseURL: https://dashboard.peachpayments.com
  tags:
  - Checkout
  properties:
  - type: OpenAPI
    url: openapi/peachpayments-checkout-api-openapi.yml
  - type: Documentation
    url: https://developer.peachpayments.com/docs/checkout-embedded-authentication
  - type: Documentation
    url: https://developer.peachpayments.com/docs/checkout-overview
  - type: APIReference
    url: https://developer.peachpayments.com/reference/payment
  - type: PostmanCollection
    url: collections/peachpayments.postman_collection.json
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payments-api-flows
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payment-links-overview
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payouts-api-1
  - type: Documentation
    url: https://developer.peachpayments.com/docs/bus-ops-recon-api
- aid: peachpayments:peachpayments-payment-links-api
  name: Peach Payments Payment Links API
  description: Shareable, single-use and bulk payment links.
  humanURL: https://developer.peachpayments.com/docs/checkout-embedded-authentication
  baseURL: https://dashboard.peachpayments.com
  tags:
  - Payment Links
  properties:
  - type: OpenAPI
    url: openapi/peachpayments-payment-links-api-openapi.yml
  - type: Documentation
    url: https://developer.peachpayments.com/docs/checkout-embedded-authentication
  - type: Documentation
    url: https://developer.peachpayments.com/docs/checkout-overview
  - type: APIReference
    url: https://developer.peachpayments.com/reference/payment
  - type: PostmanCollection
    url: collections/peachpayments.postman_collection.json
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payments-api-flows
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payment-links-overview
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payouts-api-1
  - type: Documentation
    url: https://developer.peachpayments.com/docs/bus-ops-recon-api
- aid: peachpayments:peachpayments-payments-api
  name: Peach Payments API
  description: Server-to-server debit and refund transactions.
  humanURL: https://developer.peachpayments.com/docs/checkout-embedded-authentication
  baseURL: https://dashboard.peachpayments.com
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/peachpayments-payments-api-openapi.yml
  - type: Documentation
    url: https://developer.peachpayments.com/docs/checkout-embedded-authentication
  - type: Documentation
    url: https://developer.peachpayments.com/docs/checkout-overview
  - type: APIReference
    url: https://developer.peachpayments.com/reference/payment
  - type: PostmanCollection
    url: collections/peachpayments.postman_collection.json
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payments-api-flows
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payment-links-overview
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payouts-api-1
  - type: Documentation
    url: https://developer.peachpayments.com/docs/bus-ops-recon-api
- aid: peachpayments:peachpayments-payouts-api
  name: Peach Payments Payouts API
  description: Merchant-initiated payouts and bank account verification.
  humanURL: https://developer.peachpayments.com/docs/checkout-embedded-authentication
  baseURL: https://dashboard.peachpayments.com
  tags:
  - Payouts
  properties:
  - type: OpenAPI
    url: openapi/peachpayments-payouts-api-openapi.yml
  - type: Documentation
    url: https://developer.peachpayments.com/docs/checkout-embedded-authentication
  - type: Documentation
    url: https://developer.peachpayments.com/docs/checkout-overview
  - type: APIReference
    url: https://developer.peachpayments.com/reference/payment
  - type: PostmanCollection
    url: collections/peachpayments.postman_collection.json
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payments-api-flows
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payment-links-overview
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payouts-api-1
  - type: Documentation
    url: https://developer.peachpayments.com/docs/bus-ops-recon-api
- aid: peachpayments:peachpayments-reconciliation-api
  name: Peach Payments Reconciliation API
  description: Settlement and transaction reconciliation reporting.
  humanURL: https://developer.peachpayments.com/docs/checkout-embedded-authentication
  baseURL: https://dashboard.peachpayments.com
  tags:
  - Reconciliation
  properties:
  - type: OpenAPI
    url: openapi/peachpayments-reconciliation-api-openapi.yml
  - type: Documentation
    url: https://developer.peachpayments.com/docs/checkout-embedded-authentication
  - type: Documentation
    url: https://developer.peachpayments.com/docs/checkout-overview
  - type: APIReference
    url: https://developer.peachpayments.com/reference/payment
  - type: PostmanCollection
    url: collections/peachpayments.postman_collection.json
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payments-api-flows
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payment-links-overview
  - type: Documentation
    url: https://developer.peachpayments.com/docs/payouts-api-1
  - type: Documentation
    url: https://developer.peachpayments.com/docs/bus-ops-recon-api
common:
- type: CapabilityMap
  url: capabilities/peachpayments-capability-edges.yml
  name: Peach Payments Business Capability Map
- type: X-MCPServerCandidate
  url: mcp/peachpayments-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: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/peach-payments/overview
- type: AgenticAccess
  url: agentic-access/peachpayments-agentic-access.yml
- type: TrustCenter
  url: security/peachpayments-trust-center.yml
- type: Compliance
  url: security/peachpayments-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/peachpayments-vulnerability-disclosure.yml
- type: Security
  url: security/peachpayments-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/peachpayments-domain-security.yml
- type: Authentication
  url: authentication/peachpayments-authentication.yml
- type: Packages
  url: packages/peachpayments-packages.yml
- type: SDKs
  url: packages/peachpayments-packages.yml
- type: LLMsTxt
  url: llms/peachpayments-llms.txt
- type: Overlay
  url: overlays/peachpayments-openapi-overlay.yaml
- type: Conformance
  url: conformance/peachpayments-conformance.yml
- type: ErrorCatalog
  url: errors/peachpayments-problem-types.yml
- type: DeclineCodes
  url: errors/peachpayments-decline-codes.yml
- type: Lifecycle
  url: lifecycle/peachpayments-lifecycle.yml
- type: StatusPage
  url: https://status.peachpayments.com
- type: Sandbox
  url: sandbox/peachpayments-sandbox.yml
- type: Conventions
  url: conventions/peachpayments-conventions.yml
- type: ChangeLog
  url: changelog/peachpayments-changelog.yml
- type: Components
  url: components/peachpayments-components.yml
- type: DataModel
  url: data-model/peachpayments-data-model.yml
- type: Webhooks
  url: asyncapi/peachpayments-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/peach-payments
- type: Website
  url: https://www.peachpayments.com/
- type: DeveloperPortal
  url: https://developer.peachpayments.com/
- type: Documentation
  url: https://developer.peachpayments.com/
- type: APIReference
  url: https://developer.peachpayments.com/reference
- type: GettingStarted
  url: https://developer.peachpayments.com/docs/product-portfolio-overview
- type: Support
  url: https://www.peachpayments.com/contact
- type: Blog
  url: https://www.peachpayments.com/scale
- type: Pricing
  url: https://www.peachpayments.com/fees
- type: SignUp
  url: https://www.peachpayments.com/get-started
- type: Login
  url: https://dashboard.peachpayments.com
- type: TermsOfService
  url: https://www.peachpayments.com/legal
- type: PrivacyPolicy
  url: https://www.peachpayments.com/legal
- type: Postman
  url: https://www.postman.com/peachpayments/peach-payments-public-workspace
- type: Plans
  url: plans/peachpayments-plans-pricing.yml
- type: RateLimits
  url: rate-limits/peachpayments-rate-limits.yml
- type: FinOps
  url: finops/peachpayments-finops.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Peach Payments API — frequently asked questions

Does Peach Payments have an API?

Yes. APIs.io lists 6 APIs from Peach Payments, including Peach Payments Authentication API, Peach Payments Checkout API and Peach Payments Payment Links API, and 3 more.

Is there an OpenAPI specification for the Peach Payments API?

Yes. APIs.io indexes 6 OpenAPI specifications for Peach Payments, each linked for download from this page.

How do I authenticate with the Peach Payments API?

Peach Payments uses bearer-token authentication (http/inline-credentials · 3 schemes). The details are profiled on APIs.io as Peachpayments Authentication.

How much does the Peach Payments API cost?

Peach Payments publishes its prices; its Growth plan plan is 2.95% +R1.50 per txn (ex VAT) as of 2026-10-28. APIs.io lists 10 pricing plans for Peach Payments, with each plan's price, limits and inclusions under Pricing on this page.

Is the Peach Payments API ready for AI agents?

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