Onboard verified users without repeating KYC.
Many of your customers have already been verified elsewhere. Kvick ID lets your platform receive their verified details, with the customer's consent, as signed evidence you can stand behind. The verification happens once. Your compliance decision stays yours.
What you receive: the customer's verified details and status, signed. Never a folder of documents. (Sample data.)
How it works for a platform
-
A customer arrives already verified
They completed full KYC once, with a specialist verification provider, at a participating platform. Kvick ID never holds their documents; it holds their verified details and the outcome of that check.
-
You ask, and the customer consents
Your platform asks Kvick ID a single question: is this person verified, at the level you require? Nothing is shared until the customer approves the request. You learn nothing, not even whether an account exists, until they say yes. One yes is all it takes: the approval stands until the customer withdraws it, so your later re-checks are covered without asking them again.
-
You receive signed evidence
The customer's verified details (name, date of birth, nationality, residence) and their status: verified, at what level, by which provider, valid until when. All of it cryptographically signed, so you can file it and prove later exactly what you received, and when the customer authorised it.
-
You make the decision
Kvick ID supplies verification evidence. Whether to accept it, and how it fits your onboarding, stays entirely with your platform. We supply the evidence; you make and own the compliance call.
Exactly what you receive
{
"verified": true,
"level": "standard",
"provider": "sumsub",
"verified_at": "2026-07-04",
"expires_at": "2027-07-04",
"data_scope": "identity_data",
"holder": {
"full_name": "Maria Andersen",
"date_of_birth": "1993-02-11",
"nationality": "DK",
"country_of_residence": "DK"
},
"evidence": { "documents_held_by": "kyc_provider" },
"signature": "eyJhbGciOi…" // verifiable
}
That is the complete payload: the customer's verified details, signed, timestamped, and tied to the specific consent that authorised it. Your team makes its own decision on data it can actually file. If your own regulator later asks what you saw and when, you can show them, and the evidence marker tells you where the underlying documents live, available on request from the provider that holds them. The consent behind it has no expiry date; it stands until the customer withdraws it, and you can re-check whenever your monitoring needs it. If the customer withdraws, or a verification is retracted, you are notified at once. And if a customer withdraws and later shares the same verification with you again, you are not charged again: one verification is billed once, however many times consent is toggled. Only need an extra signal on top of your own KYC? Request the status-only scope instead: same signature, no personal details. Every value above is sample data.
Built in, by design
- Zero document custody, full document access. The files stay with the specialist provider that checked them, exactly as with your own KYC today, and copies remain available on request for the day your regulator asks. You just carry no extra document store.
- A recorded consent for every field. The customer sees exactly what they are sharing before they say yes, and you can show your regulator the consent behind every data point you hold.
- Your customer list stays yours. You learn nothing about other platforms' customers through us, and they learn nothing about yours.
- Nobody can use us as a directory. A request about any email looks identical from the outside until the customer approves it, so accounts cannot be fished for.
Why platforms work with us
- Neutral by design
- No platform gets preferential treatment, and none learns about another's customers through us. Neutrality is what makes a shared verification layer trustworthy, so it is built in, not promised.
- European by design
- All personal data is hosted in EU data centres, and the operating company is being established in the EU. Built around EU AML and GDPR requirements from the first line of code.
- No document custody
- Documents stay with the specialist provider that checked them, available on request when your process requires a copy. Kvick ID holds the verified details and the outcome, never the files, so relying on us does not hand you a new pile of sensitive documents to guard.
- Provable, not just asserted
- Everything shared is cryptographically signed and tied to a recorded consent, so what was shared, and when, is verifiable later by either side.
Where the line sits. Kvick ID is a verification evidence source. It does not perform, outsource, or replace your KYC or AML programme, and it does not make onboarding decisions for you. Your platform relies on the signed evidence for its own decision, and that decision, along with responsibility for it, stays with you. We are building toward the requirements a regulated platform has to meet, but we make no compliance claims on your behalf.
Interested in a pilot?
Kvick ID is in development and running end to end on synthetic test data while formal legal review is prepared. We are speaking with regulated platforms about early pilot integrations. If that is you, we would rather talk directly than route you through a form.
Contact us about a partnership