MAP Earmarkable digital euro
FR Discuss your project
Two professionals test a journey together on a mobile device with no readable content.
Application to be explored

Carrying earmarked flows in your software

A programme operator or software publisher may need an electronic money infrastructure for the earmarked flows it organises for its clients. This is a line of work: the allocation of roles is decisive and is fixed at scoping.

Discuss your project Request a demo

This page describes a project framework. MAP announces neither a white-label offer nor a freely accessible public interface: the availability of such arrangements must be confirmed for your scope before being presented as established.

The central question is that of roles: who is the funder, who administers the programme, who contracts with the end user, who answers their requests, and who bears which obligations.

What the relevant decision-makers ask for

Product management

What do our users see and understand?

A journey to be defined together, with explicit acceptance and refusal messages.

Technical management

How do we integrate the service?

Interfaces documented at scoping, a test environment, shared acceptance testing.

General management

What contractual allocation and what obligations?

A written allocation of roles, and identification of the obligations borne by each party.

Support

Who answers a blocked user?

An explicit boundary between what falls to the programme and what falls to the service.

The journey, from decision to operation

01

Allocation of roles

Funder, operator, issuer, distributor, end user: each role is identified and documented.

02

Functional scoping

Rules required, user journey, messages, reports expected by your clients.

03

Integration

Technical exchanges, test data sets, checking of edge cases and refusals.

04

Shared operations

Allocation of support, incident monitoring, periodic review points.

Scoping points

  • Who contracts with the end user, and in which role.
  • The onboarding obligations applicable to each party.
  • The experience expected when an operation is refused, and its wording.
  • The data exchanged and each party’s role with regard to its processing.
  • The actual availability of the integration arrangements for your scope.
  • The allocation of support and the service commitments to be agreed.

Project questions

Do you offer a white-label solution?
This arrangement must be confirmed for a given scope. It is not presented here as available.
Is there a freely accessible public interface?
No. The technical documentation is provided during scoping, for the scope adopted. This site publishes neither sample requests, nor keys, nor service addresses.
Who bears the regulatory obligations?
They are allocated according to the roles actually held by each party. This allocation is established at scoping and set out in the contract.
Can we test before committing?
A test environment on fictitious data is part of the preparation stage. Its arrangements are defined with your technical teams.
Ledger and blockchain
What the ledger records, its governance and the complementary controls required.
Get in touch

Explore an integration

Present your platform, your earmarked flows and the allocation of roles envisaged.

Discuss your project