Telco
Your wallet already reaches every subscriber. Saleem connects it to institutional and cross-border payment flows through licensed partners.
Value, measured your way: institutional payments landed, wallet activity, float, transaction volume, share of subscribers reached by basic phone.
Agency and payroll runs credited to your wallet by API, with a reconciliation file.
Six client surfaces are built and demonstrable against mocked services. The production backend, licensed-partner connections and independent security testing remain pre-launch work.
Where the legal framework, licensed partners and settlement route permit it, value from abroad can land on the subscriber's existing number.
The exchange rate is set by the licensed partner, not by Saleem.
Console, screening, records and exports on your infrastructure, in local currency; no new consumer app.
No new consumer app: the subscriber keeps the handset, the SIM and the number. Nothing to install, nothing to migrate.
Five steps, from the sending institution to the counter.
What can be said today, and nothing beyond it.
You keep the subscriber and the wallet. Saleem provides the settlement layer, the payer console and the compliance record; the commercial arrangement is set per operator.
Who does what, and who answers for it.
The subscriber, the SIM, the number and the wallet stay yours.
Recipient balances are to be held by a licensed custodian and accessed through Saleem's interfaces; keys do not sit on the handset. This is the target operating model at launch.
The operator provides USSD, SIM Toolkit and the SIM estate as a channel. Licensed partners perform regulated money movement, custody, conversion and payout as required in each jurisdiction. Saleem provides instruction validation, screening orchestration, routing, records and reconciliation under the agreed operating model.
Saleem answers for screening and for the record regulators require. The operator answers for subscriber identity and its own licence conditions.
Where the operator runs a wallet, Saleem credits it by API and the operator's own menus carry the session. Where it does not, short-code sessions route to Saleem's handler over a secure connection, and where SIM Toolkit is used the applet is provisioned over the air to SIMs already in the field. No core network change is required.
Six client surfaces are built and demonstrable against mocked services. The production backend, licensed-partner connections and independent security testing remain pre-launch work.
Six client surfaces are built and demonstrable against mocked services. The production backend, licensed-partner connections and independent security testing remain pre-launch work.
Tell us which markets you run, which wallet your subscribers hold and what your short-code platform looks like, and we will scope the integration and the commercial shape together.