Skip to main content

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 callback is an HTTP notification that LigdiCash sends to your server when a transaction’s status changes — payment completed, payment failed, payout finalized. It is the primary mechanism for knowing the outcome of a transaction in real time, without polling the API in a loop.

​
How it works

You provide a callback_url in every transaction creation request. When LigdiCash has a result, it sends a POST to that URL with the details of the transaction.

​
The two requests sent

LigdiCash sends two POST requests for each event: one in application/x-www-form-urlencoded and one in application/json. Both contain the same information. Your server will therefore receive two calls per event — plan for a deduplication strategy.

​
What the callback does not guarantee

  • The received payload must never be considered as the source of truth. Anyone who knows your callback URL can send a forged payload. Always re-verify through the confirm endpoint with the token stored at creation before taking action.

​
In this section

Configuration

Define a reliable, publicly accessible callback URL.

Payin payload

Full anatomy of the payload received on an inbound payment.

Payout payload

Differences in the payload for a payout.

Security

The re-verification pattern before any processing.

Parse custom_data

Extract your transaction_id depending on the flow.

Idempotency

Deduplicate the two requests received per event.

Framework examples

Full implementations in PHP, Laravel, Node.js, Python.