Search

Are you looking for test card numbers?

Would you like to contact support?

Feature icon

Authorisation for a card payment

Mandatory sub-lines

The PaymentDetails and Card sub-lines described below are mandatory when submitting a card payment authorization 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 -white_check_mark- Record type identifier
2 Numeric -white_check_mark- 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 -white_check_mark- Transaction type.
Defines the required field types for the specific sub-line.
4 Numeric -white_check_mark- Amount.
5 Numeric -white_check_mark- The currency exponent.
6 Alphabetic -white_check_mark- The three-character ISO currency code.
7 Alphanumeric -x- 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 -x- The shopper's email address.
Required element for recurring payments and to create recurring contracts.
9 Alphanumeric -x- Shopper statement.
The soft descriptor for the transaction.
10 IP address -x- The IP address the shopper used to carry out the transaction.
11 Numeric -x- Fraud offset.
The value to be applied to offset the calculated risk score.
It can be either a positive or a negative value.

Card

  • This sub-line holds information about card payments.
  • In an authorization request for card payments, the Card sub-line needs to be submitted as sub-line 2.
Field # Format Required Description
1 Fixed value: SL -white_check_mark- Record type identifier
2 Numeric -white_check_mark- 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: Card -white_check_mark- Transaction type.
Defines the required field types for the specific sub-line.
4 Numeric -white_check_mark- Card number.
5 Numeric -white_check_mark- Expiry month.
  • Format: MM, zero-padded (eg: 03)
6 Numeric -white_check_mark- Expiry year.
  • Format: YYYY (eg: 2016)
7 Numeric -white_check_mark- CVC code.
  • Three-digit CVC/CVV code (Visa, Mastercard, Discover)
  • Four-digit CVC/CVV code (American Express)
8 Alphanumeric -white_check_mark- Cardholder name.
9 Numeric -x- Start month.
  • Format: MM, zero-padded (eg: 03)
Maestro UK only.
10 Numeric -x- Start year.
  • Format: YYYY (eg: 2016)
Maestro UK only.
11 Numeric -x- One-digit card issue number.
Maestro UK only.
FH,1.0,TEST,Company,TestCompany,Default,2,ws@Company.TestCompany,Authorisation,FileHeaderEchoData
BH,1,BlockHeaderEchoData
L,1,MerchantAccount,TestMerchant,Authorisation,Test Product 6,
SL,1,PaymentDetails,100,2,SEK,,,,,
SL,2,Card,4111111111111111,06,2016,737,CardHolderName,,,
BT,1
FT,1

Optional sub-lines

The  Address , MerchantOrderReference , and ShopperInteraction sub-lines described below can be optionally included in the payment request.

Address

You can use the Address sub-line to include information about the shopper's billing and delivery addresses.
You need to specify billing and deliver addresses on separate Address sub-lines:
  • One Address sub-line containing the billing address information;
  • One Address sub-line containing the delivery address information.
Field # Format Required Description
1 Fixed value: SL -white_check_mark- Record type identifier
2 Numeric -white_check_mark- 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: Address -white_check_mark- Transaction type.
Defines the required field types for the specific sub-line.
4 Allowed values:
  • Billing
  • Delivery
-white_check_mark- The type of address that is being submitted: either a billing or a delivery address.
5 Alphanumeric -white_check_mark- Street address.
6 Alphanumeric -white_check_mark- House number or name.
7 Alphanumeric -white_check_mark- City.
8 Alphanumeric -white_check_mark- ZIP/Post code.
9 Alphanumeric -white_check_mark- State/Province/Region.
10 Alphabetic -white_check_mark- Two-letter country code.
The country value format needs to adhere to the ISO 3166-1 alpha-2 standard. An invalid country code results in a transaction/request rejection. You can look up country codes on the ISO website.
FH,1.0,TEST,Company,TestCompany,Default,2,ws@Company.TestCompany,Authorisation,FileHeaderEchoDataBH,1,BlockHeaderEchoData
L,1,MerchantAccount,TestMerchant,Authorisation,Test Product 6,
SL,1,PaymentDetails,100,2,SEK,,,,,
SL,2,Card,4111111111111111,06,2016,737,CardHolderName,,,
SL,3,Address,Billing,South Buena Vista Street,500,Burbank,91521,CA,US
SL,4,Address,Delivery,Some Street,123,Some Town,90102,CA,US
BT,1
FT,1

MerchantOrderReference

Field # Format Required Description
1 Fixed value: SL -white_check_mark- Record type identifier
2 Numeric -white_check_mark- 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: MerchantOrderReference -white_check_mark- Transaction type.
Defines the required field types for the specific sub-line.
4 Alphanumeric -white_check_mark- Value of your order reference. 
FH,1.0,TEST,Company,TestCompany,Default,2,ws@Company.TestCompany,Authorisation,FileHeaderEchoData
BH,1,BlockHeaderEchoData
L,1,MerchantAccount,TestMerchant,Authorisation,Test Product 6,
SL,1,PaymentDetails,100,2,SEK,,,,,
SL,2,Card,4111111111111111,08,2018,737,CardHolderName,,,
SL,3,MerchantOrderReference,XY66AB
BT,1
FT,1

ShopperInteraction

Field # Format Required Description
1 Fixed value: SL -white_check_mark- Record type identifier
2 Numeric -white_check_mark- 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: ShopperInteraction -white_check_mark- Transaction type.
Defines the required field types for the specific sub-line.
4 Allowed values:
  • Moto
  • ContAuth
-white_check_mark- Value of ShopperInteraction. In this case, either Moto or ContAuth. This subline is required only for MOTO or recurring transactions.  
FH,1.0,TEST,Company,TestCompany,Default,2,ws@Company.TestCompany,Authorisation,FileHeaderEchoData
BH,1,BlockHeaderEchoData
L,1,MerchantAccount,TestMerchant,Authorisation,Test Product 6,
SL,1,PaymentDetails,100,2,SEK,,,,,
SL,2,Card,4111111111111111,06,2016,737,CardHolderName,,,
SL,3,Address,Billing,South Buena Vista Street,500,Burbank,91521,CA,US
SL,4,Address,Delivery,Some Street,123,Some Town,90102,CA,US
SL,6,ShopperInteraction,Moto,,,,,,,
BT,1
FT,1