> ## 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.

# Support

> Reach the LigdiCash team — available channels, country contacts, and how to file a quality bug report.

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

<Warning>
  **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.
</Warning>

<CardGroup cols={2}>
  <Card title="Technical support" icon="envelope" href="mailto:developper@ligdicash.com">
    For API issues, transaction errors, and integration questions.
    **[developper@ligdicash.com](mailto:developper@ligdicash.com)**
  </Card>

  <Card title="Dashboard" icon="gauge" href="https://client.ligdicash.com">
    Manage your account, API projects, keys, and transaction history.
    **client.ligdicash.com**
  </Card>
</CardGroup>

## Contacts by country

| Country          | Contact            | Email                                                                       |
| ---------------- | ------------------ | --------------------------------------------------------------------------- |
| Burkina Faso     | Mariam Koné        | [mariam.kone@ligdicash.com](mailto:mariam.kone@ligdicash.com)               |
| Côte d'Ivoire    | Ilaria Ouédraogo   | [ilaria.ouedraogo@ligdicash.com](mailto:ilaria.ouedraogo@ligdicash.com)     |
| Mali             | Hénoc Belemnegré   | [henoc.belemgnegre@ligdicash.com](mailto:henoc.belemgnegre@ligdicash.com)   |
| Niger            | Chérifatou Harouna | [cherifatou.harouna@ligdicash.com](mailto:cherifatou.harouna@ligdicash.com) |
| Senegal          | Lamine Gassama     | [lamine.gassama@ligdicash.com](mailto:lamine.gassama@ligdicash.com)         |
| Togo             | Inoussa Ouédraogo  | [inoussa.ouedraogo@ligdicash.com](mailto:inoussa.ouedraogo@ligdicash.com)   |
| Guinea (Conakry) | Sabine Traoré      | [sabine.traore@ligdicash.com](mailto:sabine.traore@ligdicash.com)           |
| Benin            | Mariam Koné        | [mariam.kone@ligdicash.com](mailto:mariam.kone@ligdicash.com)               |
| DRC              | Richard Muteba     | [richard.muteba@ligdicash.com](mailto:richard.muteba@ligdicash.com)         |
| All countries    | General support    | [developper@ligdicash.com](mailto:developper@ligdicash.com)                 |

<Note>
  For any commercial topic (pricing, contract, refund, transaction limits), your Partner Manager is the right contact.
</Note>

## How to file a quality technical bug report

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

<Steps>
  <Step title="The affected endpoint">
    Example: `POST /pay/v01/redirect/checkout-invoice/create`
  </Step>

  <Step title="The full request (without real keys)">
    Replace your keys with `{API_KEY}` and `{AUTH_TOKEN}`. Include the headers and the JSON body.
  </Step>

  <Step title="The response received">
    Paste the full JSON response, including `response_code`, `message`, and the `wiki` field if present.
  </Step>

  <Step title="Expected vs observed behavior">
    Clearly describe what you expected and what you got instead.
  </Step>

  <Step title="Timestamp and environment">
    Date and time of the request (with timezone), API project name (without the key), target country and operator.
  </Step>
</Steps>

<Tip>
  First check the [Common errors](/en/errors/common-errors) page and the [wiki field](/en/errors/wiki-field) — many recurring issues are documented there with the fix.
</Tip>

## Information to never send to support

<Warning>
  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.
</Warning>