Marketplace 2FA: Polling SMS OTP Delivery Status Without Webhooks
The operational constraint is that delivery events are pull-based, so a marketplace login cannot wait for a webhook that will never arrive. Short answer: let OTP verification decide whether the seller gets in, run the resend countdown in the client, and keep delivery-status polling off the critical path. Poll only for a bounded exception check or support investigation. This supports a…
Delivering SMS OTP codes via polling poses issues that make it unsuitable for immediate login verification. Sellers need quick access to their order, but polling introduces delays and potential duplicate OTPs. Let the verification decision determine if the seller passes, without relying on delivery status. Only poll for an isolated exception or support case.
Use the server, browser, and delivery status as the minimum integration trio. Observe, don't act. The server handles resend eligibility, attempt limits, challenge expiry, and session binding. Polling should only be used for an operator-facing exception path.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
