For a weekly fintech digest, latency and correctness pull in opposite directions. The practical answer is to validate a webhook before it enters a delayed queue, validate it again at consumption, and use the dead-letter queue as an inspection boundary rather than silently retrying malformed data. A three-boundary design adds a little CPU and logging, but it prevents a bad payload from becoming a delayed customer-facing message.
The shape of the system is simple: an external webhook arrives, a small ingress function checks its envelope, a queue holds the accepted message until the digest worker is ready, and the worker enforces the business schema before publishing the digest. The queue is a transport boundary. It is not the place to discover what the payload meant.
Keep that boundary boring.
How do I check webhook payload formatting issues in delayed queues?
Start with a contract that is narrower than the provider's full webhook object.…