Data File Accepted for Processing Webhook (Infiniport Only)

📣
This is an early look at functionality that will become available with the upcoming July 7, 2026, software update!

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

Overview

The DataFileAcceptedForProcessing event fires when a data file has been received and accepted, ahead of the file actually being processed. Use this event to confirm that a file you (or a processor) submitted has been picked up and queued, and to correlate it with the later DataFileProcessed event using the shared import identifier.

Trigger Conditions

This event is triggered when one or more data files are imported for a tenant, and it fires once per accepted file.

This event fires when a file is accepted (received and queued for processing), not when processing finishes. For the results of processing, such as rows imported, merchants affected, and any validation errors, see Data File Processed Webhook.

A webhook subscription of type DataFileAcceptedForProcessing must be configured for the tenant; if no subscription exists, no event is sent.

Note: Files imported through the legacy WorldPay flow that do not generate an import source event are skipped and do not produce this webhook event.

Payload Schema

The webhook body is the event data object serialized directly (no outer envelope).

Top-Level Fields

Field	Type	Description
`FileImportId`	String (GUID)	Correlation ID of the import process. Use this to match this event with the corresponding `DataFileProcessed` event for the same file.
`Filename`	String	The name of the accepted file.
`Source`	String	The origin of the file. `Infiniport` for files in Infiniport's native file format; `Other` for files from any other source.
`FileType`	Integer	Numeric identifier of the file type. See File Type Values below.
`ValidationErrors`	Array	Always `null` for this event. Validation errors are reported only on Data File Processed Webhook.

File Type Values

FileType is sent as a numeric value. The values are grouped by source below. Expand your integration source to view file type values. Most integrations only encounter the values for the file types they submit (such as transactions, chargebacks, fees, and ACH returns).

Name	FileType
NativeTransactions	`21`
NativeChargebacks	`23`
NativeAdjustments	`24`
NativeFees	`25`
NativeFundingDepositResults	`26`
NativeAuthorizations	`29`
NativeTransactionsMetadata	`30`
NativeConsumerACHReturns	`31`
NativeFundingRequests	`32`

Name	FileType
AdyenPaymentAccountingReport	`12`
AdyenSettlementDetailReport	`13`
AdyenReceivedPaymentsDetailReport	`14`
AdyenMarketplacePaymentsAccountingReport	`15`
AdyenDisputeReport	`18`
AdyenMarketplaceVirtualAccountPayoutReturnedFile	`22`

Name	FileType
VantivEMAF	`7`
VantivCHARTS	`8`
VantivEMAFByMid	`19`
VantivDisputes	`28`
VantivCHARTSAggregate	`34`
VantivDisputesAggregate	`35`

Name	FileType
FirstDataTransactions	`11`
FirstDataChargebacks	`16`
FirstDataCLXAuthorizations	`33`

Name	FileType
WorldpayFundingRejectReport	`20`

Name	FileType
WellsFargoACHReturn	`10`

Name	FileType
NachaACHReturn	`27`

Example Payload

{
  "FileImportId": "3f8a1c2e-9b4d-4e7a-bc11-7d2f5a0e9c34",
  "Filename": "transactions_2022_11_18_001.csv",
  "Source": "Infiniport",
  "FileType": 21,
  "ValidationErrors": null
}

Handling This Event

Store FileImportId so you can correlate this acceptance with the later DataFileProcessed event for the same file.
Read Filename and FileType to confirm which file was accepted and what kind of data it contains. Map the numeric FileType to a name using the File Type Values table.
Check Source to distinguish files in Infiniport's native format (Infiniport) from files from any other source (Other).
Treat this as a "received" signal only. Do not act on file contents yet — wait for the DataFileProcessed event to learn the outcome, including RowsImported, MerchantsAffected, and any ValidationErrors.