Skip to main content
GET
/
pay
/
v01
/
withdrawal
/
confirm
Verify the status of a payout
curl --request GET \
  --url https://app.ligdicash.com/pay/v01/withdrawal/confirm/ \
  --header 'Apikey: <apikey>' \
  --header 'Authorization: <authorization>'
{
  "response_code": "<string>",
  "token": "<string>",
  "response_text": "<string>",
  "description": "<string>",
  "custom_data": [
    {}
  ],
  "status": "<string>",
  "operator_id": "<string>",
  "operator_name": "<string>",
  "wiki": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://developers.ligdicash.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Headers

​
Apikey
string
required
API key of the LigdiCash project.
​
Authorization
string
required
Bearer {API_TOKEN}

​
Query parameter

​
withdrawalToken
string
required
Token returned by the payout creation endpoint (/withdrawal/create or /straight/payout).

​
Response

​
response_code
string
"00" = call succeeded, any other value = error.
​
token
string
JWT payout token — identical to the one passed as parameter.
​
response_text
string
Result code label. Can be empty.
​
description
string
Additional description. Can be empty.
​
custom_data
array
Always [].
​
status
string
Payout status: completed, pending, or notcompleted.
​
operator_id
string
Operator identifier. Example: "11" for Orange Burkina.
​
operator_name
string
Operator name. Example: "ORANGE BURKINA".
​
wiki
string
URL to the sub-codes documentation.
statusMeaning
completedPayout finalized successfully
pendingProcessing in progress
notcompletedPayout failed
{
  "response_code": "00",
  "token": "{PAYOUT_TOKEN}",
  "response_text": "",
  "description": "",
  "custom_data": [],
  "status": "completed",
  "operator_id": "11",
  "operator_name": "ORANGE BURKINA",
  "wiki": "https://client.ligdicash.com/wiki/createStraightWithdrawal"
}

​
Error codes

Wiki: https://client.ligdicash.com/wiki/createStraightWithdrawal — see Sub-codes per endpoint. Verify the status of a payout — polling vs callback strategy.