Verification key
Fetch Anyway’s public Ed25519 key and cache it:publicKey is the prefixed raw-key representation, while keys is the equivalent JWKS representation. The delivery envelope follows Standard Webhooks and uses an asymmetric Ed25519 (v1a) signature. Refresh the cached key if verification begins failing after a key rotation.
Events
Current order events are:
An empty endpoint event selection subscribes to all supported events. Fulfill only after a verified
order.paid.
Delivery headers and signed content
The signed message is the exact byte sequence:
Verify Ed25519 signatures
Payload
The signed envelope containstype, RFC 3339 timestamp, apiVersion, endpoint identity, and data.order.
Important order fields include:
Never authorize access solely from
merchantMetadata, a buyer note, email, or URL parameter. Compare the order, amount, currency, product, and reference with your own server-side record.
Delivery behavior
- Return a
2xxquickly after durable enqueueing. - Each attempt has a 10-second timeout.
- Transport failures,
408,429, and5xxresponses are retried. 3xxresponses and permanent4xxresponses other than408and429are not retried.- Delivery allows up to 12 attempts with exponential backoff capped at one hour.
Retry-Afteris honored for429and503, up to the one-hour cap.- Delivery is at least once and events can arrive out of order.
webhook-id or the event/order identity as an idempotency key. Do not let a late pending event regress a locally paid order.