> ## Documentation Index
> Fetch the complete documentation index at: https://nextgen-docs.enfuce.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Files

In addition to webhook notifications, we provide you with data files that includes information on events that have occurred to the following:

* Card
* Cardholder
* Transaction
* Token

These files help you to ingest data into your data warehouse, enabling you to build regulatory reporting platforms, Business Intelligence (BI) tooling, and analytics and observability dashboards. The files are a scheduled batch alternative to real-time integrations. Hence, for example, if you have subscribed to the card webhook, you will receive a real-time notification when any new card is created, or an existing card is updated or closed. The data file will contain the same details and will be sent to you at scheduled timelines.

## Scope

The following table explains the events that will be covered for each capability:

| Capability  | Description                                  | Events                                                                                 |
| ----------- | -------------------------------------------- | -------------------------------------------------------------------------------------- |
| Card        | Events relevant to the card lifecycle        | <ul><li>Card creation</li><li>Card update</li><li>Card closure</li></ul>               |
| Cardholder  | Events relevant to the cardholder lifecycle  | <ul><li>Cardholder creation</li><li>Cardholder update</li></ul>                        |
| Transaction | Events relevant to the transaction lifecycle | <ul><li>Authorisation message requests</li><li>Authorisation message advices</li></ul> |
| Token       | Events relevant to the token lifecycle       | <ul><li>Token creation</li><li>Token update</li></ul>                                  |

## File Naming Convention

The file follows the following convention:

```
<Entity>_<structure>_<yyyymmdd_hhmmss>.<format>
```

Where:

* `Entity` refers to the capability.
* `structure` refers to the structural representation of the file.
* `yyyymmdd_hhmmss` refers to the file generation timestamp.
* `format` refers to the physical file format. The current supported file format is `csv`.

**Example**:

`Card_event_log_20260519_124113.csv`

## File Schema

The schema of the data files is based on individual webhook event payloads and **does not** include client-specific information.

**Related Webhook Payloads**

* [Card Webhook](https://nextgen-docs.enfuce.com/api/cards/webhook/card-webhook)
* [Cardholder Webhook](https://nextgen-docs.enfuce.com/api/cardholders/webhook/cardholder-webhook)
* [Token Webhook](https://nextgen-docs.enfuce.com/api/wallet/webhook/token-webhook)
* [Transaction Event Webhook](https://nextgen-docs.enfuce.com/api/transaction-lifecycle/transaction-event/transaction-event-webhook-openapi)

The schema contains unique identifiers of each capability, such as, `tokenUniqueReferenceId`. The relationship between the capabilities is also maintained through the identifiers. For example, the data file for transactions will include the `transactionId` and the relevant `card.id` used for payment of the transaction.

## Data File Delivery

The files will be delivered through client-specific SFTP location.