Android SMS Gateway Scenario 1729: Ecommerce webhooks in practice

Summary

Ecommerce webhooks in scenario 1729 are gift registries: registry.item_purchased fires, SMS with registry last-four and an item window, portal for the ship-to. Unlike order.paid, restock, refund, subscription, gift-card, BOPIS, split-shipment, RMA, COD, preorder, price-match, remaining-line, warranty, loyalty expiry, backorder, invoice.corrected, donation receipt, wishlist.in_stock, try-on kit_due, sample-sale hold_expiring, dropship.ack_late, raincheck.ready, class.waitlist_released, subscription.pause_ending, kit.incomplete, storecredit.issued, layaway.due, or trade-in.quote_ready, this event is a registry clock, not a trade-in quote.

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 ship-to address in SMS is PII you leaked. Send registry last-four. Keep the address in the account. Honor STOP.

Key takeaways

• Registry webhooks are registry last-four and item window — never a gift-card PAN or registrant address in SMS.
• Verify signatures before the SIM fires. A replayed registry.item_purchased is a second nag.
• Keep checkout OTP off the CX tablet that dumps registry 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.
• Honor STOP. Registry nags are promotional even when the purchase looks transactional.

Related reading

Start from SMS webhook integration, compare device and SMS volume pricing, open transactional SMS, and review FTC advertising notes where they apply.

Context

CX desks land here after a replayed registry.item_purchased double-nagged a shopper, or after an address leaked in a “helpful” template. Checkout OTP cannot share that tablet.

Core scenario guidance

Verify signatures. Template: registry last-four + window. Drop addresses. Honor STOP. Isolate OTP.

Canary a staff registry 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 registry desk.

Operations

Daily last-seen, battery, duplicate item ids. After a webhook secret rotate, one staff canary. On-call before unattended wedding cutoffs.

Security and compliance

Registry SMS reveal purchases. Encrypt at rest. Never log addresses. Verify TLS on every callback.

Decision guide

Ship when signatures, last-four templates, STOP, and OTP isolation exist. Delay if a replay can double-nag. If zero phone ops is mandatory, evaluate CPaaS for that slice.

Checklist

• Verify signatures.
• No address in SMS.
• Honor STOP.
• OTP isolated.
• Spare paired.

Next steps

Return to Laravel SMS gateway guide, compare device and SMS volume pricing, open device setup, and confirm APIs in SMS API documentation.

Deep dive: production hardening

Signature checks before radio are non-negotiable. Replayed registry.item_purchased still spends airtime. Battery exemptions dominate overnight wedding windows.

Deep dive: scaling and failure modes

Scale is items times events, 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 item id. MCP is a REST wrapper. If zero phone ops is mandatory, evaluate CPaaS. You bring the Android phone and operator credit.