모든 전송에 대한 송신자와 수신자, 모든 전송에 대해.

Didit is infrastructure for identity and fraud, the platform we wished existed when we were building products ourselves: open, flexible, and developer-friendly, so it works as a real part of your stack instead of a black box you integrate around.

One API covers verifying people (KYC, know your customer), verifying businesses (KYB, know your business), screening crypto wallets (KYT, know your transaction), and monitoring transactions in real time, on a stack built to be:

• Fast, sub-2-second p99 on every session
• Reliable, in production with 1,500+ companies across 220+ countries
• Secure, SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person

The footprint underneath: 14,000+ document types in 48+ languages, 1,000+ data sources, and 200+ fraud signals on every session. The Didit infrastructure dynamically learns from every session and gets better every day.

The Travel Rule says that when value moves between two regulated providers, certain pieces of customer information, name, account number, address, must travel alongside the value itself.

It started in traditional finance (the US Bank Secrecy Act of 1970), was extended globally by the Financial Action Task Force (FATF) in 2019, and now applies to crypto everywhere. The standard payload format is InterVASP Messaging Standard 101 (IVMS-101), a JSON schema every major Travel Rule protocol speaks.

The regulator's goal is simple: stop bad actors from laundering proceeds anonymously through chains of providers by ensuring identity data follows the value at every hop.

Every regulated Virtual Asset Service Provider (VASP) or Crypto-Asset Service Provider (CASP), exchanges, on/off-ramps, custodial wallets, brokers, OTC desks, payment institutions that touch crypto settlement.

Live jurisdictions:

• European Union, the Transfer of Funds Regulation took full effect 30 December 2024 alongside MiCA. Applies to every CASP licensed in the EU.
• United States, the FinCEN Travel Rule has been live since 1996 in traditional finance; FinCEN's 2019 guidance extended it to crypto and lowered thresholds.
• United Kingdom, the FCA's cryptoasset rules came into force in September 2023.
• Singapore, Switzerland, UAE, Brazil, Japan, South Korea, all live, each with a slightly different threshold and message format.

FATF runs mutual evaluations of each country's implementation. Non-compliant jurisdictions risk grey-list designation.

The full flow normally takes under 30 seconds end-to-end, pick up the ID, snap the document, snap the selfie, done. That is the fastest in the market. Legacy KYC providers usually take more than 90 seconds for the same flow.

On the back end, Didit returns the result in under two seconds at p99, measured from the moment the user finishes the selfie to the moment your webhook fires. Mobile capture is tuned for slow phones and slow networks: progressive image compression, lazy software development kit load, and a one-tap hand-off from desktop to phone via QR code if the user starts on web.

The minimum FATF dataset is:

• Originator, full name, account/wallet, physical address OR national identity number OR date and place of birth
• Beneficiary, full name, account/wallet, physical address (jurisdiction-dependent)
• The transfer itself, amount, asset, timestamp

The data moves through a Travel Rule protocol between the two providers, not on-chain, not in the transaction memo. Today's market is fragmented: providers pick one or more of TRP, Sumsub Travel Rule, Notabene, Veriscope, OpenVASP, and Shyft. The shared language is IVMS-101, which every protocol reads and writes.

The receiver of the transfer verifies the data before crediting the beneficiary's account.

Every session lands on one of seven clear statuses, so your code always knows what to do:

• Approved, every check passed. Move the user forward.
• Declined, one or more checks failed. You can allow the user to resubmit the specific failed step (for example, re-take the selfie) without re-running the whole flow.
• In Review, flagged for compliance review. Open the case in the console, see every signal, decide approve or decline.
• In Progress, user is mid-flow.
• Not Started, link sent, user has not opened it yet. Send a reminder if it sits too long.
• Abandoned, user opened the link but did not finish in time. Re-engage or expire.
• Expired, the session link aged out. Create a new session.

A signed webhook fires on every status change, so your database always stays in sync. Abandoned and declined sessions are free.

Production data is processed and stored in the European Union by default, on Amazon Web Services. Enterprise contracts can request alternative regions for jurisdictions whose regulators require it.

Encryption everywhere. AES-256 at rest across every database, object store, and backup. Transport Layer Security 1.3 in transit on every API call, webhook, and Business Console session. Biometric data is encrypted under a separate Customer Master Key.

