NGO

Every payment recorded once

Lower cost-transfer ratio, faster time to recipient, and one audit trail from treasury to household, reported in the units you already use.

Where it stops today

Cash and voucher assistance still runs through a single financial service provider or an informal network in the corridors that need it most, and the cost-transfer ratio sits near 17 cents on the dollar.
Timeliness is days to weeks; the household is paid when the distribution reaches it, not when the batch is approved.
Reconciliation and donor reporting are reconstructed from field logs after the cycle closes; leakage surfaces, if at all, in post-distribution monitoring.

What changes

Value, measured your way: cost-transfer ratio, cost per beneficiary, time to recipient, execution success rate, traceability, reconciliation and donor-report time, leakage and deductions, coverage by handset, protection incidents per cycle. No figure is claimed for Saleem until a pilot has produced it.

Cost-transfer ratio (the cost of delivering each dollar)

All-in, cents per dollar, against your prior cycle. A pilot should test whether digital merchant spend reduces cash-out events and total delivery cost against the prior cycle; Saleem will not claim a saving until the measured result exists.

The peer pilot reported 29 percent lower; the digital floor on record is 1.4 to 6.7 cents.

Time to recipient

Median and 90th percentile, by handset, into the wallet the household already holds, or one we provide.

The peer pilot reported 10 hours saved per payment.

Traceability and reconciliation

A record for every payment, by design; a same-day file in the formats your treasury and your programme systems read (camt.053, camt.054, MT940, BAI2, and the per-recipient CSV for SCOPE, CashAssist and HOPE).

No dependence on a single informal transfer network.

How a disbursement runs

Four steps, from the agency treasury to the household.

Agency treasuryThe beneficiary list is uploaded and validated row by row, then approved by a second person
SaleemEach payment is screened, routed and recorded, and the recipient wallet is credited on the phone number
Recipient handsetThe household is notified and holds the value on the phone it already carries
Merchant or cash-outSpend at a Saleem merchant, or withdraw at a licensed exchange house or agent

Who pays, and what it saves

The structure, not a projection.

The agency pays for the software and the setup; the recipient pays nothing.
Saleem charges no fee to sender or recipient; FX conversion applies where currencies convert, at the licensed partner's rate. Institutions pay Saleem.
Licensed exchange houses and agents earn their own margin; merchants pay an acceptance fee where value is spent rather than withdrawn.
The agency keeps the programme and the beneficiary relationship; Saleem is the rail, not the badge, and runs white label where you want it.

What the agency keeps

Who does what, and who answers for it.

Programme ownership

Eligibility, entitlement and the beneficiary relationship stay with the agency. Saleem never decides who is paid.

Regulated activity

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.

Custody

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.

Compliance responsibility

The agency answers for programme eligibility and donor reporting; Saleem answers for screening, records and export; each partner answers for its own licence.

Reconciliation

Every batch and every failure is accounted for per recipient, exportable in treasury formats: camt.053 and camt.054, MT940, BAI2 and CSV.

Running a government social cash or payroll programme, rather than an NGO one? The government page covers it.

Programme flexibility

The mechanics, once the value case is made.

The rail is designed to be programmable per programme. The same infrastructure delivers unconditional cash or category-restricted entitlements redeemable at tagged merchants; the programme designer chooses the conditionality a donor mandate or a government programme requires, and the audit trail is identical either way. Zakat and waqf disbursement run as programme types on the same rail. This is a designed capability, because Saleem holds each programme's funds separately, not yet live.

What exists today

Six client surfaces are built and demonstrable against mocked services. The production backend, licensed-partner connections and independent security testing remain pre-launch work.

Saleem desktop console: bulk disbursement file validation — Bulk disbursement validation, before second-person approval

Saleem desktop console: treasury export format list with camt.053, camt.054, MT940, BAI2 and CSV — Treasury export in bank formats

Six client surfaces are built and demonstrable against mocked services. The production backend, licensed-partner connections and independent security testing remain pre-launch work.

Bring us a programme and your last cycle's cost-transfer ratio

Tell us the corridor, the cohort and the reporting you owe your donor, and we will walk the flow end to end.

Talk to the team

Questions partners ask

What about Syria sanctions? What is live today, what is designed but not built, and can we audit it and export to our bank? Who has used this, and what happened? How does Saleem compare with other digital aid rails?

All twelve questions