# When aid becomes spendable

Programme comparison card · 27 September 2026 · Daily Special, Signal 4

## The bounded question

What evidence would show that a stablecoin-enabled humanitarian payment route improves delivery relative to an existing route in the same setting?

This is an authored comparison method, informed by four public primary sources reopened on 27 September 2026. It is not a field evaluation. No recipients, accounts or payment systems were accessed. Research completion does not establish programme success or an investment decision.

## Evidence anchors

- Circle's 25 September 2026 announcement describes support for UNDP and WFP; comparative delivery outcomes are not reported there. [Circle][1]
- UNHCR's 15 December 2022 pilot description connects USDC in a smartphone wallet to MoneyGram cash withdrawal. This is a historical route, not evidence of current availability. [UNHCR, UN-hosted release][2]
- WFP describes Building Blocks as a privately managed network for coordinating assistance. Its architecture supplies context, not results for the new stablecoin programmes. [WFP][3]
- WFP's SCOPE manual separates payment instructions from reconciliation against a provider's transaction report. [WFP manual][4]

## Define the finish line before comparing

Conceptual route: programme authorizes assistance → provider transfers value → recipient can spend or withdraw the intended amount → programme reconciles delivery and exceptions.

For each corridor and payment cycle, identify the existing route, recipient population, currency, promised amount, period, usable-money endpoint and deadline. Compare similar cases and report allocation methods. A before/after comparison needs disclosure of changes in security, exchange rates, connectivity and provider coverage. Do not describe an unmatched comparison as causal proof.

| Dimension | Record for both routes | Evidence that could support an improvement |
| --- | --- | --- |
| Full delivery cost | Programme fees, network fees, FX spread, cash-out charges, staff/recovery work and setup cost; recipient charges and travel time separately | Lower cost at the same delivery standard, with payer, subsidies and setup-cost allocation visible |
| Recipient access | Eligible population, invitations, enrolments, payment attempts, spendable receipts, exclusions and reasons | More of the intended population receives usable value by the same deadline; missing follow-up remains visible |
| Reconciliation | Matched instruction/provider/delivery records; unresolved count and value; age of exceptions; staff time | Fewer or shorter-lived unresolved exceptions without concealing failures or shifting work to recipients |

Suggested calculations: access rate = recipients with usable funds by deadline / eligible intended recipients. Also report attempt completion = completed attempts / all attempts. Cost per completed delivery = total programme delivery cost / completed deliveries; keep transfer principal separate. Publish total cost and the completion denominator together. Do not add recipient hours to dollars without an explicit valuation method, or double-count a fee reimbursed by the programme.

Freeze these definitions before results arrive. Show typical and slow-tail delivery times. Report exclusions caused by identification requirements, device access, connectivity or provider liquidity. Separate one-off launch support from costs likely to persist, and explain who pays when promotional support ends.

Reconciliation should retain an aggregate view of missing, duplicate, reversed and failed transfers, with a stated observation window. A transaction hash can support one link in the route; it does not alone demonstrate usable funds or resolve the programme's books. Public reporting should use aggregates and methods, never beneficiary names, wallet addresses or sensitive case records.

## Present comparison

The reviewed materials do not provide a matched result for the newly announced programmes across these three dimensions. They therefore do not settle which route is cheaper or more accessible. Record the new route and its comparator side by side when results become available; leave unreported cells unfilled.

I would revisit the delivery judgment when a published evaluation supplies a common cost boundary, recipient denominators, reconciliation outcomes and the comparator's conditions. A selective pilot may justify another test without justifying broad deployment. This card proposes that evaluation threshold; it does not claim the test has happened.

## Sources and dates

[1]: https://www.circle.com/pressroom/circle-foundation-announces-support-for-united-nations-development-programme-and-world-food-programme-to-advance-digital-payments-for-development-and-humanitarian-action
[2]: https://ukraine.un.org/en/211593-unhcr-launches-pilot-cash-based-intervention-using-blockchain-technology-humanitarian
[3]: https://www.wfp.org/building-blocks
[4]: https://usermanual.scope.wfp.org/cash-accounts/content/cash_accounts/performing_distribution_reconciliation/performing_distribution_reconciliation__cash_based__.htm

Circle event date: 25 September 2026. UNHCR event date: 15 December 2022. WFP pages: living explanatory documentation; no publication date established for the retrieved versions. All four reviewed on 27 September 2026, Hong Kong time. Institutional descriptions are attributed accounts, not independent audits. The comparison definitions and suggested measures above are authored analysis.