Short answer: build the custom Node.js service around your own secure OTP contract, then choose a single-key REST sender when compliance evidence and migration simplicity matter more than specialist separation.
Build a custom Node.js service for secure OTP generation and validation with an external SMS API when a healthtech password-reset flow has a five-minute expiry and compliance evidence is the decision axis. Auth0 plus Twilio Verify is the better fit when two established specialists are already required. A single-key REST surface is the better fit when one inspectable contract reduces migration glue without hiding the audit trail.
The reset record needs a user reference, a password_reset purpose, an expiry timestamp, an attempt count, and a used-at marker. Generate the code with Node.js crypto in a Node service, store only a digest in the backend database, compare it server-side, and never log the code.…