How it works

Ask once. Get one clean answer.

Your service asks VADRA. The person signs in with an ID they already have. The issuer confirms, and VADRA returns one clean result. No identity data is stored.

The steps

Four steps, one integration.

How VADRA worksYour service asks VADRA to verify a person. VADRA routes the person to an identity they already have. The issuer confirms. VADRA checks the answer against your policy and returns one clean result. The source stays visible, the issuer stays the authority and no identity data is stored.Your serviceBank, portal or platformGatewayIdentity sourceNational eID, wallet, bank-ID1RequestVerify this person2RoutePerson signs in3ConfirmIssuer answers4ResultOne clean answerSource stays visibleSee who issued it, and at what level.Issuer stays the authorityNothing is copied or re-issued.No identity data storedWe route and check. We keep nothing.
  1. Request. Your service asks VADRA to verify a person.
  2. Route. The person signs in with an ID they already have.
  3. Confirm. The issuer answers. It stays the authority.
  4. Result. VADRA checks it against your policy and returns one clean result. No identity data is stored.

The problem

Stop building one bridge per country.

Every identity scheme has its own rules, formats and contracts. Connecting them one by one costs months and never ends. With VADRA, each service connects once.

Without a gateway versus with VADRALeft: five ID schemes and four services joined by twenty separate integrations. Right: the same schemes and services each connect once to VADRA in the middle.Without a gateway.Every service connects to every scheme.ID schemesServices20 integrations to buildWith VADRA.Every service connects once.ID schemesServices1 integration per service
Integrations to build: direct versus through VADRAAccepting 1, 5, 10, 20 or 30 identity schemes directly takes the same number of integrations. Through VADRA it always takes one.Integrations to build and maintainBy number of identity schemes a service acceptsDirect, one per schemeThrough VADRA01020301 scheme: Direct = 1 integration1 scheme: Through VADRA = 1 integration15 schemes: Direct = 5 integrations5 schemes: Through VADRA = 1 integration510 schemes: Direct = 10 integrations10 schemes: Through VADRA = 1 integration1020 schemes: Direct = 20 integrations20 schemes: Through VADRA = 1 integration2030 schemes: Direct = 30 integrations30 schemes: Through VADRA = 1 integration30Identity schemes accepted301
30 → 1

One integration instead of 30.

Accept 30 identity schemes directly and you build and maintain 30 integrations. Through VADRA, you build one.

Illustrative.

How we start

Start small. Scale fast.

A pilot proves value with real users before anything grows.

Pilot journey in five stepsSelect, Connect, Pilot, Measure, Expand.01Select2–3 countries, 1–2 use cases02ConnectLink trusted IDs through VADRA03PilotReal journeys, real services04MeasureAdoption, cost, effort05ExpandMore countries and services
  1. Select. 2–3 countries, 1–2 use cases.
  2. Connect. Link trusted IDs through VADRA.
  3. Pilot. Real journeys, real services.
  4. Measure. Adoption, cost and effort.
  5. Expand. More countries and services.

Let's build together

Connect identities.
Enable opportunity.

Tell us your corridor or use case. We'll show you the demo and map a pilot with you.