Real-time Transaction Monitoring at $0.02 per call plus Case Management with a Suspicious Activity Report-ready export. 11 seeded rule bundles, AWAITING_USER auto-remediation, 500 verifications free every month.
Robinhood Ventures
Trusted by 2,000+ organizations worldwide.
What the BSA owes
Every US financial institution owes real-time monitoring on every transaction plus a Suspicious Activity Report inside 30 days of detection. Didit ships the rule engine, the case state machine, the auto-remediation loop, and the FinCEN-schema export, at $0.02 per transaction call. 500 verifications free every month.
Pick the checks you want, ID, liveness, face match, sanctions, address, age, phone, email, custom questions. Drag them into a flow in the dashboard, or post the same flow to our API. Branch on conditions, run A/B tests, no code required.
Embed natively with our Web, iOS, Android, React Native, or Flutter SDK. Redirect to a hosted page. Or just send your user a link, by email, SMS, WhatsApp, anywhere. Pick what fits your stack.
Didit hosts the camera, the lighting cues, the mobile hand-off, and accessibility. While the user is in the flow, we score 200+ fraud signals in real time and verify every field against authoritative data sources. Result in under two seconds.
Real-time signed webhooks keep your database in sync the moment a user is approved, declined, or sent to review. Poll the API on demand. Or open the console to inspect every session, every signal, and manage cases your way.
Didit · Transaction Monitoring
Didit · Case Management
OPEN
Alert fires
T+0s
INVESTIGATING
Analyst K. assigned
T+4m
SAR_FILED
Analyst K. + Officer M.
T+2h
CLOSED
Officer M.
T+24h
Didit · SAR export
Didit · AWAITING_USER
Didit · Case Console
Didit · Retention stack
$ 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" }
}'$0.02 per call.docs →$ curl https://verification.didit.me/v3/transactions/$TXN/ \
-H "x-api-key: $DIDIT_API_KEY"
# Returns full case payload,
# flagged transactions, subject KYC,
# counterparty, behavioural context,
# reviewer narrative, HMAC signature.
# Map to FinCEN SAR XML schema.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.$0 / month. No credit card required.
Pay only for what you use. 25+ modules. Public per-module pricing, no monthly minimum fee.
Custom MSA & SLA. For large volumes and regulated programs.
Start free → pay only when a check runs → unlock Enterprise for a custom contract, SLA, or data residency.
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:
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:
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:
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:
Detailed memo, every certificate, every regulator letter: /security-compliance.
Three integration paths, pick whichever fits your stack:
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:
AWAITING_USER with a remediation verification URL on the responseAPPROVED; if not, it moves to DECLINED and a case opens for SAR considerationNet 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:
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:
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.
One API for KYC, KYB, Transaction Monitoring, and Wallet Screening. Integrate in 5 minutes.