Overview

Bizzle is a commerce and operations platform for the Tanzanian market. The payment layer accepts mobile money (M-Pesa, Airtel Money, Tigo Pesa, HaloPesa), cards, bank transfer, and USSD push, plus subscriptions, invoicing, marketplace escrow, payouts, and referrals.

Everything is exposed through a single REST API at /v1.

Base URL

All requests go to:

https://api.bizzle.my/v1

The same host serves both test and live traffic — which one you get is determined entirely by your API key.

The one-API design

The dashboard, the SDKs, and the CLI all consume the same /v1 handlers. There is no separate “internal” API. This is deliberate: it means the API is dogfooded on every dashboard interaction, so it cannot silently drift from what the product does.

Verticals

Vertical	What it covers
Payments	One-time payments, checkout links, refunds
Subscriptions	Weekly / monthly / yearly billing and renewals
Invoices	SMS invoice links with automated reminders
Payouts	Automatic vendor settlement and merchant-initiated payouts
Marketplace	Escrow-style hold and release between buyers and sellers
Events	Tiers, promos, orders, refunds, check-in, transfers
Memberships	Recurring memberships with pause / cancel / churn
Employees	Clock-in / clock-out and payroll / statutory remittance
Government payments	Control-number style government collections
Retail & Hospitality	Storefront orders, bookings, and operations
Integrations	Accounting / external system connectors

Test mode is isolated

Test keys route to a deterministic sandbox provider. Test records are tagged and skipped by background jobs, so sandbox data never touches the live pipeline. Events carry livemode: false. See Authentication.

Next steps

Settlement model — how fees and payouts work.
Quickstart — your first payment and webhook.
API Reference — generated from the OpenAPI contract.