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

# Integration protocol

> The complete journey to become a LigdiCash partner: administrative steps, training, technical integration, and go-live.

Becoming a LigdiCash partner follows a structured process in two main phases: an administrative phase (contract, KYC) led by your Partner Manager, then a technical phase (training, integration, testing) supervised by the LigdiCash technical team.

## Overview

<Steps>
  <Step title="Contact your Partner Manager">
    Reach out to the LigdiCash sales team. A **Partner Manager** will be assigned to you — they are your point of contact throughout the administrative phase.

    See the [contacts by country](/en/resources/support#contacts-by-country) to reach the Partner Manager for your region.
  </Step>

  <Step title="KYC — Complete the KYC form and provide the required documents">
    Your Partner Manager will share the full list of required documents. In particular, you will complete the **KYC (Know Your Customer) form** — the LigdiCash KYC. It includes, among others:

    * The RCCM (Registre du Commerce et du Crédit Mobilier — Trade and Personal Property Credit Register)
    * The IFU number (Identifiant Financier Unique — Unique Financial Identifier)
    * A descriptive sheet of your company
    * Any other document requested by the Partner Manager depending on your activity

    <Note>
      The exact list of documents will be communicated by your Partner Manager. It may vary depending on your country and the nature of your business.
    </Note>
  </Step>

  <Step title="Negotiate fees and sign the contract">
    Your Partner Manager discusses the pricing terms with you (commissions per operator, per transaction type). Once the terms are validated, you sign the LigdiCash partnership contract.

    If you want to enable **Visa card payments**, an additional specific contract is required at this stage. See [Activate Visa](/en/payment-api/visa-cards/activation).
  </Step>

  <Step title="Handoff to the technical team">
    After the contract is signed, your Partner Manager connects you with the **LigdiCash technical team**, who takes over the rest of the process.
  </Step>

  <Step title="Dashboard and API training">
    The technical team schedules a **training session** with you covering:

    * How to use the LigdiCash dashboard
    * The principles of the API (endpoints, authentication, payment flow, callback)

    This training lays the foundation needed before starting the integration.
  </Step>

  <Step title="Creation of the Microsoft Teams integration group">
    The technical team creates a **Microsoft Teams working group** dedicated to your integration. This group is your direct communication channel with LigdiCash throughout the integration and beyond.

    In this group, the technical team hands you your **temporary integration account** — a real LigdiCash account configured with the operators from your contract, used exclusively for your integration work. See [Environments](/en/concepts/environments).
  </Step>

  <Step title="Technical integration">
    You build the integration using the temporary account provided. You can contact the technical team at any time via the Teams group if you have questions or run into blockers.

    Key items to implement and test:

    * Invoice creation and redirect flow (or direct flow, depending on the operators in your contract)
    * Callback reception and processing
    * Status re-verification with the `confirm` endpoint

    <Warning>
      The callback is the most critical part of the integration. Make sure your callback endpoint is reachable from the internet, deduplicates requests, and calls `confirm` before fulfilling an order. This is what will be checked first during the integration sign-off tests.
    </Warning>
  </Step>

  <Step title="Integration sign-off tests">
    When you consider your integration complete, notify the technical team in the Teams group. The team will then schedule **integration sign-off tests** to validate your implementation.

    The focus of these tests is the **callback**: the technical team verifies that your endpoint receives notifications correctly, processes them idempotently, and re-verifies the status with `confirm`.

    If adjustments are needed, the technical team will support you until full validation.
  </Step>

  <Step title="Sign the integration completion certificate">
    Once all tests are validated, the technical team sends you an **integration completion certificate** (PV — procès-verbal), a digital document to sign online. This document attests that your integration is compliant and approved.
  </Step>

  <Step title="Go-live">
    After the certificate is signed, the go-live process unfolds as follows:

    1. **You create your own LigdiCash account** via the LigdiCash mobile app ([App Store / Play Store](https://www.ligdicash.com/download)).
    2. **The technical team activates your API project in production** on this account, with the operators and permissions defined in your contract.
    3. You replace the temporary integration keys with your production keys in your configuration.

    <Tip>
      If you stored your keys in environment variables from the start of the integration, the switch to production is just a matter of changing the values of those variables. No code changes required.
    </Tip>
  </Step>
</Steps>

## After go-live

The Microsoft Teams group remains active. It is your primary channel to:

* Contact the **technical support team** in case of issues
* File **disputes** or claims
* Request the activation of new operators or features

## Phase summary

| Phase           | Owner                      | What you do                       |
| --------------- | -------------------------- | --------------------------------- |
| Administrative  | Partner Manager            | KYC, contract, commissions        |
| Training        | Technical team             | Dashboard, API                    |
| Integration     | Technical team + you       | Code, callback testing            |
| Validation      | Technical team             | Final tests, sign-off certificate |
| Go-live         | Technical team             | Activate your project             |
| Ongoing support | Technical team and support | Teams group                       |

## Related pages

* [Environments](/en/concepts/environments) — temporary integration account vs production
* [Authentication](/en/concepts/authentication) — using your API keys
* [Securing the callback](/en/payment-api/callback/security) — what is checked during the sign-off tests