Identity
The LigdiCash Wallet uses two endpoints distinct from the other operators (
/v02). The flow is different: a first call triggers the OTP being sent, a second call submits the transaction with the OTP.Validation mode: SMS OTP
The customer receives an OTP code on their LigdiCash app or by SMS after your first request. They share this code with you. You then submit a second request with the OTP to finalize the transaction.Recommended UX
1
Collect the customer's number
Your form collects the phone number associated with the customer’s LigdiCash account.
2
Send the OTP — first request
Call
GET /pay/v02/debitotp/{phone_number}/{amount}. LigdiCash sends an OTP to the customer.3
Display the OTP field
After confirmation that the OTP was sent (
"error": false), display an input field for the OTP. Tell the customer to check their LigdiCash app or SMS messages.4
Submit with the OTP — second request
Call
POST /pay/v02/debitwallet/withotp with the number in customer and the OTP in otp.5
Wait for the callback
Show a waiting indicator. Confirmation arrives via your
callback_url.Step 1 — Send the OTP
phone_number and amount parameters are path parameters, not a JSON body.
Headers
string
required
The API key of your LigdiCash project.
string
required
Your API TOKEN prefixed with
Bearer .string
required
Must be
application/json.Path parameters
string
required
Customer’s phone number in the format
country code + local number, without + or spaces.integer
required
Amount in XOF (integer, no decimals).
Example
Response
Success
Step 2 — Validate with the OTP
Headers
string
required
The API key of your LigdiCash project.
string
required
Your API TOKEN prefixed with
Bearer .string
required
Must be
application/json.string
required
Must be
application/json.Body
Same structure as the/pay/v01/straight/checkout-invoice/create endpoint, with customer filled and otp containing the code received by the customer.
Example
Expected response
Limits
Related pages
- Validation modes — SMS OTP — details of the two-request flow
- Verify the status — call
confirmafter the callback
