Short answer: for an edtech signup flow, keep token creation and account state in your Next.js or Node backend, then test template ownership as a separate decision. A provider-owned template is easier to operate; an application-owned HTML template gives you tighter control over the verification experience. Use a small trial: render the same verification link in each candidate, run a suppression check before sending, and inspect pulled delivery events rather than treating delivery as synchronous.
The important constraint is ownership. The application must create the user record, generate a single-use token, set its expiry, and decide what happens when the address is unknown. The mail service should receive a fully formed transactional message or a reference to a template whose ownership is explicit.…