PAP Apply for access
Skip to content

Payments infrastructure for Africa

Payments for merchants, run through licensed aggregators.

Each aggregator runs its own payment program, and merchants accept payments under it. This is a preview before live licensing.

Reference market
Zambia
Access modes
Sandbox + approved live
Platform model
Licensed aggregators bring their own rail agreements and credentials. PAP supplies isolated payment operations infrastructure.

Current status: Payment and Mobile POS capabilities shown here are product previews. Availability will depend on country licensing, rail certification, and merchant or aggregator approval.

Choose your path

Start with the work you need to do.

Each path explains its authority boundary before PAP asks you to authenticate or apply for access.

For aggregators

Operate a licensed program and manage the merchants under it.

Apply as an aggregator Preview route remains non-authoritative.

For merchants

Work under your aggregator to run stores, teams, and payments.

Apply as a merchant Preview route remains non-authoritative.

For developers

Build against versioned contracts, sandbox applications, and integration logs.

Start developer access Preview route remains non-authoritative.

For returning users

Sign in, then choose only from roles and organizations PAP verifies for you.

Sign in to PAP Preview route remains non-authoritative.

Operational foundation

Built for exact payment authority.

  • 01

    One state vocabulary

    Customer action, pending, authorization, capture, decline, ambiguity, reversal, and recovery stay distinct.

  • 02

    Country-ready by design

    Every live claim waits for country, rail, provider, licensing, operational, and safety approval.

  • 03

    Operational from the start

    Merchant, aggregator, developer, and Mobile POS previews share one restrained system.