Project

Nzitsa Pay

The payment operations platform I built for Nzitsa products, connecting real internal payments to checkout, merchant records, developer APIs and finance review while public access is being prepared.

Processing internal Nzitsa payments; public access closedPayment infrastructureFinancial operationsDeveloper platforms

Illustrative Nzitsa Pay sandbox payment workspace and mobile checkout preview

Why I built it

Nzitsa Academy, AI Labs and future ventures need a consistent way to request and understand payments. A one-off integration can collect a response from a provider, but it leaves a wider operating question: who initiated the payment, which product owns it, what did the customer agree to, and what evidence can finance rely on later? I built Nzitsa Pay to make those relationships explicit across internal Nzitsa products.

Product and engineering approach

The platform gives each organisation projects, roles and separate sandbox and production environments. A product can create a payment intent through an API or direct a customer to hosted checkout. Merchants can prepare reusable collection links and invoices, associate payments with customer records, search transaction history and request private reports. Project-scoped API keys and signed webhooks connect these flows back to the product that initiated them.

The harder engineering work sits after the checkout screen: idempotent confirmation, durable provider events, financial records, reconciliation and recoverable operations. Those mechanisms are why the product treats a displayed payment status differently from independently verified collection or settlement. The public Nzitsa Pay website explains the product; the images below are explicitly illustrative sandbox previews.

Current stage

Nzitsa products already use the platform for real internal payments. Public onboarding remains closed while we refine the service and pursue the appropriate Bank of Zambia licence. The public site can explain the product without inviting outside businesses to transact. The attached sandbox examples show how checkout, merchant operations and developer tooling are designed; their zero verified collections do not describe the live internal service.

Internal customer, credential and financial records are intentionally omitted. Public release and wider business availability will be described only after the relevant operational and regulatory steps are complete.

Photos and product views

Select an image to inspect it at full size. Captions explain what each view shows.

Illustrative mobile money checkout in the Nzitsa Pay sandbox — Hosted checkout preview with a stated total, network choice and test-payment label.

Full mobile layout of an illustrative Nzitsa Pay sandbox checkout — The complete mobile checkout view; this is an illustrative sandbox payment.

Illustrative Nzitsa Pay merchant payment link with sharing controls — Reusable payment link and QR sharing in a sandbox merchant workspace.

Illustrative Nzitsa Pay invoice preview for a test customer — Invoice preview connects an itemised request to a customer and payment terms.

Illustrative Nzitsa Pay customer records screen — Customer records keep contact and reference information in the selected project scope.

Illustrative Nzitsa Pay private finance report form — Finance report preview with selected records, date range and CSV or PDF options.

Illustrative Nzitsa Pay API key and scope settings — Developer controls for project-scoped API credentials.

Illustrative Nzitsa Pay organisation settings screen — Organisation profile and operational contact settings.

Nzitsa Pay sandbox overview showing no verified collections — Raw sandbox overview distinguishes checkout activity from verified collections.

Nzitsa Pay sandbox payment search with unverified example records — Raw payment view labels the sample records as unverified and shows no verified collection.

The problem

A checkout button is only the beginning of a payment. Businesses also need to know which project, customer, invoice and payment attempt a transaction belongs to, and what financial evidence confirms it.

My contribution

I built Nzitsa Pay as a shared platform for Nzitsa products and continue to shape its merchant workflows, developer integration and accountable finance operations.

What the platform contains

The implementation includes payment intents, hosted checkout, reusable links, invoices, customer records, scoped API keys, webhooks, merchant search and private finance reporting.

Current boundary

Nzitsa products already use the platform for real payments internally. Public use is closed while the team refines the platform and pursues the appropriate Bank of Zambia licence. The screenshots show illustrative sandbox data, not internal transactions.