AccountUpdater request file

The structure of a batch request file from the Account Updater is as follows.

AccountUpdater lines

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: `AccountUpdater`	Processing type. Defines the type of action that is required for the specified transaction. If the column shows `ValidationError`, then the file shall have the structure of the batch result file (ValidationError) instead.
6	Alphanumeric	A merchant reference, that is, a unique identifier associated to a specific transaction.
7	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.

AccountUpdater sub-lines

There are two kinds of Account Updater requests: AccountUpdaterRecurring request and AccountUpdaterSingle request.

AccountUpdaterRecurring request

You can make an AccountUpdaterRecurring request when no payment details for the shopper are available.
The AccountUpdaterRecurring request stores shopper payment details in a recurring contract.

Mandatory sub-lines

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: `AccountUpdaterRecurring`	Transaction type. Defines the required field types for the specific sub-line.
4	Alphanumeric	A shopper's reference, which is the unique identifier for a shopper.
5	Allowed values: If the card details are not stored - The card alias If the card details are stored: recurring`DetailReference` Or `LATEST`	Allowed values: If the card details are not stored - The card alias If the card details are stored: recurring`DetailReference` Or `LATEST`

Example

FH,1.0,TEST,Company,TestCompany,Default,1,ws@Company.TestCompany,AccountUpdater,FileHeaderEchoData
BH,1,BlockHeaderEchoData
L,1,MerchantAccount,TestMerchant,AccountUpdater,MerchantReference1,EchoData1
SL,1,AccountUpdaterRecurring,s.hopper@email.com,LATEST
BT,1
FT,1

AccountUpdaterSingle request

You can make an AccountUpdaterSingle request when the shopper's card details are at least partially available in your records.

You can send live/actual card numbers with your batch file only if you encrypt the file with PGP before submitting it.

Mandatory sub-lines

This sub-line holds information about single, ad-hoc account update requests.

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: `AccountUpdaterSingle`	Transaction type. Defines the required field types for the specific sub-line.
4	Alphanumeric	Card number or card alias.
5	Numeric	Expiry month. Format: `MM`, zero-padded (eg: 03)
6	Numeric	Expiry year. Format: `YYYY` (eg: 2016)
7	Numeric	CVC code. Leave this field blank.
8	Alphanumeric	Cardholder name.
9	Numeric	Start month. Format: `MM`, zero-padded (eg: 03) Maestro UK only.
10	Numeric	Start year. Format: `YYYY` (eg: 2016) Maestro UK only.
11	Numeric	One-digit card issue number. Maestro UK only.

Example

FH,1.0,TEST,Company,TestCompany,Default,1,ws@Company.TestCompany,AccountUpdater,FileHeaderEchoData
BH,1,BlockHeaderEchoData
L,1,MerchantAccount,TestMerchant,AccountUpdater,MerchantReference1,EchoData1
SL,1,AccountUpdaterSingle,4111111111111111,06,2016,,CardHolderName,,,
BT,1
FT,1