Wallet and Registrar Requirements
Which certificates a wallet accepts depends on the wallet and its environment: a development wallet may accept self-signed certificates, while a reference implementation or national test environment may require certificates from its registrar. EUDIPLO requests certificates from the German EUDI Hub; certificates from other ecosystems are imported. Read this after Install and Connect and before Issue Your First Credential; for wallets not listed here, the wallet's own documentation is authoritative.
The certificates are different
Do not confuse the HTTPS certificate of PUBLIC_URL with the certificates of the credential protocols:
| Certificate or key | Used for | Typical source |
|---|---|---|
| HTTPS/TLS certificate | Lets the phone reach the EUDIPLO backend securely | Your tunnel or deployment |
| Attestation key chain | Signs the credentials EUDIPLO issues | Self-signed for testing; a CA or issuer PKI for production |
| Access certificate | Signs presentation requests; identifies EUDIPLO to the wallet | Self-signed in some test setups; the wallet ecosystem's registrar |
| Registration certificate | Tells the wallet which data the verifier may request (or the issuer provides) | Issued by a registrar |
Access and attestation certificates belong to key chains (Keys and Certificates). A registration certificate is a JWT configured per presentation configuration (Registration Certificates).
A registration certificate obtained elsewhere goes into the same place as one from the EUDI Hub: registration_cert.jwt in a presentation configuration, registrationCertificate.jwt in the issuance configuration (Registration Certificates).
Choose the wallet path
The exact acceptance rules can change between wallet releases and sandbox deployments.
| Wallet or environment | Access certificate | Registration certificate |
|---|---|---|
| Paradym Wallet test setup | Self-signed can be sufficient: Access Certificate → Self-Signed Certificate | Usually not needed for a minimal test |
| EU Reference Implementation | Import the key and certificate from the ecosystem operator: Access Certificate → External Certificate | If the setup requires one, import the certificate from the ecosystem operator into registration_cert.jwt |
| German wallet or German ecosystem sandbox | Request from EUDI Hub (EUDI Hub), or import a certificate the EUDI Hub already issued | Select Request from EUDI Hub on the presentation configuration's Security tab and in Issuer Settings (EUDI Hub) |
| Other wallets | Check the wallet ecosystem's documentation | Check whether verifier requests must carry one; import it into registration_cert.jwt |
The wallet compatibility record tracks protocol support and known wallet limitations; it does not replace the current onboarding requirements of the wallet or registrar operator.
Minimal Paradym test path
- Create the credential-signing attestation key chain.
- Create the access key chain with Access Certificate → Self-Signed Certificate.
- Leave the registration certificate unset.
- Issue and verify the test credential with the cookbook.
If Paradym rejects the certificate, check the wallet version and test environment. A self-signed certificate that works with one wallet is not evidence that another wallet accepts it.
Imported certificate path (EU Reference Implementation)
- Obtain the access key and certificate from the reference implementation's ecosystem operator.
- In Keys → Create Key, choose Access Certificate → External Certificate and provide the private key (EC JWK or PKCS#8 PEM) and the certificate chain, leaf first. Via the API, use
POST /api/key-chain/import(Keys and Certificates). - If the tenant has more than one access key chain, make this key chain the tenant's default access key chain, which also signs the issuer metadata, or select it as
accessKeyChainIdin the presentation configuration. Without either, the default picked by rule prefers this certificate over a self-signed one while it is valid. - Repeat the health, issuance and presentation checks with the wallet, keeping the public HTTPS address stable.
German ecosystem path (EUDI Hub)
- Register and verify your organization in the EUDI Hub portal. The tenant that owns the issuer and verifier settings needs the
registrar:managerole. - Create a standalone access key chain with Access Certificate → Self-Signed Certificate, then select Request from EUDI Hub on its Active Certificate card (EUDI Hub).
- Request a registration certificate for each presentation configuration that needs one, and for the issuer (EUDI Hub). Request new ones before they expire.
- Repeat the health, issuance and presentation checks with the target wallet. A successful health check only proves HTTPS connectivity, not that the wallet accepts your certificates.
Next: Issue Your First Credential.