Skip to content
Wallets and payouts

A wallet per beneficiary, payouts by the batch

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.

Illustration of an executed payout batch: number of beneficiaries, total amount and failed lines.

Payout batch

ORD-2026-0148

Executed
Beneficiaries
124
Total amount
62,000.00 MAD
Failed lines
0

Illustrations. Names and amounts are fictional.

Several wallet types

Gift, meal, cashback, expense reimbursement: each type carries its own rules of use, expiry and acceptance.

Checked payout batches

A batch is uploaded, checked and approved before it executes. Failed lines come back with their reason, without blocking the rest.

Traceable movements

Every credit and debit carries its date, its author, its reason and its document. The history exports for accounting reconciliation.

Checks before execution, not after

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.

Illustration of an executed payout batch: number of beneficiaries, total amount and failed lines.

Payout batch

ORD-2026-0148

Executed
Beneficiaries
124
Total amount
62,000.00 MAD
Failed lines
0

Illustrations. Names and amounts are fictional.

Approval that scales with the amount

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.

Illustration of a transaction feed with the cashback credited for each one.

Cashback credited

Rule applied : 5% — Food

MerchantPurchaseCredited
Épicerie Bab Doukkala240.00+12.00
Marché Central180.00+9.00
Boulangerie Nakhil60.00+3.00

Illustrations. Names and amounts are fictional.

From one transfer to a hundred beneficiaries credited

  1. Fund

    The company wallet is credited by transfer; the available balance becomes the ceiling on what you can distribute.

  2. Upload the batch

    You import the list of beneficiaries and amounts, by file or by API, and the platform checks it.

  3. Approve and execute

    Once approved, the batch executes and hands you back the detail line by line, executed and failed alike.

Where they actually earn their place

Three flows payout batches simplify.

Payroll and HR

One-off bonus

A single payment to part of the headcount, uploaded once, approved by two people and evidenced by one export.

Expenses

Expense reimbursement

Approved expenses feed a reimbursement batch, credited to the employee's wallet instead of an individual transfer.

Partner network

Settling affiliates

Periodic merchant settlement goes out as one batch, with the detail of the transactions behind it.

Questions about wallets and payouts

What happens if one line in a batch fails?

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.

Can a payout batch be cancelled?

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.

Can a beneficiary hold several wallets?

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.

How do movements reconcile with accounting?

Every batch and every movement exports with its identifiers, amounts and timestamps, to be matched against the corresponding bank debit.

Set up Wallets and payouts

Tell us the volume, the rhythm and the rules you have in mind. We reply with a costed proposal and a rollout schedule.