Skip to content

Identification with ID Austria

Secure identification in customer service, without security questions.

Your customers confirm their identity with the official Austrian electronic ID, directly from the ongoing contact. Your system receives the result and knows for sure who is asking, at the trust level eIDAS Level High. The solution is based on OpenID Connect and also works with other identity providers.

Who is it really?
Security questions are no longer enough.

Customer service teams usually identify customers with knowledge-based questions such as date of birth, address or customer number. Exactly this data turns up more and more often in data breaches, and phone numbers can be spoofed. With ID Austria, customers confirm their identity with the official electronic ID. Your system then checks whether this identity matches the customer account.

How it works

1. Receive a link

If a request requires identification, the customer receives a link to the official ID Austria login, for example by text message or in chat.

2. Log in with ID Austria

The customer logs in with the “ID Austria” app. The login page shows your company's name and logo.

3. Receive the result

Within seconds, your system receives the result: identity confirmed, matching customer account, trust level. The request continues right away.

Your benefits

Highest trust level

The identity is confirmed by the state, at the highest trust level under eIDAS. That is far more secure than security questions or caller ID.

Data minimization under GDPR

Name and date of birth from ID Austria never leave the authentication component. Only the result, customer number and trust level reach your application.

Any OIDC provider

The process is based on the open OpenID Connect standard and works with any OIDC identity provider, not just ID Austria.

Your use cases

Voice agent

In the middle of the call, the agent sends the login link by text message, and the conversation continues authenticated. You will find an example further down.

Chat

The agent sends the login link in the chat, and the result comes back into the ongoing conversation.

Handover to your team

Identification runs automatically beforehand. Your agents take over a customer who has already been verified.

Use case:
Identification in the voice agent

A caller wants to change their address with their insurance company. This is how the login works during the call. Our demo runs against the ID Austria reference environment with test identities.

1. Recognize the request

The agent recognizes a protected request, such as a change of address, and looks up the matching customer records via the phone number. It only discloses customer data after confirmation.

2. Code by text message

With the caller's consent, the agent sends a text message with a four-digit code from the registered sender.

3. Read out the code

The caller reads the code directly from the notification. This proves that they are holding the mobile phone that belongs to the number.

4. Link to ID Austria

Only now does a second text message follow, with a link directly to the official ID Austria login page – no intermediate page and no short link.

5. Log in with ID Austria

The caller logs in with the “ID Austria” app. The login page shows the company's name and logo. The call stays open.

6. Back to the conversation

The result comes back into the ongoing call within seconds. If name and date of birth match the customer account, the agent unlocks the request and states the trust level.

Watch the demo in 4 minutes

A call to an insurance company: the voice agent logs the caller in with ID Austria in the middle of the conversation and receives the result – confirmed, customer number, trust level “high”.

Shown with a public test identity in the ID Austria reference environment. Xenogent Insurance is a fictitious company.

Secure on the phone

Protection against smishing

The link leads directly to id-austria.gv.at, the sender is listed in the RTR register, and the agent announces both in advance. The text message creates no time pressure and asks for no data entry.

Protection against spoofed numbers

Anyone calling from someone else's number doesn't know the code from the first text message and never receives a login link. If a different person logs in, name and date of birth don't match.

No hanging up

The caller stays on the line during the login. No callback is needed, and the request is completed in the same call.

For IT and architecture:
the technical implementation

OpenID Connect with ID Austria

  • Authorization Code Flow with PKCE (S256) and client authentication via client_secret_post, as required by ID Austria
  • Endpoints and signature algorithms taken from the identity provider's discovery document, nothing hard-coded
  • Full validation of the ID token: signature against the JWKS, issuer, audience, validity, nonce and trust level eIDAS Level High

Stateless auth bridge

The only custom-built component is a lean auth bridge in Node.js and TypeScript. It stores nothing: everything it needs for the return path is encrypted in the OIDC parameter state.

  • state sealed with AES-256-GCM and limited to 10 minutes; tampered or expired responses are rejected
  • PKCE verifier and nonce are derived cryptographically from the state – without a database and without session storage
  • Matching of first name, last name and date of birth against the candidates from the CRM; the state only contains truncated HMAC values for this, no plain-text data
  • Result: unique match, no match or ambiguous. The caller is not told the reason for a mismatch.

Feedback into the ongoing call

The bridge reports the result via the Cognigy Inject API directly into the Voice Gateway session. The voice agent only accepts the first valid result for the current request and discards all others.

Running in Azure Austria East

  • Azure Container Apps with scale-to-zero; secrets exclusively in Azure Key Vault, accessed via managed identity
  • Infrastructure as code with Bicep, deployment via GitHub Actions with OIDC federation instead of stored credentials
  • Minimal dependencies, a waiting period for new package versions, signature and vulnerability checks in CI, and a distroless container without root privileges

Experience the live demo

We show you identification with ID Austria using the example of a call, from the call to the approved change of address, and discuss how it can be integrated into your customer service.