Upcoming changes in Enhanced Scheme Data (ESD) requirements as of April 12, 2024

February 22, 2024 17:07

Adyen will be updating the submission requirement of existing Enhanced Scheme Data (ESD) fields, as well as introducing a new field for Airlines starting on April 12, 2024, as part of scheme announcements. These changes will impact the US domestic Visa, Mastercard and Amex transactions for those accounts participating in the ESD program. The changes aim at fulfilling the scheme requirements, in order to benefit from a cheaper interchange rate. 

ESD is an optional program in which transactions can target lower interchange rates with (Visa and Mastercard) or benefit from fraud protection and reporting (Amex).

When opting-in for this service, schemes expect the additional data with mandatory fields to pass certain validation. Not meeting these requirements may provoke targeting sub-optimal interchange rates.

Why are these changes happening?

Adyen is adjusting the ESD requirements as part of scheme announcements. 

What customers are impacted?

Customers submitting Enhanced Scheme Data with the US Domestic transactions, with the following MCCs:

  • Lodging: MCCs 3501-3999 or 7011 

  • Car rental: MCCs 3351-3500, 7512, 7513 or 7519

  • Airline: MCCs 3000-3350, 4511 or 4722 

When will these changes happen?

These requirements will become effective on April 12, however, we recommend completing readiness as soon as possible.

What consequences will be caused by not meeting the new requirements?

Transactions initiated after April 12, 2024 that fail to meet the updated ESD criteria will not impact the authorization success rates and be subject to authorization refusals. 

If the customer submits US Domestic transactions with invalid ESD mandatory fields, transactions may experience:

  1. If the customer submits lodging or car rental ESD fields in /capture request, the capture request will be rejected.

  2. If the customer submits airline ESD fields in /capture request, the capture request will still proceed without ESD fields.

  3. If the customer submits lodging, car rental or airline ESD field in /payment request, the payment request will still proceed without ESD fields.

Processing payments that do not follow the scheme requirements may bring transactions to target sub-optimal rates (Mastercard and Visa) or incorrect data in reporting (Amex). 

What is changing?

See below an overview of what fields and requirements are being introduced:

Lodging:

The changes are applicable if you have MCC 3501-3999 or 7011 and submit Lodging ESD:

Business Type

Name of Field

Current Requirement

New Requirement

Is there a change?

Lodging

lodging.room[itemNr].numberOfNights 

Optional

Mandatory

Yes

Lodging

lodging.room[itemNr].rate

Optional

Mandatory

Yes

Lodging

lodging.customerServiceTollFreeNumber 

Mandatory

Optional

Yes

Lodging

lodging.propertyPhoneNumber 

Mandatory

Optional

Yes

Lodging

lodging.totalRoomTax 

Mandatory

Optional

Yes

Lodging

lodging.checkInDate 

Mandatory

No

Lodging

lodging.checkOutDate 

Mandatory

No

Lodging

lodging.folioNumber

Mandatory

No

Car Rental:

The changes are applicable if you have MCC 3351-3500, 7512, 7513 or 7519 and submit Car rental ESD:

Business Type

Name of Field

Current Requirement

New Requirement

Is there a change?

Car Rental

carRental.rate

Optional

Mandatory

Yes

Car Rental

carRental.rateIndicator 

Optional

Mandatory

Yes

Car Rental

carRental.daysRented 

Optional

Mandatory

Yes

Car Rental

carRental.customerServiceTollFreeNumber 

Mandatory

Optional

Yes

Car Rental

carRental.rentalAgreementNumber 

Mandatory

No

Car Rental

carRental.renterName 

Mandatory

No

Car Rental

carRental.returnCity 

Mandatory

No

Car Rental

carRental.returnStateProvince 

Mandatory

No

Car Rental

carRental.returnCountry 

Mandatory

No

Car Rental

carRental.returnLocationId 

Mandatory

No

Car Rental

carRental.checkOutDate 

Mandatory

No

Car Rental

carRental.returnDate 

Mandatory

No

Airline:

The changes are applicable if you have MCC 3000-3350, 4511 or 4722 and submit Airline ESD:

Business Type

Name of Field

Current Requirement

New Requirement

Is there a change?

Airline

airline.leg[itemNr].flight_number

Optional

Mandatory

Yes

Airline

airline.issue_date*

N/A

Mandatory

Yes

Airline

airline.airline_code

Mandatory

No

Airline

airline.ticket_number

Mandatory

No

Airline

airline.passenger_name

Mandatory

No

Airline

airline.leg[itemNr].carrier_code 

Mandatory

No

Airline

airline.leg[itemNr].class_of_travel 

Mandatory

No

Airline

airline.leg[itemNr].destination_code 

Mandatory

No

Airline

airline.leg[itemNr].date_of_travel 

Mandatory

No

Airline

airline.leg[itemNr].depart_airport 

Mandatory

No

(*) airline.issue_date validation:

Airline field airline.issue_date is an (required) ESD field never documented before, and it will contain the following validation:

  • Description: Date in which the ticket was issued to the passenger.

  • Date format: YYMMDD

  • minLength: 6 characters

  • maxLength: 6 characters

These fields are currently supported in /authorise, /capture and /payments end points.

What actions are required from customer's side?

If you are a customer with one of the MCCs below and submitting ESD data with your payment or capture request, please be aware of the new requirements.

Where can customers find more information?

An updated overview of all ESD requirements, including their fields’ validation, is available in this documentation.