Specifications
| JSON PATH | Description | Example | Mandatory |
|---|---|---|---|
| file_date_and_time | UTC Date transmitted by processor Format: YYYY-MM-DD hmmss | 2023-01-15 011525 | Mandatory |
| total_number_of_records | Details how many records are included in the report. | 1 | Mandatory |
| networkfee | |||
| nmi | The numeric Network Management Identifier (ICA/BID) associated with the fee. | 123456 | Mandatory |
| program_name | Program Name associated with the card. | CLOWD9 | Optional |
| program_id | Program ID associated with the card. Generated by CLOWD9. | 1028c3d4-06fc-401d-bbb2-9df36a06e06b | Optional |
| fee_id | Product ID associated with card. Generated by CLOWD9 represented as a GUID. | ed85a7cc-eef9-4df9-a440-a29ead50a5d3 | Mandatory |
| card_id | The identifier associated to the card used represented as a GUID. | 333933ef-a6f1-4ac1-8d24-68a34d9564ea | Optional |
| fee_description | The description associated with the fee provided by the Network. | Connectivity Fee | Mandatory |
| fee_reason_code | Reason code provided by the Network. | 7800 | Mandatory |
| fee_type | The fee type provided from the Network. | 783 | Mandatory |
| direction | To identify if the amount is a Debit or Credit. | Debit Credit | Mandatory |
| fee_date | The date associated to the fee, YYYYMMDD. | 1ae4af71-720d-4657-a742-24c7bc809985 | Mandatory |
| fee_amount | The fee amount in units represented in transaction_currency. For example 10000 = 100.00 | 10000 | Mandatory |
| fee_currency | The currency code associated to the fee. | GBP | Mandatory |
| settlement_date | Date of settlement from the network, YYYY-MM-DD. | 2025-01-25 | Optional |
| settlement_amount | The fee amount in units represented in settlement_currency. For example 10000 = 100.00 | 10000 | Optional |
| settlement_currency | The settlement currency code associated to the fee. | GBP | Optional |
Updated about 1 month ago
Did this page help you?