How to Build a Compliant Password Reset Email System Without SMTP

A healthtech engineering approach outlines how to implement a secure, auditable password reset flow using an API-first email delivery model instead of a traditional SMTP relay. The design separates three distinct audit records — the security decision, the delivery attempt, and the delivery event — linked by a shared correlation ID that never exposes the reset token. Sensitive data such as the recipient's email address is stored only as a keyed digest, and the rendered message body is excluded from logs to prevent audit records from becoming credential stores. Reset links are given a configurable expiry (for example, 10 minutes), with the policy value stored rather than the URL itself, making compliance review straightforward. The framework emphasizes that a successful API response confirms only that the handoff was accepted, not that the recipient received the message — a distinction auditors must be able to verify months later.