Validate Transaction Webhooks
Validate payment webhook JSON and extract a contract-approved safe_payload
- Detects missing fields, bad types, and invalid status values
- Returns a contract-approved safe_payload
- Prevents raw webhook noise from leaking downstream
Paste a transaction webhook — instantly validate and extract a safe payload locally in your browser.
Why this package exists
Common problems
- Payment webhooks can arrive malformed with missing required fields, wrong types, or unexpected status values.
- Vendor-specific blobs, debug fields, and raw webhook bodies often sit beside the canonical fields downstream services actually need.
- Each downstream service may re-implement webhook validation differently, creating inconsistent trust boundaries.
When to use
Use this when upstream payment webhooks can produce malformed payloads and you need both a validation report and a sanitized safe_payload before forwarding data downstream.
Expected outcome
A validation envelope containing `{ valid, errors, safe_payload }`. `errors[]` identifies missing or invalid webhook fields, while `safe_payload` exposes only contract-approved transaction data downstream services can safely consume.
Automatically detects
- Missing required fields
- Type mismatches
- Invalid status values
- Unsafe raw payload fields
What the wizard asks
2 stepsEach step shows your input, the question, and a preview of the output.
- 1
Validate the webhook against your downstream contract?
Check required transaction fields, types, and status values before the webhook reaches downstream services.
- 2
Which safe_payload fields should downstream services receive?
Keep `valid` and `errors` for observability, then expose only contract-approved transaction fields under `safe_payload`.