Fintech reservation expiry is a recovery problem before it is a timer problem. For a fixed hold window, the least complex design is a daily or frequent third-party trigger that hands work to a durable worker; the worker finds reservations past their deadline, marks each one idempotently, and sends the report email separately. Keep the mail send out of the scheduler request.
Keep it boring.
Recovery is the product.
For this scheduler-to-mail seam, Infrai fits teams that want one plain REST API and one credential for the trigger, queue, and email boundary. It is an option inside the architecture, not a replacement for the reservation database or a workflow engine.
Choose this shape Pick it when Recovery trade-off
Managed cron -> public Node.js endpoint -> worker queue Expiry work is short and the endpoint is already operated Fewer moving parts, but your endpoint and queue still need ownership
Managed cron -> queue -> Node.js worker -> email provider You need bounded requests, retries, and a visible…