Skip to main content
SmartRetry - Payment Recovery Platform

Visa

  • Cards

Visa is a global card payment network enabling merchants to accept secure electronic payments worldwide.

Struggling with your approval ratio for this payment provider?

contact SmartRetry team →
Published
Last updated
1 min
Visa
Visa payment phone

Proceed payment with

Visa Company Overview

Foundation
1958
Stock ID
NYSE:V
Company Type
public
Employees
20,000+
Location
USAUSA
Channel
OnlineIn person
For developers
Status pageStack Overflow

Features

Global Acceptance Network

Accepted worldwide across online and in-store merchants.

Fast Authorization

Low-latency authorization with high network reliability.

Issuer Risk Signals

Detailed issuer responses and decline reason codes.

Fraud Prevention

Built-in network-level fraud and risk protection.

Visa Secure (3DS)

Support for strong customer authentication with frictionless flows.

Cross-Border Ready

Optimized for international and multi-currency transactions.

Tokenization & Wallets

Native support for network tokens and digital wallets like Apple Pay.

Tip from SmartRetry Merchants can improve Visa approval rates by ensuring accurate transaction data, using authentication only when required, and handling issuer decline signals correctly to avoid unnecessary retries.

Currencies

Processing currenciesUSD, EUR, GBP, JPY, AUD, CAD, CHF, CNY, HKD, SGD, SEK, NZD, MXN, BRL, INR

Available in

Available countries
  • Global

FAQ

While issuers make the final authorization decision, Visa’s network standards, data quality requirements, and authentication frameworks can help reduce unnecessary declines.
Visa is a card network that defines rules and routes transactions, while a PSP connects merchants to acquirers and manages integrations, APIs, and payment flows.
Visa is considered a global network with acceptance in over 200 countries and territories, making a global availability classification appropriate.
Issuer declines originate from the issuing bank. Merchants should review authentication, transaction data quality, and retry strategies rather than assuming a technical failure.
Merchants should follow Visa’s official dispute and evidence rules, maintain clear transaction records, and track dispute lifecycle stages through their acquirer or PSP.

Statuses

Statuses — All
CodeDescriptionLevelFrequencyResolution
ECI Codes
05

Cardholder authentication is successful (step-up or frictionless)

---
06

Authentication was attempted but not completed (e.g. frictionless or passive)

---
07

Non-authenticated e-commerce transaction

---
Issuer Response Codes
10

Approved, partial

---
11

Approved, VIP

---
12

Invalid transaction

---
13

Invalid amount

---
14

Invalid card number

---
15

No such issuer

---
19

Re-enter transaction

---
21

No action taken

---
25

Unable to locate record on file

---
28

File update file locked out

---
39

No credit account

---
41

Lost card

---
43

Stolen card

---
46

Closed account

---
51

Not sufficient funds

---
52

No checking account

---
53

No savings account

---
54

Expired card

---
55

Incorrect personal identification number

---
57

Transaction not permitted to cardholder

---
58

Transaction not permitted to terminal

---
59

Suspected fraud

---
61

Exceeds withdrawal amount limit

---
62

Restricted card

---
63

Security violation

---
64

Transaction does not fulfill AML requirement

---
65

Exceeds withdrawal frequency limit

---
70

Pin data required

---
74

Different value than that used for PIN encryption errors

---
75

Allowable number of PIN tries exceeded

---
76

Unsolicited reversal

---
78

Card not activated

---
79

Reversed (by switch)

---
80

No financial impact (used in reversal responses to declined originals)

---
81

Cryptographic error found in PIN (during PIN decryption)

---
82

CVV failure

---
85

No reason to decline (AVS/CVV2/credit voucher or return)

---
86

Cannot verify PIN (e.g., no PVV)

---
89

Ineligible to receive financial position information (GIV)

---
91

Issuer or switch inoperative

---
92

Routing error

---
93

Violation of law

---
94

Duplicate transmission

---
96

System malfunction

---
00

Approved or completed successfully

---
01

Refer to card issuer

---
02

Refer to card issuer's special conditions

---
03

Invalid merchant

---
04

Pick-up card

---
05

Do not honor

---
06

Error

---
07

Pick-up card, special conditions

---
1A

Additional customer authentication required

---
6P

Verification data failed

---
B1

Surcharge amount not permitted on Visa cards or EBT food stamps (U.S. acquirers only)

---
B2

Surcharge amount not supported by debit network issuer.

---
N0

Force STIP

---
N3

Cash service not available

---
N4

Cash request exceeds issuer or approved limit

---
N5

Ineligible for resubmission

---
N7

Decline for CVV2 failure

---
N8

Transaction amount exceeds preauthorized approval amount

---
P5

Denied PIN unblock—PIN change or unblock request declined by issuer

---
P6

Denied PIN change—requested PIN unsafe

---
Q1

Card Authentication failed

---
R0

Stop Payment Order

---
R1

Revocation of authorization order

---
R2

Transaction does not qualify for Visa PIN

---
R3

Revocation of all authorizations order

