> EU DPP registration prep: EU Login, seal, data | dpp.coach · https://eu.dpp.coach/en/preparation · English · Markdown version of this page > Free to use · independent, vendor-neutral guide · Sponsored by Narravero (https://www.narravero.com/) Track A · National level · done at your own pace # Preparation: build everything the EU platform will ask for Three steps, each with a result you can tick off. Complete all three before you open the EU registry — the execution phase assumes every one of them exists. Last updated: 26 October 2026 · Checked against the European Commission’s [DPP Registry User Guide for Economic Operators](https://single-market-economy.ec.europa.eu/document/download/079a45e2-469f-4eec-b1e5-32e8e05d1357_en?filename=dpp_registry_user_guide_for_economic_operators.pdf) (v1.03, 16 September 2026). Step 1 · Identity for the EU platform ## Set up a valid, working EU Login **In short:** Create an EU Login with a company mailbox, add a second factor (EU Login app or SMS) and test the sign-in on the computer you will use for Track B. ### Instructions [EU Login](https://webgate.ec.europa.eu/cas/) is the European Commission’s single authentication service. The DPP Registry has no accounts of its own — it trusts EU Login, so this account is the key to everything in Track B. 1. Open the EU Login portal and choose “Create an account”. Use a company mailbox that you control and that will outlive individual employees. 2. Confirm the verification e-mail and set a password that meets the stated policy. 3. Add a second factor: install the EU Login Mobile app and register your phone, or add a mobile number for SMS codes. The registry requires two-factor authentication. 4. Complete your profile with your real name and the GmbH you act for. 5. Test it: sign out, sign in again with the second factor, and confirm you reach the EU Login dashboard without errors. ### Helper tool **EU Login readiness check** Tick what you have verified. The step counts as prepared only when all four are green. - Account created with a company mailbox - E-mail address verified - Second factor (mobile app or SMS) registered and tested - Sign-in tested from the computer you will use for execution ### Typical pitfalls - Registering with a personal address: when that person leaves, the company loses access to its registry account. - Skipping the second factor: the registry will refuse the sign-in and send you back here. - Setting up the second factor on a phone that is not with you on execution day. Step 2 · The company’s electronic seal ## Build a working qualified electronic seal infrastructure **In short:** Order a qualified electronic seal for your GmbH from a qualified trust service provider — on a smart card or USB token, or as a qualified remote sealing service, never as a .p12/.pfx file — and make a test seal that the Commission’s DSS Validation WebApp shows as “QESeal”. ### Instructions The registry requires the Commission’s declaration to be countersigned with a qualified electronic seal issued to your GmbH under the eIDAS Regulation ((EU) No 910/2014) — not a personal signature. The seal must be created on a qualified device (a smart card or USB token from your provider) or by a qualified remote sealing service. Set it up and test it before execution day. 1. Choose a qualified trust service provider (QTSP) on the [EU Trusted List](https://eidas.ec.europa.eu/efda/trust-services/browse/eidas/tls) and order a qualified seal certificate for your GmbH — on a smart card or USB token, or as a qualified remote sealing service. In Germany, D-Trust (Bundesdruckerei group) is a proven choice. 2. Complete the provider’s identification procedure for the company and its legal representative (Geschäftsführer) — with D-Trust via Post-Ident. 3. Receive the seal card that carries the company’s private key, and the PIN letter, by separate post. 4. Obtain a certified chip-card reader and install the provider’s middleware on the computer you will use (not needed for a remote sealing service). 5. Make a test seal on any PDF and check it in the Commission’s free [DSS Validation WebApp](https://ec.europa.eu/digital-building-blocks/DSS/webapp-demo/validation): the qualification must show “QESeal” and the format PAdES-BASELINE. 6. When the certificate arrives, confirm that its organisation identifier equals the NTR identifier from the tool below and its organisation name equals your registered legal name — you will enter both in Track B, step 2. ### Helper tool **Seal stack check** Four components, one chain. If any link is missing, the seal in Track B step 3 will fail. - Qualified seal certificate on a card or token, or a qualified remote sealing service (Issued to the GmbH by a QTSP on the EU Trusted List — not a .p12/.pfx software file) - Identity verification completed (Company and legal representative identified with the provider) - Certified card reader connected (Recognised by the operating system (not needed for remote sealing)) - Middleware installed and a test seal validated (DSS Validation WebApp shows “QESeal” and PAdES-BASELINE) ### Helper tool Trickiest part **Your National Trade Register (NTR) identifier — what the seal certificate must contain** When D-Trust issues the seal, it writes your trade register entry into the certificate as a coded NTR identifier. The EU registry later compares this value with your form, character by character. Work it out now so you can order the seal with exactly the right register data and check the certificate when it arrives. (Two minutes: what the NTR identifier is and how it is assembled.) (When the seal card arrives, open the certificate details in your middleware and confirm the organisation identifier equals this value. If it differs, ask D-Trust to reissue before you continue to Track B.) ### Typical pitfalls - Ordering a personal qualified signature (QES) instead of a qualified seal for the GmbH. - Accepting the certificate as a software file (.p12/.pfx): it only produces an advanced seal, and the registry rejects the verification. - Company name or register number in the certificate differs from the Handelsregister entry — the registry will reject the mismatch later. - Underestimating lead time: identification, card production and postal delivery can take several weeks. - Installing the middleware on a different computer than the one used on execution day. **Worked example: D-Trust seal for a German GmbHOne proven combination of card, identification, reader and middleware** A chain that has been used successfully for this registration: a D-Trust seal card, identification via Post-Ident, a Reiner SCT cyberJack reader and the cv cryptovision middleware. Equivalent components from other providers work the same way: card, proof of identity, reader and middleware. A qualified remote sealing service from a QTSP replaces card, reader and middleware. 1 · The key ### D-Trust seal card, standard 5.4 A chip card that holds the company’s private key. The key never leaves the card; the seal is computed on the chip. 2 · The proof ### Identity verification via Post-Ident The authorised signatory proves their identity and authority for the company at a post office or online, before the card is produced. 3 · The reader ### Reiner SCT cyberJack Comfort A certified reader with its own keypad, so the PIN is entered on the device and never on the computer. 4 · The link ### Middleware: cv cryptovision (Eviden) Software that makes the card visible to the operating system and the signing application, linking card, reader and PDF tool together. **How the chain is assembled** 1. Order the seal card from D-Trust for the GmbH and start Post-Ident. 2. While waiting: buy the cyberJack reader, connect it and install its driver. 3. Install the cv cryptovision middleware and restart the computer. 4. When card and PIN letter arrive, insert the card and check that the middleware shows the certificate. 5. Produce a test seal on a scratch PDF and validate it in the DSS Validation WebApp. (Product names are those of the respective manufacturers. Check the current model and version with the provider before ordering.) Step 3 · Data for the forms ## Gather all company information ahead of time **In short:** Copy legal name, registered address, register court and HRB number from a current Handelsregisterauszug, and note a compliance contact and the legal representative who will seal — exactly as the EU form asks for them. ### Instructions The application form in Track B asks for company data that must match the Handelsregister and your seal certificate letter for letter. Collect it now from a current Handelsregisterauszug, not from memory. 1. Retrieve a current Handelsregisterauszug (e.g. via handelsregister.de) and keep it next to you. 2. Copy the legal name (Firma) and the registered address (Sitz) exactly as printed, together with the Registergericht and the HRB number. 3. Choose a compliance contact (e-mail and phone) that authorities may use for questions about your DPP registrations — ideally a team mailbox. 4. Note the legal representative who will seal the declaration (name and e-mail) — usually a Geschäftsführer named in the seal certificate. 5. Save the data sheet below; on execution day you copy from it into the EU form. ### Typical pitfalls - Typing the company name from memory: abbreviations and punctuation differ from the register and from the seal. - Using a branch or office address instead of the registered seat. - Mixing up HRB number and Registergericht: both are part of the NTR identifier. ### Helper tool **Company data sheet** Fill this in from the Handelsregisterauszug. It is saved in this browser only and can be printed. - Legal name (Firma) (Exactly as registered and as in the seal certificate, including “GmbH”) - Registered address (Sitz) (Street, postal code, town — the seat, not a branch) - Registergericht (e.g. Amtsgericht Münster) - HRB number (Digits only, e.g. 12345) - NTR identifier (From the builder, e.g. NTRDE-R2713.HRB12345) - Compliance contact (E-mail and phone, not shown publicly) - Legal representative who seals (Name and e-mail, usually a Geschäftsführer) Next: Track B ### Execution on the EU platform Five steps on the EU platform, in one sitting and in strict order: log in, create the organisation application, request the EC-sealed declaration, countersign it with your seal, then upload and verify. [Go to execution](https://eu.dpp.coach/en/execution) ## Prefer a human to walk you through it? A Narravero Expert takes you through every step personally — from ordering the seal to the final verification. [Hire a Narravero Expert](https://www.narravero.com/en/contact)