CS-15
CS-15 is the WE BUILD conformance specification for the interface between a European Business Wallet and a Qualified Trust Service Provider (QTSP). It describes how a wallet uses the Wallet Messaging Protocol (WMP) to send and receive messages through a Qualified Electronic Registered Delivery Service (QERDS), and what evidence comes back.
CS-15 is one of the WE BUILD Conformance Specifications that the consortium's QERDS architecture decision calls for, written by the WP4 Architecture group. It is at version 1.0.
It covers one leg of the four-corner QERDS model only: the one between a European Business Wallet and its own QTSP. The wallet never talks to another wallet or another QTSP directly, because the QTSP mediates every exchange. The relay between two QTSPs, the requirements on directory and service metadata publisher operators, and credential issuance or presentation between wallets are all outside its scope.
CS-15 defines no new protocol methods. It profiles WMP by combining four WMP specifications, WMP-CORE, WMP-MLS, WMP-EDELIVERY and WMP-EVIDENCE, all of them mandatory, and it narrows the choices they leave open. Subscribers are identified with ebcore identifiers built on ISO 6523 schemes. Onboarding runs through the QTSP: the wallet proves the organisation's identity to the QTSP with an OpenID4VP presentation as defined in conformance specification CS-02, and the QTSP then issues a subscriber certificate and registers the subscriber in the SMP. Sessions are authenticated with mutual TLS using that certificate, and bearer tokens are refused.
Message content is protected end to end with MLS. WMP treats MLS as optional, but CS-15 makes it mandatory. The QTSP routes and queues the ciphertext without ever holding the plaintext, which is how it can offer a qualified delivery service over content it cannot read. Metadata is a different matter: the QTSP sees who corresponds with whom, when and how much, and the specification says so openly. The sender signs the content with a detached JWS and includes an EBWOID identity assertion, at least on the first message of a correspondence, which the recipient verifies before presenting the content.
Every delivery event produces two artefacts: a WMP evidence notification sent to the wallet, and an ERDS evidence record, a JSON form of the evidence defined in ETSI EN 319 522 that carries a JAdES signature. A QTSP must support all thirteen event types, the signed record prevails if the two disagree, and it must be kept for at least ten years.
CS-15 is a consortium specification, not EU legislation, and WMP, which it builds on, is itself still a draft. Read it as the agreed technical interface for the WE BUILD work rather than as a legal requirement. It defines four conformance classes: QTSP, EBW, and sender-only and recipient-only variants of EBW.
Is CS-15 the same as QERDS or WMP?
No. QERDS is the qualified trust service under eIDAS that delivers messages and produces legal evidence about them. WMP is the draft messaging protocol a wallet speaks. CS-15 is the profile that joins the two on one leg: it says how a European Business Wallet uses WMP to reach the QERDS of its QTSP.
It adds no protocol of its own. It narrows the choices WMP leaves open, for example by making MLS encryption mandatory.
Does CS-15 cover credential issuance and presentation between wallets?
No. The specification puts credential issuance and presentation between wallets out of scope, because a QERDS only delivers content and produces evidence. Credentials do appear in two places: at onboarding, where the QTSP verifies the organisation with the OpenID4VP flow of conformance specification CS-02, and as the EBWOID identity assertion a sender attaches to its messages.
A profile for credential exchange over QERDS, if the consortium decides one is needed, would be a separate specification.