Interoperability · EU Digital Identity Wallet · Test ecosystem

CodeB Playground: test without a sandbox of your own

You are building a wallet, a verifier or an issuer for the EU Digital Identity Wallet ecosystem, and your country has no register or sandbox you can use yet. Use ours: register a test organisation and get an access certificate and a registration certificate in minutes. Self-service and free.

In one sentence: the CodeB Playground gives your test relying party or test issuer the same moving parts a real registrar would – register entry, access certificate, registration certificate, revocation list and status list – clearly marked as test data and valid nowhere in production.

ARF 3.0 · ETSI TS 119 411-8 · ETSI TS 119 475 · OpenID4VP 1.0 · OpenID4VCI 1.0 · SD-JWT VC · ISO mdoc

Free. Test data only. Not certified.

In short

What
A test register and test certificates for relying parties and issuers, on our test site phone.codeb.io.
For whom
Teams building verifiers, issuers or wallets that have no national sandbox or registrar to test against.
What you get
An access certificate for your own key, a registration certificate for exactly what you ask for or issue, and a revocation list, a status list and a public register entry behind them.
What it costs
Nothing. A CodeB account with an e-mail address is all you need.
Limits
2 test organisations per account, 5 valid certificates each, 30 days per certificate.
What it is not
Not a Member State register, not a way into a national wallet app, not production. Nothing you enter is verified.

How it works

Four steps, a few minutes.

Register a test organisation

Name, a test identifier, country and a contact. Choose relying party, issuer or both. The name appears everywhere as “TEST …”.

Get an access certificate

Paste a certificate request for your ECDSA P-256 key, or let your browser create key and request. You receive the certificate and the CA certificate.

Get a registration certificate

Paste the DCQL query you send to wallets, or list the attestation types you issue. The certificate names exactly those, so a wallet can check that you do not ask for more.

Test, revoke, repeat

Sign your requests or your issuer metadata with them. Revoke a certificate with one click and watch the revocation list change at once.

What you get

Access certificate

The profile of ETSI TS 119 411-8: organisation, identifier, contact and, if you need them, host names for x509_san_dns. Your software sees the structure of a real one.

Registration certificate

rc-wrp+jwt per ETSI TS 119 475 with your credentials and purpose, or your attestation types and entitlements as an issuer. Valid 30 days.

Revocation you can watch

A revocation list for access certificates and a status list for registration certificates. Revoke your own certificate and test how your software and the wallet react.

A register entry

Every test organisation has a public entry behind the registry_uri of its registration certificate, marked as test data.

Your key stays yours

We receive a certificate request and nothing else. A key created on the page is created in your browser and never sent.

Who it is for

Relying parties

Send a real, signed presentation request with an access certificate and a registration certificate, before your national register exists.

Issuers

Sign your issuer metadata with an access certificate and carry a registration certificate that lists what you issue.

Wallet builders

Add the CA of this test site as a test trust anchor: one anchor covers the relying parties registered here and our own verifier. CodeB Wallet and the CodeB web wallet accept the test entries of the playground through their switch for CodeB test certificates.

Integrators and trainers

Show customers and students the complete flow with certificates they can inspect, revoke and renew themselves.

An independent implementation

Testing against a second code base finds what testing against yourself cannot.

Written from the specifications

Issuer, verifier, register, CA and the web wallet are our own code. They are not based on the reference implementation or on a public EUDI or OpenID4VC library.

A different platform

The servers run on Windows and IIS with .NET. The Android wallet builds on the EU reference wallet and its libraries, extended with our own code. Differences in encoders, parsers and TLS stacks show up here.

Built to ARF 3.0

We build to the Architecture and Reference Framework 3.0 and keep it compliant with it. That is our own assessment; nothing here is certified.

We benefit too

Every mismatch you find is an interoperability problem found early, on your side or on ours. Tell us: info@aloaha.com.

Security, privacy, limits

Marked as test, everywhere

Organisation names start with TEST, every certificate carries a marker for playground entries, and the register entry says it is test data. Wallets can refuse them by default.

No trust outside the playground

The certificates come from the CA of our test site. It is on no trust list, and nothing issued here has legal effect. See the policy.

Little data, no trackers

We keep your account’s e-mail address with your test organisations and the test data you enter. No third-party analytics. Use test data only, no personal data of real people.

