모든 거래를 모니터링하고 SAR을 제출하세요.

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 Bank Secrecy Act (BSA) is the foundational US anti-money-laundering law, passed in 1970 and amended many times since. It requires US financial institutions to help the government detect and prevent money laundering by keeping records, reporting suspicious activity, and reporting large currency transactions.

The rulebook is enforced by the Financial Crimes Enforcement Network (FinCEN), a bureau of the US Treasury. Examinations are run by the institution's primary federal regulator, the OCC for national banks, the Federal Reserve for state-member banks, the Federal Deposit Insurance Corporation (FDIC) for state non-member banks, the National Credit Union Administration (NCUA) for credit unions, and the SEC + FINRA for broker-dealers.

In 2020 the Anti-Money Laundering Act of 2020 modernised the regime, beneficial-ownership reporting, regulatory expansion to cover dealers in antiquities, and the Corporate Transparency Act layered on top.

A Suspicious Activity Report (SAR) is a confidential filing a US financial institution submits to FinCEN whenever it spots a transaction or pattern that may indicate money laundering, fraud, terrorist financing, or other criminal activity.

Filing rules:

• Threshold, banks file when an aggregate transaction reaches $5,000 and the institution suspects illicit activity. Money services businesses file at $2,000.
• Timing, file within 30 days of detection, extendable by 30 days if a suspect is being identified.
• Confidentiality, prohibited from disclosing the filing to the subject. Tipping-off violations carry criminal penalties.
• Format, submitted via the BSA E-Filing System in the FinCEN SAR XML schema.
• Retention, keep a copy of the filed SAR plus all supporting documentation for 5 years.

FinCEN uses SARs to build investigative leads; agencies like the FBI, IRS-Criminal Investigation, and DEA query the database constantly.

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.

FinCEN's SAR guidance covers many categories; the common ones:

• Structuring, breaking large transactions into smaller ones to avoid the $10,000 Currency Transaction Report (CTR) threshold. Pattern of $9,500 deposits over a few days.
• Velocity anomalies, sudden burst of transactions inconsistent with the customer's profile
• Geographic risk, transactions to or from high-risk jurisdictions, FATF grey-list countries
• Mule patterns, money flowing in and immediately out, often to multiple beneficiaries
• Sanctions hits, counterparty matches an OFAC list
• Identity fraud, synthetic identities, document forgery indicators surfaced post-onboarding
• Cyber-event-related, transactions connected to a ransomware payment, business email compromise, or account takeover
• Insider abuse, embezzlement, employee-driven activity

FinCEN expects rule-based and behavioural detection, not just a checklist. A real Transaction Monitoring programme tunes rules to the customer base and the institution's risk profile.

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.

A common monitoring outcome is we need more information from the customer before clearing this transaction, proof of source of funds, an updated address, a re-verified selfie.

Legacy stacks force your operations team to handle this manually: email the customer, wait, chase, re-screen. AWAITING_USER auto-remediation closes the loop automatically:

• The transaction returns status AWAITING_USER with a remediation verification URL on the response
• Send the URL to the customer (email, app deep-link, push), they complete the additional verification on their phone in hosted flow
• The remediation session is linked to the original transaction; on completion, a signed webhook reopens the transaction and Didit re-runs the relevant rules with the new evidence
• If the user clears, the transaction moves to APPROVED; if not, it moves to DECLINED and a case opens for SAR consideration

Net effect: a remediation loop that used to take days now takes minutes, the audit trail is complete, and your team only touches the cases that genuinely need human judgement.

Didit produces SAR-ready evidence; you bring whatever filing and investigation tooling you already use.

Integration patterns:

• Direct e-filing, pull the case XML via the API and post it to FinCEN's BSA E-Filing system from your own back-end
• Investigation case management, push case identifiers + payload URLs into Actimize, NICE, Quantexa, ComplyAdvantage Workflow, or your internal queue via webhook
• Data warehouse, every transaction event lands on your warehouse via webhook for long-horizon analytics
• AML hits enrichment, Didit's AML Screening produces 1,300+ source-cited hits; chain into your investigation team's preferred enrichment provider for deeper open-source intelligence
• MCP server, your AI agent (Claude, Cursor, internal copilots) can read cases and propose narrative drafts via the Didit MCP server

Didit's surface is intentionally narrow: it captures, scores, monitors, opens cases, and stores evidence. Whether the SAR file leaves Didit or your downstream system is your call.

BSA requires 5 years of records on every SAR plus supporting documentation. Didit's defaults:

• Indefinite retention while your subscription is active, no per-record retention bill, no expiry surprises
• EU-resident storage by default, regulated EU data centres, with US data-residency available on enterprise contracts for institutions that need it
• Every payload signed with HMAC SHA-256 so chain-of-custody is provable for an examiner
• Configurable per workflow if your supervisor mandates a specific duration
• Export anytime via the Business Console or the API, bulk ZIP per date range or single-record JSON

Didit is SOC 2 Type 1 and ISO/IEC 27001 certified, with the audit reports and controls catalogue available under NDA from /security-compliance. For US institutions specifically, the platform's separation-of-duties, encryption-at-rest, and access-logging meet the standards examiners look for under FFIEC Information Technology guidance.