Developer preview API v1

Sandbox only. No real funds moved. No production access is granted here. Access requirements

Server-to-server

Call the API from your private merchant backend

The merchant backend holds the credential and issues POST /v1/payments directly against the reviewed payment contract.

Recommended path

Run a private server backend for merchant mer_01900000000000000000000000 under aggregator programme agg-zm-dc1-demo in country cell zm-dc1. The backend stores the developer-app credential and calls POST /v1/payments directly.

Contract-matched request

Send integer minor units and ISO 4217 currency codes. Reuse the same idempotency_key across timeouts and retries, and keep a durable record of the intended operation before the first call.

Prohibited

Do not embed a live credential, a credential-shaped live key, or a second tenant's developer-app credential in browser code, logs, screenshots, or public repositories. Do not let a customer device call the payment endpoint with a shared secret.

Create payment

POST /v1/payments
Authorization: Bearer <developer-app-credential>
Content-Type: application/json

{"amount_minor":1500,"currency":"ZMW","capture_method":"automatic","idempotency_key":"order-1042","setup_future_usage":"none"}

Create refund

POST /v1/refunds
Authorization: Bearer <developer-app-credential>
Content-Type: application/json

{"payment_id":"pay_01900000000000000000000000","amount_minor":500,"reason":"customer_request","idempotency_key":"refund-order-1042"}