This endpoint initiates a payment directly from your interface. You provide the customer’s phone number and, depending on the validation mode of the operator, either the OTP or an empty field. LigdiCash returns a token to store and triggers the validation process on the operator’s side.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.
The LigdiCash Wallet uses distinct endpoints (
/pay/v02/debitotp and /pay/v02/debitwallet/withotp). See the LigdiCash Wallet page for its specific integration.Headers
The API key of your LigdiCash project.
Your API TOKEN prefixed with
Bearer . Example: Bearer eyJ0eXAiOiJKV1Qi...Must be
application/json.Must be
application/json.Body
Root object of the request.
Request examples
The examples below show two cases depending on the validation mode. Only theotp field changes.
Response
"00" if the transaction was created successfully, "01" on error.Identifier of the transaction on the LigdiCash side. Store it in your database immediately — required to call the
confirm endpoint and re-verify the status.On success:
"Votre requête est en cours de traitement". On failure: the error sub-code in the form Echec (CodeXX).URL to the documentation of error codes for this endpoint. Consult when
response_code is "01".Response example
Related pages
- Validation modes — choosing the
otpvalue depending on the operator - Verify the status — calling
confirmwith the creation token - The transaction_id pattern — best practices for
custom_data
