Per-customer reader

Apple Wallet

Present eligible government IDs from Apple Wallet to an approved web verifier.

Countries listed2

Credential profiles3

Exchange pathDigital Credentials API · org-iso-mdoc

What this route means

The wallet is
one layer.

Apple currently ties web verification to an approved customer brand, purpose, domain, and reader certificate. Alentra can operate the reader and certificate lifecycle; the customer completes the Apple-controlled organization and domain actions.

Country+Credential+Apple=Accepted route

Canonical routes

Japan, United States

Every row is reviewed separately. A listed route can remain unavailable until provider approval, issuer trust, configuration, and acceptance all pass.

JP Japan

Credential My Number Card

Wallet Apple

Coming soon

US United States

Credential US mDL

Wallet Apple

Coming soon

US United States

Credential US Digital ID

Wallet Apple

Coming soon

Customer onboarding

Who does
what.

Alentra keeps provider keys and verification infrastructure away from customers wherever the provider permits it.

Customer approvalCustomer action required

Apple Wallet customer reader

Business: Verify your organization with Apple, approve the customer brand and use case, and prove your domain. Alentra generates the CSR, protects the private key, hosts the reader, and operates verification for you.

Alentra: Operate a separate reader identity for this business on its approved domain. Validate the returned Apple certificate, attach the customer hostname, and activate only after every customer and staff check passes.

Read the provider source ↗

Stable product surface