You will know who the service depends on, and for what share
A payment service relies on third parties. Your procurement department wants to know which ones, for what share, and what happens if one of them stops. You will find here the exact category of each type of party, the contractual allocation of responsibilities and the documents that establish it. Every third party named here rests on a verified relationship and written authorisation.
The ecosystem diagram
Your organisation covers the digital euro account rules, the users and the authorised suppliers. The operator, where that role is distinct from the funder, covers the review of situations and day-to-day administration. Your contract is with MAP, which covers the earmarkable digital euro, the application of the rules, the checking of operations, the recording of payments and reporting back to you. MAP works with three categories of parties, each filed in its own: the provider, which performs a function for MAP and for which MAP answers towards you; the technology partner, which supplies a component or interoperability; the use partner, which carries a digital euro account with MAP, where its role is described.
Validated parties
Three categories, clearly distinct
Naming a third party commits that third party as much as MAP. This page describes the categories of parties, and cites a name once the relationship is verified and authorised in writing
- Provider
- Performs a function on behalf of MAP, under contract. MAP remains responsible for the function towards you, and answers for the provider it has chosen.
- Technology partner
- Supplies a component or interoperability. Its role is technical; your contract remains with MAP.
- Use partner
- Carries a digital euro account with MAP. Its role is described within the digital euro account concerned.
These three categories remain distinct, and each relationship is filed in its own.
Contractual roles
Who answers for what towards you
The question that matters to your legal team is the address of a complaint. Here it is, by role
- MAP
- Issuance of the earmarkable digital euro, application of the digital euro account rules, checking of operations before execution, recording of every payment and reporting back to you.
- Your organisation
- Definition of the digital euro account rules, designation of users and of the authorised supplier categories, accountability towards its own funders.
- Operator
- Review of individual situations and day-to-day administration, where that role is distinct from the funder.
- MAP’s providers
- Technical or financial functions performed under contract with MAP, within a defined framework; MAP answers for them towards you.
The allocation applicable to your digital euro account is settled at the first discussion and written into the contract. It is what determines where a request goes, and who answers for an operation.
What each technical function covers
Each technical function is identified: hosting, processing of operations, account keeping, card issuance, recording of payments on the blockchain. The location of processing is stated for each of them. These functions are described in the integration documentation, together with the authorised formats and channels.
Dependencies and unavailability
A critical dependency is a function whose interruption stops the service. It is identified together with the consequences of its unavailability and the measures planned. These elements are dealt with upstream, alongside service continuity.
Digital euro account contacts
While the digital euro account is being prepared, you are given your contacts. One for day-to-day operation, one for contractual and documentary requests, and the route to follow for a complaint. These details are given by name and written into the contract.
Documents The documents that establish this page
A document appears here once it exists and can be provided in the mode indicated
Need a document for your assessment?
Tell us the document you need, your organisation and the context of your assessment.