Introduction

This article provides an overview of common Reason Response Codes (RRC) 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 next steps.

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

RRC	Description
RRC 100	Successful Transaction – The payment has been successfully authorized and can be transmitted for funding.
RRC 101 & 102	Declined – Missing or Invalid Data – One or more required fields are missing or contain invalid data. Review missingField or invalidField_0..N in the reply message, correct errors, and resend.
RRC 104	Duplicate Request – The merchantReferenceCode matches another request from the past 15 minutes.
RRC 233	Processor Decline – Invalid Data – The processor returned a general decline. Request an alternate payment method.

2. Bank Declines

Note: If the customer must contact their issuer/bank, provide the Transaction Reference Number (TRN).

RRC	Description
RRC 200	Soft Decline – AVS No Match – Approved by the issuer but flagged due to an AVS mismatch. Authorization may be captured, but review for fraud.
RRC 201	Hard Decline – Issuer requires clarification. No authorization code was received.
RRC 202	Hard Decline – Payment method expired. Request updated expiration date.
RRC 203	Hard Decline – Card Refused – General decline with no additional issuer details. Request another form of payment.
RRC 230	Soft Decline – CVN No Match – Approved but flagged due to CVN mismatch.

3. System and Configuration Errors

These responses indicate either a system‑level issue or a merchant/processor configuration issue. Do not repeatedly retry transactions without validating transaction status and configuration.

RRC	Description
RRC 150	System Error – A system error occurred during transaction processing. Depending on the payment processor handling the transaction, this response may indicate: A valid temporary system error, or A processor rejection due to invalid or incomplete data. Merchants should design transaction handling logic to correctly manage system errors and avoid endlessly retrying failed requests. Always verify transaction status before retrying and refer to the documentation for the connection method being used. If RRC 150 occurs repeatedly for the same merchant or transaction type: This may indicate a configuration issue rather than a transient system error. Confirm the merchant configuration matches the information on the VAR sheet. If using Visa Acceptance Platform (VAP), review the processor setup entered on the platform. If not using VAP, submit the VAR sheet in a support case for configuration validation. After validation, confirm with the Merchant Acquirer that the processor account and VAR sheet details are correct.
RRC 232	Decline – The card type is not accepted in the merchant's processor configuration.
RRC 234	Configuration Error – A setup issue exists with the merchant account. If recurring, contact Client Services for correction.
RRC 240	Decline – Card type sent is invalid or does not match the card number.
RRC 261	Decline – Merchant account setup is invalid or missing on the processor gateway.

Action for System or Configuration Errors:
Validate transaction status first. 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

RRC	Description
RRC 400	Soft Decline – Fraud – Fraud score exceeds AFS threshold. Review before capture.

Refunds and Credits Related to RRCs

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 in the API response or Business Center.
2. Review the Description – Determine whether the transaction succeeded, failed, or requires review.
3. Apply Recommended Actions:
   • Correct missing or invalid fields where applicable.
   • Review AVS/CVN mismatches for fraud.
   • Request a different payment method for general declines.
   • For RRC 150, verify transaction status before retrying and investigate configuration if recurring.
4. Contact Relevant Party:
   • Bank declines → Customer contacts issuer with the TRN.
   • System or processor issues → Contact your processor.
   • Configuration issues → Validate VAR sheet and contact Client Services.
5. Prevent Recurrence – Maintain accurate payment data, validate inputs, and follow fraud‑prevention best practices.

Summary Table

Category	Example RRCs	Next Action
Successful Transactions	100	Proceed to settlement
Cybersource Declines	101, 102, 104, 233	Correct missing or invalid fields
Bank Declines	200, 201, 202, 203, 230	Customer or bank follow‑up
System / Configuration Errors	150, 232, 234, 240, 261	Check status; validate VAR sheet if recurring
Fraud Flags	400	Review in AFS before capture