Data File Processed Webhook (Infiniport Only)

NOTE: This event currently fires only for transactions imported through Infiniport. It does not fire for transactions imported by other methods.

Overview

The DataFileProcessed event fires once for each data file after Infinicept finishes processing it, whether the file imported successfully or failed validation. Use this event to confirm that a file you submitted (or that arrived from a processor) has been fully processed, to record how many rows and merchants were affected, and to surface validation errors back to your own systems when a file fails.

The webhook body contains the event data fields only — there is no enclosing event-type wrapper in the payload.

Trigger Conditions

This event is triggered when a data file completes processing, after either transaction file processing (a transaction, authorization, or transaction-metadata file finishes importing) or dispute file processing (a chargeback or ACH-return file finishes importing).

Additional notes:

• This event requires a webhook subscription of type DataFileProcessed. If no subscription exists for the tenant, no event is sent.
• The event fires once per file. A single import batch that contains multiple files produces multiple events that share the same FileImportId.
• The event fires for both successful and failed processing. On failure, RowsImported and MerchantsAffected are 0 and ValidationErrors is populated.

Payload Schema

The webhook body is the event data object serialized directly (there is no outer envelope). Field names are PascalCase.

Top-Level Fields

ValidationErrors Fields

Common Validation Errors

The Error field is a free-form string. A subset of messages follow fixed templates (placeholders shown in {braces}):

File Type Values

FileType is sent as a numeric value. 0 (Unknown) is a fallback used when the file type cannot be determined; all other values are grouped by source below — expand your integration source. Most integrations only encounter the values for the file types they submit (such as transactions, chargebacks, fees, and ACH returns).

Note: Values 1–6, 9, and 17 are reserved for retired integrations (legacy TSYS and Merlin) and are not emitted. They remain in the sequence to preserve ordinal consistency with historical data.

Example Payload

Successful processing:

​json { "FileImportId": "3f2504e0-4f89-41d3-9a0c-0305e82c3301", "Filename": "transactions_2022_11_18_001.csv", "Source": "Infiniport", "FileType": 21, "ValidationErrors": null, "RowsImported": 9001, "MerchantsAffected": 91 } ​

Failed processing:

​json { "FileImportId": "3f2504e0-4f89-41d3-9a0c-0305e82c3301", "Filename": "transactions_2022_11_18_001.csv", "Source": "Infiniport", "FileType": 21, "ValidationErrors": [ { "Error": "File is empty", "Row": null }, { "Error": "Rows are corrupt", "Row": 24 } ], "RowsImported": 0, "MerchantsAffected": 0 } ​

Handling This Event

1. Check ValidationErrors to determine the outcome. A null value means the file processed successfully; a populated array means processing failed and no rows were imported.
2. On success, read RowsImported and MerchantsAffected to reconcile the import against your own records and confirm the expected volume.
3. On failure, surface each Error (with its Row, when present) to the team or system responsible for the file so it can be corrected and resubmitted.
4. Use FileImportId to group events that belong to the same import batch, since one import can produce multiple DataFileProcessed events across different files.
5. Store FileImportId and Filename to correlate this event with the file you submitted and with any prior DataFileAcceptedForProcessing event (see Data File Accepted for Processing Webhook).