Product
Everything between “new user” and “trusted user”
Identity Inc. is a product built by RORO Technology. It takes a person from an identity check to a sponsored account they can keep, and it leaves the identity documents with the provider that captured them, so your team never has to store or secure them.
Identity before the account
A government ID and a selfie come first. Only an approved person receives a sponsored account, and they choose the name. Email and phone codes, if you use them, are a separate step and are not identity.
Identity verification on demand
Trigger an ID check from your backend whenever your rules require one. The user photographs an ID and takes a selfie; you get an approved or rejected result back, usually in minutes.
Business verification
For company customers, verify the company and the people who control it, not just an individual.
Sanctions and watchlist screening
Every verified person is checked against sanctions and politically-exposed-person lists, then re-checked as those lists change.
Proof that survives an audit
Every decision is written to a log where each entry is chained to the one before it, so you can hand an auditor an export and demonstrate that nothing was edited or removed.
Fraud and abuse limits
Signup caps, shared-device clustering, and access that only widens after a clean verification — so your free tier does not become a farm.
One integration, every app
Run several products from one account, each with its own key, its own country policy, and its own retention rules. Your users verify once.
Data you do not have to hold
Identity documents stay with the verification provider. You hold a signed result and a fingerprint of each document — never the document itself.
What you have to do
- Call the API from your own server.
- Start identity verification, wait for approval, create the sponsored account with the one-time token, and store the account ID.
- Have the user sign the bind challenge on their own device, then unlock the account.
- Read one status field before allowing the sensitive action.
That is the whole integration. Most teams have it running the same day.
Plain English
This industry is full of acronyms. Here is every one we use, in ordinary words. You do not need any of them to buy or use the product.
- KYC — Know Your Customer
- Checking that a person is who they say they are, usually with a government ID and a selfie. Required by law before many financial services can be offered.
- KYB — Know Your Business
- The same idea for a company: confirming the business exists and identifying the people who own or control it.
- AML — Anti-Money Laundering
- The set of rules that require you to check customers against sanctions lists and watch for suspicious activity.
- PEP — Politically Exposed Person
- Someone in a prominent public role, or close to one. Not an accusation — it simply means the account carries more risk and needs extra care.
- IDV — Identity Verification provider
- The company that inspects the ID document and the selfie. In production that is Shufti Pro. The documents stay on their side, not ours.
- PII — Personally Identifiable Information
- Any data that identifies a real person: name, date of birth, passport number, photograph. The less of it you store, the smaller your risk.
- DID — Decentralized Identifier
- A permanent ID for a person or an account that is not owned by any one company. In practice: the API returns a string and you save it next to your user record. You never have to think about it beyond that.
- Backend, server-side, BFF
- Code that runs on your own servers rather than in the user's browser or app. A BFF (“backend for frontend”) is just the small server your own app talks to. Our API key must only ever be used there — anything shipped to a browser can be read by anyone.
- Binding
- The step where a verified person signs a one-time message with the key on their own device. It is what ties one verification to one account so it cannot be reused elsewhere.
- Attestation
- A signed statement from us saying “this check happened and this was the result”, without repeating the personal data behind it.
- Contact proof
- A one-time code sent to an email address or phone number. It proves that channel works. It is not KYC, it does not identify a person, and it cannot be swapped in for an ID check.
- Provisional account
- A real blockchain account that exists before full verification, with sponsored fees and tighter limits. After KYC and bind, those limits lift.