MAP Earmarkable digital euro
Two specialists connect a test module to a computer in a product laboratory.
Infrastructure

From scoping to day-to-day operation

Integrating MAP means describing a use, settling rules, establishing exchanges with your systems and defining who operates the programme day to day. Responsibilities are allocated explicitly, before the service goes live.

Journey

Four project stages

01

Scoping

Use to be framed, actors, expected volumes, obligations specific to your organisation, reports required.

Deliverable: shared scoping note.

02

Scope validation

Rules adopted, roles and access rights, applicable contractual documents, data exchanged.

Deliverable: scope settled and documented.

03

Preparation and testing

Technical exchanges, test runs on fictitious data, verification of refusal cases and reports.

Deliverable: shared acceptance testing.

04

Operation

Opening of the programme, monitoring of operations, review points, handling of requests and incidents.

Deliverable: programme in service, within a defined scope.

Responsibilities

What falls to whom

Indicative allocation, to be settled at scoping and set out in the contract.
SubjectMAPYour organisationProviders
Issuance and keeping of the ledgerEnsures issuance and the recording of operations.Pays in the funds and approves the framework.Not applicable
Programme configurationImplements the agreed rules.Decides the rules and their values.Not applicable
Referencing of recipientsApplies the programme’s reference list.Provides and keeps up to date the list or the criteria.May be involved depending on the use.
Technical exchangesDocuments the available interfaces.Carries out the developments on its side.Intervenes according to the contract.
Support to end usersHandles what falls under the service.Handles what falls under the programme.According to the agreed allocation.
Technical documentation
Interfaces, exchange formats and authentication arrangements are described in the technical documentation provided during scoping. This site publishes no sample request, key or service address: the applicable documentation is that of the scope adopted for your programme.
Prerequisites

What to gather before starting

On the programme side

Purpose of the funding, scope of use, list or criteria of recipients, rules wanted, reports expected, designated contacts.

On the technical side

Systems concerned, data available to apply the rules, exchange capability, test environment, identified technical lead.

On the contractual side

Documents applicable to your organisation’s role, internal approval, processing of personal data, service commitments to be agreed.

On the operations side

Who administers the programme, who handles user requests, who receives the reports, who is called in the event of an incident.

Get in touch

Prepare the integration

We examine your systems, the data available and the steps to plan before going live.