Key Takeaways
- A travel-notice CSV is a time window. When the user cancels the trip, the row must die before the next drip.
- Card-shipment “out for delivery” is logistics copy. It is not a cross-sell for insurance.
- Free is 1 device, 300 SMS lifetime, and 300 contacts. Developer is 25,000 SMS per year. Platform price is devices plus send volume.
- Step-up OTP stays off the travel-batch SIM.
- Idempotency is notice-id plus day — issuers re-export overlapping windows.
Summary
Scenario 221 is fintech bulk CSV for travel notices and physical-card shipment — not payouts, not KYC, not chargebacks. Fraud wants “we expect spend in Lisbon.” Ops wants “card left the vault.” Marketing wants travel insurance. Only the first two belong on this file. 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 the batch stay apart. Uncapped platform volume is not free airtime. Confirm fields in Developer Center.
window start · cancel join · card scan
cancelled trip drops before tonight’s file
Travel notices are not a campaign
Allowed: notice id, E.164, locale, window start/end, destination country code, type (travel / card-ship), correlation id. Forbidden: PAN, PIN, CVV, passport numbers, raw OTP. No insurance upsell on this worker.
OTP, transactional SMS, security.
If the cardholder deletes the trip at 18:00 and the 18:10 export still lists Lisbon, the join must skip. A “we expect foreign spend” text after they cancelled is how you train them to ignore fraud SMS.
Travel and card-ship matrix
| Row | Gate | If skipped |
|---|---|---|
| Travel window | Live itinerary still active | Nag after cancel |
| Same notice-id + day | Skip | Two “we expect spend” texts |
| Card first-scan | Ship event, not vault print | Customer waits at the door for a card in the cage |
| Insurance offer | Not this file | STOP-less promo on a fraud number |
Card-shipment rows
Vault print is silent. First carrier scan can SMS. OTP for activation is a different device. Live JSON in Developer Center. DLR.
Window overlap and cancel
Persist notice-id + day. Drip inside OEM and carrier fair-use. BIS CPMI is framing, not your statute.
Devices, volume, and airtime
Holiday travel weeks spike. We meter devices and platform sends. Free (1/300/300) is a dry run.
Fraud-desk operations
Pairing, charge, OTP isolated, staff canary on a fake notice. Setup, Downloads, pricing.
Decision guide
Ship when cancel-join and activation OTP isolation exist. Delay if marketing rides the travel file. No-phone-ops: aggregator.
Travel-file checklist
- No PAN/PIN in file or body.
- Live itinerary join.
- Idempotency = notice-id + day.
- Card-ship after first scan only.
- OTP isolated.
- Developer Center fields confirmed.
Next steps
Scenario 41 payouts, scenario 101 KYC, scenario 161 chargeback.
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
