Visa Secure, long known as Verified by Visa (VbV), is Visa's version of 3-D Secure: an extra authentication step that checks the person paying online is the genuine cardholder. For merchants, the main draw is liability shift, which moves the cost of fraud chargebacks it covers from you to the card issuer.
What changed: from Verified by Visa to Visa Secure
Visa renamed Verified by Visa as Visa Secure, and the technology underneath moved from the original 3-D Secure 1.0 (the bank password pop-up) to EMV 3-D Secure, often called 3DS 2.0. Visa and Mastercard both retired support for 3DS 1.0 in October 2022.
The newer protocol sends the issuer far more data about the device, the order and the account, so most low-risk purchases are approved with no prompt at all (a "frictionless" flow). Only riskier payments are challenged, usually with a one-time passcode or an approval in the bank's app. In Europe, strong customer authentication rules under PSD2 make this step a legal requirement for many online payments.
Everything below, from how liability shift works to which orders it covers and how to treat each result, still applies. The details differ by region and acquirer, so confirm current rules with yours.
How it works
- The consumer goes through checkout normally and enters the same fields as always.
- The merchant's authentication software sends an enrollment check to Visa and the card issuer.
- The issuer decides whether to approve silently or challenge. In the classic flow, an enrolled consumer saw a pop-up that looked like it came from the issuing bank.
- If challenged, the consumer enters a password, PIN, one-time passcode or approves in the banking app.
- The issuer validates the response and returns the result to the merchant, who never sees or handles the password.
Depending on the issuer and regional mandates, two-factor authentication or a one-time password may be required instead of a static password. The classic pop-up carried a secret message only the consumer knew, so they could tell it was real and not a phishing copy.
What's required to implement it
- E-commerce only. The consumer authentication programs do not work on mail or telephone orders, so keep fraud processes for MOTO traffic.
- Everyone has to participate. The merchant, issuer and acquiring bank must all take part. Make sure your acquirer supports the e-commerce indicator (ECI) and ask about its certification requirements.
- Send the right data. Mark the order as e-commerce with the ECI, check AVS, check enrollment, and capture the CAVV/AAV authentication value and the XID transaction identifier, which prove the order was checked.
- Certification. In the classic setup you obtained a digital certificate from Visa through your acquirer, a process that took about two weeks. Today most merchants get this through their gateway or processor.
- Keep your other checks. It only covers certain Visa transactions, and there are legitimate cases where a customer cannot complete authentication.
- Low-volume merchants should consider an outsourced service bureau rather than building this themselves.
What's covered
Transactions authenticated through Visa Secure shift the liability for fraud chargebacks from the merchant to the issuer. The shift also applies when you attempt authentication but the cardholder is not enrolled in the program. If the cardholder is enrolled but cannot authenticate, you get no liability shift.
Under Visa's original reason codes, the shift covered 83 (Fraudulent Transaction, CNP), 75 (Cardholder Does Not Recognize Transaction), 23 (Invalid Travel & Entertainment) and 61 (Fraudulent Transaction, MO/TO/EC). Since Visa introduced its current dispute framework in 2018, card-not-present fraud disputes are generally coded 10.4 (Other Fraud, Card-Absent Environment), so expect to see that code on today's chargebacks.
Under the original rules, these were not covered: procurement cards, recurring billing, split shipments or back-ordered goods, and "one-click" sales. Higher-risk segments such as adult content and gaming may also fall outside coverage, so check with Visa or your acquirer before relying on it. Country mandates vary too (for example, dynamic tokens required of issuers in the UK).
How to use the results
- Enrolled and authenticated, covered order type: accept the order.
- Not enrolled, covered order type, enrollment was checked, and the order looks normal for you: accept the order.
- Not enrolled, enrollment was checked, but the order does not look normal: review it or run further fraud checks, favoring sales conversion.
- Enrolled but could not authenticate, and the order looks normal: run other fraud screening or manually review it, favoring risk aversion.
- Not a covered order type: use your traditional checks.
Limits and edge cases
- Legitimate customers fail authentication. Pop-up blockers, timeouts, and cardholders who registered long ago and forgot their password or PIN all cause good customers to fail. A failed authentication is not proof of fraud.
- The shift is not a guarantee. Fraudsters have taken over issuer accounts, changed the address and registered for the program themselves. Merchants who followed the rules were still covered, but you should not treat it as your only control.
- It simplifies disputes. When the cardholder authenticated, the dispute plays out between the issuer and the cardholder rather than between you and your customer.
Visa's VAMP program: why it matters to merchants
Authentication is one way to cut fraud before it becomes a chargeback, and Visa now measures that outcome through the Visa Acquirer Monitoring Program (VAMP). VAMP took effect on April 1, 2025. Visa describes it as consolidating five earlier fraud and dispute programs into a single acquirer program with one remediation process. It replaces the older merchant-focused programs (VDMP and VFMP, among others), and its counts feed back to merchants through their acquirer.
How the ratio works. VAMP looks at card-not-present transactions, domestic and cross-border, and divides the fraud reports (TC40) plus disputes (TC15) by settled transactions. The same sale can count twice, once as a fraud report and again if it also becomes a formal dispute, which is why catching problems before a dispute is filed (for example, with pre-dispute alerts) matters.
- Merchants: the "Excessive" level was 2.2% when the program launched and dropped to 1.5% on April 1, 2026 in the US, Canada, the EU and Asia-Pacific. Other regions differ, so confirm yours. A minimum monthly count of fraud and dispute reports applies (1,500 in those regions).
- Acquirers: an acquirer's portfolio is "Above Standard" at 0.5% and "Excessive" at 0.7%.
- Cost: merchants in the Excessive tier are generally charged a per-transaction fee, passed through by the acquirer. Ask your acquirer for the current amount.
- Enumeration: VAMP also has separate criteria for enumeration, the brute-force card-testing attacks that run at checkout, so a spike in test transactions can trigger the program long before chargebacks appear.
These thresholds have changed since launch and differ by region, so treat the figures above as a guide and check Visa's own material: Introducing the Visa Acquirer Monitoring Program and the Visa VAMP fact sheet (PDF). Ask your acquirer how authenticated and liability-shifted transactions are treated in your ratio.
Learn to measure and forecast your VAMP ratio. Lesson 2 of our Advanced Chargeback Analytics course gives a full VAMP overview: the ratio formula, the 2026 merchant and acquirer thresholds, the enumeration ratio, and how to forecast how many months of runway you have before you cross a threshold.
Key notes
- Alternatives: Mastercard Identity Check (formerly SecureCode), American Express SafeKey (originally limited to the UK and Singapore) and J/Secure by JCB. Most gateways offer them together.
- Building in-house: not practical. Use a gateway, processor or authentication provider.
- Cost: available as an outsourced service or software. Expect per-transaction or annual fees plus changes to your checkout engine.
- Sample vendors: Cardinal Commerce.
Related reading: Consumer Authentication, Visa and Mastercard upgrade 3-D Secure, and EMVCo's 3DS 2.0 specification.
Not sure where 3-D Secure fits in your fraud strategy? Talk to a senior consultant: no junior hand-offs and no vendor pitch, just a vendor-neutral read on where you actually stand. See our consulting services.