免费
免费
每月 $0。无需信用卡。
- 免费 KYC 套件（身份验证 + 被动活体检测 + 人脸匹配 + 设备与 IP 分析）, 每月 500 次，永久有效
- 黑名单用户
- 重复检测
- 每次会话 200+ 欺诈信号
- Didit 网络中可重复使用的 KYC
- 案件管理平台
- 工作流构建器
- 公开文档、沙盒、SDK、MCP（模型上下文协议）服务器
- 社区支持
全球2,000多家组织信赖。
BSA 的要求
监控每笔转账。开启每个案例。按时备案。
所有美国金融机构都必须对每笔交易进行实时监控， 并在发现可疑活动后 30 天内提交可疑活动报告 (SAR)。Didit 提供 规则引擎、案例状态机、自动修复循环以及 FinCEN 格式的导出功能, 每笔交易调用仅需 $0.02。每月免费 500 次验证。
工作原理
从注册到验证用户，仅需四步。
- 步骤 01
创建工作流
选择您需要的检查项, 身份、活体、人脸匹配、制裁、地址、年龄、电话、电子邮件、自定义问题。在控制台中拖放以创建流程，或通过我们的 API 发布相同的流程。支持条件分支、A/B 测试，无需代码。
- 步骤 02
集成
通过我们的 Web、iOS、Android、React Native 或 Flutter SDK 进行原生嵌入。重定向到托管页面。或者直接通过电子邮件、短信、WhatsApp 等任何方式向用户发送链接。选择适合您技术栈的方式。
- 步骤 03
用户完成流程
Didit 负责托管摄像头、光线提示、移动端切换和无障碍功能。在用户进行流程时，我们实时评估 200 多个欺诈信号，并根据权威数据源验证每个字段。结果在两秒内返回。
- 步骤 04
您收到结果
实时签名 Webhook 可确保用户获批、拒绝或发送审核时，您的数据库立即同步。按需轮询 API。或者打开控制台，检查每个会话、每个信号，并按您的方式管理案例。
01 · 规则包
十一个预设规则包。
结构化、速度、Mule 模式、地理风险、受制裁交易方、加密货币特定、旅行规则完整性、新账户激增、休眠-活跃、跨境分层。所有这些都可在无代码工作流构建器中编辑。
交易监控模块Didit · Transaction Monitoring
Eleven seeded rule bundles.
- StructuringUnder $10,000 patterns
- Velocity spikevs user baseline
- High-value txnAbove tier
- Mule patternFast in / out
- Geographic riskFATF grey-list
- Counterparty riskSanction · PEP
- Crypto-specificMixer · sanctioned
- Travel Rule gapMissing IVMS
- New-account spikeFirst 30 days
- Dormant active90+ day gap
Plus cross-border layering bundle · 11 total · all editable in Workflow Builder.
Didit · Case Management
OPEN → INVESTIGATING → SAR_FILED → CLOSED.
1
OPEN
Alert fires
T+0s
2
INVESTIGATING
Analyst K. assigned
T+4m
3
SAR_FILED
Analyst K. + Officer M.
T+2h
4
CLOSED
Officer M.
T+24h
Every transition signed, timestamped, attributed.
03 · SAR 就绪导出
导出时生成 SAR 就绪包。
FinCEN SAR XML 架构，以及支持证据包, 主体 KYC 捆绑包、标记交易、交易方数据、行为上下文、审查员叙述、HMAC 签名。可从您的后端进行电子申报，或推送到您的调查工具。
AML 筛选模块Didit · SAR export
SAR-ready package, on export.
- Subject identityKYC bundle · signed
- Transaction setFlagged + history window
- Counterparty dataVASP attribution + wallet
- Behavioural contextBaseline · velocity stats
- Reviewer narrativeAnalyst notes · timestamps
- HMAC signatureEnd-to-end signed
E-File from your back-end or push into your investigation queue.
04 · AWAITING_USER 自动修复
数据缺失时自动补救。
当交易需要更多客户数据（资金来源、更新地址、刷新自拍）时，Didit 会自动创建补救会话。响应中包含验证 URL，完成后有签名 webhook，交易重新运行。
用户验证模块Didit · AWAITING_USER
Auto-remediation when data is missing.
TriggerAsked of userAction
- Source-of-funds queryBank statementRemediate
- Updated addressProof of addressRemediate
- Selfie re-verificationLive selfieRemediate
- Document re-scanRefreshed IDRemediate
- Counterparty attestationBeneficiary identityRemediate
Verification URL on response · email or in-app deep-link.
Didit · Case Console
Live alerts. One queue.
RuleSubjectScoreStatus
- Structuringuser-4292Open
- Sanctioned walletuser-11898Block
- Velocity spikeuser-9167Review
- Travel Rule gaptx-900144Review
- Mule patternuser-20381Open
Assign · investigate · file · close, same surface.
06 · 留存堆栈
5 年数据保留。欧盟 + 美国驻留。
订阅期间无限期保留，默认欧盟数据驻留，企业合同可选择美国数据驻留。通过 SOC 2 Type 1 和 ISO/IEC 27001 认证。符合 FFIEC 标准的控制措施。
安全与合规Didit · Retention stack
5-year retention. EU + US residency.
- IndefiniteWhile subscribed
- EU by defaultRegulated EU DCs
- US residencyEnterprise
- SOC 2 Type 1+ ISO 27001
- Export ZIPPer date range
- Audit logEvery action
FFIEC-aligned controls
集成
一次交易调用。一个案例。一份签名导出。
提交每笔转账。分类标记的案例。导出 SAR。提交。
POST /v3/transactions/监控
$ curl -X POST https://verification.didit.me/v3/transactions/ \
-H "x-api-key: $DIDIT_API_KEY" \
-d '{
"transaction_id": "tx-9001",
"transaction_details": { "direction": "OUTBOUND", "currency": "USD", "amount": 9500 },
"subject": { "full_name": "J. Doe" },
"counterparty": { "full_name": "Counterparty" }
}'201已创建状态 APPROVED · IN_REVIEW · DECLINED · AWAITING_USER
标记的交易自动开启案例。
每次调用 $0.02。文档 →GET /v3/transactions/{id}/SAR
$ curl https://verification.didit.me/v3/transactions/$TXN/ \
-H "x-api-key: $DIDIT_API_KEY"
# 返回完整的案例负载,
# 标记的交易、主体 KYC、
# 交易对手、行为上下文、
# 审查员叙述、HMAC 签名。
# 映射到 FinCEN SAR XML 架构。200OK案例 OPEN · INVESTIGATING · SAR_FILED · CLOSED
从控制台导出 ZIP，或从您的后端 POST 到 BSA E-Filing。文档 →
代理就绪集成
一键部署 BSA 监控 + SAR 备案。
粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填入您的技术栈。Agent 将构建工作流，连接规则包，开启案例，运行 AWAITING_USER 补救循环，并显示 SAR XML 导出。
didit-integration-prompt.md
You are integrating Didit into a US financial institution (bank, money services business, crypto VASP, broker-dealer, casino, mortgage lender) to satisfy Bank Secrecy Act monitoring + Suspicious Activity Report (SAR) filing under the Financial Crimes Enforcement Network (FinCEN). Three obligations:
1. Monitor every transaction in real time against the eleven seeded rule bundles (structuring, velocity, mule patterns, geographic risk, sanctioned counterparties, etc.).
2. Open and manage cases on every flagged transaction.
3. Export the SAR-ready package matching the FinCEN SAR XML schema for filing via the BSA E-Filing System.
Pricing (verified live 2026-05-16):
- Transaction Monitoring: $0.02 per transaction call
- Anti-Money Laundering (AML) Screening on flagged subjects: $0.20 per check, $0.07 per user per year for ongoing monitoring
- User Verification (Know Your Customer (KYC)) for remediation: $0.33 per check
- First 500 verifications free every month, forever
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60 seconds, no credit card).
- Webhook endpoint with HMAC SHA-256 verification of the X-Signature-V2 header.
HMAC-SHA256 verification MUST run against the raw body bytes (the raw payload as Didit sent it) BEFORE any JSON parsing — re-serialising the parsed body changes whitespace and key order, which invalidates the signature. - A workflow_id for KYC sessions (used on remediation), and Transaction Monitoring + Case Management enabled in the Business Console.
- Optional: integration with the BSA E-Filing System on your back-end OR push to your existing investigation tool (Actimize, NICE, Quantexa, ComplyAdvantage Workflow).
STEP 1 — Monitor every transaction with the Transactions API
POST https://verification.didit.me/v3/transactions/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body (required fields verified live 2026-05-16):
{
"transaction_id": "<your internal transaction id>",
"transaction_category": "finance",
"transaction_details": {
"direction": "OUTBOUND",
"amount": "9500",
"currency": "USD",
"currency_kind": "fiat",
"action_type": "payment"
},
"subject": {
"entity_type": "individual",
"vendor_data": "<your user id>",
"full_name": "<user name from verified KYC>"
},
"counterparty": {
"entity_type": "individual",
"full_name": "<counterparty name if known>",
"payment_method": {
"method_type": "wire",
"account_id": "<counterparty account or routing reference>"
}
}
}
REQUIRED fields the API rejects if missing:
- subject.vendor_data + subject.full_name
- counterparty.full_name
- transaction_details.direction + currency + currency_kind + amount
Response shape (excerpted from a real successful 201):
{
"uuid": "<server transaction uuid>",
"txn_id": "<your transaction_id echoed back>",
"status": "APPROVED",
"score": 0,
"severity": null,
"cost_breakdown": {
"total_price": 0.02,
"items": [{ "usage_type": "transaction_monitoring", "price": 0.02 }]
}
}
Transaction status enum (exact case, UPPER_SNAKE_CASE): APPROVED | IN_REVIEW | DECLINED | AWAITING_USER.
STEP 2 — Branch on the verdict
APPROVED → clear the transaction. Webhook may still update later if Ongoing Monitoring catches a delayed signal.
IN_REVIEW → hold the transaction. Case opens automatically in the Business Console for analyst triage.
DECLINED → refuse the transaction. Case opens at SAR-candidate priority.
AWAITING_USER → the workflow needs more data from the customer (source of funds, updated address, refreshed selfie). The response includes a remediation verification URL — send it to the customer.
STEP 3 — Handle AWAITING_USER auto-remediation
Push the verification URL on the response to the customer (email, app deep-link, push notification). They complete the additional verification in hosted flow on their phone.
On completion:
- The remediation session is LINKED to the original transaction (you'll see the linkage in both webhooks).
- Didit re-runs the relevant rules with the new evidence.
- The transaction moves to APPROVED (clear) or DECLINED (case opens for SAR consideration).
The whole loop takes minutes for the user; your team only touches the cases that genuinely need human judgement.
STEP 4 — Case Management — every flagged transaction opens a case
Cases live in the Business Console with a state machine:
OPEN → alert fires, no reviewer yet
INVESTIGATING → reviewer assigned, gathering context
SAR_FILED → SAR exported and filed; case awaits regulator response
CLOSED → case resolved, no SAR (with reviewer notes explaining why)
Each transition is signed, timestamped, and attributed (analyst name + officer name).
Per case, you get:
- The flagged transaction(s) + the rule(s) that fired
- The subject's verified KYC bundle (document, biometric, AML, device + IP)
- The counterparty data (for crypto: wallet screen; for fiat: counterparty identity if known)
- Behavioural context (user's transaction history, baseline, velocity)
- Reviewer narrative (analyst notes, decisions, escalations)
STEP 5 — Export the SAR package
Two paths:
Path A — Direct from the Console
Click "Export SAR XML" on a case. You get a downloadable package matching the FinCEN SAR XML schema. Upload through the BSA E-Filing System manually.
Path B — Via API + your back-end
GET https://verification.didit.me/v3/transactions/{id}/
Headers:
x-api-key: <your api key>
The full case payload — every field above — is returned as JSON. Map to the FinCEN schema in your back-end and POST to the BSA E-Filing System programmatically.
STEP 6 — Webhook event names
Sessions: standard session webhook for remediation completions (verify X-Signature-V2).
Transactions:
- transaction.created
- transaction.updated
- transaction.status.changed
- transaction.alert.generated
Every payload signed with X-Signature-V2 HMAC SHA-256.
STEP 7 — Ongoing AML monitoring is automatic on every verified subject
Every approved user is re-screened daily against 1,300+ sanctions, PEP, and adverse-media lists at $0.07 per user per year on heavy-volume accounts. When a previously-clean subject crosses an AML threshold, a transaction.alert.generated webhook fires and a case opens automatically.
CONSTRAINTS
- Session statuses Title Case With Spaces; transaction statuses UPPER_SNAKE_CASE. Don't mix.
- SAR filing deadlines: 30 days from detection (extendable by 30 days for suspect identification).
- SAR thresholds: $5,000 aggregate transaction for banks; $2,000 for money services businesses.
- BSA retention: 5 years on every SAR + supporting documentation.
- Tipping-off: NEVER disclose the SAR filing to the subject. Encode this in your customer-comms workflow.
- Default record retention is indefinite while subscribed; configurable per workflow if your supervisor mandates a specific duration.
Read the docs:
- https://docs.didit.me/transaction-monitoring/overview
- https://docs.didit.me/transaction-monitoring/transactions
- https://docs.didit.me/transaction-monitoring/aml-screening
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/integration/webhooks
Start free at https://business.didit.me — sandbox key in 60 seconds, 500 verifications free every month, no credit card.需要更多上下文？请参阅完整的模块文档。docs.didit.me →
合规性设计
一键开启新国家/地区业务。 我们为您解决难题。
我们负责设立当地子公司、获取许可证、进行渗透测试、获得认证，并与所有新法规保持一致。要在新国家/地区发布验证服务，只需轻点开关。已覆盖220多个国家/地区，每个季度进行审计和渗透测试, 是唯一一个被欧盟成员国政府正式认定比线下验证更安全的身份提供商。
阅读安全与合规性档案欧盟金融沙盒
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
信息安全 · 2026
SOC 2 · Type I
AICPA · 2026
iBeta Level 1 PAD
NIST / NIAP · 2026
GDPR
EU 2016/679
DORA
EU 2022/2554
MiCA
EU 2023/1114
AMLD6 · eIDAS 2.0
原生符合欧盟标准
数据证明
数据证明
- $0.00每次交易监控调用, 实时筛选每笔转账。
- 0预设规则包涵盖结构化、速度、洗钱模式、地域风险、受制裁交易对手以及其他典型的《银行保密法》场景。
- 0+对每个主体进行制裁、政治公众人物 (PEP) 和负面媒体名单筛选。
- 0每月每个账户免费验证。
三个层级，一份价目表
免费开始。按使用量付费。可扩展至企业级。
每月 500 次免费验证，永久有效。生产环境按量付费。企业版提供定制合约、数据驻留和 SLA (Service Level Agreements)。
最受欢迎
按用量付费
按用量计费
按实际用量付费。25+模块。公开的模块定价，无每月最低费用。
- 完整KYC $0.33（身份+生物识别+IP/设备）
- 10,000+ AML数据集, 制裁、PEP、负面媒体
- 1,000+ 政府数据源用于数据库验证
- 交易监控 $0.02/笔交易
- 实时KYB $2.00/家企业
- 钱包筛选 $0.15/次检查
- 白标验证流程, 您的品牌，我们的基础设施
企业版
企业版
定制MSA和SLA。适用于大批量和受监管项目。
- 年度合同
- 定制MSA、DPA和SLA
- 专属Slack和WhatsApp频道
- 按需人工审核员
- 经销商和白标条款
- 独家功能和合作伙伴集成
- 指定CSM、安全审查、合规支持
免费开始 → 仅在检查运行时付费 → 解锁企业版以获取定制合约、SLA 或数据驻留。
FAQ
常见问题
What is Didit?
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.
What is the Bank Secrecy Act, in plain English?
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.
What is a Suspicious Activity Report?
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.
How fast is the verification for my end user?
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.
What patterns trigger a SAR?
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.
What happens if a user fails, abandons, or expires?
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.
Where does my customer data live and how is it protected?
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.
Is Didit compliant for my industry?
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.
How fast can I integrate and start verifying users?
- 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.
What is AWAITING_USER auto-remediation, and why does it matter?
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_USERwith 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 toDECLINEDand 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.
How does Didit's stack interact with my existing AML investigation tools?
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.
What about record retention and EU vs US data residency?
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.