Receive the merchant's webhooks

Register the merchant’s endpoint in the Maxana dashboard and store its signing secret when it is shown. Each delivery belongs to this merchant.

At the receiver, read the raw request body, verify the signature and timestamp, persist and deduplicate the event ID, return a successful status after durable receipt, and process the business transition asynchronously. Reconcile the referenced resource when current state matters. The shared webhook reference defines headers, payload vocabulary, acknowledgement, and retry behavior.

Current limits

Webhooks do not provide a total order and a browser callback is not a delivery guarantee. Your handler must accept duplicates and out-of-order events. A parsed-and-re-serialized JSON body cannot be used for signature verification; the signature covers the bytes received.

Continue to Issue refunds.