Mastercard: optional 3DS data elements to become mandatory
With the latest publication of Mastercard’s 3DS Identity Check Guide on 26 th of May 2026, Mastercard has increased the number of mandatory data elements to be sent in a 3DS Authentication Request (AReq) to meet their Enhanced Data Standards Requirements .
This change aims to allow Mastercard and Issuers to make a better risk decisioning, resulting in a better consumer experience, more frictionless authentications and reduced fraud.
Mastercard’s approach is similar to the Visa mandate that came into effect in August 2024, however with more mandatory fields.
Fees
Merchants that do not meet Visa’s Data Quality Criteria are paying a higher 3DS fee since 1 st April 2026.
Fees or penalties for not meeting Mastercard’s Enhanced Data Standards Requirements are expected in 2027 . Worldline will inform partners and merchants as soon as more details are available.
Below is the list of Mastercard fields required to fulfil the mandate, compared with Visa:
Category |
Data Point |
Mastercard Enhanced Data Standards |
Visa Data Quality Criteria |
Cardholder |
Name |
Mandate |
Mandate |
Email address |
Mandate |
Mandate (either email or phone number is sufficient) |
|
Phone number (one out of: home / mobile / work) |
Mandate |
||
Address / Delivery |
Billing Address Line 1 (Street / House number / PO Box…) |
Mandate |
Recommended |
Shipping Address Line 1 (Street / House number / PO Box…) |
Mandate |
Recommended |
|
Browser / Device |
IP Address (browser or device) |
Mandate |
Mandate |
Device ID |
Mandate |
Recommended |
|
Device Location (latitude/longitude) |
Mandate |
Recommended |
|
SDK APP ID * |
Mandate |
Recommended |
|
Browser information (height, width, language, time zone…) |
Recommended |
Recommended |
*(Fallback factor for Android users who do not consent to share any of the other technical factors)
Our recommendation
Browser data and cardholder name are fields that should be already sent in the Authentication request as these are considered mandatory for Mastercard. Support your merchants in making these fields available to you or if you are in control of the 3DS process on behalf of your merchants, make the necessary changes to capture this data.
We do advice to always attempt an authentication request even though these new fields are not completed. Do not decline or stop the 3DS process if any of this new mandatory data is missing.