Network

Connect your network

If you run a mobile money service, a bank, a fintech, a PSP or a switch, this is how you start. One connection reaches every other participant, instead of one bilateral integration per counterparty, which is the arithmetic that keeps African payments fragmented.

What happens after you send it

  1. 1

    You tell us who you are

    The form below. Five minutes, no documents, no commitment. We ask what you can do, not what you can prove yet.

  2. 2

    A person reads it

    Not a scoring model. Someone works out whether there is a real fit, and writes back either way. A no comes with a reason.

  3. 3

    You get sandbox credentials

    A participant record and a signing key for sandbox. Sandbox talks only to sandbox, so nothing you do here can touch live money or another participant.

  4. 4

    You run certification

    17 tests against your connector, published in advance so there are no surprises. Roughly half are about failing correctly, which is the part that separates a rail we can reconcile from one we cannot.

  5. 5

    You go live, capability by capability

    A capability becomes real when it is certified, not when it is claimed. Going live is a deliberate decision on both sides, and it is reversible.

Read the protocol first if you would rather know exactly what you are being asked to support: all 8 capabilities, the full transaction lifecycle and every certification test are published.

Apply

Sending this commits you to nothing and gives you no access. It starts a conversation.

Your organisation
Who we should talk to
What you can do

Tick what you believe you can support. Nothing here is binding and nothing is taken as proved: the certification suite is what establishes a capability, and you run it in sandbox before anything carries live money.

We do not want licences or compliance documents through a form. If there is a fit, we will ask for those over a channel where someone has agreed to receive them.