Reusable compliance: check once, prove everywhere

Open an account at a bank and you will be asked for your ID, proof of address and the source of your funds. Open an account at a second bank next week and you will be asked for exactly the same things. Neither bank trusts the other’s check, and neither is wrong to be cautious.

The result is a system where the same person is verified dozens of times, at real cost, without the outcome being any safer.

The idea in one paragraph

A regulated institution performs the check once. It then issues a signed statement saying “this customer passed this level of check on this date.” Other institutions can verify the signature and decide whether that level of assurance is enough for their purposes. No documents change hands.

What is actually shared

This is the part people worry about, so it is worth being precise.

• The statement contains the outcome and the level, not the underlying documents.
• The customer chooses when a statement is shared and with whom.
• Every access is recorded in an append-only log the customer can inspect.

What is not shared

Names of other banks the customer uses, transaction history, and anything not needed for the specific check.

Objections we hear

1. “Our regulator will not accept someone else’s check.” Some will not. Many will, if the assurance level is explicit and the audit trail is clean.
2. “Who is liable if the first check was wrong?” This must be agreed up front. We recommend a simple rule: the issuer stands behind the statement it signed.
3. “What about revocation?” Statements carry an expiry and can be revoked; verifiers check status at the time of use.

Where this goes

If it works, onboarding drops from days to minutes for customers who have already been verified, and institutions spend their compliance effort on the cases that genuinely need human judgement. That is a better use of everyone’s time.