Several wallet types
Gift, meal, cashback, expense reimbursement: each type carries its own rules of use, expiry and acceptance.
The wallet is the shared foundation under the other products: it holds the balance, records the movements, applies the rules. Payout batches are how you fund it in bulk, with checks before execution.
Gift, meal, cashback, expense reimbursement: each type carries its own rules of use, expiry and acceptance.
A batch is uploaded, checked and approved before it executes. Failed lines come back with their reason, without blocking the rest.
Every credit and debit carries its date, its author, its reason and its document. The history exports for accounting reconciliation.
A payout batch is verified before it goes out: unknown beneficiaries, implausible amounts, insufficient balance. You fix a pending batch rather than chase transfers that already left.
Payout batch
ORD-2026-0148
Illustrations. Names and amounts are fictional.
Past a threshold you set, a batch requires a second approval from someone other than the person who uploaded it. The rule lives in the platform, not in an internal memo.
Cashback credited
Rule applied : 5% — Food
| Merchant | Purchase | Credited |
|---|---|---|
| Épicerie Bab Doukkala | 240.00 | +12.00 |
| Marché Central | 180.00 | +9.00 |
| Boulangerie Nakhil | 60.00 | +3.00 |
Illustrations. Names and amounts are fictional.
The company wallet is credited by transfer; the available balance becomes the ceiling on what you can distribute.
You import the list of beneficiaries and amounts, by file or by API, and the platform checks it.
Once approved, the batch executes and hands you back the detail line by line, executed and failed alike.
Three flows payout batches simplify.
Payroll and HR
A single payment to part of the headcount, uploaded once, approved by two people and evidenced by one export.
Expenses
Approved expenses feed a reimbursement batch, credited to the employee's wallet instead of an individual transfer.
Partner network
Periodic merchant settlement goes out as one batch, with the detail of the transactions behind it.
It comes back with its reason and doesn't stop the others executing. You fix that line and replay it without re-uploading the whole batch.
As long as it hasn't executed, yes: a batch awaiting approval can be cancelled from the portal. Once executed, the correction is a reversing movement, traced as such.
Yes. The same beneficiary can hold a meal wallet, a gift wallet and a cashback wallet, each with its own rules and its own balance.
Every batch and every movement exports with its identifiers, amounts and timestamps, to be matched against the corresponding bank debit.
Tell us the volume, the rhythm and the rules you have in mind. We reply with a costed proposal and a rollout schedule.