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.

Hosted payin is the fastest integration method. You create an invoice via the API, retrieve a payment link, and redirect your customer to the page hosted by LigdiCash. The customer chooses their operator, completes their payment, and is sent back to your site. You do not have to manage the payment interface. This method works on the web as well as in native mobile applications: the payment link opens in a WebView, and you detect the customer’s return by listening to URL changes.

​
How it works

1

Create the invoice

You call POST /pay/v01/redirect/checkout-invoice/create with the order details. LigdiCash returns a token and a payment link in response_text.
2

Redirect the customer

You open the payment link in the same tab, a new tab, or a popup. The customer lands on the LigdiCash payment page where they choose their mobile money operator.
3

The customer pays

The customer enters their number and validates the payment following their operator’s instructions. LigdiCash fully handles this step.
4

Notification and redirect

LigdiCash sends a callback to your callback_url and redirects the customer to your return_url (success) or cancel_url (cancellation).

​
Important constraints

Iframes are blocked by LigdiCash. The payment link must open in the same tab, a new tab, a popup, or a native WebView on mobile — never in an iframe.
The customer field must remain empty (""). If you fill it with a phone number, LigdiCash filters the payment page to only show operators matching that number, hiding the others.

​
In this section

Create an invoice

Parameters, full payload, and response of the create endpoint

Redirect the customer

Opening the payment link: same tab, popup, WebView

Verify the status

Call the confirm endpoint with the creation token

Mobile integration

Open the link in a native WebView and detect the return

Common pitfalls

Iframe, empty customer, popup blocking — the frequent errors