← All endpoints
sicher.halowerk.com v1 webhook-signature
https://sicher.halowerk.com/v1/webhook-signature
answers 402
Providers each build their signing string differently — some sign only the body, others prepend a timestamp, an id, or a version marker in a fixed order — and getting that order wrong produces a mismatch that looks exactly like an attack. This checks the signature the way the named provider actually specifies, with constant-time comparison, and returns the string that was signed so a mismatch can
We sent a real
POST request to this endpoint and it
answered 402 with payment requirements we could parse.
- Price
- $0.002
- Network
- base
- Pay to
- 0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E
- Spec dialect
- v2 (declares x402Version 2)
- Transport
- PAYMENT-REQUIRED header
- HTTP method
- POST
- Response latency
- 165 ms
- Payment options
- 1 usable of 1
- Last checked
- 2026-09-06T01:23:47.952Z (21d ago)
- Category
- other
Re-check it yourself:
curl "https://api.the402.dev/validate?url=https%3A%2F%2Fsicher.halowerk.com%2Fv1%2Fwebhook-signature"