Payload anatomy — Payin

On an inbound payment, LigdiCash sends two POST requests to your callback_url — one in application/json, one in application/x-www-form-urlencoded. Both contain the same data. This page details the JSON structure.

Full example

{
  "date": "2026-05-09 07:20:23+00",
  "wiki": "https://client.ligdicash.com/wiki/confirmInvoice",
  "token": "",
  "amount": 4200,
  "status": "completed",
  "montant": 4200,
  "customer": "22676275726",
  "oreference": "",
  "request_id": "P2777636082026",
  "custom_data": [
    {
      "keyof_customdata": "transaction_id",
      "valueof_customdata": "ART5A7044E5",
      "datecreation_customdata": "2026-05-09 07:20:23.362788"
    },
    {
      "keyof_customdata": "hash",
      "valueof_customdata": "f918c54d54cdc334ade09f8c228a224b1d3df646250c84dcdd99af528ddcd450",
      "datecreation_customdata": "2026-05-09 07:20:23.362788"
    },
    {
      "keyof_customdata": "logfile",
      "valueof_customdata": "2026050907202369fee03756652",
      "datecreation_customdata": "2026-05-09 07:20:23.362788"
    }
  ],
  "description": "",
  "external_id": "ART5A7044E5",
  "operator_id": "11",
  "operator_name": "ORANGE BURKINA",
  "response_code": "00",
  "response_text": "",
  "customer_details": {
    "email": "firstname.lastname@example.com",
    "phone": "22676275726",
    "details": "",
    "lastname": "LASTNAME",
    "firstname": "Firstname"
  }
}

Main fields

string

Event timestamp in the format YYYY-MM-DD HH:MM:SS+TZ.

string

Result code. "00" = success. Any other value indicates an error — consult wiki for details.

string

Transaction status: "completed", "pending", or "notcompleted". Base your business logic on this field.

integer

Transaction amount in XOF.

integer

Same as amount. Both fields coexist in all LigdiCash responses.

string

Payer’s phone number, with country code, no + or spaces.

string

Unique request identifier generated by LigdiCash. Use it for deduplication when custom_data is empty or unavailable.

string

Concatenation of the values of all custom_data fields whose key contains "id". Can be reliable if you only have one field with "id" in the name — but parse custom_data directly for a guaranteed result.

string

Always empty (""). This field cannot be used for verification — use the token stored at transaction creation.

string

Identifier of the operator that processed the payment (e.g. "11" for Orange Burkina).

string

Operator name (e.g. "ORANGE BURKINA").

string

Transaction description. Can be empty.

string

Operator reference. Can be empty.

string

Textual label of the result. Can be empty.

string

URL to the documentation of error codes for this endpoint. Consult when response_code !== "00".

The custom_data array

array

Array of custom data associated with the transaction. Contains your merchant fields plus the fields automatically added by LigdiCash.

Show Structure of an element

string

Key of the entry.

string

Value of the entry.

string

Creation timestamp of the entry.

LigdiCash systematically adds two entries to your custom_data:

`keyof_customdata`	Origin	Description
`hash`	LigdiCash	Transaction hash generated by LigdiCash
`logfile`	LigdiCash	Internal LigdiCash log reference

Always filter on keyof_customdata to extract your own fields. See Parse custom_data.

Customer information

object

Payer information when available.

Show Fields

string

First name.

string

Last name.

string

Email address.

string

Phone number.

string

Additional information. Usually empty.

Getting started

Core concepts

Payment API

Guides

Error handling

SDKs & Plugins

Other products

AI tools

Resources

Payload anatomy — Payin

Full example

Main fields

The custom_data array

Customer information

​Full example

​Main fields

​The custom_data array

​Customer information

​Related pages

Full example

Main fields

The custom_data array

Customer information

Related pages