Visa Merchant Business News Digest

In the rapidly evolving payment ecosystem, cardholders are increasingly looking for convenient and personalized payment experiences, while oftentimes managing financial accounts with various providers. Visa recognizes these challenges and is dedicated to improving the payment experience through innovative technology. To that effect, Visa launched Visa Flex Credential (VFC) in the U.S. region in April 2024. VFC is a new capability designed to streamline the payment process and enhance the overall user experience.

The initial rollout of VFC in the U.S. will involve a consumer debit primary (lead) credential that provides access to a consumer credit account as the secondary (funding) credential. VFC-enabled cards participating in this use case will display the “Debit/Flex” name on the physical and digital card art. Before an authorization, Acquirers and Merchants can also identify the VFC credentials electronically through ARDEF tables and Product Eligibility Inquiry messages (PEI).

More information can be found through the FAQ for Merchants

Visa is reminding all acquirers that their merchants should send authentication transactions on the highest protocol supported by the issuer. Acquirers whose merchants are not sending authentications on the highest protocol supported by the issuer account ranges are not adhering to the Visa Secure program requirements. If the highest protocol version is EMV 3DS 2.2.0, merchants must send EMV 3DS 2.2.0 authentications. The highest-protocol version supported by the issuer can be determined using the Preparation Request (PReq) / Preparation Response (PRes) message flow.

Additionally, Visa will discontinue support for EMV 3DS 2.1.0 on September 25, 2024. After this date, Visa Secure will no longer process EMV 3DS 2.1.0 transactions.

The Consumer Bill Payment Service program will be expanded effective 13 April 2024 to make Merchant Category Code (MCC) 8111—Legal Services and Attorneys eligible globally.

Visa is also reminding acquirers that Consumer Bill Payment Service (CBPS) providers that are misusing merchant category codes (MCCs), not properly submitting the CBPS indicator or submitting ineligible MCCs are not adhering to Visa Rules. Acquirers with third party bill payment providers utilizing the CBPS program without proper registration are also not adhering to Visa Rules.

CBPS is an optional service that can improve the bill payment experience for cardholders by allowing them to make card payments for bills via third party bill payment providers. CBPS is available to third party consumer bill payment providers that accept payments for various types of bills including rent, education, utilities and more.

For information regarding participation requirements and how to register for CBPS, contact your Visa representative.

The current EMV 3DS SDK encryption key certificate will expire on August 22, 2024. This will be a multi-step process starting March 1, 2024, and all EMV 3DS SDKs must update their encryption key certificate by August 21, 2024.

Merchants can start integration as soon as their SDK provider has updated their encryption key certificate. Merchants must work with their SDK provider to integrate the updates into their merchant app to avoid service disruption. Merchants must push the updated app to devices, publish a new version of the app and advise end consumers / device holders to update the merchant app on their device(s) before the expiration date.

To avoid service interruption, all Visa Secure 3DS endpoints must abide by the August 21, 2024 update timeline. Please reach out to your EMV 3DS SDK provider with any additional questions.

• Three response codes are moving from Category 4—Generic Response Codes to Category 2—Issuer Cannot Approve At This Time. For both Category 4 and Category 2 response codes, 15 retries in 30 days are permitted so there is no merchant/acquirer authorization retry impact. The response codes moving are:
  • Response Code 39 (no credit account)
  • Response Code 52 (no checking account)
  • Response Code 53 (no savings account)
• In response to merchant and acquirer requests for clarification, Response Code 14 will be removed from Category 3 excess reattempts. It will still be treated as a Category 1—Issuer Will Never Approve decline code and will remain in the Data Quality Program. As a Category 1, merchants must not reattempt an authorization request after a decline.
• A new response code, Z5 (valid account but amount not supported) is being introduced as a Category 2 decline code.

The updates are intended to improve authorization processing, minimize invalid authorization reattempts, and optimize the consumer experience through greater transaction approvals.

Merchants should work with their acquirers and acquirer processors to ensure they receive the information needed to understand if authorization reattempts are prohibited, or if issues need to be corrected before an authorization reattempt is made.