Key Takeaways
- A payroll-credit CSV fires after the core says posted — not when HR scheduled the run.
- Amount and last-four only. No full account. No “need cash until Friday?” footer.
- Free is 1 device, 300 SMS lifetime, and 300 contacts. Developer is 25,000 SMS per year. Platform price is devices plus send volume.
- Login OTP stays off the payday batch SIM.
- Idempotency is employee-id plus pay-period — payroll re-exports when a line is corrected.
Summary
Scenario 341 is fintech bulk CSV for payroll and wage-credit notices — not EMI, not KYC, not travel. HR wants a text when “payroll ran.” The radio should wait until the core posts the credit. A premature SMS is how you get a queue at the ATM before the money exists. Service pricing is devices plus SMS send volume. You bring the phone and operator credit. Free is 1 device, 300 SMS lifetime, and 300 contacts.
Developer is 25,000 SMS per year. Starter allows 2 devices so OTP and payday stay apart. Uncapped platform volume is not free airtime. Confirm fields in Developer Center.
scheduled · posted · SMS
HR schedule is not a radio event
Payroll credit is not a payday loan ad
Allowed: employee id, E.164, locale, pay-period, amount token, last-four, correlation id. Forbidden: full account, national id, raw OTP, loan offers. Counsel owns the body.
Transactional SMS, security, OTP.
If payroll corrects one line and re-exports the file, your key of pay-period alone will skip the correction or re-text everyone. Key employee-id plus pay-period plus file hash of the posted amount.
Payroll CSV matrix
| Row state | Gate | If skipped |
|---|---|---|
| Scheduled, not posted | Hold | ATM queue before money exists |
| Posted | One SMS | Re-export nags the whole company |
| Corrected amount | Delta SMS or portal-only | Silent wrong figure |
| Loan / tip-pool promo | Not this file | STOP-less marketing on payday |
Join posted, not scheduled
Live core status at import. Drip inside OEM and carrier fair-use. DLR. MCP wraps REST only.
What the row may contain
Last-four + amount token. BIS CPMI is framing, not your statute.
Devices, volume, and airtime
Payday is a planned spike. We meter devices and platform sends. Free (1/300/300) is a dry run.
Payday operations
Pairing, charge, OTP isolated, staff canary on a fake employee id. Setup, Downloads, pricing.
Decision guide
Ship when posted-join exists and loan ads cannot ride the file. Delay if HR emails a schedule CSV. Not a CodeCanyon payroll blaster.
Payroll checklist
- Posted, not scheduled.
- Employee-id + period + amount hash.
- No full account or loan footer.
- OTP isolated.
- Developer Center fields confirmed.
Next steps
Scenario 41 payouts, scenario 281 EMI.
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
