TL;DR: Validate the signature from the authorization header first (401 on failure), parse the event, then re-fetch the resource (ach, wire, card, whatever the event names) via the API before acting on it. Treat every webhook as a notification, not as data. Respond 200 after handling so the event is not redelivered.

## Fix
1. Validate the signature from the authorization header first (401 on failure), parse the event, then re-fetch the resource (ach, wire, card, whatever the event names) via the API before acting on it.
   Expected: the value or setting is exactly right, nothing ambiguous.

## Details
Respond 200 after handling so the event is not redelivered. Treasury Prime intentionally sends a thin payload and does not guarantee delivery order, so the state embedded in the event may already be stale by the time you read it.

## When to use
You hit exactly this: Treasury Prime webhooks send thin payloads with no delivery order; always re-fetch the resource in Treasury Prime.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Treasury Prime.

## Root cause
Treat every webhook as a notification, not as data.

## Edge cases
- Never branch your business logic on fields inside the payload alone; two out-of-order deliveries will silently corrupt state if you do.
- Context from the original thread: Community SDK docs (fintech-sdk/treasuryprime-sdk README, webhooks section): describes the webhook payload gotcha that trips agents that trust the event body as current state.