Tip from SmartRetry Configure your webhook parsers to explicitly whitelist non-standard approval codes like Visa 11, ensuring they never flow into automated retry queues where they could trigger accidental duplicate charges.
Visa
Visa Issuer Response Code 11: Approved, VIP
technical decline
Last updated: September 25, 2026
About 11 - "Approved, VIP"
Key details
- 11
- Issuer Response Codes
- 11
- Approved, VIP
technical decline
What it means
Visa response code 11 indicates that a transaction has been successfully 'Approved (V.I.P)' by the issuing bank. Unlike standard decline codes, this is a positive authorization signal signifying a successful payment outcome. The 'VIP' designation refers to Visa's internal classification, but for payment operations, it functions entirely as a standard approval.
Classification & retryability
technicalRetryable: no
Why does code 11 occur?
- The issuing bank successfully authorized the transaction and assigned it Visa's VIP approval designation.
- A payment gateway or downstream system incorrectly mapped this successful authorization response as a decline.
How to solve 11?
Treat the transaction as an approval and proceed with your standard authorization-success and capture workflows. Do not initiate any decline recovery, involuntary churn messaging, or account updater logic. If your payment gateway or processor has erroneously categorized this transaction as a decline, escalate the discrepancy to their technical support team to correct their response code mapping.
Solving as a merchant
Ensure the transaction is captured according to your processor's rules and reconcile the authorization with your settlement records. If your system incorrectly flagged this as a payment failure, do not retry the payment, as a second authorization attempt will likely result in duplicate charges or duplicate-capture risks.
Solving as a customer
No action is required from the customer, as their payment was successfully approved by their issuing bank.
Frequently asked questions about this topic
Share this article
Author
Kyle Regacho
Find me on LinkedinFocused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue
Read all articles >Related codes
Articles you may find interesting:
View all
Turning Payment Declines into Revenue with Context-Aware Retry Logic
Blind retries waste fees and damage issuer trust. By analyzing decline codes and timing reattempts around payroll cycles, payment teams can successfully salvage recurring revenue without customer disruption.
Why Payments Fail: Decoding Decline Codes and Modernizing Retry Logic
Surface-level decline messages conceal critical issuer signals. Discover how intelligent retries, network tokens, and behavioral timing protect MID health and systematically recover lost recurring revenue.
Decoding Payment Declines: Turning Authorization Failures into Recovered Revenue
Blindly retrying failed transactions hurts authorization rates and risks network fines. Discover how decoding issuer responses turns card declines into recovered revenue.
The Real Cost of Payment Declines and How to Recover Lost Revenue
Payment failures cost merchants billions in uncaptured revenue and customer churn. Discover how data-driven retries and response code intelligence help teams recover failed transactions and protect conversion.