how it works

Four steps, one thread. You integrate once. We sell, collect and settle. Here is what actually happens between a customer in Nairobi tapping pay and money landing in your account.

  1. 01

    step one. integrate once.

    One integration, whichever shape suits you. Drop in the hosted checkout and be live in days, or integrate the API and keep your own front end. If you already run a billing engine you like, keep it: your engine owns the schedule and calls Settld to execute each charge. Sandbox first, real rails behind it.

  2. 02

    step two. we sell as the legal seller.

    When your customer buys, the sale happens between them and Settld. Our name carries the contract, the invoice, the tax and the consumer-protection duties in that market. Your terms govern the product. Your brand fronts the experience. The legal seller changes, and that single change is what unlocks everything below.

  3. 03

    step three. we collect across every rail.

    The customer pays the way their market actually pays. Cards acquired in-market so they present as domestic. M-Pesa, MTN MoMo and Airtel Money with proper mandates where the network supports them. Capitec Pay, instant EFT, vouchers where they win. Routing is picked per market and per transaction. You never think about it.

  4. 04

    step four. we settle you, net.

    Collections roll up across markets and currencies into one consolidated settlement in the currency you elect. Every payout is itemised gross to net: the sale, the fees, the tax we carried, the reserves. Settlement runs on a fixed monthly cycle: transactions accrue through the month, the payout is created on the first, and funds are sent by the fifteenth. Automatically, every cycle, with a threshold you control.

05 / integration

what integration actually involves

The honest answer for your engineering team. Hosted checkout is a redirect or embed with webhooks for state changes: days, not months. API integration is a single call to open a session, signed webhooks at every state change, and server SDKs in preview. Recurring needs one decision up front: our billing engine drives the schedule, or yours does and executes through us. Either way you get the same ledger, the same reporting and the same sandbox to prove it all before anything touches production. Start on the developers page, or book a technical walkthrough and bring your hardest question.