Does a COD webhook include carrier credit?

No. Priced by devices and SMS send volume. You use your own phone and operator SMS credit. A replayed confirm still costs airtime if you send again.

Should COD confirm use the same SMS as cart.abandoned?

No. COD is a cash-collection notice. Cart is promo with STOP. Mixing them is how you coupon a doorstep payment.

Can checkout OTP share the COD confirm phone?

No. Isolate OTP from cash-on-delivery traffic so a van-day queue cannot starve authentication.

Android SMS Gateway Scenario 217: Ecommerce webhooks in practice

Key Takeaways

COD confirm is a door-step yes/no: HMAC, order id, one SMS — not a coupon after cash is collected.
cod.confirmed and fulfillment.failed are two templates; do not reuse paid-card copy.
Checkout OTP stays off the COD SIM so a cash-on-delivery wave cannot starve login codes.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Courier retries still meter platform volume and carrier airtime.
Free is 300 SMS lifetime on one device — canary one COD order, not a whole van.
Developer Center owns live API parameters; the courier app owns the confirm topic.

Summary

Cash on the door is not a card receipt. COD confirm needs HMAC, an order id, and one SMS — never an abandon-cart coupon after the courier already collected. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.

If the van app retried the confirm, your order id is the only thing stopping a second “please keep cash ready” text.

COD confirm vs promo

Topic	SMS type	Skip when
cod.confirmed	Cash-ready, once	HMAC fail or duplicate order id
cod.failed	Short fail, no coupon	Already refunded
cart.abandoned	Promo + STOP	Never on the COD SIM
checkout OTP	Auth only	Any courier phone

Key takeaways

COD confirm is a door-step notice, not a coupon.
Failed COD is its own template — no paid-card copy.
Checkout OTP stays off the COD SIM.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
Developer Center owns live API parameters.
Canary one COD order on staff before a van day.

Context

Courier engineers use this ecommerce scenario to fire COD confirm SMS only after HMAC and order-id checks say the cash collection is new.

Radio reality still wins: offline phones and OEM killers break scenarios overnight.

Cross-link hub cornerstones instead of rewriting the product overview.

Keep examples conceptual until Developer Center confirms live request shapes.

Budget airtime for retries — failed loops still cost operator credit.

Core scenario guidance

Map COD confirm, COD fail, and checkout-OTP to separate templates and radios before you subscribe van topics.

Separate configuration mistakes from radio failures during incidents.

Write acceptance criteria before seasonal or clinic-hour traffic.

Prefer gradual rollout with feature flags when automation is involved.

Cost and ownership

Model a van day as devices plus volume plus airtime on every un-deduped confirm retry. Free is 300 lifetime SMS for one staff COD order.

Failed retries still burn credit during scenario experiments.

Assign who owns SIM top-ups and spare handsets.

Keep marketing spend out of OTP device pools.

Operations

Daily checks: pairing health, battery, queue depth, and DLR anomalies.

After OEM updates or SIM swaps, re-test the scenario path end to end.

Keep a spare charged device ready for failover drills.

Name an on-call owner before unattended sends go live.

Security and compliance

Protect API keys per environment; rotate after contractor access ends.

STOP and consent still apply on promotional scenario lanes.

Avoid logging full OTP bodies into shared chat.

Verify webhook signatures and TLS on every callback path.

Decision guide

Ship COD webhooks only when HMAC, order idempotency, and OTP isolation are written.

Delay if you cannot explain offline-phone behavior during peak hours.

If zero phone ops is mandatory, evaluate CPaaS for that lane.

If local SIM economics matter, harden the Android path and monitor airtime.

Checklist

Scenario moments listed with owners.
OTP vs marketing isolation confirmed.
Spare device funded and paired.
Canary on staff numbers passed.
Developer Center checked if API-shaped.
Webhook/DLR monitoring ready.
Airtime budget includes retries.
On-call owner named.
Rollback path documented.
Hub cornerstone reviewed.

Next steps

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

Deep dive: production hardening

Multi-device failover only helps if spare phones stay charged and paired.

MMS attachments inherit carrier size and APN limits.

USSD requests are carrier- and region-sensitive; treat timeouts as expected.

Contact lists need consent metadata stored with the number.

OTP priority queues fail when marketing blasts share the same device pool.

Spare charged devices matter more than brochure SLAs when phones send the SMS.

Airtime surprise bills happen when bulk loops ignore radio pace.

OTP and marketing must stay on separate lanes on every scenario.

Never claim unlimited free cloud SMS credits with no device or volume meter.

Name an on-call owner before unattended schedules go live.

Canary on staff numbers before customer OTP.

Battery exemptions and OEM killers dominate overnight reliability.

Cross-link Setup, Pricing, Downloads, and Developer Center with keyword-rich anchors.

If zero phone ops is mandatory, evaluate CPaaS for that lane instead.

Webhook signature verification is non-negotiable for scenario automation.

Document who owns SIM top-ups for multi-site scenario rollouts.

Prefer honest latency expectations over marketing claims about global SLAs on SIM paths.

Scenario playbooks still bill by devices and SMS send volume. You bring the Android phone and operator SMS credit.

Developer Center owns live API parameters. Scenario blogs teach process and failure modes, not endpoint catalogs.

Ecommerce webhooks must verify signatures before they trigger SMS sends.

Clinic reminders need consent records and STOP handling even when messages feel transactional.

Logistics ETAs should degrade gracefully when devices go offline mid-route.

Edtech OTP spikes at exam windows — capacity plan devices before the semester starts.

Fintech OTP is high-stakes: isolate devices, rotate keys, and avoid logging full codes.

Real-estate nurture is promotional; keep it off OTP SIMs and honor quiet hours.

Restaurant reservation SMS still needs STOP on marketing lanes.

SaaS onboarding OTPs should canary on staff numbers before paid scale.

Field-service dispatch needs two-way inbox ownership so techs are not double-booked.

Marketplace seller alerts need multi-device failover when a single phone is the SPOF.

NGO outreach must separate fundraising blasts from operational alerts.

Appointment businesses live on reminder deliverability the morning of the visit.

Bulk CSV import needs validation before radio send; bad rows burn airtime.

Scheduled SMS must survive device sleep and timezone mistakes.

Auto-reply and STOP protect promotional lanes — never auto-reply into OTP threads.

Dual SIM routing fails when slot maps drift after reboot without re-pair.