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

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

(tick)

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

4

Alphabetic data [A-Z, a-z]

(tick)

Card number or card alias.

5

Numeric [0-9]+

(tick)

Expiry month.

  • Format: MM, zero-padded (eg: 03)

6

Numeric [0-9]+

(tick)

Expiry year.

  • Format: YYYY (eg: 2016)

7

Numeric [0-9]+
(error)

CVC code.
Leave this field blank.

8

Alphabetic data [A-Z, a-z]

(tick)

Cardholder name.

9

Numeric [0-9]+

(error)

Start month.

  • Format: MM, zero-padded (eg: 03)

Maestro UK only.

10

Numeric [0-9]+

(error)

Start year.

  • Format: YYYY (eg: 2016)

Maestro UK only.

11

Numeric [0-9]+

(error)

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