Key Takeaways
- Marketplace architecture is: buyer event → platform API → policy check → gateway → SIM. Sellers do not hold the token.
- OTP, order, and support inbox are separate pools. Seller promo is usually not this SIM.
- Idempotency keys must include vendor id and order id so retries do not double-text.
- We do not sell a turnkey “sell SMS as a business” product. Custom branding is contracted; meters stay devices + volume.
- You bring phones and operator credit.
One hub radio, many shops
Marketplaces want one operational number buyers recognize. Architecture is how you stop every seller plugin from becoming a spam cannon on that number. Compliance notes are the sibling. This page is the hop list.
Pricing: devices plus send volume. You fund SIMs. Peak is checkout OTP plus “order packed,” not average listings.
Vendor A
Vendor B
Vendor C
↓ policy API ↓ one SIM hub
Request path
- Marketplace core emits “order paid” / “login requested.”
- Policy service: is this vendor allowed, is this template allowed, is this buyer suppressed?
- Send adapter calls the gateway with device/slot from config.
- Android radio; DLR to your webhook, not to the vendor’s laptop.
“If a vendor can POST /messages with your Bearer token, your architecture is a shared prepaid with extra GitHub stars.”
Components
| Component | Owns | Must not own |
|---|---|---|
| Shop / vendor plugin | Intent (order id, buyer id) | Gateway API key |
| Policy API | Consent, template allow-list, rate limits | Raw radio retries |
| Send adapter | Idempotency, live fields | Business copy |
| Device pools | OTP vs orders vs inbox | Seller newsletters |
Tenancy without a reseller SKU
Log vendor id on every job. Do not build a fake multi-tenant CPaaS on our panel. Custom branding, if any, is contracted and still meters devices and volume. Sellers who need their own From need their own SIM or CPaaS.
Policy engine
Allow-list templates. Cap sends per vendor per hour. Honor platform STOP. STOP. OTP never goes through vendor copy. Two-way: inbox with a human queue, not a seller bot war.
Scale
Add phones for peak. Multi-device. Dual SIM ≠ two marketplaces. OEM ceilings and carrier fair-use remain. Webhooks: DLR.
Samples: PHP— REST, not a marketplace SDK.
Next steps
Put policy in front of send, split pools, canary one vendor’s order SMS. Setup: pairing. Plans: pricing.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS API documentationLive endpoint reference
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
- download the Android gateway appGet the APK
