AuthorisationReferral request

When you process  MOTO transactions, you may need to handle transactions with a resulting Declined status and a corresponding Referral reason.

If the shopper contacted their issuing bank and you have the authorisation code for the transaction, you can submit it in a batch file to update the transaction in the Adyen payments platform.

When we receive and process the batch file, we book a new Authorised journal entry for the transaction and then proceed with the standard workflow.

Mandatory sub-lines

The PaymentDetails and AuthoriseReferral sub-lines described below are mandatory when submitting a bank transfer authorisation request.

PaymentDetails

  • This sub-line specifies transaction amount and customer details.
  • Optional fields: if you do not populate one or more non-mandatory fields and leave them blank, you need in any case to insert delimiting commas because the Adyen payments platform expects a preset, fixed number of fields per line/sub-line. 

Field #

Format

Required

Description

1

Fixed value: SL
(tick)

Record type identifier

2

Numeric [0-9]+

(tick)

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

(tick)

Transaction type.
Defines the required field types for the specific sub-line.

4

Numeric [0-9]+

(tick)

Amount.

5

Numeric [0-9]+

(tick)

6

Alphabetic data [A-Z, a-z]

(tick)

The three-character ISO currency code.

7

Alphabetic data [A-Z, a-z]

(error)

A shopper's reference, which is the unique identifier for a shopper.

Required element for recurring payments and to create recurring contracts.

8

Email address

(error)

The shopper's email address.

Required element for recurring payments and to create recurring contracts.

9

Alphabetic data [A-Z, a-z]

(error)

Shopper statement.
The soft descriptor for the transaction.

10

IP address

(error)

The IP address the shopper used to carry out the transaction.

11

Numeric [0-9]+

(error)

Fraud offset.
The value to be applied to offset the calculated risk score.
It can be either a positive or a negative value.

AuthoriseReferral

Field #

Format

Required

Description

1

Fixed value: SL

(tick)

Record type identifier

2

Numeric [0-9]+

(tick)

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

(tick)

Transaction type.
Defines the required field types for the specific sub-line.

4

Numeric [0-9]+

(tick)

The original payment PSP reference.

5

Alphabetic data [A-Z, a-z]

(tick)

The authorisation code for the transaction (authCode).

Example AuthorisationReferral request
FH,1.0,TEST,Company,TestCompany,Default,2,ws@Company.TestCompany,Modification,FileHeaderEchoData
BH,1,BlockHeaderEchoData
L,1,MerchantAccount,TestMerchant,AuthoriseReferral,Test Product 6,
SL,1,PaymentDetails,100,2,EUR,,,,,
SL,2,AuthoriseReferral,8452147851579029,259016
BT,1
FT,1