The custom_data field in the callback is an array of objects. Each entry matches a field you passed at transaction creation. LigdiCash automatically adds its own entries — always filter by keyof_customdata to extract your own.
Structure of custom_data
LigdiCash always adds hash and logfile to your array. Do not rely on the index or the order of entries — always filter by keyof_customdata.
The external_id field
external_id is a concatenation of the values of all custom_data fields whose key contains "id". If your custom_data contains only one field with "id" in the name (e.g. transaction_id), external_id will match its value. But if several keys contain "id", their values will be concatenated — which makes it unreliable for identifying the transaction.
Do not rely on external_id as a unique identifier. Always parse custom_data directly with keyof_customdata to extract your transaction_id reliably.
Related pages