Who
The beneficiaries enrolled in the programme, and nobody else. Instant activation of the account and the card.
How it works
From budget to proof, every payment checked before it is executed.
You choose who, when, how much, where and what for. MAP issues the earmarkable digital euro matching the funds received, checks every operation before it is executed and records every payment on a tamper-proof blockchain. This page describes the full journey, from budget to proof.
- A funder opens the Equipment 2026 programme and safeguards a 7 200,00 € allocation.
- Each of the twelve designated beneficiaries receives 600,00 € on an account, with their own IBAN and universal payment card.
- At the checkout, the drill bought from an approved supplier is accepted for 120,00 €, the purchase outside the category is declined.
- The accepted payment is recorded on the tamper-proof blockchain.
Budget life cycle
Five steps, from collection to tracking.
The budget always follows the same path. What changes from one programme to the next are the rules written at step three.
-
Collection
Funds arrive in euros: a transfer from the funder, donations, a fundraising pot, corporate giving, a grant. Every contribution is linked to the programme it finances.
-
Issuance
MAP issues the earmarkable digital euro up to the funds received, one for one. Nothing is issued without funds received.
-
Earmarking
Your rules are written before the first payment: beneficiaries, suppliers, geographic area, period, ceilings.
-
Payment
The beneficiary pays an authorised supplier: payment card, online payment, QR code, transfer from their IBAN.
-
Tracking
Every payment is recorded on a tamper-proof blockchain. Every role sees it, in real time.
AI supervision across the whole chain. It analyses the supporting documents, checks the programme rule, detects and blocks anomalies. 100% of operations are checked before execution.
Diagram of how it works. For a programme, the rules, the payment methods and what each role sees are settled from the first conversation and set out in the contract.
Four roles
Who does what, from allocation to payment
Four roles share the journey, from allocating a budget through to payment. Each one decides what is theirs to decide, sees what is theirs to see, and everything stays under your control.
- Funder
- Decides on the budget, pays in the funds in euros and sets the rules. The funder is the one who chooses who, when, how much, where and what for. They find every payment of their programme.
- The programme team
- The local authority, the charity or the company that runs the programme day to day: enrolling beneficiaries, allocating budgets, adjusting rules, handling requests.
- Beneficiary
- Has an account with an IBAN, a universal payment card, online payment, the QR code and the app. They spend freely, within the frame that has been set.
- Supplier
- Takes the payment like any other card payment, in store, online or by QR code. No specific equipment, no membership of a closed network.
- MAP
- Issues the earmarkable digital euro, applies the programme’s rules, checks every operation before it is executed and records every payment on the blockchain.
The roles stay distinct: the funder does not allocate individual budgets, the programme team does not issue the electronic money, MAP does not assess individual situations.
Rules before payment
You choose who, when, how much, where and what for
The rules are written before the first payment, and checked before every operation. They are not discovered after the spend.
What for
The suppliers selected, by name or by category.
Where
A town, a department, a region, France, anywhere in the world. Online payments allowed or not.
When
A period of use, with a start date and an end date.
How much
Ceilings per operation, per day, per month. Cash withdrawals allowed, capped or blocked.
What earmarking controls, and what it does not prove
A supplier category frames where the money is spent, not the contents of the basket. Item-by-item control requires an integration and suitable payment data: we look together at whether it is feasible, programme by programme.
Authorisations and settlements
An operation lives twice, authorised then settled
Authorisation and settlement are two distinct events. Confusing them leads to two false readings of the same budget.
| Status | Effect on the budget | What is kept |
|---|---|---|
| Authorised | The amount is reserved against the available budget. | The rule checked before execution, the time stamp, the supplier. |
| Settled | The amount is charged to the budget used. | The payment recorded on the blockchain: amount, supplier, date, rule applied. |
| Refused | No effect: the budget stays available. | The reason for the refusal, given to the beneficiary and to the programme team. |
The control takes place before execution: an operation that falls outside the frame is blocked, not corrected afterwards. That is what allows us to say 100% of operations are checked before execution.
What you see
Each role sees what is theirs to see, in real time
This is not an overall report sent at the end of a period. It is the payment itself, in each role’s view.
| Role | What they are shown |
|---|---|
| Funder | The budget and its consumption in real time, then every payment with its amount, its supplier, its date and the rule applied. |
| Contributor | In a fundraising programme, the use of their contribution, payment by payment. |
| The programme team | The settings, the budgets allocated, the beneficiaries’ requests, the payments and the reasons for refusal. |
| Beneficiary | Their balance, their payments, and the reason for a refusal concerning them. |
| Supplier | The payments they have taken. |
Controls
Checked before execution, recorded after
Two distinct mechanisms, serving the same thing: being able to account for the funds.
AI supervision
Before execution, every operation is measured against the programme’s rules. The AI analyses the supporting documents, checks the applicable rule, detects anomalies and blocks whatever falls outside the frame. 100% of operations are checked before execution.
Proof on the blockchain
After execution, the payment is recorded on a tamper-proof blockchain: amount, supplier, date, rule applied. Neither MAP nor the funder can alter that entry. That is what makes compliance demonstrable rather than declared.
What the proof covers
The proof covers the payment: its amount, its supplier, its date and the rule applied. It covers neither the contents of the basket, nor the delivery of the good or the service. Nor does it cover a social impact, which is assessed with other evidence. No personal data are recorded on the chain. The electronic money issued is not a bank deposit, bears no interest and is not covered by a deposit guarantee scheme.
Seven services
Compose the programme you need
A programme brings together the services useful to your need. None is imposed, and nothing is invoiced before it is adopted with you.
Fund collection
Bring together funds from several funders and link every contribution to the programme it finances.
Programme electronic money
The earmarkable digital euro: euros, on an account, that can only be used for what you decided. Issued, allocated, used and redeemed within the programme.
Earmarking and rules of use
You choose who, when, how much, where and what for. 100% of operations are checked before execution.
Accounts and payments
An account, a universal payment card, a QR code and an app. Your beneficiaries pay anywhere in the world and online, within the rules you set.
Traceability and blockchain proof
Every payment recorded on a tamper-proof blockchain; the proof covers the payment, through to the supplier.
White-label programme
Your brand at the front, MAP’s financial services behind it, each party’s role written down and shown to users.
Local currency and territorial programme
A payment programme serving one area: a scheme holder, participating suppliers, rules of use and tracking.
Going further
How it works, in detail
Three pages develop this journey: what your teams find, how the programme is set up, and which controls apply.
Request a demo
Let us talk about the programme you have to fund.
Describe the budget you have to account for, the beneficiaries and the spending expected.