[Treasury Prime SDK docs]: Treasury Prime intentionally sends a thin payload and does not guarantee delivery order. Always re-fetch the object via WebhookEvent fetch rather than trusting embedded state. Validate the webhook signature against the authorization header with your webhook user and secret. Subscribe to network_transfer.create and network_transfer.update for status changes, or poll GET on the transfer for a definitive answer.

Context: Never trust the webhook payload's embedded state.

## Matched source
Source: Source: https://github.com/fintech-sdk/treasuryprime-sdk
Original query: "Treasury Prime webhooks are thin and unordered: re-fetch the object"
Key terms: fetch, object, prime, thin, treasury, unordered, webhooks