Retention is yours to control. Default retention is indefinite (unlimited) unless you configure shorter, between 30 days and 10 years per application, and you can delete any individual session at any time from the dashboard or the API.

Certifications: SOC 2 Type 1 (Type 2 audit in progress), ISO/IEC 27001:2022, iBeta Level 1 PAD, and a public attestation from Spain''s Tesoro / SEPBLAC / CNMV that Didit''s remote identity verification is safer than verifying someone in person. Full report at /security-compliance.

Didit ships compliant by default for the regulators that matter to identity infrastructure:

• GDPR + UK GDPR, controller / processor split, full Data Processing Agreement published, lead supervisory authority named (Spain''s AEPD).
• AMLD6 + EU AML Single Rulebook, 1,300+ sanctions, politically exposed person, and adverse-media lists screened in real time.
• eIDAS 2.0, EU Digital Identity Wallet aligned; reusable-identity ready.
• MiCA (Markets in Crypto-Assets), ready for crypto on-ramps, exchanges, and custodians.
• DORA, Digital Operational Resilience Act, EU financial-services operational resilience.
• BIPA, CUBI, Washington HB 1493, CCPA / CPRA, US biometric privacy (Illinois, Texas, Washington) and California consumer privacy.
• UK Online Safety Act, age-gating and child-safety obligations.
• FATF Travel Rule, originator and beneficiary data on crypto transfers, IVMS-101 interoperable.

Detailed memo, every certificate, every regulator letter: /security-compliance.

• 60 seconds to a sandbox account at business.didit.me, no credit card.
• 5 minutes to a working verification through Claude Code, Cursor, or any coding agent via our Model Context Protocol (MCP) server.
• A weekend to a production-ready integration with signed-webhook verification, retries, and a remediation flow when a user is declined.

Three integration paths, pick whichever fits your stack:

• Embed natively with our Web, iOS, Android, React Native, or Flutter SDK.
• Redirect the user to the hosted verification page, zero SDK.
• Send a link by email, SMS, WhatsApp, or any channel, zero front-end work.

Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.

Real life rarely produces clean Travel Rule packets, counterparties send partial data, fields don't match the KYC name, address formats differ. Two paths:

• Material missing data (no originator name, no counterparty wallet) → the transaction returns DECLINED and the user is prompted to resubmit
• Partial mismatch (slightly different name spelling, missing middle name) → the transaction returns IN_REVIEW and a case opens in the Business Console with the diff highlighted
• Enhanced due diligence required (high-value transfer, high-risk geography) → the transaction returns AWAITING_USER and Didit creates a remediation session automatically, returning a verification URL on the response

Your compliance team triages the case, requests more data if needed, and approves or rejects from inside the Console. Reviewer notes, decision, and timestamps are recorded for the audit pack.

Travel Rule data is collected per transfer, not per relationship, there is no "refresh" of a Travel Rule packet. But the users behind the transfers must be monitored continuously under the EU AML package and equivalent regimes.

Didit runs:

• Continuous AML monitoring on every verified user, automatic daily re-screen against 1,300+ sanctions, PEP, and adverse-media lists, $0.07 per user per year on heavy-volume accounts
• Transaction Monitoring rule engine on every transfer, velocity, amount, geography, counterparty wallet category, structuring patterns
• Wallet Screening refresh on persistent counterparty addresses, if a previously-clean wallet later becomes sanctioned, the system surfaces it

All three feed the same Case Management surface, so a single reviewer sees the full picture per user.

Most regulators require at least 5 years of records on every Travel Rule transfer and the underlying user identity, sometimes longer if your supervisor requests it.

Didit's retention model:

• All evidence stored in the European Union, regulated EU data centres, no cross-border transfer for EU customers
• Per-transfer record, full IVMS-101 payload, wallet-screen result, verdict, signed HMAC timestamps
• Per-user record, KYC evidence (document, biometric, AML, device + IP), updates over the relationship
• Retained indefinitely while your subscription is active, no per-record retention bill
• Configurable per workflow if your supervisor mandates a specific duration (the AML package allows extension up to 10 years on high-risk relationships)
• Export anytime via the Business Console or the API

Didit is the only KYC provider with a formal EU member-state government attestation, Spain's Treasury, Banco de España, and SEPBLAC jointly attested the service as safer than in-person verification. The report files directly into your CASP authorisation pack.