# rivr verify catches a receiver that re-serializes JSON, and one that refuses events out of order

- Date: 2026-11-01
- Type: New
- Surface: Developer portal and CLI
- What you need to do: Nothing.
- Address: https://developers.rivr.io/changelog/2026-11-01-cli-verify-escaped-unicode-and-order

`rivr verify` (CLI 0.6.0) runs eight checks against your webhook receiver instead of six. Escaped unicode sends a correctly signed delivery whose `reference` and `metadata` hold å, ä and ö written as `\u` escapes with uppercase hex, exactly as Rivr writes them, and expects `2xx`. A receiver that parses the JSON and signs `JSON.stringify` of it again gets another signature than Rivr's and refuses real deliveries with non-ASCII text, while it passes every check with plain ASCII; when it answers `400`, `401` or `403` the check says to compute the signature over the raw bytes that arrived. Out of order sends the same order as `Completed` before `Created`, each with its own `Rivr-Webhook-Id`, and expects `2xx` on both, as the guides say a receiver must not rely on the order of events. Every delivery has 5 seconds to answer, and the statement you can quote when all checks pass names the eight. Run the install command again to update.