Short answer: for a fintech renewal reminder that must wait until a business deadline, accept the webhook into durable storage first, then let a bounded worker queue handle delivery, 429 responses, Retry-After , and idempotent replay. The public HTTPS endpoint and its framework are transport details; the delivery guarantee is the design decision.
This distinction matters because a reminder is often attached to a financial state change. A duplicate notification is noisy, but a duplicate renewal command can create a ledger discrepancy. A missed reminder can also make a later reconciliation difficult to explain. The subscriber therefore needs a small, explicit state machine: received, durably accepted, scheduled, attempted, delivered, or dead-lettered for review.
The deadline belongs to the business operation, not to the HTTP request. If the request arrives early, store the target time and acknowledge the delivery after the write commits.…