# What changes (if any) do I need to make to my integration for Visa's new mandatory field requirement for Authentication requests?

To improve 3D Secure authentication data quality, Visa is changing certain data elements from “required conditional” to “required” in the Visa Secure Program Guide.
Stripe is in touch with Visa regarding the changes. Following initial consultations, Visa has reduced the number of required fields from 12 to 5 for browser transactions and 3 fields for in-app transactions. Additionally, Visa has changed the enforcement date to August 12, 2024.
### Consequences for not meeting the requirements
Our understanding is that failing to send the fields will not cause authentication failures, but an integrity fee may apply on a future date for transactions that don’t meet requirements. This would come with advanced notice.
### Merchants are responsible for collecting the following cardholder information:
* Name
* Either email address or phone number
These can be provided via the [customer object](https://docs.stripe.com/api/customers/object) or the [billing details](https://docs.stripe.com/api/payment_methods/object#payment_method_object-billing_details) field in a payment method object. These fields being populated should also contribute to better authentication rates.
### Stripe collects the following data:
* Browser IP Address (browser payments only) - Mandatory
* Browser Screen Height (browser payments only) - Mandatory
* Browser Screen Width (browser payments only) - Mandatory
* Common Device Identification Parameters (in-app payments only) - Device IP Address for SDK transactions, Mandatory
These are collected via [Stripe.js or our payment SDK](https://docs.stripe.com/payments/3d-secure/authentication-flow), which includes our hosted surfaces.