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.

Have a technical question, an integration issue, or need access to your account? This page lists the available channels and helps you get a fast answer.

​
Support channels

Preferred channel — Integration Teams group: if LigdiCash has added you to a Microsoft Teams group dedicated to your integration, use this group first for all technical questions. It is the fastest channel to reach the LigdiCash team during your integration phase.

Technical support

For API issues, transaction errors, and integration questions. developper@ligdicash.com

Dashboard

Manage your account, API projects, keys, and transaction history. client.ligdicash.com

​
Contacts by country

CountryContactEmail
Burkina FasoMariam Konémariam.kone@ligdicash.com
Côte d’IvoireIlaria Ouédraogoilaria.ouedraogo@ligdicash.com
MaliHénoc Belemnegréhenoc.belemgnegre@ligdicash.com
NigerChérifatou Harounacherifatou.harouna@ligdicash.com
SenegalLamine Gassamalamine.gassama@ligdicash.com
TogoInoussa Ouédraogoinoussa.ouedraogo@ligdicash.com
Guinea (Conakry)Sabine Traorésabine.traore@ligdicash.com
BeninMariam Konémariam.kone@ligdicash.com
DRCRichard Mutebarichard.muteba@ligdicash.com
All countriesGeneral supportdevelopper@ligdicash.com
For any commercial topic (pricing, contract, refund, transaction limits), your Partner Manager is the right contact.

​
How to file a quality technical bug report

A good report lets the team reproduce and fix the issue quickly. Always include:
1

The affected endpoint

Example: POST /pay/v01/redirect/checkout-invoice/create
2

The full request (without real keys)

Replace your keys with {API_KEY} and {AUTH_TOKEN}. Include the headers and the JSON body.
3

The response received

Paste the full JSON response, including response_code, message, and the wiki field if present.
4

Expected vs observed behavior

Clearly describe what you expected and what you got instead.
5

Timestamp and environment

Date and time of the request (with timezone), API project name (without the key), target country and operator.
First check the Common errors page and the wiki field — many recurring issues are documented there with the fix.

​
Information to never send to support

Never share your Apikey or Auth Token in email threads or support tickets. If you need to share access details, ask your Partner Manager for a secure channel. If keys are compromised, regenerate them immediately from the Dashboard.