Data Files is an additional service and may not be included in your standard contract. Contact Enfuce Support to confirm availability and commercial terms.
Data Files and webhooks
The Enfuce platform is event-based. Every change in your card program generates an event: a card is issued or updated, a cardholder is onboarded, a token is provisioned into a wallet, a transaction is authorised and cleared. Enfuce delivers these events to you in real time through webhooks. Webhooks are the primary way to integrate with Enfuce. Use them for anything that should happen immediately, such as notifying a cardholder, updating your app or triggering an operational action. You can also use webhooks to build and maintain your own databases: store each event as it arrives, and your data stays current throughout the day. Some processes, however, are naturally periodic: a data warehouse loaded overnight, a finance team reconciling the previous day, a regulatory report compiled each month. Data Files serves these processes. It is built from the same underlying events as webhooks and gives you a daily batch view of the same activity, in a form that fits directly into your existing data and reporting processes.Value for you
- Ready to use from day one. You receive a documented, standard schema rather than a bespoke export to specify, build and maintain.
- Your data, your logic. Atomic, event-level data lets you build your own reports, controls and dashboards, and change them without raising a change request with Enfuce.
- Reliable to automate. The same file structure arrives every day, with a file for every entity, so your ingestion works the same way every time and gaps are immediately visible.
- Payments expertise included. Values that require payments knowledge, such as the reason a transaction was not strongly authenticated, are derived for you.
What Enfuce takes care of
Every day, Enfuce extracts the previous day’s data and makes it available to you as a complete set of files. Enfuce:- organises the data into standard entity files for Card, Cardholder, Transaction and Token
- keeps the file structure consistent from day to day, so your ingestion works the same way every time
- derives values that require payments expertise, such as the SCA exemption reason for each transaction, using a defined prioritisation when more than one exemption applies
- delivers a file for every entity every day, including days with no activity, so you can monitor completeness yourself
What you need to do
- Collect the files from the Enfuce-hosted SFTP location once they are available.
- Read columns by their header name rather than by position, and ignore columns you do not recognise, so your ingestion keeps working as the schema evolves.
- Monitor completeness: expect one file per entity per day, and treat a missing file as a delivery issue.
- Build your own aggregation, reporting and reconciliation on top of the event-level data.
What you can do with Data Files
The files contain atomic, event-level data in a standardised structure and format, not predefined reports. You decide how to aggregate, combine and present the data. You can join it with your own data, build your own controls and dashboards, and adapt them as your needs change. Typical uses include:- regulatory reporting, such as reporting on transactions where strong customer authentication was not applied, and why
- reconciling transactions, fees and interchange
- analysing card lifecycle and portfolio development
- tracking digital wallet adoption
Service principles
Data Files is a standardised data-sharing service. You receive the same file format, file structure and schema as every other Enfuce customer. Because the data model is shared and documented, the service behaves predictably from the first delivery, and every improvement Enfuce makes to the data model reaches you as well. The service is built around entity-oriented files. Each file represents one entity, such as Card or Transaction, and contains all event types related to that entity. For example, the Card file contains card creation, card update and card closure events.File scope
The service includes the following entity files.
Each entity has exactly one daily file, which contains every event type for that entity. For example, authorisation requests, advices, notifications, anti-fraud advices and clearing events all arrive together in the Transaction file; there is no separate file per event type. Use the
event_type column to tell the rows apart or to filter for the events you need.
Delivery
Daily schedule
Data extraction starts at 03:00 UTC each day and covers the previous full day, from 00:00:00 to 23:59:59 UTC. Files are available for collection before 05:00 UTC.Completeness
You receive a complete daily set for every entity. Partial files are not sent. A file is delivered for every entity every day, including when there are no events for that day. Such a file contains the header row and no data rows, and is never a zero-byte file.The absence of a file always indicates a delivery failure, never a day without activity.
Next steps
- Working with the files: file naming, structure, format, relationships and schema changes.
- File schemas: Card, Cardholder, Token and Transaction.