Your brand at the front, MAP’s financial services behind it.
We have the solution, built with you. You carry the experience and the identity of the programme. MAP provides the financial services, and each party’s role stays written down and shown to users.
The experience is yours. The issuance of electronic money and the obligations attached to it remain with the authorised institution.
Three possible levels
Skinning an existing journey, a dedicated programme space, or integration into your own application. Each level is studied, priced and tested separately.
Responsibilities written down
Account opening, support, data, compliance, operations and exit: who does what is settled before go-live.
Your rules
What we set with you, before go-live.
The core is the same for every programme. What varies from one programme to the next is set with your teams, before the first spend.
The level adopted
Skinning an existing journey, a dedicated programme space, or integration into your own application. The level adopted is the subject of a feasibility study, a quotation and acceptance tests.
Example: a dedicated programme space
The branded journey
What can be customised and the branded journey, screen by screen.
Example: your brand displayed, the issuer shown
The services embedded
The financial services embedded in the product and the interfaces actually available.
Example: money, earmarking, payments
Who does what
The allocation of account opening, support, data, compliance and operations.
Example: written down before go-live
Deliverables and how it works
What we put in place with you.
✓What can be customised and the branded journey.
✓The choice of financial services to embed and the interfaces available.
✓The allocation of account opening, support, data, compliance and operations.
✓The conditions for leaving the programme and getting your data back.
A clear framework
A precise framework, known before you sign.
The proof covers the payment: amount, supplier, date, rule applied. The rest is written here, so that nobody discovers it afterwards.
White label is not the hire of an authorisation
White label means neither a white-label bank, nor the hire of an authorisation, nor the automatic assumption of all your obligations.
Nothing is promised without validation
A native app, interfaces, multi-organisation hosting and a timetable are not promised without validation.
The issuer stays visible
The notices of the issuing institution stay visible to users.
What we show before any commitment. Before any commitment, we have the end-to-end journey validated, along with the notices, the interfaces actually available, the rights per organisation, the support and the exit arrangements.
A worked example
A business software vendor, or the head of a network.
A vendor offers a partner budget inside its own branded space. The payment services and the obligations of each party are built into the journey, validated before it opens.
Level adopted (example)
a dedicated programme space
Brand displayed
the client’s
Issuer of the money
the authorised institution, shown to users
Budget per user (example)
€600.00
Services embedded (example)
money, earmarking (the rules set before the spend), payments
Tests
the end-to-end journey, before opening
Situation and values given as an example. No result and no price is announced.
Yes. The journey, the interfaces and the responsibilities are defined with your technical teams, from the first conversation. The interfaces opened to your programme are set out there. They are opened programme by programme, not as a self-service catalogue.
Yes. An account with an IBAN, incoming and outgoing transfers. A universal payment card, not a prepaid card. Online payment, the QR code and the app, usable anywhere in the world. Your programme’s rules decide where and what they work for.
How much does a programme cost and when can it start?
The terms and the timetable depend on what is covered, the uses, the number of users and the integration. No price and no lead time are announced on this site. A MAP expert will get back to you, with no commitment.
What can we see before committing?
An earmarked payment accepted, then a payment refused. What each role sees in both cases, and the record written to the blockchain. The demonstration draws on the Mes Potos solidarity programme, documented with what it covers, and is set around your own programme.
Tell us who funds the programme, who uses the funds and what it must allow people to pay for. We identify the rules, what you must be able to track and the points that need validation.
