Product, engineering and operations teams Tailored programme

Embed earmarked budgets in your users’ journey.

Your service organises funding, a collection or a support journey. Pair it with a programme in earmarkable digital euros: euros, held in a real account, that can only be used for what you decided. Those rules, set before the money is spent, are the earmarking. Your users hold a real account and a universal payment card. Every payment is recorded on a tamper-proof blockchain.

Two professionals test a journey together on a mobile device with no readable content.

You want to…

You want to connect your product journey to budgets and payments. You want to know who holds the funds, who decides the rules and who receives which information.

We have the solution: an earmarked programme, backed by an authorised electronic money institution. The roles are written down, and your service receives tamper-proof evidence of every payment.

You choose who, when, how much, where and what for.

Concrete benefits

What the programme changes for your teams.

Payment in service of the journey

The programme starts from what your user is trying to do, not from our tooling.

Responsibilities that are defined

Platform, funder, beneficiary and supplier hold explicit roles, written down before the first payment.

Information your service can use

Statuses, rules applied and reconciliation data are defined with your teams. For example, €250.00 per user, with authorised suppliers.

Every integration is run with your teams, with no self-service route. The interfaces opened to your service, the contracts and the operating model are settled in the first conversation.

A scenario in three steps

Connecting a product journey to earmarked budgets

The first conversation

You describe the journey, where the funds come from, the rules you want and the information you expect.

Funding and payment

We settle the interfaces retained, the responsibilities and the tests to run.

Tracking and reconciliation

Once validated, the journey links payments, the rules applied and their evidence to the information expected.

Who does what

Funder: Your platform’s customer, or the platform itself, depending on how the programme is organised
Decision-maker: Product and engineering management
Who runs the programme: The platform, with the MAP services retained
Beneficiary: The end user of the journey
Supplier: The suppliers paid within the journey

Roles as they would be defined in the programme, to be confirmed in the first conversation.

What you see

The information exchanged with your service: operation statuses, rules applied and reconciliation data. Each role sees what concerns it, as agreed with your teams.

Related services

The services retained for this need.

The availability level is stated on each service. The services retained are confirmed with your teams, in the first conversation.

Compose a programme

White-label programme Your brand at the front, MAP’s financial services behind it, each party’s role written down and shown to users. Programme electronic money The earmarkable digital euro: euros, on a real account, that can only be used for what you decided. Issued, allocated, used and redeemed within the programme. Accounts and payments A real 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. Earmarking and rules of use You choose who, when, how much, where and what for. 100% of operations are checked before execution. Traceability and blockchain proof Every payment recorded on a tamper-proof blockchain; the proof covers the payment, through to the supplier.

Terms and questions

What we settle with you.

Services, means of payment, rules and tracking are settled in the first conversation, then configured for your programme. The proof covers payments, not the results of your action.

What we establish on the record

The interfaces opened to your programme, the contracts and the operating model are defined with your teams. MAP announces neither a self-service public API, nor an off-the-shelf white label, nor an integration in a few days.

The Poto reference and its limits Compliance centre

Frequently asked questions

Can MAP be integrated into a platform?

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.

Does MAP provide an account, an IBAN and a card?

Yes. A real 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.

What information do my teams get?

Every payment, its status and the rule applied, in real time, in the view set for each role. Authorisation and final settlement remain two distinct steps.

The twelve answers

Get in touch

Let us describe your programme.

Tell us who funds the programme, who uses the funds and what it must make it possible to pay for. A MAP expert gets back to you, with no commitment.

Talk to an expert How it works A MAP expert will get back to you, with no commitment.