Does a payout list include carrier credit?

No. Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Imported seller numbers do not come with operator balance.

Can I merge seller payouts and buyer refunds into one blast?

No. Keep role, settlement_id or refund_id, and purpose on the row. A combined festival file is how you notify the wrong party.

Should seller-panel OTP use the payout SIM?

No. Isolate OTP from settlement and refund traffic so a Friday payout wave cannot starve login codes.

Android SMS Gateway Scenario 167: Marketplaces contact lists in practice

Key Takeaways

Seller payout lists settle money; buyer refund lists unwind a purchase — they never share a dump.
settlement_id and refund_id are different keys; mixing them texts a payout into a refunded order.
Seller-panel OTP stays off both the settle SIM and the refund SIM.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free caps contacts at 300 and 300 SMS lifetime.
A seller who opted in for settlement alerts did not opt in for buyer-refund marketing.
Developer Center owns live API parameters; finance owns the settle-once rule.

Summary

Friday settlement and a buyer refund are opposite money directions. If they share a marketplace list, a seller gets a refund tone and a buyer gets a payout notice. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.

If the row cannot say settlement_id or refund_id, it does not get a send. Direction-less numbers are how finance spends Monday in Slack.

Seller payout vs buyer refund

List	Key	Never send
Seller payout	settlement_id	Buyer refund copy, seller OTP
Buyer refund	refund_id	Payout tone, festival promo
Hold	legal freeze	Anything until finance signs

Key takeaways

Payout and refund are opposite money directions.
settlement_id and refund_id never share a dump.
Seller-panel OTP stays off both SIMs.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
Developer Center owns live API parameters.
Canary settle vs refund on staff accounts before Friday payout.

Context

Finance ops use this marketplace scenario to keep seller settlement lists and buyer refund lists on separate Android SIMs with direction keys on every row.

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 Friday payout, buyer refund, and seller-OTP moments to lists and radios before you import last week’s settle file.

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 payout Friday as devices plus volume plus airtime. Free is 300 SMS and 300 contacts on one lab phone.

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 payout and refund lists only when direction keys, hold rules, and seller 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 Open source guide, compare device and SMS volume pricing, open device setup guide, and confirm APIs in SMS API documentation.

Deep dive: production hardening

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.

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.