---
Z1

Offline-declined

---
Z3

Unable to go online; offline-declined

---
5C

Transaction not supported/blocked by issuer

---
9G

Blocked by cardholder/contact cardholder

---
3DS Transaction Status Reason
10

Stolen card

---
11

Suspected fraud

---
12

Transaction not permitted to cardholder

---
13

Cardholder not enrolled in service

---
14

Transaction timed out at the ACS

---
15

Low confidence

---
16

Medium confidence

---
17

High confidence

---
18

Very high confidence

---
19

Exceeds ACS maximum challenges

---
20

Non-payment transaction not supported

---
21

3RI transaction not supported

---
22

ACS technical issue

---
23

Decoupled authentication required by ACS but not requested by 3DS requestor

---
24

3DS requestor decoupled max expiry time exceeded

---
25

Decoupled Authentication was provided insufficient time to authenticate cardholder. ACS will not make attempt

---
26

Authentication attempted but not performed by the cardholder

---
27

Preferred authentication method not supported

---
01

Card authentication failed

---
02

Unknown device

---
03

Unsupported device

---
04

Exceeds authentication frequency limit

---
05

Expired card

---
06

Invalid card number

---
07

Invalid transaction

---
08

No card record

---
09

Security failure

---
80

Error connecting to ACS

---
81

ACS timed out

---
82

Invalid response from ACS

---
83

System error response from ACS

---
84

Internal error while generating Cardholder Authentication Verification Value (CAVV)

---
85

Visa Merchant ID (VMID) not eligible for requested program

---
86

Protocol version not supported by ACS

---
87

Transaction is excluded from attempts processing — includes non-reloadable prepaid card and Non-Payments (NPA)

---
88

Requested program not supported by ACS

---
89

CAVV is included in response

---
90

Issuer Strong Customer Authentication (SCA) required

---
91

CanBeUsedForFidoEnrollment

---
92

CanNotBeUsedForFidoEnrollment

---
3DS Transaction Status
Y

Authentication / Account Verification Successful

---
N

Not Authenticated / Account Not Verified; Transaction denied

---
U

Authentication / Account Verification Could Not Be Performed (technical or other problem)

---
A

Attempts Processing Performed; not authenticated/verified, but proof of attempted authentication is provided

---
C

Challenge Required; additional authentication required (CReq/CRes flow)

---
D

Decoupled authentication confirmed

---
R

Authentication / Account Verification Rejected; issuer requests authorization not be attempted

---
I

Informational only; 3DS Requestor challenge preference acknowledged

---
CAVV Result Codes
0

CAVV could not be verified or was missing. No liability shift; merchant is not protected.

---
1

CAVV failed verification – cardholder authentication. Liability remains with issuer.

---
2

CAVV passed verification – cardholder authentication. Liability shift applies.

---
3

CAVV passed verification – attempted authentication. Liability shift applies.

---
4

CAVV failed verification – attempted authentication. Liability shift applies.

---
5

Reserved – Not used.

---
6

Issuer not participating in CAVV verification. Liability shift applies.

---
7

CAVV failed verification – attempted authentication. Liability shift applies.

---
8

CAVV passed verification – attempted authentication. Liability shift applies.

---
9

CAVV failed verification – attempted authentication. Liability shift applies.

---

CAVV not present or not verified. No liability shift; merchant is not protected.

---
A

CAVV passed verification – attempted authentication. Liability shift applies.

---
B

CAVV passed verification – no liability shift. Merchant is NOT protected.

---
C

CAVV not verified (Attempted Authentication). Liability shift applies.

---
D

CAVV not verified (Cardholder Authentication). Liability shift applies.

---

Articles you may find interesting:

View all
Why Issuer Decline Codes Are Inconsistent and How to Build Smarter Payment Recovery

June 18, 2026

Why Issuer Decline Codes Are Inconsistent and How to Build Smarter Payment Recovery

This article explains why issuer decline codes are unreliable and how payment teams can use better customer messaging, smarter retries, and context-aware optimization to recover revenue and reduce false failure handling.

Why Payment Routing Changes Trigger Approval Rate Drops and How to Recover

June 11, 2026

Why Payment Routing Changes Trigger Approval Rate Drops and How to Recover

This article explains why issuer trust breaks during payment routing changes and how operators can restore performance with gradual traffic shifts, cleaner auth data, and smarter decline recovery to protect revenue.

When Issuers Build Around Customer Money Flows, Authorization Performance Improves

June 4, 2026

When Issuers Build Around Customer Money Flows, Authorization Performance Improves

This article explains how issuers use deposit timing, recurring behavior, and better signals to approve more payments. For operators, the payoff is fewer false declines, smarter retries, and stronger recurring revenue retention.

How to Avoid Payment Declines at the 2026 FIFA World Cup

May 9, 2026

How to Avoid Payment Declines at the 2026 FIFA World Cup

This article explains how merchants can reduce cross-border declines during the World Cup through smarter routing, richer auth data, and recovery tactics that protect revenue and lift approval rates.