Key Takeaways
- Merchant-settlement CSV is a batch-paid notice: last-four of the batch and amount, never a full MID or PAN.
- Validate rows before radio send. A bad MSISDN still burns operator credit.
- Keep merchant-portal OTP off the SIM that dumps daily settlement files.
- 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.
- Canary a staff settlement after every OS update, not only after a schema change.
Summary
Fintech CSV in scenario 449 is merchant settlement and batch-payout notices: funds landed, last-four of the batch, and a portal link. Unlike statements, collections, card-decline, payroll, insurance claims, loan drawdown, or KYC expiry, this drop tells a merchant money moved.
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.
batch · amt
If the radio can see a full MID, so can a stolen phone. Strip at import. Idempotency on batch id, not on “send again.”
Key takeaways
- Merchant-settlement CSV is a batch-paid notice: last-four of the batch and amount, never a full MID or PAN.
- Validate rows before radio send. A bad MSISDN still burns operator credit.
- Keep merchant-portal OTP off the SIM that dumps daily settlement files.
- 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.
- Canary a staff settlement after every OS update, not only after a schema change.
Related reading
Start from device setup, compare device and SMS volume pricing, confirm DLR in SMS delivery reports, and review ISO payments-messaging notes.
Context
Acquiring ops land here after a daily settlement file replayed because someone clicked import twice and the row key was the phone number. Merchant-portal OTP cannot share that dump.
Core scenario guidance
Validate MSISDN, amount format, and batch last-four. Reject rows with MID/PAN-shaped columns. Idempotency on batch id. Pace the radio. Isolate OTP.
| Column | Pass | Fail closed |
|---|---|---|
| Merchant | DBA / last-four id | Full MID or PAN |
| Amount | Canonical decimal | Free-text “about 2k” |
| Idempotency | Batch id | Phone as unique key |
| Portal OTP | Separate device | Same SIM as dump |
Canary a staff settlement after OS updates. MCP wraps REST. Developer Center owns fields.
Cost and ownership
Devices + volume + operator airtime on every retry. Developer is 25,000 SMS per year. Free (1 / 300 / 300) proves pairing, not a merchant book.
Operations
Daily last-seen, battery, import reject rate, duplicate batch ids. After SIM reseat, one staff row. On-call before unattended daily files.
Security and compliance
Settlement notices are financial personal data. Encrypt files at rest. Rotate keys after contractor access. Do not log full bodies in Slack. Verify webhooks if a core system triggers the import.
Decision guide
Ship when strip, idempotency, and OTP isolation exist. Delay if the file still carries MIDs. If zero phone ops is mandatory, evaluate CPaaS for that slice.
Checklist
- MID/PAN stripped at import.
- Batch id idempotent.
- OTP isolated.
- Retry cap per row.
- Spare paired.
Next steps
Return to Laravel SMS gateway, compare device and SMS volume pricing, open device setup, and confirm APIs in SMS API documentation.
Deep dive: production hardening
Bulk CSV burns airtime on bad rows. Dual-SIM phones fail when the send slot swaps after reboot. Battery exemptions dominate overnight closets holding the import tablet.
Deep dive: scaling and failure modes
Scale is batches times notices, not “blast the book.” Never claim unlimited free cloud SMS credits with no device or volume meter.
Deep dive: integration discipline
Developer Center owns live API parameters. Persist batch id and template version. 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
