Funds
NGO keeps programme money.
ReliefPay records card credits, claims, and payout references. The NGO still pays vendors from its own account and keeps custody of programme funds.
Trust center
Built for field money.
ReliefPay is designed for NGOs that need card-based aid without losing control of funds, field operations, vendor payments, or the audit trail.
Cards
Balances are checked server-side.
The vendor terminal subtracts pending offline spend locally, then the backend verifies programme, card, nonce, vendor assignment, and remaining entitlement before a claim can move to payment review.
Vendors
Shops are approved before terminal access.
A vendor cannot simply open the terminal and get paid. ReliefPay or the NGO assigns approved shops to a programme and issues access only after verification.
Data
Evidence without public recipient identity.
Operational proof uses programme IDs, card hashes, claim references, and settlement records. Recipient names are not needed in the public proof story.
Offline
Offline claims are stored, sealed, and reviewed.
Field claims can queue on the device when connectivity drops. Sync never destroys field data, but risky or malformed claims stay visible for operator review.
Audit
Exports are designed for funders and finance teams.
The audit workbook summarises card balances, transactions, claims, settlements, and proof notes for the selected programme.
Readiness checklist
What has to be true before field use.
01
Programme created and card quantity confirmed
02
Invoice sent, paid, and marked in Admin Orders
03
Cards provisioned, scanned, activated, and shipped
04
Vendors verified and assigned to the programme
05
Cards funded before the first field transaction
06
Claims reviewed, vendors paid, and audit exported