01
One entry point
Create, inspect and cancel verifications through the same Product API used by your integration and the console.
AFFINITY / Verify Gateway
Verify what matters.
Keep less.
Accept verifiable credentials through a QR code or deep link. Connect a wallet presentation to your process and limit how long disclosed data is retained.
Pilot integration · scope agreed with you
Verify GatewayInteractive example
One proof. One answer.
Requested requirementOver 18
OIDC4VPExample resultRequirement verified
The requested attribute meets the example requirement.
Presented attribute
age_over_18: trueChange the credential status
Try the controls · simulated data
01 / The problem
More data does not always mean more certainty.
Every check adds another integration, another document copy and another decision to explain. Your product needs a clear result without taking on all the complexity of a wallet.
02 / What's included
From a credential to a usable result.
02
Trust checks
Combine signature, holder binding, status and issuer checks according to the format and configuration.
03
Controlled retention
Configure how long disclosed attributes are retained and their scheduled deletion, separately from the receipt.
04
Operational context
Inspect statuses and technical reasons. Supported flows attempt to generate evidence of the decision.
03 / How it works
From a request to a decision.
- 01
Define the request
Start a verification through the API with your requirements and a published trust model where applicable.
- 02
Connect the wallet
Display a QR code or deep link so the holder can present a credential from a compatible wallet.
- 03
Receive the result
Check the status, decision reasons and associated receipt when one has been generated.
04 / IN YOUR CONTEXT
Built around real problems.
Every integration starts with a specific use case. Here are a few starting points.
Let's talk01Age eligibility
Request an eligibility attribute, such as being over 18, rather than a complete document copy. Agree the model and acceptance criteria for each integration.
02Professional credentials
Check a credential, its issuer and validity using the available sources. Validate the wallet, format and process rules in the pilot.
03Credential-based onboarding
Explore accepting PID or a KYC credential from an agreed issuer. Technical verification complements your organisation’s obligations.
PRODUCT SCOPE
Clarity from day one.
What you can explore today
Pilot flow with Product API, OIDC4VP QR/deep links and result queries. Interoperability, decision criteria and receipt generation are validated for the specific use case.
Where it is heading
Complete business policy enforcement, external interoperability and operational guarantees continue to evolve. Compatibility with every wallet and EUDI certification are not assumed.
Verify Gateway
Your use case. Our next conversation.
Tell us what you want to solve. We’ll define the scope and the next step together.
Let's talkView overview