01
Reconcile across ledgers
The rail reads bank core ledgers, public Layer-1s, and permissioned chains and reconciles them into one record anyone with access can verify.
Pan-Africa · Financial infrastructure
The rail beneath tokenized African financial life.
Pan-Africa develops tokenized financial infrastructure and controlled issuance workflows for institutions operating across African markets. PASC is the first proposed product on the rail.
Proposed productSubject to approvalInstitutional access only
The problem we are built for
Many ledgers.
No shared truth.
African financial life runs across many ledgers — bank core systems, public Layer-1 blockchains, and permissioned chains. Each keeps its own record, and value moving between them is slow, costly, and hard to verify.
For thirty years the continent has watched capital leave for want of infrastructure that institutions here can settle on with confidence. The gap is not ambition — it is a shared, verifiable record that the banks and financial institutions operating across African markets can trust.
The rail · how it works
One rail.
Many ledgers, one source of truth.
Pan-Africa is the infrastructure company developing the rail — the reconciliation layer and the controlled issuance workflows the banks and financial institutions operating here can build on.
02
Controlled issuance workflow
Every issuance moves through three accountable steps — request, review, and issuance — each owned by a role and recorded, never a single unchecked action.
03
Recorded on chain
The outcome of each step is written to chain so the record is independently verifiable, not a private claim made behind a counter.
Built in Kigali · the home of the rail
The first product on the rail
PASC.
Proposed, not promised.
Proposed productDemo environmentNo yieldNot legal tender
PASC is the first proposed product on the Pan-Africa rail — a USD-denominated token designed for controlled, institutional issuance. It is how the rail is demonstrated end to end today, and the shape of the production product intended for the future.
Proof, not promises
Every claim has a control,
an owner, and a record.
Controlled issuance
Demo environment- What control exists
- A three-step request → review → issuance workflow, with a 14-status state machine; no token is issued by a single unchecked action.
- Who operates / reviews
- Issuance and compliance roles operating the dashboard; each step is gated to its own role.
- What is recorded
- Each state transition and administrative action is written to an audit log and, for issuance, to chain.
- Approval required
- Production issuance is subject to applicable regulatory approval; the current environment is a public testnet.
Reserves model
Illustrative reserve model- What control exists
- The production token is intended to be fully reserved through a regulated trust, with reserves intended to be held on the continent.
- Who operates / reviews
- A regulated trust arrangement and its administrators — a partner relationship, not Pan-Africa acting as a bank.
- What is recorded
- Reserve attestations are intended to be published and verifiable; the demo token is mint-and-burn only and holds no reserve.
- Approval required
- The trust and the production reserve model are forward-looking and subject to regulatory approval.
What we are — and are not
Not a bankPartner-dependent
Treasury & operations
Submit and track issuance requests for a wallet.
The issuance dashboard remembers wallets it has seen and preloads the profile so the second request from the same counterparty takes a fraction of the time.
Open issuance dashboard →Compliance & review
Review the queue. Decide on the record.
Wallet profiles, review queue, issuance ops, and an audit log of every administrative action — Supabase Auth gated, allow-listed.
Open issuance dashboard →Admin · allow-listed access