Bank of Botswana Regulatory Sandbox — Eligibility Assessment Stage
Gaborone · Botswana · +267 723 06377
Partnership

Connect once. Reach everyone.

IPA is built to be the rail between Botswana's payment service providers, banks, mobile money operators and corporate disbursers. Partnership is how that rail comes together — one technical integration, one commercial agreement, one supervised connection point.

Currently engaging
  • Mobile money operators — MyZaka (Mascom), Orange Money (Orange Botswana)
  • Commercial banks — BancABC, Stanbic, FNB, Absa
  • Mobile network operators — Mascom, Orange, BTC (direct USSD & rail integration)
  • Corporate disbursers — payroll, supplier and grant programmes
Why partner with xL · 01

Four reasons partners say yes.

IPA is designed to make the path from "we'd like to be reachable across providers" to "we're live in production" the shortest possible route — without compromising on regulatory posture, technical rigour, or the partner's commercial interests.

01 / REACH
One integration, full national reach
A single REST integration connects you to every other PSP, bank and wallet on the network. No bilateral agreements. No N×N integration matrix.
02 / SUPERVISION
Compliance-native, not bolted on
AML screening, immutable logs, and real-time supervisor visibility live in the transaction path itself. Your compliance team inherits this; they don't rebuild it.
03 / TIME
Predictable onboarding
A defined four-phase path from first conversation to go-live, with clear ownership of each step. We respect that you have a roadmap and don't impose ours on top of it.
04 / STANDARDS
Documented, auditable, open
OpenAPI specs, integration guides, and architecture documentation are shared under NDA early in the process. You evaluate us on the artefacts, not the pitch deck.
Who partners with us · 02

Three audiences. One agreement.

We work with three groups, each engaging IPA in a different way. The partnership process is unified — the same discovery, technical, and sandbox steps — but the questions we work through together depend on who's joining the rail.

PSP / BANK / MNO
Provider partners

Banks, mobile money operators, and mobile network operators integrate as PSPs — participants whose customers can send and receive across the rail. The conversation centres on technical fit, settlement model, and how your existing back office connects.

  • Single REST integration, OpenAPI documented
  • PSP Participant Agreement scope & commercials
  • Reconciliation & settlement against your ledger
  • USSD provisioning if you're an MNO (direct, no aggregator)
CORPORATE CLIENT
Disburser clients

Companies that need to pay many people — payroll, suppliers, grant recipients — without forcing every recipient into the same provider. The conversation centres on volume, file format, and the operations model your finance team needs.

  • Bulk B2P disbursements across all six PSPs
  • Banked and unbanked recipients on one file
  • Built-in reconciliation & status reporting
  • API or operations-portal access depending on your stack
REGULATOR / POLICY
Supervisory partners

The Bank of Botswana and adjacent regulators engage with IPA primarily as a supervised system. The conversation centres on governance, the real-time supervisor view, AML reporting, and how partner risk is managed across the network.

  • Real-time supervisor dashboard & data feed
  • NPS Act and AML/CFT alignment documentation
  • Participant due-diligence and onboarding governance
  • Incident, escalation, and continuity-of-service framework
How partnership unfolds · 03

A defined path from first conversation to live.

Every partnership runs through four phases, regardless of audience. Each phase has clear inputs, clear outputs, and clear owners. We don't over-specify durations — partner readiness varies — but the sequence is fixed.

PHASE 01
Discovery
Mutual fit conversation. We share product, architecture, and compliance documentation under NDA. You share your roadmap and constraints. We agree whether to proceed.
Owners: Both teams · sponsor & product lead
PHASE 02
Technical fit
API walkthrough, integration spec review, security & data residency assessment. Your engineering and compliance teams meet ours. We document the integration plan.
Owners: Engineering, compliance, security
PHASE 03
Sandbox testing
Integration against the IPA sandbox environment. End-to-end test cases. AML and reconciliation validation. The Participant Agreement is finalised in parallel.
Owners: Engineering, legal, BoB observer
PHASE 04
Go-live
Production cutover under a phased traffic ramp. Joint operations review. Steady-state hand-off to support. First settlement cycle completed and reconciled.
Owners: Operations, finance, support
The mutual ask · 04

Partnership runs both ways.

We're explicit about what we ask from partners and what partners can ask from us. Honest expectations early prevent expensive surprises later.

What we ask of you

As a partner
  • An engaged sponsor Someone senior enough to unblock procurement, legal, and IT when the four-phase process meets your internal governance.
  • Engineering & compliance availability Time from your technical and compliance teams during Phases 02 and 03 — not full-time, but reliably available for working sessions.
  • Honest constraints Tell us what your roadmap, ledger system, or regulatory commitments require. We design around real constraints; we waste time around hidden ones.
  • Confidentiality We share commercial terms, technical specifications, and roadmap detail under mutual NDA. Standard for the sector; we expect it observed.

What you can ask of us

In return
  • Documentation, not assertions We provide OpenAPI specs, architecture diagrams, security model, and compliance documentation. You evaluate the artefacts, not the slide deck.
  • Predictable engagement A named point of contact, scheduled working sessions, written outcomes, and clear next steps after every meeting.
  • Engineering access When Phase 02 needs deep technical questions answered, you talk to engineers, not account managers.
  • Direct line to the CEO Until we're large enough for this to break, the founder is reachable. Escalations don't queue.
Start a conversation

If any of this describes you.

We'd like to hear from you. Send a short note — what you do, what you're trying to solve, and how you'd want to engage — and we'll come back to schedule a Phase 01 discovery call within a few working days.