--- description: Learn why CVV errors cause declined payments, what triggers them, and how merchants can reduce CVV-related declines without adding checkout friction. title: CVV Errors: Causes, Impact & Merchant Solutions image: https://cdn.smartretry.com/uploads/2026/09/resolving-cvv-mismatch-payment-declines.jpg --- [Skip to main content](#main-content) Payment Approval Optimization # Solving CVV Mismatch Declines: Root Causes and Practical Remediation for Merchants Published September 15, 2026 Last updated September 15, 2026 ![Reading time](https://cdn.smartretry.com/cdn-cgi/image/width=3840&quality=75&format=auto&fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Fclock.337f-cmnyb532.svg)11 min ![](https://cdn.smartretry.com/cdn-cgi/image/width=3840&quality=85&format=auto&fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F09%2Fresolving-cvv-mismatch-payment-declines.jpg) ## Still letting failed transactions slip through? SmartRetry turns declines into approvals - automatically, intelligently, and without changing your payment provider. Email address Let’s talk Table of Contents ![](https://cdn.smartretry.com/cdn-cgi/image/width=48&quality=75&format=auto&fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Fblog_star.1bil3v51fayky.svg) A rejected transaction due to a security code mismatch often looks like fraud, but genuine customer typos and rigid gateway rules drive significant false declines. Optimizing your checkout interface and risk calibration protects **authorization rates** while keeping fraud defenses intact. 1. Issuers may approve transactions with a CVV failure, leaving **gateway risk rules** to trigger the final hard decline. 2. Dynamic input validation and **digital wallets** eliminate manual typing mistakes before transactions reach card networks. 3. Deploying **network tokenization** bypasses recurring CVV requirements and prevents renewal payment failures. 4. Automated retries must be avoided on CVV failures because a **data correction** is required for successful processing. A customer fills out their billing details, reviews their cart, and hits the buy button. The loading spinner cycles for a moment, then the transaction is rejected: a CVV error has derailed the purchase. For merchants, these specific payment failures represent a frustrating intersection of security and lost revenue. The card verification value exists for a very specific reason: it protects the ecosystem against unauthorized use of account details. When this check fails, the immediate assumption is often that a bad actor is testing stolen credentials. But the reality of a payment declined for a CVV mismatch is rarely that straightforward. Genuine customers make typographical errors during checkout, payment service providers apply inconsistent filtering rules that block valid buyers, and issuers evaluate the security code alongside dozens of other risk signals, creating a complex web of decision-making. Understanding the mechanics behind a CVV decline is the first step in fixing the leak, and the objective is to reduce payment declines without compromising security or adding unnecessary checkout friction. ## The Mechanics of CVV2 Verification To address these checkout issues, it helps to look at what exactly the payment network is verifying. The industry generally refers to this code as CVV2, separating it from the CVV1 data embedded in the magnetic stripe of a physical card. Because merchants are strictly prohibited by the Payment Card Industry Data Security Standard (PCI-DSS) from storing the CVV2 after authorization, its presence in a transaction request serves as proof that the purchaser is physically holding the card at that exact moment. When a CVV mismatch occurs, it generally stems from one of three scenarios. The most common is a simple typographical error, such as a user typing quickly on a mobile device and entering a ‘4’ instead of a ‘7’. The second scenario involves card-not-present fraud, where malicious scripts or botnets run stolen primary account numbers (PANs) through a checkout page, guessing the CVV or leaving it blank to see what the gateway will allow. The third scenario involves outdated card data: a customer might update their expiration date in a saved profile after receiving a replacement card but forget that the CVV has also changed. In all these cases, the issuer response flags a mismatch, but the underlying intent of the user is vastly different. ## Behind the Scenes: Issuers vs. Payment Gateways The [payment processing flow](https://www.smartretry.com/blog/how-payments-work) for a CVV check is more nuanced than a simple pass or fail. When a merchant submits a transaction, the payment gateway routes the authorization request to the issuing bank. The issuer evaluates the PAN, the expiration date, the address data, and the CVV. The issuer then sends back an authorization response alongside a specific CVV match code. Common codes include ‘M’ for match, ‘N’ for no match, ‘P’ for not processed, or ‘U’ for issuer not certified. Interestingly, an issuer might financially approve the transaction, meaning the account exists and has sufficient funds, but still return an ‘N’ for the CVV check. This introduces a critical layer: PSP handling of CVV failures. Most modern payment service providers and gateways have built-in risk configurations. If the gateway receives an ‘N’ from the issuer, local fraud rules often trigger an automatic, [hard decline](https://www.smartretry.com/glossary/hard-decline), overriding the issuer’s financial approval. This mechanism protects the merchant from potential chargebacks, but it also means the merchant’s own gateway is responsible for the final rejection. Understanding whether a declined transaction originated from the issuer’s hard rejection or the PSP’s local risk threshold dictates how a merchant should troubleshoot the problem. ![Diagram illustrating how payment gateways evaluate CVV match codes and trigger hard declines independently of issuer financial approval.](https://cdn.smartretry.com/uploads/2026/09/issuer-gateway-cvv-response-routing-768x419.jpg) ## The Interplay Between CVV and AVS CVV checks rarely operate in a vacuum. They are typically evaluated alongside the Address Verification System (AVS). When the payment authorization request is sent, the issuer evaluates both data points simultaneously. A common scenario in payment operations is receiving an AVS match paired with a CVV mismatch, or vice versa. Merchants must configure their gateway rules to decide which combinations are acceptable based on their specific risk tolerance. For instance, a digital goods merchant might tolerate a partial AVS mismatch if the CVV matches perfectly, relying on the physical card possession as the stronger signal. Conversely, a merchant shipping high-value physical goods will likely reject any transaction where the CVV fails, regardless of whether the address is correct. Calibrating this matrix requires a clear understanding of your customer base and fraud exposure. ## The Cost of the False Decline When security settings are calibrated without consideration for user behavior, merchants face the challenge of the [false decline](https://www.smartretry.com/blog/false-declines-revenue-impact). A false decline happens when a legitimate buyer with valid intent and sufficient funds is blocked from completing a purchase. If a PSP’s rules are exceptionally rigid, a simple fat-finger mistake turns into a lost customer. The cost of these lost transactions extends beyond the immediate cart value, with false declines costing U.S. merchants an estimated $118 billion a year [(Source)](https://www.clear.sale/blog/everything-you-need-to-know-about-false-declines). Customers who experience repeated card declined messages often abandon the site entirely, and 27% of loyal customers do not return to the retailer after a false decline. In many cases, a customer will check their banking app, see a pending charge because the issuer approved the funds before the PSP rejected the CVV, and blame the merchant for the confusion. Merchants are forced into a balancing act. If they disable CVV checks entirely, they invite card testing and risk a spike in chargebacks. If they enforce strict checks without optimizing the user interface, their [transaction approval rate](https://www.smartretry.com/glossary/approval-rate) suffers. ## Remediation: Proactive Merchant Steps Mitigating CVV errors begins long before the transaction reaches the payment network. Merchant remediation steps should focus on creating a frontend experience that gently guides the user toward accurate data entry. ### Dynamic Input Validation The first line of defense is dynamic input validation. Checkout forms can be designed to recognize the card brand as soon as the user types the first few digits of the PAN. Since [American Express](https://www.smartretry.com/payment-providers/amex) uses a four-digit code on the front of the card, and [Visa](https://www.smartretry.com/payment-providers/visa) and [Mastercard](https://www.smartretry.com/payment-providers/mastercard) use a three-digit code on the back, the form should dynamically adjust the maximum length of the CVV field based on the detected network. If a user tries to type four digits into a Visa CVV field, the form should restrict the input. ### Numeric Masking and Clear Messaging Masking the field with a numeric-only keyboard on mobile devices prevents users from accidentally typing letters or special characters. Clear error messaging is equally important. When a transaction fails due to a CVV mismatch, presenting a generic “Payment Failed” banner leaves the user guessing. Instead, prompting them with “Please verify the security code on your card” provides clear direction, allowing them to correct the typo and try again. ### Encouraging Digital Wallets Another effective way to bypass CVV friction is to offer accelerated checkouts via digital wallets like [Apple Pay](https://www.smartretry.com/payment-providers/apple-pay) or [Google Pay](https://www.smartretry.com/payment-providers/google-pay). These methods use biometric authentication and device-specific cryptograms in place of a traditional CVV. Because the authentication is handled by the device and the tokenized data is passed securely, the risk of a user typing the wrong security code is eliminated entirely. ## Handling Subscription Payment Issues CVV requirements present a distinct challenge in the world of recurring billing. Because merchants cannot store the CVV, they cannot include it in subsequent billing cycles. This creates unique subscription payment issues when a merchant transitions from the initial checkout to automated renewals. During the initial checkout, known as a Customer Initiated Transaction (CIT), the merchant collects the CVV and passes it to the network to establish a baseline of trust. For subsequent billing cycles, or Merchant Initiated Transactions (MIT), the payment is submitted without the CVV. Instead, the merchant relies on specific network flags that indicate the transaction is part of an established recurring agreement. Problems arise when merchants fail to properly flag these recurring transactions in their payment authorization requests. If a gateway expects a CVV for a recurring charge because the MIT flag is missing, the transaction will fail. Properly utilizing network tokens resolves much of this friction, offering a 4% authorization uplift for token-based transactions versus PAN transactions. Network tokenization replaces the raw PAN with a merchant-specific token issued by the card network. Because the token is bound to the merchant and mathematically linked to the original, authenticated transaction, it bypasses the need for ongoing CVV checks. When a card is reissued, the network automatically updates the token, preventing the declines that typically occur when a CVV or expiration date changes. ![Conceptual diagram showing the shift from initial customer-initiated CVV checks to tokenized merchant-initiated recurring billing.](https://cdn.smartretry.com/uploads/2026/09/network-tokenization-recurring-billing-flow-768x419.jpg) ## The Role of 3D Secure in Modern Checkout Another layer of payment optimization involves 3D Secure (3DS). When a merchant routes a transaction through a 3DS challenge, the authentication responsibility shifts directly to the issuer. The customer authenticates via an SMS one-time password or a biometric prompt in their banking app. In many cases, a successfully authenticated 3DS transaction reduces the strict reliance on a manual CVV match, as the issuer has already verified the cardholder’s identity through a stronger, multi-factor channel. This is particularly relevant in markets operating under Strong Customer Authentication (SCA) mandates, where a standalone CVV is no longer considered sufficient proof of identity. By leaning on 3DS for higher-risk transactions, merchants can secure the payment processing flow without obsessing over single-digit typos. ## Intelligent Retry Logic and Payment Recovery When a transaction fails, the operational instinct is often to try again. However, retrying a CVV error requires careful handling. Submitting the exact same payload after a CVV mismatch will almost certainly result in another failure. Worse, rapid, identical retries on a bad CVV look suspiciously like a brute-force card testing attack, which can quickly lead to account velocity blocks or strained relationships with acquiring banks. Automated attempts to retry failed payments are generally reserved for soft declines, such as temporary network timeouts or suspected insufficient funds, where the passage of time or a different routing path might yield a different result. A CVV error is an explicit data failure: the data must change for the outcome to change, which usually means routing the customer back to the checkout interface. This is where intelligent payment recovery strategies come into play. Modern payment optimization involves categorizing decline codes and applying appropriate logic to each. Platforms like SmartRetry focus on this exact layer of transaction management, applying intelligent retries for declined payment transactions when the underlying conditions allow for it, while properly handling terminal data errors like a CVV mismatch. By understanding the distinction between a recoverable network timeout and a hard CVV failure, this nuanced approach helps merchants recover revenue and improve transaction approval rates by applying the right remedy to the right decline code, rather than using a blanket retry strategy that risks network penalties. ![Operational state representation showing terminal CVV mismatches separated from recoverable soft declines in automated retry systems.](https://cdn.smartretry.com/uploads/2026/09/intelligent-retry-decline-code-classification-768x419.jpg) ## Decoding the Dashboard and Analyzing Trends To manage these errors over time, merchants must look beyond individual transactions and analyze their processing data in aggregate. A sudden spike in CVV errors rarely indicates that a customer base has collectively forgotten how to type. An abrupt increase usually signals one of two things: a card testing attack or a systemic misconfiguration. Fraudsters frequently deploy automated scripts to test lists of stolen card numbers. Because these lists often lack the corresponding CVV, the bots submit the transactions with random guesses or empty fields. If a merchant’s dashboard shows thousands of rapid, low-value declines tied to CVV failures, they are likely weathering an attack. In these cases, deploying velocity checks, CAPTCHA, or pre-authorization risk scoring is necessary to protect the gateway. Conversely, a steady, persistent rate of CVV errors among seemingly legitimate customers might point to an issue with the checkout interface or an overly aggressive PSP fraud rule. Regularly auditing these decline logs allows payment operations teams to spot friction points, adjust their gateway configurations, and smooth out the checkout experience. ## Finding the Balance in Payment Operations The card verification value remains a structural pillar of card-not-present commerce. As long as raw card numbers are handled by consumers, the need to verify physical possession of the card will persist. However, a decline driven by a CVV error does not automatically mean the transaction is unrecoverable, nor does it always mean malicious intent is present. Merchants who view CVV checks merely as a binary security gate miss an opportunity to refine their operations. By designing intuitive user interfaces that catch formatting errors early, understanding the distinct difference between issuer responses and local gateway rules, and utilizing network tokens for recurring billing, businesses can minimize unnecessary friction. Security and revenue do not have to be opposing forces. When payment systems are configured to communicate clearly with the customer and route errors logically based on the specific decline code, merchants create an environment where the business is protected, and legitimate customers can complete their purchases with minimal interruption. Balancing these elements is the foundation of a mature, resilient payment operation. ### Frequently asked questions about this topic What causes a CVV mismatch decline during checkout? CVV mismatches typically occur due to customer typos, malicious card-testing bots guessing security codes, or outdated CVV data on reissued cards. Can an issuing bank approve a payment if the CVV fails? Yes. Issuers may approve funds while returning a CVV mismatch code, leaving the merchant gateway's local risk rules to decide whether to decline. Should merchants automatically retry transactions that fail CVV checks? No. Retrying identical bad CVV data causes repeat failures and risks card-testing penalties. The customer must update the security code directly. How do network tokens prevent CVV renewal declines? Network tokens mathematically link recurring billing to the initial authenticated purchase, bypassing recurring CVV checks even after card renewals. ### Help us to help others Follow us on Google, to see insights from us for your questions about payments. Make us your preferred source #### Share this article [![Share on X](https://cdn.smartretry.com/cdn-cgi/image/width=3840&quality=75&format=auto&fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Ftwitter.21z6yr9njnznr.svg)](https://twitter.com/intent/tweet?text=Solving%20CVV%20Mismatch%20Declines%3A%20Root%20Causes%20and%20Practical%20Remediation%20for%20Merchants&url=https%3A%2F%2Fwww.smartretry.com%2Fblog%2Fcvv-errors-causes-merchant-solutions "Share on X")[![Share on Facebook](https://cdn.smartretry.com/cdn-cgi/image/width=3840&quality=75&format=auto&fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Ffacebook.3sbfjbsxa26qg.svg)](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.smartretry.com%2Fblog%2Fcvv-errors-causes-merchant-solutions "Share on Facebook")[![Share on LinkedIn](https://cdn.smartretry.com/cdn-cgi/image/width=3840&quality=75&format=auto&fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Flinkedin.09sdc8tnlrn4a.svg)](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.smartretry.com%2Fblog%2Fcvv-errors-causes-merchant-solutions "Share on LinkedIn") ![Kyle Regacho](https://cdn.smartretry.com/cdn-cgi/image/width=256&quality=75&format=auto&fit=cover/https%3A%2F%2Fsecure.gravatar.com%2Favatar%2Faa4329c7f45a68c68f2fbccab899d0f43f3740f3f9e92d5c6ea711171fc1a35f%3Fs%3D96%26d%3Dmm%26r%3Dg) Author ##### Kyle Regacho [![LinkedIn](https://cdn.smartretry.com/cdn-cgi/image/width=32&quality=75&format=auto&fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Flinkedin.09sdc8tnlrn4a.svg)Find me on Linkedin](https://www.linkedin.com/in/kdregacho/) Focused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue [Read all articles >](/authors/kyle-regacho) ## Join our newsletter! Real strategies to recover lost revenue - straight to your inbox Email address Subscribe ## Articles you may find interesting: [View all](/blog) [![Optimizing Payment Performance: From Intelligent Routing to Soft Decline Recovery](https://cdn.smartretry.com/cdn-cgi/image/width=3840&quality=75&format=auto&fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F09%2Fpayment-performance-optimization-strategies-1.jpg) September 15, 2026 Optimizing Payment Performance: From Intelligent Routing to Soft Decline Recovery Maximizing payment approvals requires moving beyond passive processing. Discover how dynamic routing, network tokens, and smart decline recovery protect revenue and reduce involuntary customer churn across enterprise payment stacks.](/blog/payment-optimization)[![Payment Dispute Resolution and Revenue Recovery Strategies for 2026](https://cdn.smartretry.com/cdn-cgi/image/width=3840&quality=75&format=auto&fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F09%2Fpayment-dispute-resolution-revenue-recovery-strategy.jpg) September 7, 2026 Payment Dispute Resolution and Revenue Recovery Strategies for 2026 Discover how modern payment teams balance fraud prevention with user experience, using network interception tools and intelligent recovery logic to protect baseline revenue and cut false declines.](/blog/payment-dispute-resolution-revenue-recovery)[![Standardizing Payment Gateway Data to Optimize Authorization Rates](https://cdn.smartretry.com/cdn-cgi/image/width=3840&quality=75&format=auto&fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F08%2Fstandardizing-payment-payload-data-for-routing.jpg) August 19, 2026 Standardizing Payment Gateway Data to Optimize Authorization Rates Extracting and standardizing transaction fields like MCC and acquirer country turns raw gateway logs into actionable routing logic, protecting revenue and eliminating checkout drop-off.](/blog/parse-payment-payload-data-routing)[![Evaluating Payment Recovery Software to Prevent Involuntary Churn](https://cdn.smartretry.com/cdn-cgi/image/width=3840&quality=75&format=auto&fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F09%2Fsubscription-payment-recovery-software-evaluation.jpg) September 15, 2026 Evaluating Payment Recovery Software to Prevent Involuntary Churn Explore how modern payment recovery platforms use intelligent retries, automated account updaters, and targeted dunning to curb involuntary churn and recover recurring subscription revenue.](/blog/failed-payment-recovery-software) --- ```json {"@context":"https://schema.org","@type":"BlogPosting","headline":"Solving CVV Mismatch Declines: Root Causes and Practical Remediation for Merchants","url":"https://www.smartretry.com/blog/cvv-errors-causes-merchant-solutions","datePublished":"2026-09-15T09:47:51.000Z","dateModified":"2026-09-15T10:18:06.000Z","image":"https://cdn.smartretry.com/uploads/2026/09/resolving-cvv-mismatch-payment-declines.jpg","description":"Learn why CVV errors cause declined payments, what triggers them, and how merchants can reduce CVV-related declines without adding checkout friction.","publisher":{"@type":"Organization","@id":"https://www.smartretry.com/#organization","name":"SmartRetry","url":"https://www.smartretry.com","logo":{"@type":"ImageObject","url":"https://cdn.smartretry.com/logo.png","width":{"@type":"QuantitativeValue","value":175,"unitCode":"PX"},"height":{"@type":"QuantitativeValue","value":29,"unitCode":"PX"}},"description":"SmartRetry is a smart payment recovery platform that helps businesses save revenue from failed payment transactions and reduce false declines.","sameAs":["https://x.com/smartretry","https://www.facebook.com/smartretry","https://www.instagram.com/smartretry","https://www.linkedin.com/company/smartretry","https://www.youtube.com/@smartretry"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","availableLanguage":["Hebrew","English"],"url":"https://www.smartretry.com/contact"},"address":{"@type":"PostalAddress","streetAddress":"Menachem Begin","addressLocality":"Tel Aviv-Yafo","addressCountry":"IL"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://www.smartretry.com/blog/cvv-errors-causes-merchant-solutions","name":"Solving CVV Mismatch Declines: Root Causes and Practical Remediation for Merchants"},"inLanguage":"en","author":{"@type":"Person","@id":"https://www.smartretry.com/authors/kyle-regacho","name":"Kyle Regacho","url":"https://www.smartretry.com/authors/kyle-regacho","image":"https://secure.gravatar.com/avatar/aa4329c7f45a68c68f2fbccab899d0f43f3740f3f9e92d5c6ea711171fc1a35f?s=96&d=mm&r=g","sameAs":["https://www.linkedin.com/in/kdregacho/"]},"articleSection":"Payment Approval Optimization","wordCount":2126,"keywords":"CVV mismatch, CVV decline codes, false decline reduction, network tokenization, payment authorization optimization, how to fix cvv errors, reducing card not present false declines, 3D Secure authentication"} {"@context":"https://schema.org","@type":"FAQPage","author":{"@type":"Organization","@id":"https://www.smartretry.com/#organization","name":"SmartRetry","url":"https://www.smartretry.com","logo":{"@type":"ImageObject","url":"https://cdn.smartretry.com/logo.png","width":{"@type":"QuantitativeValue","value":175,"unitCode":"PX"},"height":{"@type":"QuantitativeValue","value":29,"unitCode":"PX"}},"description":"SmartRetry is a smart payment recovery platform that helps businesses save revenue from failed payment transactions and reduce false declines.","sameAs":["https://x.com/smartretry","https://www.facebook.com/smartretry","https://www.instagram.com/smartretry","https://www.linkedin.com/company/smartretry","https://www.youtube.com/@smartretry"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","availableLanguage":["Hebrew","English"],"url":"https://www.smartretry.com/contact"},"address":{"@type":"PostalAddress","streetAddress":"Menachem Begin","addressLocality":"Tel Aviv-Yafo","addressCountry":"IL"}},"mainEntity":[{"@type":"Question","name":"What causes a CVV mismatch decline during checkout?","acceptedAnswer":{"@type":"Answer","text":"CVV mismatches typically occur due to customer typos, malicious card-testing bots guessing security codes, or outdated CVV data on reissued cards."}},{"@type":"Question","name":"Can an issuing bank approve a payment if the CVV fails?","acceptedAnswer":{"@type":"Answer","text":"Yes. Issuers may approve funds while returning a CVV mismatch code, leaving the merchant gateway's local risk rules to decide whether to decline."}},{"@type":"Question","name":"Should merchants automatically retry transactions that fail CVV checks?","acceptedAnswer":{"@type":"Answer","text":"No. Retrying identical bad CVV data causes repeat failures and risks card-testing penalties. The customer must update the security code directly."}},{"@type":"Question","name":"How do network tokens prevent CVV renewal declines?","acceptedAnswer":{"@type":"Answer","text":"Network tokens mathematically link recurring billing to the initial authenticated purchase, bypassing recurring CVV checks even after card renewals."}}]} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.smartretry.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://www.smartretry.com/blog"},{"@type":"ListItem","position":3,"name":"Solving CVV Mismatch Declines: Root Causes and Practical Remediation for Merchants","item":"https://www.smartretry.com/blog/cvv-errors-causes-merchant-solutions"}]} ```