Use these Visa test values in PCE to simulate approvals, declines, and AVS/CVV outcomes. This page helps QA and developers validate user messaging, fraud rules, and retry flows without touching real cards.

Prerequisites

• Sandbox account, a test gateway enabled, and logging of payment responses (risk fields).

Limitations

• Test PANs work only in sandbox; AVS/CVV/EMS behavior can vary by gateway. Amount caps below are maximums for a scenario. Do not store PANs outside approved tools.

AVS & CVV/CSC

Use this data effectively. For more information on AVS and CVV/CSC, visit our dedicated documentation.

1. Map each scenario to your flow: AVS fail, CVV fail, delays, partials, timeouts.
2. Verify EMS risk handling (scores, reason codes, approval overrides).
3. Test fallback behavior when EMV is missing or a timeout occurs.
4. Confirm decline copy and retry paths are precise and actionable in your UI.

The AVS & CVV response signals appear in the risk object of payment responses:

"risk": {
  "cvvResponseCode": "Y",
  "cvvResponse": "Match",
  "cvvMatch": true,
  "avsResponseCode": "Y",
  "avsAddressMatch": true,
  "avsZipMatch": true,
  "avsAccountNameMatchPerformed": false
}

Visa AVS & CVV Scenarios (Sandbox)

Issuer Response Codes for Visa

This is a brief list of Issuer Response Codes for Visa. For the full list, please download this file.