saascode
legal, compliance & regtech·run 118 · May 2026

Unionsign

A consented credential exchange that carries signed evidence claims, freshness and revocation while preserving each financial institution's verification duty.

Genesis score6.43/10
Make Unionsign real.0/500
500 more votes and Unionsign is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

Financial counterparties repeatedly request overlapping identity, ownership and investigation evidence. The supplied research confirms a funded investor-profile product, a published verifiable-credential standard and a KYC-oriented credential schema, supporting the premise that portable evidence is becoming practical.

Unionsign lets an authorized issuer create a signed credential containing narrowly scoped claims and evidence references. The subject controls presentation to a named verifier for a stated purpose. The verifier checks issuer trust, signature, schema, freshness, revocation and consent, then decides what additional evidence or investigation its own policy requires.

A credential proves that an issuer made a claim under a stated process; it does not make the claim universally true, satisfy another institution's regulatory duty or establish current risk. Source evidence, issuer finding, credential issuance, subject presentation, verifier validation, verifier decision, refresh and revocation remain separate.

The product must minimize sensitive data, support selective disclosure, preserve correction and avoid a permanent shared investigation dossier. The first release should carry a small set of low-ambiguity business identity facts between willing institutions under explicit legal and governance agreements.

Who pays — and why

Compliance operations, financial-crime, onboarding or data-interoperability leader at a bank, fund, custodian, exchange or regulated financial counterparty

What it unlocks
A credential schema separating issuer, subject, claim, evidence reference, collection purpose, method, assurance level, jurisdiction, issuance time, expiry and revocation endpoint
A presentation workflow separating subject consent, requested fields, selective disclosure, verifier identity, stated purpose, delivery, receipt and withdrawal
A verifier ledger separating signature validation, issuer trust, freshness, revocation, policy comparison, additional evidence, investigator decision, review date and correction
How Genesis scored it
6.43across seven criteria
tension 7temporal 7blindspot 6buyer 8leverage 6convergence 5why-not 5
8
Buyer persona

Enterprise compliance and onboarding leaders are concrete, though the first bilateral use case and budget owner require discovery.

7
Productive tension

Portability can reduce repeated collection while creating dangerous overreliance and concentrated privacy risk.

5
Why nobody did it

Standards help interoperability, but the record does not show that institutional trust and liability barriers have broken.

Why it scored well

The supplied research confirms a funded portability product and two active standards relevant to signed compliance claims.

What's holding it back

Cross-institution trust, liability, data protection, revocation and regulator acceptance are governance problems; four referenced interfaces remain unverified in the source record.

Signals detected3 sources crossed
SignalSupplied company and funding research

SignalSupplied standards research

SignalSupplied standards research

Direction briefunionsign.md
unionsign.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.