Tidy by design

Short lifetimes and fixed limits per account. Organisations unused for 90 days are removed; an organisation you remove yourself is deleted with its records after a short retention period.

For developers

Everything on the page is also an API. Register the test organisation on the page once, then script the rest.

Key and certificate request

shell
# 1. Key and certificate request (the key stays with you)
openssl ecparam -name prime256v1 -genkey -noout -out verifier-key.pem
openssl req -new -key verifier-key.pem -subj "/CN=playground" -out verifier.csr

Access certificate

shell
# 2. Access certificate for your test organisation (TOKEN = your CodeB access token, ID = pg-... from the page)
curl -s https://phone.codeb.io/playground.ashx?op=cert \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d "{\"id\":\"$ID\",\"csr\":\"$(awk '{printf "%s\\n",$0}' verifier.csr)\",\"dns\":[\"verifier.example.com\"]}"
# -> { "certificate_pem": "...", "ca_pem": "...", "x5c": [ leaf, CA ], "not_after": "..." }

Registration certificate

shell
# 3. Registration certificate for exactly the query you send to wallets
curl -s https://phone.codeb.io/playground.ashx?op=rc \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"id":"'$ID'","kind":"verifier","purpose":"Age check in the test shop",
       "dcql_query":{"credentials":[{"id":"pid","format":"dc+sd-jwt",
         "meta":{"vct_values":["urn:eudi:pid:1"]},"claims":[{"path":["family_name"]}]}]}}'
# -> { "registration_certificate": "<rc-wrp+jwt>", "exp": 1765500000 }

Trust anchor, revocation, register

shell
# 4. What a wallet or your own tests check against
curl -s "https://phone.codeb.io/wrpac-ca.ashx?ca&format=pem"   # the CA to add as a TEST trust anchor
curl -s  https://phone.codeb.io/wrpac-ca.ashx?crl -o ca.crl     # revocation list of access certificates
curl -s  https://phone.codeb.io/wrpac-ca.ashx?rc-status         # status list of registration certificates
curl -s "https://phone.codeb.io/wrpac-ca.ashx?registry=$ID"     # public register entry ("test": true)

Frequently asked questions

What is the CodeB Playground?

A free, self-service test ecosystem for projects around the EU Digital Identity Wallet. You register a test organisation as relying party, issuer or both and receive an access certificate and a registration certificate, with a revocation list, a status list and a public register entry behind them. It is for teams that have no national sandbox or registrar to test against.

Who can use it?

Anyone with a CodeB account that has an e-mail address. There is no contract, no approval step and no fee.

Are the certificates valid in production?

No. Everything is test data: nothing you enter is verified, every organisation name starts with TEST, every certificate carries a marker for playground entries and lasts 30 days at most. The certificates come from the CA of our test site, which is on no trust list. They have no legal effect.

Does a national wallet app accept playground certificates?

No. A national wallet trusts only the certificates of its own registrar. The playground is for testing your own software: your verifier or issuer against a wallet that you or others configure with our test CA as a test trust anchor, and your wallet against relying parties registered here.

Where does my private key go?

Nowhere. You send a certificate request (PKCS#10) with your public key. If you let the page create the key, it is created in your browser and handed to you once; it is never sent to us.

What are the limits?

Two test organisations per account, five valid certificates per organisation, certificates and registration certificates of 30 days. Organisations that are not used for 90 days are removed.

Is this the EU reference implementation?

No, and that is the point. Issuer, verifier, register, CA and the web wallet are our own implementation, written from the specifications and not based on the reference implementation or on a public EUDI or OpenID4VC library. If your verifier or issuer and ours agree, both follow the specification rather than share the same code. The Android wallet builds on the EU reference wallet and its libraries, extended with our own code.

Is it certified?

No. The playground follows the ARF 3.0, ETSI TS 119 411-8, ETSI TS 119 475, OpenID4VP 1.0 and OpenID4VCI 1.0. It is not certified and not a Member State register.

Why do you offer this for free?

Because we benefit too. Every mismatch between your implementation and ours is an interoperability problem found early, on your side or on ours.

Start testing

Sign in with your CodeB account, register a test organisation, and have your first certificate a few minutes later. Found something that does not interoperate? That is what the playground is for.