Key Takeaways
- Scenario 1613 is a merchant settlement / payout-notice CSV — not payroll, EWA, collections, KYC, travel, card PIN, or dividends.
- Default body is “batch settled” plus HTTPS. Amounts only as a policy-approved band.
- Dashboard OTP stays on a dedicated Android. A Tuesday settlement file will starve it.
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free is 1 / 300 / 300. Developer is 25,000 SMS per year.
- Never import IBAN, MID secrets, or OTP in the file.
- REST send fields live in Developer Center — not a CodeCanyon acquirer listing.
Summary
Scenario 1613 is fintech bulk CSV for merchant settlement notices. The acquirer ledger owns the batch. Your worker checks template id and E.164, then texts a short HTTPS stub. The Android is a radio, not the settlement engine. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
If the header still has
ibanormid_secret, fail CI. Ops will concatenate it on a funding delay.
Merchant settlement files
Signed artifact from funding ops. Idempotency per batch+MID. CSV habits · fintech playbook. Fields: Developer Center. Industry context: GSMA.
File classes
| File | Body | Device | Hard fail |
|---|---|---|---|
| Batch settled | HTTPS + optional band | Notice pool | IBAN/OTP/secret column |
| Funding delayed | Reason code + portal | Notice pool | Row count ≠ control |
| Dashboard OTP | Digits + expiry | Dedicated OTP phone | Shared with the CSV |
Bands, not the batch
E.164 from a known column. Number formats · Trust Center. Resume by batch+MID. Idempotent send.
Cost
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free: 1 device, 300 SMS lifetime, 300 contacts. Developer: 25,000 SMS per year. Paid plans uncap platform volume; devices still meter. Free/Developer pause when the allowance is exhausted. Pricing.
Ops
Canary staff MIDs. Pace under OEM ceilings. Rate ceilings · setup. Name an abort owner before funding day.
Security
Encrypt extracts. SoftPOS promo needs STOP on another MSISDN. STOP · OTP.
Checklist
- IBAN/secret denylist in CI.
- Control totals signed.
- OTP phone isolated.
- Amount-band policy written.
- Airtime for retries.
Next steps
Transactional SMS · SMS API documentation.
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
