Identity verification for crypto and Web3

What crypto and Web3 services ask of identity checks

A wallet address says nothing about who holds it. A service that opens accounts, takes deposits or sends assets out has to tie each account to a verified person, keep that person from opening many accounts, and be able to say who stands behind a transfer. The rules for these services are written around exactly those points.

• Verify a person with a document and a live face before the account is used.
• Screen the person against sanctions and PEP lists.
• Keep blocked people and duplicate accounts out.
• Verified customer details are the starting point for the originator and beneficiary information that the transfer rules ask for.

The flow

1. Questionnaire. Collect name, birth date, contacts and custom fields before the KYC starts.
2. Document, selfie and active liveness. The user photographs the document, the selfie is matched to the document portrait, and the user moves the face through two ovals. Deepfake and face-swap detection runs inside the selfie and liveness steps.
3. Blocklists and duplicates. Repeat-user search looks for the same face among earlier verified users, and your own person lists and blocklists are checked in the same flow.
4. AML screening. Sanctions of OFAC, EU, UK and UN plus 50+ national lists, PEP with relatives and close associates, and adverse media in 40+ languages.
5. Account level. Rules in the scenario editor decide which account level the result unlocks, and cases that need a person go to the dashboard.
6. Ongoing screening. Monitored profiles are re-screened every day.

Modules used

• Document verification, face verification and liveness.
• Repeat-user search and blocklists, described on the face verification page.
• AML screening with a match threshold from 0 to 100, billed separately.
• Scenario editor and dashboard.
• REST API and webhooks.

Regulatory frame

What the European Union's primary texts say about crypto-asset service providers. The first two statements are from the AML Regulation, which is forthcoming and applies from 10 July 2027. The last two are from the Regulation on information accompanying transfers of funds and certain crypto-assets, which applies from 30 December 2024.

• From 10 July 2027, under Article 19(3) of Regulation (EU) 2024/1624, a crypto-asset service provider applies customer due diligence measures to an occasional transaction of at least EUR 1,000, and at least the identification and verification of the customer's identity to an occasional transaction below that value.
• From 10 July 2027, Article 79(1) of Regulation (EU) 2024/1624 prohibits credit institutions, financial institutions and crypto-asset service providers from keeping anonymous bank and payment accounts, anonymous passbooks, anonymous safe-deposit boxes or anonymous crypto-asset accounts, as well as any account otherwise allowing for the anonymisation of the customer account holder or the anonymisation or increased obfuscation of transactions, including through anonymity-enhancing coins.
• Under Article 14(1) of Regulation (EU) 2023/1113, the crypto-asset service provider of the originator ensures that a transfer of crypto-assets is accompanied by the name of the originator; by the originator's distributed ledger address, where the transfer is registered on a network using DLT or similar technology, and the crypto-asset account number of the originator, where such an account exists and is used to process the transaction; by the originator's crypto-asset account number, where the transfer is not registered on such a network; and by the originator's address, including the name of the country, official personal document number and customer identification number, or, alternatively, the originator's date and place of birth.
• Under Article 14(3), a transfer of crypto-assets that is not registered on a network using DLT or similar technology and is not made to or from a crypto-asset account is accompanied by a unique transaction identifier instead. Article 15 sets separate rules for batch file transfers from a single originator.
• Article 14(1), point (e), adds, subject to the existence of the necessary field in the relevant message format and where provided by the originator, the current LEI or, in its absence, any other available equivalent official identifier of the originator.
• Under Article 16(3), the crypto-asset service provider of the beneficiary verifies the accuracy of the information on the beneficiary on the basis of documents, data or information obtained from a reliable and independent source before making the crypto-assets available to the beneficiary.

This block describes the texts, not our service. For information; not legal advice.

Sources

• Regulation (EU) 2024/1624 of the European Parliament and of the Council, Official Journal text, fetched 26 October 2026.
• Regulation (EU) 2023/1113 of the European Parliament and of the Council on information accompanying transfers of funds and certain crypto-assets, Official Journal text, fetched 27 October 2026.

Next

Try the interactive tour, read the AML screening page or talk to us.