Skip to content

IN Groupe — Aptitude Playground

Overview

IN Groupe provides two public development environments for testing EUDI Wallet interoperability:

  • Aptitude Verifier Playground for OpenID4VP presentation flows;
  • Aptitude Issuer Studio for OpenID4VCI credential-offer and issuance flows.

These services are intended exclusively for interoperability tests and demonstrations. They do not issue production credentials, establish legal identity, or provide a qualified trust service.

Public services

Service Link
Aptitude Verifier Playground Open the verifier
Ready-made intermediary checks Open the intermediary page
Aptitude Issuer Studio Open the issuer

No authentication is required to open these test interfaces.

The screenshots below were captured from the public development services on 6 October 2026. The interfaces evolve with the interoperability work, so live readiness indicators and the published protocol metadata remain authoritative.

Aptitude Verifier Playground

Purpose

The Verifier Playground lets developers and wallet teams prepare a presentation request, hand it to a wallet, and inspect the server-confirmed outcome. The UI does not infer successful verification from the requested claims: it reports only results returned by the verifier or intermediary service.

Supported capabilities

  • OpenID4VP 1.0 request creation;
  • DCQL credential and claim selection;
  • QR code and same-device wallet-link handover;
  • direct_post and encrypted direct_post.jwt response modes, according to the selected profile;
  • browser-mediated OpenID4VP using openid4vp-v1-signed and dc_api.jwt when the browser and wallet expose the required Digital Credentials API support;
  • mso_mdoc and dc+sd-jwt credential formats;
  • standard OpenID4VP, HAIP-oriented and EU age-verification tracks;
  • issuer metadata import for building requests from a published credential catalogue;
  • session history, sanitized technical evidence and CSV statistics export;
  • interactive guidance and a simulated tutorial.

The Playground performs live readiness checks. A track remains blocked when a required verifier identity, trust configuration, browser capability or backend service is unavailable. It does not silently replace a blocked profile with a less restrictive one.

Scenario catalogue

The landing page is organised around verification outcomes rather than raw protocol options. A tester can start from identity, age, document, combination or advanced scenarios, or import an existing request.

Aptitude Verifier Playground scenario catalogue

The status strip separates profile readiness from channel readiness. In the example above, standard OpenID4VP and the QR/link channel are ready, while HAIP and browser-mediated presentation still require their own checks. A yellow indicator is not treated as success and does not trigger a fallback.

Start a PID verification

  1. Open the Verifier Playground.
  2. Select a PID verification scenario.
  3. Choose the required claims and delivery channel.
  4. Validate the server readiness checks.
  5. Create a fresh request.
  6. Scan the QR code from another device, open the wallet link on the same device, or use the browser-mediated action when it is available.
  7. Approve or refuse the request in the wallet.
  8. Return to the session page to inspect the result confirmed by the server.

A displayed QR code means only that a presentation request was created. It does not mean that a compatible credential was found or successfully verified.

Profile and channel configuration

The first step makes the security profile and handover channel explicit. The description explains the effect of each choice before any request is created.

Verifier profile and channel configuration for a PID request

The tester then selects credential formats, requested information and trust or status policy. The final action validates the current server configuration and creates a fresh request; drafts can be saved without creating a transaction.

Ready-made intermediary checks

The Intermediary page provides five controlled tests:

  1. PID identity verification;
  2. age-over-18 verification;
  3. mobile driving licence verification;
  4. PhotoID identity verification;
  5. combined PID and mobile driving licence presentation.

Each card fixes the requested credential type, format and claims. The intermediary obtains its own authorization and applies its own trust and status policy. A transaction in READY state means that the wallet handover can start; it is not a successful verification result.

Ready-made intermediary verification checks

The five cards expose only the controlled inputs for their use case. This keeps the intermediary route distinct from the general request builder and avoids silently falling back to direct Verifier Core when the intermediary is not ready.

Profiles and channels

Track Typical response Availability rule
Standard OpenID4VP — Link or QR direct_post or direct_post.jwt Available when Verifier Core and the selected configuration are ready
HAIP — Link or QR direct_post.jwt Available only when the HAIP verifier identity and required trust material are configured
OpenID4VP over Digital Credentials API dc_api.jwt Available only in a compatible browser with a compatible wallet
EU age verification direct_post Available when its dedicated profile checks pass
Intermediary Service-defined wallet link or QR Available when the intermediary authorization and request services are reachable

