Batch result file with validation errors

This topic describes the structure of a batch result file when a parsing or validation error occurs. For the batch result structure in case of success, see the specific batch result file type page. Note that this does not mean that the entire batch result file is an error. There can be successful lines and validation errors within the same batch result file.

Batch line

The line record [L] holds the metadata information that applies to its corresponding sub-line [SL] records.

Field #	Format	Description
1	Fixed value: `L`	Record type identifier.
2	Numeric	`L` line record number reference within the batch file block it belongs to. The counter starts at 1, and it increments sequentially by one unit.
3	Fixed value: `MerchantAccount`	Account type. Defines the type of account the transactions are related to.
4	Alphanumeric	Specifies the merchant account name.
5	Fixed value: `ParseOrValidationError`	Indicates that an error occurs while processing the batch request.
6	Alphanumeric	A merchant reference, that is, a unique identifier associated to a specific transaction. This field is populated and is returned if an optional merchant reference value is included in the corresponding request file.
7	Fixed value: `ValidationError`	Indicates that an error occurs while processing the batch request.
8	Alphanumeric	`EchoData` In this field you can specify any data you may want to be returned with the result file. When this field is populated, its content is returned exactly as is. The Adyen payments platform does not use this data. Maximum character length: 80 characters.

Batch sub-line

Field #	Format	Description
1	Fixed value: `SL`	Record type identifier.
2	Numeric	`SL` sub-line record number reference within its parent line. The counter starts at 1, and it increments sequentially by one unit.
3	Fixed value: `ValidationErrorResult`	Indicates that an error occurs while processing the batch request.
4	Empty	This value must be empty.
5	Alphanumeric	The description of the error message. Possible values: Invalid amount specified Original pspReference required for this operation Payment type is invalid For the full list, refer to Response handling (Error codes returned).

Examples

The following example shows the response when invalid amount was specified in a modification request:

L,1,MerchantAccount,TestMerchant,ParseOrValidationError,N/A,ValidationError,
SL,1,ValidationErrorResult,,Invalid amount specified

The example below shows the response when a PSP reference was missing in a modification request:

L,1,MerchantAccount,TestMerchant,ParseOrValidationError,441231,ValidationError,
SL,1,ValidationErrorResult,,Original pspReference required for this operation

The following example shows the response when an invalid merchant account was specified in an Account Updater request:

L,14,MerchantAccount,N/A,ParseOrValidationError,441231,ValidationError,
SL,1,ValidationErrorResult,,Invalid Merchant Account