Verify Credentials

Gataca Studio enables you to quickly create customizable verification templates for onboarding and sign-in processes while reducing personal data stored in your infrastructure.

Verification templates define identity verification requirements that can be integrated into various applications.

A verification template outlines the entire verification process, including:

• Required Verification Credentials: Specifies the credentials users must share to enable successful authentication.

• Level of Trust: Determines the legitimacy of the credentials needed.

• Additional Security Requirements: Specifies any extra security measures, such as two-factor authentication (2FA), that users must comply with.

Once the verification process is implemented, users simply scan a QR code on your website, consent to sharing the required data for identity verification, and gain access.

Create a Verification Template

To create a new verification template, navigate to the main dashboard or click Create Template in the verification templates section.

Step 1: Configuration

Verification Template Identifier The first step is to name your verification template. This name will be associated with the verification process and will serve as the primary reference throughout the platform.

DID Choose the DID (Decentralized Identifier) you want to use as the Verifier. By default, a DID named “My DID” is pre-created for you and can be selected for your first verification template. If needed, you can create another DID.

Jump to the tutorial on creating DIDs

QR Code Viewing Duration Set the duration (in seconds) that the QR code will be visible for users to scan. Once this time elapses, the QR code will expire, and users will need to reload the page to generate a new one. Each QR code has a unique session ID to ensure secure, one-time use.

Consent Duration Specify how long (in days) your organization will store and process the data shared by users. Ensure compliance with local data protection regulations, such as GDPR, which mandates minimizing the retention period for personal data.

When the consent duration has been reached, the user data will be deleted from your Studio account.

Service Description Briefly describe the service for which the user is requesting access.

Step 2: Request

Define which verifiable credentials are required for user verification.

Browse through the list and select the necessary credentials, or use the search bar to find them.

Users must have these credentials in their wallets before requesting access to your services.

Step 3: Requirements

Required and optional credentials

Required credentials mean that the information is mandatory to comply with your authentication process. Any other nice-to-have information should be marked as optional.

Purpose

Select the reason for requesting the previously required credentials from your users. This explanation will be shown to them.

Advanced option: Data agreement

When turned off, there won't be an agreement between you and the user.

Users won't appear as Verified Users, and your organization won't be listed as a Connected Service in their wallets. Therefore, the user won't be able to revoke consent.

Step 4: Restrictions (Optional)

Level of trust

Level of Trust

When requesting credentials from users, decide if they need to meet a specific level of trust. This level, based on standards set by Gataca, is related to the eIDAS regulation’s levels of assurance.

The level of trust reflects how reliable the credential is and how confident you can be that the person presenting it is who they claim to be. This confidence is based on the trust framework in place.

Trusted Credentials are issued by entities that are listed in the Gataca's Public Issuer Registry. To register your DID in a Trusted Registry, submit a ticket.

Trusted Credentials are those whose Issuer is registered in Gataca’s Public Issuer Registry.

Th

Security configuration

Set up any additional security measures users must complete before accessing your services, such as two-factor authentication (2FA) via biometrics, OTPs (one-time passwords), or in-app authentication.

Successful Configuration

Once you've configured the verification template, you’ll see a confirmation that the process has been successfully saved. You can now test your template using our sandbox or can integrate your template with your system.

We recommend testing your templates in the sandbox before integrating it with your system. This allows you to experience the user process firsthand and ensures everything works as expected before going live.