Payout statuses

Status Meaning Is Final? Webhook RESULT
OK Payout accepted for processing No
PROCESSING Status not yet determined No
PAID Payout completed successfully Yes 1 (success)
NOT_PAID Payout rejected by provider Yes 0 (fail)
ERROR Payout failed Yes 0 (fail)

Non-final statuses (OK, PROCESSING) mean the payout is still being processed. The final result will be delivered via webhook. Use POST /check to poll if the webhook was not received.

When webhook RESULT is 0, the ERROR field contains the failure reason.

Handling errors and missing results

Read both the HTTP status and the XML body. A successful HTTP request does not necessarily mean a successful payout.

Response What to do
HTTP 200 with ERROR or NOT_PAID from /payout or /check Handle the reported rejection or failure and inspect <error>. Do not mark the payout as paid.
HTTP 200 with NOT FOUND from /check Verify the original payout id, service, and environment. This means no matching operation was found; it is not a final payout status.
HTTP 400 Correct the request or signature according to the endpoint's API Reference. An ERROR element in a rejected status-check request does not describe the payout's outcome.
HTTP 403 or 404 Check the service configuration, access settings, and environment. A service error does not establish the outcome of an earlier payout.
HTTP 5xx, a network timeout, or an unrecognized result Keep the outcome unresolved and check the status again with a delay. Do not treat an unknown result as a failure.

If a create request times out, retry with the same payout id to avoid creating a duplicate. Set a limit on automated retries and waiting. If the outcome remains unresolved, contact support with the service and payout ids, and continue accepting late webhooks.

/notify has its own response format: HTTP 200 with <result>1</result> means a webhook was requested, while other values can report an error, including an invalid signature. It does not confirm webhook delivery or the payout's outcome.