Modification result file

This topic describes the structure of a result file in case of a successful modification. When parsing or validation errors occur, the result file has the structure described in Modification result file (ValidationError).

Modification 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 [0-9]+

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

Alphabetic data [A-Z, a-z]

Specifies the merchant account name.

5

Allowed values:

  • Cancel
  • Refund
  • Capture
  • CaptureOrRefund
  • AuthoriseReferral

Processing type.
Defines the type of action that is required for the specified transaction.

6

Alphabetic data [A-Z, a-z]

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
Allowed values:
  • Success
  • Error
  • Pending

Transaction status.
A Pending status means that the modification request needs to be postponed for processing.

8

Alphabetic data [A-Z, a-z]

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.

Modification sub-line

Field #

Format

Description

1

Fixed value: SL

Record type identifier.

2

Numeric [0-9]+

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: ModificationResult

Result type identifier.

4

Numeric [0-9]+

The unique PSP reference identifier for this modification.

5

Numeric [0-9]+

The unique PSP reference identifier for the original payment authorisation.

6

Alphabetic data [A-Z, a-z]

When the payment is not authorised, it is refused, or if an error occurs, this field holds Adyen's mapped reason for the refusal or a description of the error.

Possible error messages:

  • Transaction not found
  • Transaction is expired
  • Insufficient balance on payment
  • Only possible to refund the full amount
  • Only possible to capture the full amount
  • Modification in different currency than authorisation
  • Internal error
  • Operation not available
  • Operation not allowed
  • Operation failed
  • Recurring not supported for this payment method
  • Recurring transaction failed
  • Recurring contract is not active
  • Recurring contract not found
  • Recurring initial payment not found
  • Recurring initial payment not available
  • Recurring contract already exists
  • Fund Transfer not supported for this payment method
  • Fund Transfer failed
  • Fund Transfer: initial payment not found
  • Fund Transfer: Original Transaction is never authorised
  • The payment details have expired
  • Fund Transfer: unable to transfer to this bankaccount
  • InvoiceLines are incorrect
  • Incomplete or invalid payment details
  • No suitable capture found for partial refund
  • Invalid referral authorisation code

Example

FH,1.0,TEST,Company,TestCompany,Default,1,ws@Company.TestCompany,Modification,FileHeaderEchoData
BH,1,BlockHeaderEchoData
L,1,MerchantAccount,TestMerchant,Capture,9874560210158741,Success,
SL,1,ModificationResult,9874560210158741,9248732154865245,
L,2,MerchantAccount,TestMerchant,Capture,9541236985175236,Error,EchoData1
SL,1,ModificationResult,9541236985175236,9248732154851572,Transaction not found
L,3,MerchantAccount,TestMerchant,Refund,95412367785175236,Error,EchoData2
SL,1,ModificationResult,95412367785175236,9358752154851572,Insufficient balance on payment
BT,3
FT,1