Skip to main content

For business

Request what you need.
Let customers choose.

Ask for the details your process needs. The customer sees the request, chooses what to share, and you get the result.

Ask about integration

Consent

The customer reviews every request

Less

Only the details your process needs

Recorded

Each request and response on file

New request

Purpose

Tenant application

Full name Current address Date of birth
Official status check
Send request
  1. Request
  2. Review
  3. Result

The cost of asking for everything

Asking for everything costs twice.
Once at signup. Again in storage.

Drop-off

Long signups lose applicants

Every extra document you ask for slows the application down, and some people never finish it.

Liability

Every copy you keep is yours to protect

ID copies and utility bills on a shared drive, carrying far more than you needed.

Bottleneck

Manual checks do not scale

Chasing documents and reading them by hand turns your team into a queue.

Result Shared
Full name John Doe
Current address 123 Main Street
Date of birth Not shared
Customer approved · 17 Sep, 10:42

What comes back

The details they approved.
A clear record.

The customer sees the request and approves it. You get what they shared, with a record of the request.

Two kinds of request

Shared information is not an official check.

Virtuall keeps them apart, so you both know which one you asked for.

Shared information

Share information

The customer shares details from their Virtuall identity, like their name or address. You get what they approve.

  • Details or a supported proof the customer approved
  • The customer sees the purpose and every field
  • A record of what was shared and when
  • Ask only for what your process needs
Official status

Require official status

When your process needs an official check, the request says so. The customer agrees before it runs.

  • Clearly marked in the request
  • The customer consents before any check runs
  • For processes that need an official status
  • Your own compliance obligations still apply

Official status checks are still in testing. The customer is always asked first.

Not sure which one you need? Tell us what you have to check.

Ask about integration

Who it's for

For teams that have to ask.

  • Property

    Tenant applications, current address, contact details

  • Financial services

    Account opening details, address confirmation

  • Insurance

    Policy applications, address and identity details

  • Employers

    Onboarding details for new staff

  • Retail & e-commerce

    Delivery address, age checks where supported

  • Telco

    Contract applications, proof of address

Don't see your industry? Tell us about your process.

Talk to us

Records and responsibility

A clear record of every request.

Every request keeps its story

The purpose, the fields and the customer's answer. When someone asks later why you held an address, the record says so.

Virtuall helps you ask for less.

Your POPIA and FICA obligations stay yours. Anything you keep is still yours to protect.

Customer consent

The customer reviews the information before sharing.

Selected details

Review the approved details and the sharing record.

Restricted access

Access to stored documents is controlled.

Official status

Checks that ask the customer to consent first.

Under the hood

Built on open standards.

Credentials belong to the person holding them, not to us, and not to you. We are aligning to the same formats the EU digital identity wallets use, so what your customers hold keeps working outside Virtuall. Here is what runs today and what we are still building.

Credentials held by the person
Live Each credential is bound to a key on the holder’s own device, so it cannot be replayed by someone else.
Selective disclosure
Live The customer approves field by field. What they leave out is never sent to you.
Verifiable credential formats
In development Moving to SD-JWT VC under the EU HAIP profile, with mdoc for ID and licence credentials.
Open issuance and presentation
In development OpenID4VCI for issuing and OpenID4VP for presentation, so other wallets and verifiers can take part.
Proofs that answer without revealing
Planned Predicate proofs, such as 18 or older, aligned to the EU mdoc-ZK work rather than a scheme of our own.
Standards-based revocation
Planned Credential status published as an IETF Token Status List.

Anything marked in development or planned is not something you can rely on today. Ask us where a specific piece stands before you build against it.

Ask for what you need.
Let customers choose.

Tell us what you need to check. We will walk you through it.

Ask about integration