Reusable KYC. The verification you already built doesn't travel, until now.

No external organization runs this in production yet; the demo shows what portability looks like, not who has bought it. That's the whole claim on this page. Everything below is the arithmetic and the mechanics behind it.

The credential pipeline has not been through an external audit. SOC 2, ISO 27001, and eIDAS QTSP status are 2027 roadmap items, none are held today. No named customer, pilot, or design partner exists yet.

The mechanism, briefly

A relying party runs one KYC check through Solidus and the result is issued back to the user as a W3C Verifiable Credential, not stored as a record only the issuer can query. The full mechanism, issuance, presentation, the trust triangle, is covered in how it works; this page assumes that and moves straight to what portability is worth.

Reuse clusters: where "different relying party" isn't hypothetical

The wedge only pays off if reuse crosses organizational boundaries, not just repeat visits to the same vendor. Two clusters make that concrete:

The Traveller cluster, hotel check-in → airport transfer → car rental → the next flight's identity check. A guest KYC'd once at check-in carries the same credential through three more unrelated businesses on the same trip. /industries/hotel-kbs works this cluster's entry point in the context of Turkey's KBS guest-registration requirement.

The Resident cluster, telecom SIM registration → bank account opening → an age-gated purchase → a property lease → a pharmacy pickup. These are five different regulatory regimes today, each demanding its own KYC pass on the same person. /industries/esim-telecom seeds this cluster from the telecom end; /industries/age-verification sits in the middle as the universal primitive: an age check is the one verification almost every relying party in the Resident cluster eventually needs, regardless of vertical.

Neither cluster requires the relying parties to know about each other or integrate with one another. They only need to trust the same credential.

The worked economics

These numbers are not derived independently on this page, they're the same inputs /pricing uses. If the two ever disagree, that's a defect to fix, not a stylistic choice.

Take a modeled Solidus first-check price of $5.00 (KYC L2 rack rate) against Sumsub's own sourced range of $1.50–$2.50/verification, using $1.50 as the representative incumbent first-check price. After the first check, Solidus reuse is modeled at $0.05 per presentation; an incumbent re-verifying the same person from scratch charges its full first-check price again, every time.

Cumulative cost after n verifications:

• Solidus: 5.00 + 0.05n
• Incumbent (re-verify every time): 1.50(n + 1)

Setting them equal: 5.00 + 0.05n = 1.50(n + 1) → n ≈ 2.4. Below roughly 2–3 verifications of the same person, Solidus is the more expensive option: the first check costs more than an incumbent's first check, plainly. Past that crossover, every additional reuse is a small fraction of a repeat incumbent check, and the gap widens with every relying party that joins the cluster.

Underneath the $0.05 reuse price sits a separate, lower number: a modeled protocol-layer floor near $0.001 per verification, the marginal compute and storage cost of validating one presentation on-chain, before any product margin or operational overhead is added. That figure is illustrative of how much room exists between protocol cost and reuse price; it is not a rate anyone is billed.

What reuse is not

A reused credential is convenience and cost savings for the relying party: it is not a transfer of their own regulatory KYC obligation. Each relying party still owns its own compliance posture; Solidus shortens the re-verification step, not the obligation itself.

The term this page extends

"Credential portability" is defined plainly in the Lexicon. That's where the term is owned and kept precise. This page doesn't redefine it; it gives the term its commercial shape: the reuse-cluster mechanics and the crossover math above are what portability is worth to a vendor deciding whether to plug into the network.

Sizing the network, not one relationship

A software vendor embedding Solidus into a PMS, POS, or telco dealer flow isn't pricing a single relying-party relationship, see /pricing for that math, it's sizing a network where every additional relying party that accepts the same credential pushes more of its own users past the crossover point for free. That's the ROI shape worth modeling before committing engineering time to the integration: not "what does my first check cost," but "how many of the relying parties my users already touch would accept a credential they already hold."