For Agents
Create checkout sessions, query payment status, and manage transactions for African payment processing. Supports Embedded and Hosted Checkout flows.
Use for: I need to create a checkout session for an African customer, I want to check the status of a payment transaction, Get details of a specific checkout session by ID, Retrieve payment information for a completed transaction
Not supported: Does not handle subscription billing, payouts, or multi-party marketplace payments — use for checkout session creation and payment status queries only.
Jentic publishes the only available OpenAPI specification for Peach Payments Checkout API, keeping it validated and agent-ready. Peach Payments Checkout API v2 provides payment processing for businesses operating in Africa. The API supports creating checkout sessions for both Embedded and Hosted Checkout integrations, querying checkout and payment statuses, and managing transactions. It handles multiple payment methods common in African markets including cards, mobile money, and bank transfers.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Peach Payments Checkout API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Peach Payments Checkout API.
Create checkout sessions for Embedded or Hosted Checkout integrations
Query checkout session status and retrieve payment details
Check individual payment transaction status by payment ID
Process payments across multiple African payment methods
Support card, mobile money, and bank transfer payment types
Patterns agents use Peach Payments Checkout API for, with concrete tasks.
★ E-Commerce Checkout for African Markets
Create checkout sessions for online stores serving customers across Africa. Peach Payments Checkout API v2 handles the checkout flow with support for local payment methods including cards, mobile money (M-Pesa, MTN Mobile Money), and bank transfers. Merchants can choose between Embedded Checkout (on-site) or Hosted Checkout (redirect) based on their integration preference.
POST to /v2/checkout with amount, currency (ZAR), and payment methods to create a checkout session for a South African transaction
Payment Status Monitoring
Query the status of checkout sessions and individual payments to confirm successful transactions, detect failures, and trigger fulfillment workflows. The API provides separate endpoints for checkout-level and payment-level status, enabling granular monitoring of the payment lifecycle.
GET /v2/checkout/{checkoutId} to check session status, then GET /v2/checkout/{checkoutId}/payment to retrieve the associated payment details
Transaction Reconciliation
Retrieve individual payment records by payment ID for financial reconciliation. Each payment record includes transaction amount, currency, status, and payment method used. This supports automated reconciliation between the payment gateway and merchant accounting systems.
GET /v2/payments/{paymentId} to retrieve the full payment record for reconciliation with the merchant accounting system
AI Agent Payment Processing via Jentic
AI agents create checkout sessions and monitor payment status as part of automated commerce workflows by calling Peach Payments through Jentic. The agent searches for African payment operations, receives the schema, and executes without managing bearer tokens or understanding the Embedded vs Hosted Checkout distinction.
Search Jentic for 'create checkout session Africa', load the /v2/checkout operation schema, and execute with amount and currency to initiate a payment
4 endpoints — jentic publishes the only available openapi specification for peach payments checkout api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/v2/checkout
Create a new checkout session
/v2/checkout/{checkoutId}
Query checkout session status
/v2/checkout/{checkoutId}/payment
Retrieve payment details for a checkout
/v2/payments/{paymentId}
Query individual payment transaction status
/v2/checkout
Create a new checkout session
/v2/checkout/{checkoutId}
Query checkout session status
/v2/checkout/{checkoutId}/payment
Retrieve payment details for a checkout
/v2/payments/{paymentId}
Query individual payment transaction status
Three things that make agents converge on Jentic-routed access.
Credential isolation
Peach Payments bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped access — the raw API key never enters the agent context, preventing credential exposure in payment workflows.
Intent-based discovery
Agents search by intent (e.g., 'create checkout session Africa' or 'check payment status') and Jentic returns matching Peach Payments operations with full schemas including amount, currency, and payment method parameters.
Time to first call
Direct integration: 2-3 days for auth setup, checkout flow selection, and status polling implementation. Through Jentic: under 30 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
NOWPayments API
Cryptocurrency payment processing for global transactions
Choose NOWPayments when you need cryptocurrency payment acceptance rather than traditional African payment methods.
Stripe API
Comprehensive payment infrastructure with global coverage
Choose Stripe for broad global coverage and extensive developer tooling — Peach Payments offers deeper integration with African local payment methods.
Specific to using Peach Payments Checkout API through Jentic.
Why is there no official OpenAPI spec for Peach Payments Checkout API?
Peach Payments does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Peach Payments Checkout API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Peach Payments Checkout API use?
Peach Payments Checkout API uses bearer token authentication. You pass your Peach Payments API key as a Bearer token in the Authorization header. Through Jentic, this key is stored encrypted in the vault and injected into requests automatically.
What is the difference between Embedded and Hosted Checkout?
Embedded Checkout renders the payment form within your website using a JavaScript widget. Hosted Checkout redirects customers to a Peach Payments-hosted page for payment. Both are initiated via POST /v2/checkout but differ in how the checkout session is presented to the customer.
Which payment methods does Peach Payments support?
Peach Payments supports cards (Visa, Mastercard), mobile money services common in African markets (M-Pesa, MTN Mobile Money), bank transfers, and other local payment methods. Available methods vary by country and merchant configuration.
How do I check payment status through Jentic?
Install with pip install jentic, search for 'check payment status'. Jentic returns the /v2/checkout/{checkoutId} or /v2/payments/{paymentId} schemas. Execute to retrieve the current transaction status. Jentic handles bearer auth automatically.
Which African countries does Peach Payments cover?
Peach Payments operates primarily in South Africa, Kenya, and Mauritius, with expanding coverage across the African continent. Supported currencies include ZAR, KES, and USD depending on the merchant configuration and country.
GET STARTED