Introduction

This article explains how to settle a transaction that has received a card verification number (CVN) mismatch response. It applies to merchants and developers integrating with Visa payment processing APIs, specifically the Simple Order API, SCMP API, and REST API. Use this article when a transaction has already been authorized despite a CVN mismatch and you need to proceed with settlement, or when you want to configure your integration to bypass CVN mismatch blocks on future transactions.

Settling a Transaction After a CVN Mismatch

A transaction that has received a CVN mismatch can still be settled using its authorization code, provided an authorization code was received from the bank. To proceed with settlement, use the authorization code returned during the original authorization response.

Preventing Future CVN Mismatch Blocks on Authorization and Capture Transactions

To prevent future transactions that request both an authorization and capture from being blocked due to a CVN mismatch, set the applicable field to the value indicated for your API integration.

Simple Order API

businessRules_ignoreCVResult = true

SCMP API

ignore_bad_cv = yes

REST API

ignoreCvResult = true

Important Consideration

While uncommon, some banks may decline a transaction when the CVN is mismatched, regardless of the configuration settings above. In these cases, the decline originates from the issuing bank and cannot be overridden at the merchant or gateway level.

Potential Client Questions

• Can a transaction be settled if it received a CVN mismatch?
  • Yes. A transaction that received a CVN mismatch can be settled using its authorization code, as long as an authorization code was returned by the bank during the original authorization.
• How can future CVN mismatch blocks be prevented for authorization and capture transactions?
  • Set the appropriate field in your API integration to ignore CVN mismatch results. The field name varies by API: use businessRules_ignoreCVResult = true for the Simple Order API, ignore_bad_cv = yes for the SCMP API, and ignoreCvResult = true for the REST API.
• Will setting the ignore CVN field guarantee the transaction is approved?
  • No. While uncommon, some banks may still decline a transaction when the CVN is mismatched, even if the ignore CVN field is set. The issuing bank has final authority over the authorization decision.
• Which APIs support the CVN ignore configuration?
  • The Simple Order API, SCMP (Secure Commerce Messaging Protocol) API, and REST (Representational State Transfer) API all support a CVN ignore configuration field, each with a different field name and value format.

Additional Resources

• Payments - Understanding the Difference Between a Soft Decline and Hard Decline (200, 203, 204, 205, 230)