Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Apr 09, 2025 - 18:00 EDT
Scheduled
Target Audience - Only applicable to clients processing UPI transactions on VCAS.
We're excited to let you know that VCAS will soon support Union Pay International’s EMV 3DS v2.2.0 before it phases out. This transition aims to enhance your experience and ensure seamless transactions. UnionPay 3-D Secure Program (UP3DS) is a secure e-commerce payment solution designed for Issuers and Merchants who want to reduce the risk of fraudulent transactions. UP3DS divides the online payment process into separate authentication and authorization flows.
Union Pay International released a product bulletin on November 30, 2023, with the following requirements: 1. All new components used in UPI 3DS products must be certified under the EMV Co. v2.2.0 standards starting January 1, 2024. 2. Issuers and acquirers must support EMV 3DS v2.2.0 by October 31, 2024. UPI will soon release its sunset plan for UP3DS v2.1.
Key Date: • May 14, 2025: VCAS will collaborate with UPI to update Issuer BIN ranges to support v2.2.
These requirements apply to participants in all regions globally, including EU, AP, LAC, NA, and CEMEA. VCAS is fully certified for UPI v2.2.0 and ready to support issuers. Outside of issuers in the EEA supporting PSD2, customers do not need any configurations in VCAS to support it. To support UPI 2.2, all BIN ranges on the UPI Directory Server need to be loaded with a "Protocol" of 2.2.0.
To eliminate the large manual effort for both VCAS issuer services teams and VCAS issuers, VCAS teams have coordinated with UPI to programmatically update all VCAS registered BIN ranges at the DS to End Protocol 2.2.0 on a coordinated date. The UPI team will enable ranges and set “ACS Protocol Version” and “ACS URLs” to VCAS to “2.2.0”.
The target implementation date for this migration is May 14, 2025, however, notifications will be sent out to issuers prior if this date changes.
If you prefer to opt out of this mass update, please work with your Visa Account Manager (or Support Center) to open a project by April 23, 2025. Your assigned VCAS Implementation Manager will work with you and the UPI team to enable your ranges in the UPI Directory server.
Additional Support and Recommendations:
Message Version Field (RDX): For issuers integrated to the VCAS RDX API, we recommend confirming that you do not have any validation logic on the Message Version field as this could cause issues when the new 2.2.0 value passes through in RDX. - Ensure any hard-coding logic in place for the ‘messageversion’ field is removed, if present. For instance, if a 2.2.0 message is sent and the messageversion field populates 2.1.0 as a hard-coded field by the issuer, the system will throw an error and result in authentication failure. - In principle, avoid hard-coding values in the ‘messageversion’ field.
VCAS recommends all issuers monitor their VCAS authentication traffic and authorization traffic to ensure there are no unexpected errors or issues after the update to 2.2. Internal support teams have been made aware of the upcoming UPI 2.2 boarding activities by issuers and will be vigilant during this time to any issues related to UPI 2.2.
Please do not hesitate to contact your Local VISA support if you have any questions or concerns.