Android SMS Gateway Scenario 779: Marketplaces contact lists in practice

Summary

Marketplace lists in scenario 779 are VAT/GST mismatch holds: seller last-four, hold code, portal. Unlike mute union, KYC, dispute, locker-ready CSV, seller ban, payout holds, holiday cutoff, listing hold, review-request, inbound dock slots, IP takedown, or serial-returner, this sheet is tax ops closing a number mismatch.

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 VAT number in SMS is a tax identifier you leaked. Union mute first. Send last-four and hold code. Keep the ID in the portal.

Key takeaways

• VAT-mismatch lists are tax ops: seller last-four and hold code — not a tax-ID essay in SMS.
• Union the seller mute sheet with the VAT-hold list before the daily drop.
• Keep login OTP off the tablet that dumps tax notices.
• 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.
• Never put a VAT or GST number in an unauthenticated SMS.

Related reading

Start from SMS webhook integration, compare bulk SMS from Excel and CSV, open SMS auto-reply and STOP keywords, and review OECD VAT notes where they apply.

Context

Tax desks land here after a growth blast hit sellers already muted, or after a hold text included a VAT number. Login OTP cannot share that burst.

Core scenario guidance

Union mute. Template: last-four, hold code. Certificate in portal. Isolate OTP. Cap retries. Never put a tax ID in the body.

Canary a staff hold after OS updates. MCP wraps REST. Developer Center owns fields.

Cost and ownership

Devices + volume + operator airtime on every drop. Developer is 25,000 SMS per year. Free (1 / 300 / 300) proves pairing, not a tax desk.

Operations

Daily last-seen, battery, mute-union miss, duplicate hold codes. After SIM reseat, one staff hold. On-call before unattended filing weekends.

Security and compliance

VAT events reveal tax IDs. Encrypt at rest. Rotate list keys. Never log certificates. Verify TLS on every callback.

Decision guide

Ship when mute union, hold-code templates, and OTP isolation exist. Delay if growth can ride the hold list. If zero phone ops is mandatory, evaluate CPaaS for that slice.

Checklist

• Mute union before drop.
• Hold code only.
• No VAT number in SMS.
• OTP isolated.
• Spare paired.

Next steps

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

Deep dive: production hardening

Mute union is non-negotiable. Dual-SIM tax tablets fail when the send slot swaps after reboot. Battery exemptions dominate overnight filing desks.

Deep dive: scaling and failure modes

Scale is holds times notices, 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 hold code. MCP is a REST wrapper. If zero phone ops is mandatory, evaluate CPaaS. You bring the Android phone and operator credit.