Introduction

This article provides an overview of common Reason Response Codes (RRCs) used in Visa Acceptance and Cybersource payment processing. RRCs indicate the outcome of a transaction, including successful authorizations, declines, errors, and fraud-related flags. Understanding these codes helps merchants quickly identify transaction status, troubleshoot issues, and determine appropriate next steps.

This article applies to Visa Acceptance and Cybersource clients who process payments and need to interpret transaction response codes returned via the API or the Enterprise Business Center (EBC). Internal support teams may also reference this article when assisting merchants with transaction troubleshooting.

When a decline or error occurs, reviewing the Request ID (RID) and Transaction Logs in the Enterprise Business Center (EBC) is strongly recommended as a first step. These logs contain more specific details about the error or decline reason beyond what the RRC alone provides, and are accessible to both merchants and internal support teams.

For the complete list of RRCs, refer to the Support Article: "What does this Reason Code mean?". For API inquiries:

• Visa Acceptance Clients: developer.visaacceptance.com
• Cybersource Clients: developer.cybersource.com

Overview of Reason Response Codes

1. Successful Transactions and CyberSource Declines

2. Bank Declines

Note: If the customer must contact their issuer or bank, provide the Transaction Reference Number (TRN). Additionally, reviewing the Request ID (RID) and Transaction Logs in the Enterprise Business Center (EBC) can provide more specific details on the decline reason returned by the issuing bank, beyond what the RRC alone indicates.

3. System and Configuration Errors

These responses indicate either a system-level issue or a merchant or processor configuration issue. Do not repeatedly retry transactions without first validating transaction status and configuration. As a first step, review the Request ID (RID) and Transaction Logs in EBC to obtain more specific error details before escalating.

Action for System or Configuration Errors:
Validate transaction status first by reviewing the RID and Transaction Logs in EBC. If errors persist, obtain or confirm the VAR sheet with your Merchant Acquirer and contact Client Services for platform configuration review.

4. Fraud and Chargebacks

Refunds and Credits Related to Reason Response Codes

Some RRCs may require issuing a refund or stand-alone credit after authorization or settlement. For step-by-step instructions, refer to:

Payments – How to Issue a Refund or Credit

Procedure: Merchant Action Steps

1. Identify the RRC – Review the code returned in the API response or within the Enterprise Business Center (EBC).
2. Review the Request ID (RID) and Transaction Logs in EBC – Before taking further action, check the RID and Transaction Logs in EBC. These logs contain more specific details about the decline or error reason beyond what the RRC alone provides.
3. Review the Description – Determine whether the transaction succeeded, failed, or requires further review based on the RRC and EBC log details.
4. Apply Recommended Actions:
   • Correct missing or invalid fields where applicable.
   • Review Address Verification System (AVS) or Card Verification Number (CVN) mismatches for potential fraud.
   • Request a different payment method for general declines.
   • For RRC 150, verify transaction status in EBC before retrying and investigate configuration if the error is recurring.
5. Contact the Relevant Party:
   • Bank declines → Customer contacts their issuer with the Transaction Reference Number (TRN).
   • System or processor issues → Contact your processor.
   • Configuration issues → Validate the Value Added Reseller (VAR) sheet and contact Client Services.
6. Prevent Recurrence – Maintain accurate payment data, validate inputs, and follow fraud-prevention best practices.

Summary Table

Potential Client Questions

• Why am I receiving an RRC 150 repeatedly for the same transaction type?
  • Repeated RRC 150 responses for the same merchant or transaction type typically indicate a configuration issue rather than a temporary system error. Review the RID and Transaction Logs in EBC for more specific details, confirm your merchant configuration matches the VAR sheet, and contact Client Services if the issue persists.
• Where can I find more details about why my transaction was declined beyond the RRC?
  • The Request ID (RID) and Transaction Logs in the Enterprise Business Center (EBC) contain more granular details about the decline or error reason. These logs are accessible to both merchants and internal support teams and should be the first place reviewed when troubleshooting a decline.
• My customer received a general decline (RRC 203). What should I do?
  • RRC 203 indicates a general decline from the issuing bank with no additional details provided in the RRC itself. Request an alternate form of payment from the customer. For more specific decline details, review the RID and Transaction Logs in EBC, which may contain a more specific response code returned by the issuing bank. If the customer needs to follow up directly, provide them with the Transaction Reference Number (TRN).
• What is the difference between a soft decline and a hard decline?
  • A soft decline (for example, RRC 200 or RRC 230) means the transaction was approved by the issuer but flagged for review due to a mismatch such as AVS or CVN. A hard decline (for example, RRC 201, 202, or 203) means the issuer has refused the transaction outright. Soft declines may still be captured but should be reviewed for fraud risk before doing so.
• What is a VAR sheet and why does it matter for RRC errors?
  • A Value Added Reseller (VAR) sheet contains the merchant's processor configuration details. When system or configuration-related RRCs such as 150, 234, or 261 occur repeatedly, validating that the merchant configuration matches the VAR sheet is a critical troubleshooting step. Contact your Merchant Acquirer to confirm VAR sheet details and reach out to Client Services for platform configuration review if needed.

Additional Resources

• Payments – How to Issue a Refund or Credit
• Support Article: What does this Reason Code mean? — For the complete list of RRCs.
• Visa Acceptance Developer Portal — For Visa Acceptance API inquiries.
• CyberSource Developer Portal — For CyberSource API inquiries.

Glossary