Result URL Callbacks¶

Method¶

Your endpoint at result_url (or webhook_url) must accept:

POST <your configured URL>
Content-Type: application/json

Hivemind Payments calls your server — there's nothing to call on the Hivemind Payments side for this flow.

How callbacks work¶

When a transaction you initiated via Initiate Payment reaches a final state (completed or failed), Hivemind Payments sends an asynchronous POST request with the result payload to the callback URL associated with the transaction.

There are two places a callback URL can be configured:

Field	Set where	Scope
`result_url`	In the body of each `POST /payments/initiate/` request	Per-transaction
`webhook_url`	On your API application; contact Hivemind Payments to set or change it	Per-application (default)

What to expect¶

Hivemind Payments will POST a result payload to the given URL once the transaction completes or fails — this is not a synchronous response to the initiate call.
Your endpoint should respond quickly (e.g. 200 OK) and process the payload asynchronously if it triggers slow downstream work, to avoid retries or timeouts on Hivemind Payments' side.

See Payload Reference for the confirmed payload shape, and Verifying & Testing Webhooks for how to validate incoming callbacks and test them in sandbox.