Skip to content

Age Verification iOS App

Table of contents

Overview

The Age Verification App is an iOS application built on top of the EUDI Wallet Reference Implementation. It provides age verification functionality using digital credentials based on the Architecture Reference Framework.

The Age Verification App allows users to:

  1. Obtain, store, and present age verification credentials.
  2. Verify presentations.
  3. Support age verification use cases.

💡 Specifications Employed

The app consumes the SDK called EUDIW Wallet core Wallet kit and a list of available libraries to facilitate remote presentation and issuing test/demo functionality following the specification of the ARF, including:

Relying Party functionality:

To support development and testing, one can access a test/demo service for remote presentation at:

Important things to know

The main purpose of the reference implementation is to showcase the ecosystem and act as a technical example of how to integrate and use all of the available components.

If you're planning to use this application in production, we recommend reviewing the following steps: - Configure the application properly by following the guide here - The Pin storage configuration matches your security requirements, or provide your own by following this guide Pin Storage Configuration - The application meets the OWASP MASVS industry standard. Please refer to the following links for further information on the controls you must implement to ensure maximum compliance: - OWASP MASVS

How to use the application

Minimum device requirements

  • Any device that supports iOS 17.0

Prerequisites

To complete the flows described below, you must build and run the application with Xcode.

App launch

  1. Launch the application
  2. You will be presented with a welcome screen where you will be asked to create a PIN for future logins.

Issuance flow (Scoped - Wallet initiated)

  1. Navigate to the "Dashboard" screen, go to the "Documents" tab, and tap on the "+" icon (top-right of the screen). Select "From list". If it's your first time opening the app, you will be redirected here automatically after entering or setting up your PIN.
  2. Select "PID".
  3. In the web view that appears, choose "Country Selection", then "FormEU", and tap "Submit".
  4. Fill in the form. Any data will suffice, but selecting a birth date older than 18 years is recommended, as it is required for certain app functionalities (e.g., RQES).
  5. After submission, a success screen will appear. Tap "Close".
  6. You will be redirected to the "Dashboard" screen. If this was your first document added to the Wallet, you will land on the "Home" tab; otherwise, you will be on the "Documents" tab. The flow is now complete.

Issuance flow (Credential Offer - Issuer-initiated)

  1. Go to the "Dashboard" screen, navigate to the "Documents" tab, and tap the "+" icon (top-right of the screen). Select "Scan a QR".
  2. Scan the QR code from the issuer's website EUDI Issuer
  3. Review the documents included in the credential offer and tap "Add".
  4. In the web view that appears, select "Country Selection", then "FormEU", and tap "Submit".
  5. Fill in the form. Any data will suffice, but selecting a birth date over 18 is recommended, as it is required for certain app functionalities (e.g., RQES).
  6. After submission, a success screen will appear. Tap "Close".
  7. You will be redirected back to the "Documents" tab within the "Dashboard" screen. The flow is now complete.

To delete a document, navigate to the 'Documents' tab within the 'Dashboard' screen, tap on the document you wish to remove, and then tap the 'Delete Document' button in the 'Document Details' screen.

Presentation (Online authentication/Same device) flow.

  1. Go to the browser application on your device and enter "https://verifier.eudiw.dev"
  2. Expand the Person Identification Data (PID) card and select:
    1. "Attributes by" → "Specific attributes".
    2. "Format" → Choose the format of your choice.
  3. Tap "Next", then select "Select Attributes".
  4. Choose the fields you want to request from the Wallet (e.g., "Family Name" and "Given Name").
  5. Review your presentation request, tap "Next", and then select "Open with your Wallet".
  6. When prompted to open the wallet app, tap "Open".
  7. You will be redirected to the app’s "Request" screen, where you can select or deselect which attributes to share with the Verifier. You must select at least one attribute to proceed.
  8. Tap "Share".
  9. Enter the PIN you set up during the initial steps.
  10. Upon successful submission, tap "Close".
  11. A browser will open, confirming that the Verifier has accepted your request.
  12. Return to the app. The flow is now complete.

How to build - Quick start guide

This document describes how you can build the application and deploy the issuing and verification services locally.

Application configuration

You can find instructions on how to configure the application here

Package structure

logic-resources: All app resources reside here (images, etc.)

logic-core: Wallet core logic.

logic-analytics: Access to analytics providers. Capabilities for test monitoring analytics (i.e., crashes) can be added here (no functionality right now)

logic-business: App business logic.

logic-storage: Persistent storage cache.

logic-authentication: PinStorage and System Biometrics Logic.

logic-ui: Common UI components.

feature-common: Code that is common to all features.

feature-dashboard: The application's main screen.

feature-startup: The initial screen of the app.

feature-presentation: Online authentication feature.

feature-issuance: Document issuance feature.

logic-assembly: This module has access to all the above modules and assembles navigation and DI graphs.

graph TD;
  logic-business --> logic-authentication
  logic-core --> logic-authentication
  logic-analytics --> logic-authentication
  logic-resources --> logic-authentication

  feature-common --> logic-assembly
  feature-startup --> logic-assembly
  feature-dashboard --> logic-assembly
  feature-presentation --> logic-assembly
  feature-issuance --> logic-assembly

  logic-business --> logic-core
  logic-resources --> logic-core
  logic-resources --> logic-storage

  logic-business --> logic-analytics

  feature-common --> feature-issuance

  feature-common --> feature-presentation

  feature-common --> feature-dashboard

  logic-storage --> feature-common
  logic-core --> feature-common
  logic-business --> feature-common
  logic-analytics --> feature-common
  logic-ui --> feature-common
  logic-api --> feature-common
  logic-authentication --> feature-common

  feature-common --> feature-startup

  logic-business --> logic-storage

  logic-core --> logic-api
  logic-business --> logic-api
  logic-analytics --> logic-api

  logic-resources --> logic-business

  logic-business --> logic-ui
  logic-analytics --> logic-ui
  logic-resources --> logic-ui

  logic-core --> logic-ui

Demo videos

Issuance

Issuance

Presentation

Presentation

Disclaimer

The released software is an initial development release version: - The initial development release is an early endeavor reflecting the efforts of a short time-boxed period, and by no means can it be considered the final product.
- The initial development release may be changed substantially over time and might introduce new features, but also may change or remove existing ones, potentially breaking compatibility with your existing code. - The initial development release is limited in functional scope. - The initial development release may contain errors or design flaws and other problems that could cause system or other failures and data loss. - The initial development release has reduced security, privacy, availability, and reliability standards relative to future releases. This could make the software slower, less reliable, or more vulnerable to attacks than mature software. - The initial development release is not yet comprehensively documented. - Users of the software must perform sufficient engineering and additional testing to properly evaluate their application and determine whether any of the open-sourced components are suitable for use in that application. - We strongly recommend not putting this version of the software into production use. - Only the latest version of the software will be supported. - This project is tested with BrowserStack.

How to contribute

We welcome contributions to this project. To ensure that the process is smooth for everyone involved, follow the guidelines found in CONTRIBUTING.md.

License

License details

Copyright (c) 2025 European Commission

Licensed under the EUPL, Version 1.2 or - as soon they will be approved by the European Commission - subsequent versions of the EUPL (the "Licence"); You may not use this work except in compliance with the Licence.

You may obtain a copy of the Licence at: https://joinup.ec.europa.eu/software/page/eupl

Unless required by applicable law or agreed to in writing, software distributed under the Licence is distributed on an "AS IS" basis, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licence for the specific language governing permissions and limitations under the Licence.