Key Takeaways
- Sanctions-hit CSV is case last-four and queue code — never a full legal name or list-match essay in SMS.
- Validate rows before the SIM. A bad hit column still burns operator credit.
- Keep login OTP off the ops tablet that dumps screening-file bursts.
- Service pricing is devices plus SMS send volume. You bring the Android phone and operator credit.
- Free is 1 device, 300 SMS lifetime, 300 contacts. Developer is 25,000 SMS per year.
- Idempotency on screening-trace id, not on “entity + today.”
Summary
Fintech CSV in scenario 989 is a sanctions-screening hit queue: case last-four, queue code, portal. Unlike statements, collections, card-decline, payroll, insurance claims, loan drawdown, KYC expiry, merchant settlement, chargeback, APR change, dividend, travel-card FX-reload, ACH R-codes, wire recall, BNPL skip, or UBO refresh, this file is a compliance-hold batch.
Service pricing is devices plus SMS send volume. You bring the Android phone and operator SMS credit. Free is 1 device, 300 SMS lifetime, 300 contacts. Developer is 25,000 SMS per year. Starter, Professional, and Business list Unlimited SMS as platform send volume; devices and airtime stay metered.
A list-match dump in SMS is screening evidence you leaked. Validate the CSV. Send case last-four and queue code. Keep the match in the portal.
Key takeaways
- Sanctions-hit CSV is case last-four and queue code — never a full legal name or list-match essay in SMS.
- Validate rows before the SIM. A bad hit column still burns operator credit.
- Keep login OTP off the ops tablet that dumps screening-file bursts.
- Service pricing is devices plus SMS send volume. You bring the Android phone and operator credit.
- Free is 1 device, 300 SMS lifetime, 300 contacts. Developer is 25,000 SMS per year.
- Idempotency on screening-trace id, not on “entity + today.”
Related reading
Start from two-way SMS inbox, compare contacts, lists, and segments, open transactional SMS for orders and alerts, and review FATF screening notes where they apply.
Context
Ops desks land here after a replayed screening file texted twice, or after a column leak included a full legal name. Banking OTP cannot share that tablet.
Core scenario guidance
Validate rows. Strip names and match detail. Template: case last-four, queue code. Idempotency on screening-trace id. Isolate OTP. Cap retries.
| Column | SMS body | Fail closed |
|---|---|---|
| Case | Last-four + queue code | Full name / list match |
| Idempotency | Screening-trace id | Entity + today |
| Retry | Cap + DLR | Blind re-import |
| Banking OTP | Separate device | Same SIM as screening burst |
Canary a staff hold after OS updates. MCP wraps REST. Developer Center owns fields.
Cost and ownership
Devices + volume + operator airtime on every bad import. Developer is 25,000 SMS per year. Free (1 / 300 / 300) proves pairing, not a screening desk.
Operations
Daily last-seen, battery, validation fail, duplicate screening-trace ids. After SIM reseat, one staff case. On-call before unattended screening windows.
Security and compliance
Screening files reveal identity matches. Encrypt at rest. Strip name columns. Never log match detail. Verify TLS on every callback.
Decision guide
Ship when row validation, screening-trace-id idempotency, and name isolation exist. Delay if the importer can replay the file. If zero phone ops is mandatory, evaluate CPaaS for that slice.
Checklist
- Rows validated.
- Screening-trace id idempotent.
- No names in SMS.
- OTP isolated.
- Spare paired.
Next steps
Return to Phone as SMS gateway guide, compare device and SMS volume pricing, open device setup, and confirm APIs in SMS API documentation.
Deep dive: production hardening
CSV validation is non-negotiable. Dual-SIM ops tablets fail when the send slot swaps after reboot. Battery exemptions dominate overnight screening windows.
Deep dive: scaling and failure modes
Scale is cases times notices, not a blast of the catalog. Never claim unlimited free cloud SMS credits with no device or volume meter.
Deep dive: integration discipline
Developer Center owns live API parameters. Persist screening-trace id. MCP is a REST wrapper. If zero phone ops is mandatory, evaluate CPaaS. You bring the Android phone and operator credit.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- bulk SMS from Excel and CSVSpreadsheet campaigns
- contacts, lists, and segmentsAudience hygiene
- bulk SMS with consent best practicesHigh-volume outreach
- SMS API documentationLive endpoint reference
