Composable rules
By merchant, by category, by minimum amount, over a period: rules combine and apply to whichever transaction satisfies them.
You set the rule — a percentage, a threshold, a merchant, a category — and the amount is credited to the customer's wallet once the eligible transaction clears. No card to stamp, no points to convert.
By merchant, by category, by minimum amount, over a period: rules combine and apply to whichever transaction satisfies them.
As soon as the transaction is eligible, the amount lands on the beneficiary's wallet. No claims to handle, no conversion to explain.
Caps per customer and per period, an overall campaign budget: the spend is bounded before it is committed, not observed afterwards.
Cashback lands on a wallet usable across the same network. It doesn't leave your ecosystem: it funds the next visit instead of being cashed out and forgotten.
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.
Each credit is tied to its rule and its transaction. You read the real cost of a campaign and the behaviour it triggered, rule by rule.
Amount
500.00 MAD
Available balance
320.00 MAD
Valid until
31/12/2027
Illustrations. Names and amounts are fictional.
You describe the trigger — merchant, category, amount — and the reward, as a percentage or a fixed amount.
You set caps per beneficiary and for the campaign, along with the validity period.
The rule applies to incoming transactions; you track credits issued and budget consumed.
Three mechanics cashback makes simple.
Retail
A boosted percentage on a product family for two weeks, with a per-customer cap and a bounded total budget.
Merchant network
A reward on the first transaction at a newly affiliated merchant, to get footfall started.
Employee programme
Cashback on everyday spending that adds to the budget already given, without raising the amount distributed.
Once the transaction is recognised as eligible by the rule. The delay depends on the merchant confirming the transaction; the credit and its trigger stay linked in the history.
Stacking is a configuration choice. You can allow several rules to add up, or keep only one, according to a priority you define.
Through caps: a maximum per beneficiary and per period, and an overall budget beyond which the rule stops crediting. Both are set before activation.
It funds a wallet spendable across the network. Withdrawal conditions, if any, depend on how the programme and the wallet type are configured.
Tell us the volume, the rhythm and the rules you have in mind. We reply with a costed proposal and a rollout schedule.