Interoperability workspace

The Interop page groups executable tracks by operational readiness: Available now, Needs setup, Coming soon and History. This makes the gap between specification support and a runnable deployment visible.

Interop Week workspace with currently available verifier tracks

The cards describe the channel, response protection and credential families before the tester enters configuration. A negative age answer remains a valid completed verification result; it is not converted into a protocol error.

Privacy and diagnostics

The interface exposes sanitized session state and technical failure codes for interoperability diagnostics. It must not be used with real personal data. Raw credentials, disclosed PID values, private keys, access tokens and complete wallet links are not part of statistics exports.

Aptitude Issuer Studio

Purpose

Issuer Studio lets a tester choose a credential from the public catalogue, enter test holder data, configure delivery, and create an OpenID4VCI credential offer. The holder completes the actual protocol flow in a compatible wallet.

Creating an offer does not mean that a credential has been issued or stored in the wallet. The Studio displays issuance status only when it is confirmed by the issuer service.

Credential catalogue

The public catalogue presents the credential configurations currently exposed by the development issuer. Search and filtering happen before an offer draft is created. Built-in Guide me and Watch tutorial actions explain the flow without issuing on the user's behalf.

Aptitude Issuer Studio credential catalogue

Supported capabilities

  • OpenID4VCI credential offers;
  • pre-authorized-code and authorization-code journeys, depending on the selected credential and configuration;
  • public-client and attestation-based token authentication as advertised by the authorization server;
  • DPoP with ES256;
  • pushed authorization requests (PAR);
  • optional transaction codes displayed separately from the wallet link;
  • immediate and deferred credential availability;
  • mso_mdoc and dc+sd-jwt credential formats;
  • QR code and same-device wallet-link delivery;
  • guided help, animated tutorial and CSV statistics export.

Example credential families

The current public catalogue includes test configurations for PID, mDL, PhotoID, age verification, education, employment, business and professional authorization use cases. The authoritative list is always the issuer metadata, not this documentation page.

Start an issuance test

  1. Open Aptitude Issuer Studio.
  2. Select an available credential, such as PID.
  3. Review its format, validity and requested attributes.
  4. Enter test holder information or select the supported authorization route.
  5. Configure QR/link delivery, availability and the optional transaction code.
  6. Create the offer.
  7. Scan the QR code or open the wallet link.
  8. Complete the flow in the wallet and inspect the status reported by the Studio.

There is no separate Review step in this flow.

Step 1 — Documents

The Documents step selects the representation, validity and attributes carried by the credential. Required attributes stay selected; optional attributes are explicit. The summary remains visible throughout the flow.

Issuer Studio PID document, format, validity and attribute selection

Additional documents can be added from the same published catalogue when the selected configuration supports a multi-credential offer.

Step 2 — Holder

The holder route is chosen before data is entered:

  • We already know who they are uses the test values entered in the Studio for direct collection;
  • They sign in first redirects the holder through the configured authorization server.

Issuer Studio holder route and test-data entry

Switching routes does not silently clear the draft. Only selected credential attributes are shown. The example values in the screenshot are synthetic demo data and must not be replaced with real personal data.

Step 3 — Delivery

Delivery separates three decisions: reference versus embedded offer, optional transaction-code protection, and immediate versus deferred availability.

Issuer Studio delivery configuration

When enabled, the server generates the transaction code only when the offer is created. The code is displayed separately from the QR and wallet link. The user must click the real Create the offer action; the Studio and its tutorial do not create one automatically.

Public protocol metadata

Resource URL
Credential issuer identifier https://aptitude-issuer.utoconnect.com
OpenID4VCI issuer metadata Issuer metadata
Authorization server identifier https://aptitude-auth.utoconnect.com
OAuth authorization-server metadata Authorization metadata
Public test trust manifest Trust manifest

Wallet-facing metadata uses public HTTPS identifiers. Internal service names are reserved for server-to-server communication and must not appear in a credential offer.

Test trust

The issuer publishes a test-only credential-signing chain and public root in its trust manifest. Publication does not automatically make that root trusted: wallet operators must verify its fingerprint and explicitly enroll it in the appropriate development trust store.

Only public certificates may be exchanged. Private keys, keystores and .p12 files must never be uploaded or shared.

Contact

For interoperability tests and technical coordination, contact the IN Groupe Aptitude team through the existing EUDIW Unfold participant channel.