For business
Gifting your finance team will actually sign off
Staff rewards, client gifts, festive programmes and incentives — issued in bulk, controlled by budget, approved by someone other than the person who requested it, and reconciled to the naira.
Three controls, not three reports
Budgets are enforced
A programme cannot issue past its budget. Cards awaiting approval consume budget too, so two approvals in the same afternoon cannot quietly overspend it.
The maker is never the checker
Whoever raises an issuance cannot approve it. Not a policy in a handbook — the system refuses.
Unspent value comes back
Value on cards nobody accepted can be reclaimed to the programme. Cards a recipient already accepted are theirs and are never clawed back.
What companies use it for
- Staff rewards and long-service recognition
- Festive and end-of-year gifting at scale
- Client and partner appreciation
- Sales incentives and spot bonuses
- Referral and loyalty programmes
- Conference, event and research incentives
How a programme runs
- 1Fund a programmeOne transfer sets the budget. Every card issued draws against it.
- 2Upload your listNames, emails and amounts. Each row is checked against the remaining budget on its own, so a bad row cannot take the batch down.
- 3Someone else approvesThe request goes to an approver who was not the requester. Their decision is recorded with a reason.
- 4Recipients chooseEach person gets a card they own and spend at any verified store — you are not picking gifts for two hundred people.
- 5ReconcileIssued, accepted, spent and reclaimed, to the naira, from the same ledger that moved the money.
If you would rather not use a dashboard
There is an API for issuance, approval workflow and reporting, with signed webhooks so your own systems learn when a card is issued or accepted. Sandbox keys need no approval.
Read the developer docs