Consider the page an e-commerce on-call should investigate when a login flow lets a user choose SMS or email: an authenticated request succeeds after the shopper's account-deletion transaction has committed. The evidence needs an account state version, a session version, and a request outcome. A green message-delivery dashboard cannot explain that request. This is a proposed incident drill, not a report of a production incident.
Short answer: let the shopper choose SMS or email from destinations already verified for that account, replace the outstanding challenge when they switch channels, and check account eligibility again when consuming the code and authorizing every session. For a Node.js login flow, those are three separate decisions: channel selection, proof consumption, and continued session authorization.…