LigdiCash exposesDocumentation Index
Fetch the complete documentation index at: https://developers.ligdicash.com/llms.txt
Use this file to discover all available pages before exploring further.
confirm endpoints that let you query the state of a transaction from the token obtained at creation. This active verification is the essential complement to the callback: it lets you reconcile your database when the callback is unavailable, was missed, or must be re-verified for security reasons.
Available endpoints
| Flow | Method | Endpoint | Parameter |
|---|---|---|---|
| Payin (hosted & direct) | GET | /pay/v01/redirect/checkout-invoice/confirm | token |
| Payout | GET | /pay/v01/withdrawal/confirm/ | withdrawalToken |
The same
confirm endpoint is used for hosted payin and direct payin. The difference is in when you call it, not in the endpoint itself.status values
Whatever the flow, the confirm response contains a status field with three possible values:
status | Meaning | Recommended action |
|---|---|---|
completed | Transaction finalized successfully | Fulfill the order or confirm the payment |
pending | Awaiting operator processing | Wait and re-poll, or wait for the callback |
notcompleted | Transaction did not go through (cancelled or failed) | Offer to retry or notify the user |
When to call confirm
There are three situations where you must call confirm:
1. After the redirect to return_url (hosted payin)
When the customer returns to your site after payment, your frontend triggers a call to your backend, which calls confirm with the token stored at creation. Never call confirm directly from the browser — your API keys would be exposed.
2. In your callback handler (all flows)
Before fulfilling an order following a callback, always re-verify with confirm. Anyone who knows your endpoint URL can send a forged payload — re-verification is the only guarantee.
3. As fallback polling (callback unavailable or delayed)
If the callback is unavailable in your development environment, or if it is slow to arrive in production, poll confirm at regular intervals until you get a terminal status (completed or notcompleted).
Polling is a safety net, not the primary strategy. See Polling vs callback to choose the right approach for your context.
Creation token vs callback token
Reference pages
- Verify the status — hosted payin — full reference, response fields, and real payloads
- Verify the status — direct payin — specifics of the direct payin flow
- Verify the status — payout —
withdrawal/confirmendpoint - Polling vs callback — choosing the right strategy
- Recommendations — intervals, timeouts, hybrid pattern
- Callback — security — why always re-verify with
confirm