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 from the past 15 minutes.
RRC 233	Processor Decline – Invalid Data – The processor returned a general decline. Request an alternate payment method.
RRC 150	Error – General System Failure – A system error occurred. Do not continuously retry; review transaction status first.
RRC 151	Error – Server Timeout – The request was received but the server timed out. Check the Business Center before retrying to avoid duplicates.

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. Configuration Errors

These declines indicate an issue with the merchant setup that must be corrected. Do not retry the transaction until configuration is fixed.

RRC	Description
RRC 232	Decline – The card type is not accepted in the merchant's processor configuration.
RRC 234	Configuration Error – A setup issue exists with your merchant account. • If isolated to one transaction → likely a bank decline. • If recurring → indicates an account configuration problem. 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 Configuration Errors: Contact your Merchant Acquirer for a VAR sheet to verify processor setup. Then contact Client Services to correct platform configuration.

4. Fraud and Chargebacks

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

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:
   • For declines: correct missing or invalid fields.
   • For duplicate submissions: confirm customer intent.
   • For AVS/CVN mismatches: review for fraud.
   • For general declines (203, 233): request a different payment method.
   • For system errors (150, 151): check status before retrying.
4. Contact Relevant Party:
   • Bank declines → Customer contacts their issuer with the TRN.
   • Processor/system issues → Contact your processor.
   • Configuration errors (232, 234, 240, 261) → Obtain VAR sheet and contact Client Services.
5. Prevent Recurrence – Maintain accurate payment info, validate customer input, and follow fraud prevention/SCA 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
System Errors	150, 151	Check status, retry carefully
Bank Declines	200, 201, 202, 203, 230	Customer or bank follow-up
Configuration Errors	232, 234, 240, 261	Contact Acquirer for VAR sheet, then Client Services
Fraud Flags	400	Review in AFS before capture