BSA SAR workflow
From AML alert to filed SAR, documented end to end.
A suspicious activity report is only as strong as the trail behind it. Amani raises alerts from AML screening and ongoing monitoring, packages the evidence into a case, routes it through review, and exports a filing-ready record.
The challenge
Compliance teams stitch alerts, spreadsheets and email threads into SAR narratives by hand - slow, inconsistent, and hard to defend when examiners ask how a decision was reached.
With Amani
- Alerts raised from sanctions, PEP and adverse-media matches
- Investigation workspace with the linked identity evidence
- Four-eyes approval and SLA tracking built in
- Filing-ready exports aligned to BSA SAR and goAML formats
- Complete, immutable audit trail per case
The stack
Modules powering this flow.
Switch these on in Amani Studio - or call them directly from one API.
For developers
Build this flow.
Three API calls start the session; the modules above run inside it. Compose the journey in Amani Studio without code, or let your AI coding agent wire up the SDK from a single prompt.
- JWT auth with refresh tokens
- Regional base URLs (EU · TR · UAE)
- HMAC-signed webhooks with retries
- 27 languages in the SDKs
verify.sh
# 1 · Authenticate (server-side only)
curl -X POST 'https://ae.amani.ai/api/v2/user/login/' \
--form 'username="you@company.com"' \
--form 'password="••••••••"'
# 2 · Create the customer profile
curl -X POST 'https://ae.amani.ai/api/v2/profile' \
-H 'Authorization: Bearer $ACCESS_TOKEN' \
--form 'id_card_number="784199012345678"' \
--form 'name="Layla Haddad"'
# 3 · Generate the verification URL
curl -X POST 'https://ae.amani.ai/api/v2/profile/url' \
-H 'Authorization: Bearer $ACCESS_TOKEN' \
-H 'Content-Type: application/json' \
--data '{
"profile": PROFILE_ID,
"web_sdk_url": "https://verify.amani.ai",
"language": "en",
"return_url": "https://yourapp.com/verified"
}'
# This session runs: AML / Sanctions Screening, Amani Studio, KYC.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › In our Node backend, screen every new customer against Amani AML on signup and store the report ID against their record.
# The matching skill fetches the live docs, pins the
# current SDK version and wires up the integration -
# secrets left as placeholders. Claude Code, Cursor and
# any Agent-Skills-compatible tool.webhooks.ts
// Amani signs every webhook with an HMAC signature using
// your secret. Always verify it before processing.
import crypto from 'node:crypto';
app.post('/webhooks/amani', (req, res) => {
// Confirm the exact header name in the Webhooks API reference.
const signature = req.get('X-Amani-Signature') ?? '';
const expected = crypto
.createHmac('sha256', process.env.AMANI_WEBHOOK_SECRET)
.update(req.rawBody)
.digest('hex');
const valid =
signature.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
if (!valid) return res.status(401).end();
const { profile, status } = req.body;
if (status === 'approved') activateAccount(profile);
res.status(200).end();
});BSA SAR workflow - common questions
Does Amani file the SAR for us?
No - Amani produces the investigation record and filing-ready export; submission remains with your MLRO.
Can we customise the narrative template?
Yes - case templates and required fields are configurable to your internal standards.
How long is case data retained?
Retention is configurable to your regulatory obligation, with immutable audit logging throughout.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.