PAP Apply for access
Skip to content

Developer preview API v1

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

Client kinds

Choose the integration path that matches your client kind

One recommended path per client kind, matched to the reviewed PAP contracts and free of shared secrets in client code.

One recommended path per client kind

Each quickstart names exactly one supported integration shape: merchant backend, aggregator backend, server-rendered web through a same-origin BFF, browser public client with PKCE, hosted checkout, native mobile app, Mobile POS, or partner gRPC.

Contracts stay server-authoritative

Every example is generated from and tested against the actual payment and refund DTOs. The server derives tenant, aggregator, country cell, and execution mode; clients cannot select or override those authority fields.

No shared secret in client code

A browser, mobile binary, or point-of-sale device never holds a live credential. The developer app credential for country cell zm-dc1 and aggregator agg-zm-dc1-demo remains server-side in every recommended flow.

Start in sandbox

Rehearse with synthetic identities such as merchant mer_01900000000000000000000000 and store store_01900000000000000000000000. Production access is separate and is not granted by documentation.