HOLD · THE SCREEN WHERE YOU DECIDE

You approve a specific request, or you do not.

Every consent screen you have ever met was designed to be got past. This one is designed to be read, because it is short enough to read: one screen, five questions, and no third option hidden behind a link called "manage preferences".

The one thing this page is about.

What the screen says, line by line — and why every line is a specific fact rather than a category.

The screen, drawn.

Line by line, and why.

Who is asking

Northbank Building Society

Their own verified name on the internet, not a logo somebody uploaded. If that name cannot be checked, the wallet says so here instead of drawing a badge.

What for

To open an account, they must confirm you are over eighteen.

The reason is written by whoever is asking and shown to you unedited. A request with no stated reason is still shown — with the reason line reading that none was given.

Exactly what will be sent

over_18 — yes

One line, named, with its value. Not "your identity details". Not "basic profile". If a request asks for four things, four lines appear here and you can see all four before anything moves.

What stays

date_of_birth · full_name · home_address · document_number

The lines that are not being sent are printed as well, so the screen is a comparison and not an assurance. These are not withheld from the message. They are not put into it.

For how long

This request only. Nothing is kept open afterwards.

There is no standing permission and no "remember this site". A second request is a second screen.

The three tricks this screen refuses.

No pre-ticked boxes. Nothing is agreed to on your behalf while you read. The screen opens with nothing selected, and closes with nothing sent unless you sent it.
No category words. "Basic profile information" is a way of not telling you. Every line on this screen names a field and shows its value.
No quieter refusal. The control that declines is the same size, the same weight and the same distance from your thumb as the one that approves.

In every language we ship.

A consent screen that only works in English is a consent screen that most of the world cannot give consent on. The five questions are translated with the rest of the wallet, and the two right-to-left languages we ship lay the screen out in their own direction rather than mirroring an English page badly.

A permission somebody could not read is not a permission.

Before you go any further.

The screen above describes how approval works in the wallet. Whether you can reach that wallet, on what device, is a separate question, and it has its own answer.

Sending one line instead of five, the wallet on the web, the wallet on a phone, and the account behind both.

PLANNED A wallet a person installs from an app store. wallet-native You cannot hold a credential on a phone you own. Everything a person would do with a proof waits behind this.

The register holds 17 live · 2 partial · 2 planned · 5 not yet.

3 of the 4 capabilities this page depends on have no row in the register yet, so this page will not print a state for them. They are named rather than dropped, because a slice that silently shortens itself is the same defect as a claim with no receipt.

selective-disclosure
wallet-web
holder-portal

The register route serves, but it carries no row for these yet. List what it does carry:

curl -s https://id.orbis.id/api/site/register | jq -r '.entries[].slug'

Straight answers.

Can I approve part of a request?: No. A request is a set of lines and you either send that set or you send nothing. Partial approval sounds generous and in practice becomes a negotiation you always lose, because the other side simply asks again.
What if I approve something by mistake?: The line has been sent and cannot be recalled — this is a message, not a permission you can switch off later. What you can do is stop the next one: nothing stays open after a request.
Does ORBIS see this screen, or what I chose?: No. The decision happens on your device, between you and whoever asked. There is no approval log on our side to read, and therefore none to hand over.
Why is the reason written by the person asking?: Because we cannot know their business and will not invent it. Showing their words unedited is also what makes a bad reason visible — a request that cannot explain itself in one line looks exactly as thin on this screen as it is.