Non VBV Bins Explained
Published: October 20, 2026 · By Marcus Hale
Non VBV refers to card ranges whose issuer does not enforce 3D Secure (Verified by Visa / Mastercard SecureCode) during authorisation. These ranges are valuable because transactions are less likely to trigger an additional authentication step.
VBV vs non VBV
VBV (Verified by Visa) and Mastercard SecureCode are 3D Secure protocols. When a card is in a VBV-enabled range, the issuer may challenge the transaction with a password or OTP. Non VBV ranges skip this step, making authorisation smoother but potentially less secure.
Why issuer behavior varies
Whether a range is VBV or non VBV depends on the issuer's configuration, which changes over time. A range that is non VBV today may become VBV tomorrow. Always verify before relying on a non VBV assumption.
How to identify non VBV ranges
Non VBV ranges are identified by their BIN prefix. Dedicated tools and databases track which BINs are currently non VBV. The status changes, so freshness of data matters.
Why non-VBV ranges exist
3D Secure adds friction: the cardholder is redirected or challenged, and some transactions fail because the cardholder abandons the challenge. Issuers in some regions and segments keep ranges outside 3DS enforcement to reduce that friction, especially for low-risk or recurring transactions. Those ranges are described as non-VBV.
The risk of assuming a range is non-VBV
Issuer configuration changes. A range that skipped 3DS last quarter may enforce it today. Relying on stale non-VBV data leads to failed transactions and wasted authorization attempts. Always verify the current behavior and treat non-VBV status as a probability, not a guarantee.
How to test the current behavior
The only reliable test is an authorization attempt against the issuer. Observing whether the response includes a 3DS challenge tells you the current behavior for that card and merchant combination. Record the result with a timestamp so you know how fresh the data is.