Para que puedas comprender los motivos de los rechazos en tus cobros, o al intentar registrar tarjetas cuando utilizas Cybersource, te dejamos una lista de los mensajes de error y los detalles.
Reason Code | Reply Flag (SCMP) | Description | Possible Action |
100 | SOK | Successful transaction. | No action required. |
101 | DMISSINGFIELD | Declined. The request is missing one or more fields. | See the response fields missingField_0...N for which fields are invalid. Resend the request with the correct information. |
102 | DINVALIDDATA | Declined. One or more fields in the request contains invalid data. | See the response fields invalidField_0...N for which fields are invalid. Resend the request with the correct information. |
104 | DDUPLICATE | Declined. The merchant reference code sent with this authorization request matches the merchant reference code of another authorization request that you sent in the past 15 minutes. | Resend the request with a unique merchant reference code. |
105 | DDUPLICATE | Merchant transaction identifier (MTI) sent with this request has already been used in the past 60 days. | Resend this request with a unique MTI. |
110 | SPARTIALAPPROVAL | Partial amount was approved. | See "Partial Authorizations" in Credit Card Services Using the Simple Order API |
150 | ESYSTEM | Error. General system failure. A system error occurred. | You must design your transaction management system to correctly handle system errors. Depending on which payment processor is handling the transaction, the error might indicate a valid system error or it might indicate a processor rejection because of some type of invalid data. In either case, it is best not to design your system to endlessly resend a transaction when a system error occurs.For information about how to handle system errors and retries, see the documentation for the client (SDK) that you are using. |
151 | ETIMEOUT | Error. The request was received, but a server timeout occurred. This error does not include timeouts between the client and the server. | To avoid duplicating the transaction, do not resend the request until you review the transaction status in the Business Center.For information about how to handle system errors and retries, see the documentation for the client (SDK) that you are using. |
152 | ETIMEOUT | Error. The request was received but a service did not finish running in time. | To avoid duplicating the transaction, do not resend the request until you review the transaction status in the Business Center.For information about how to handle system errors and retries, see the documentation for the client (SDK) that you are using. |
153 | ESYSTEM | Your account is not enabled for the OCT service. | Contact customer support to have your account enabled for this service. |
154 | ESYSTEM | Bad MAC key. The payout failed due to MAC validation failure. | The merchant is safe to retry the payout as it was not sent to the customer. On receipt of this response code, the TID used is quarantined for 24 hours. Cybersource Operation Team gets an alert and then requests a MAC reset by Barclays. The TID then comes back into service 24 hours after it went out of service. To prevent the quarantining process from causing hard downs related to payouts, merchants using payouts should be boarded with multiple TIDs. |
200 | DAVSNO | Soft decline. The authorization request was approved by the issuing bank but was flagged because it did not pass the Address Verification Service (AVS) check. | You can capture the authorization, but consider reviewing the order for the possibility of fraud. |
201 | DCALL | Decline. The issuing bank has questions about the request. You do not receive an authorization code programmatically, but you might receive one verbally by calling the processor. | Call your processor to possibly receive a verbal authorization. For contact phone numbers, refer to your merchant bank information. |
202 | DCARDEXPIRED | Decline. Expired card. You might also receive this code or flag if the expiration date you provided does not match the date on file with the issuing bank.Note: The ccCreditService field does not check the expiration date. Instead, it passes the request to the payment processor. If the payment processor allows credits to be issued to expired cards, this functionality is not limited. | Request a different payment card or other form of payment. |
203 | DCARDREFUSED | Decline. General decline of the card. No other information provided by the issuing bank. | Request a different payment card or other form of payment. |
204 | DCARDREFUSED | Decline. Insufficient funds in the account. | Request a different payment card or other form of payment. |
205 | DCARDREFUSED | Decline. Stolen or lost card. | Refer the transaction to your customer support center for manual review. |
207 | DCARDREFUSED | Decline. Issuing bank unavailable. | Wait a few minutes and then resend the request. |
208 | DCARDREFUSED | Decline. Inactive card or card not authorized for card-not-present transactions. | Request a different payment card or other form of payment. |
209 | DCARDREFUSED | Decline. Card verification number (CVN) did not match. | Request a different payment card or other form of payment. |
210 | DCARDREFUSED | Decline. The card has reached the credit limit. | Request a different card or other form of payment. |
211 | DCARDREFUSED | Decline. Invalid Card Verification Number (CVN). | Request a different payment card or other form of payment. |
212 | DCARDREFUSED | EMV transaction was rejected. | Resubmit the request with chip and PIN. |
213 | DCARDREFUSED | Decline. Fraud Status. | Request a different payment card or other form of payment. |
216 | DCARDREFUSED | Decline. Some of the card data was invalid (CVV, expiration date, card number, name on card). | Request a different payment card or other form of payment. |
220 | DCHECKREFUSED | Decline. Generic decline. | Request a different form of payment. |
221 | DCHECKREFUSED | Decline. The customer matched an entry in the processor's negative file. | Review the order and contact the payment processor. |
222 | DCHECKREFUSED | Decline. The customer's account is frozen. | Review the order or request a different form of payment. |
230 | DCV | Soft decline. The authorization request was approved by the issuing bank but was flagged because it did not pass the Card Verification Number (CVN) check. | You can capture the authorization, but consider reviewing the order for the possibility of fraud. |
231 | DINVALIDCARD | Decline. Invalid account number. | Request a different payment card or other form of payment. |
232 | DINVALIDDATA | Decline. The card type is not accepted by the payment processor. | Contact your merchant bank to confirm that your account is set up to accept the card type. |
233 | DINVALIDDATA | Decline. General decline by the processor. | Request a different payment card or other form of payment. |
234 | DINVALIDDATA | Decline. There is a problem with your merchant configuration. | Do not resend the request.Contact your customer support to correct the configuration problem. |
235 | DINVALIDDATA | Decline. The requested amount exceeds the originally authorized amount. For example, this occurs when you try to capture an amount larger than the original authorization amount. | Issue a new authorization and capture request for the new amount. |
236 | DINVALIDDATA | Decline. Processor failure. | Wait a few minutes and then resend the request. |
237 | DINVALIDDATA | Decline. The authorization was already reversed. | No action required. |
238 | DINVALIDDATA | Decline. The transaction was already settled. | No action required. |
239 | DINVALIDDATA | Decline. The requested transaction amount must match the previous transaction amount. | Correct the amount and resend the request. |
240 | DINVALIDDATA | Decline. The card type sent is invalid or does not correlate with the credit card number. | Confirm that the card type correlates with the credit card number specified in the request, and then resend the request. |
241 | DINVALIDDATA | Decline. The referenced request ID is invalid for all follow-on transactions. | No action required. |
242 | DNOAUTH | Decline. The request ID is invalid.You requested a capture, but there is no corresponding, unused authorization record. This issue occurs if there was not a previously successful authorization request or if the previously successful authorization was already used in another capture request. | Request a new authorization, and if successful, proceed with the capture. |
243 | DINVALIDDATA | Decline. The transaction was already settled or reversed. | Correct and resend the request. |
244 | DINVALIDACCOUNT | Account number did not pass a verification check. | Correct and resend the request. |
246 | DNOTVOIDABLE | Decline. The capture or credit cannot be voided because it was already submitted to your processor. Or, you requested a void for a type of transaction that cannot be voided. | No action required. |
247 | DINVALIDDATA | Decline. You requested a credit for a capture that was voided. | Correct and resend the request. |
248 | DBOLETODECLINED | Decline. The Boleto request was declined by your processor. | Correct and resend the request. |
250 | ETIMEOUT | Error. The request was received, but a timeout occurred at the payment processor. | To avoid duplicating the transaction, do not resend the request until you review the transaction status in the Business Center. |
251 | DCARDREFUSED | Decline. The PINless debit card's use frequency or maximum amount per use was exceeded. | Request a different payment card or other form of payment. |
254 | DINVALIDDATA | Decline. Account is prohibited from processing stand-alone refunds. | Submit a follow-on credit by including a request ID in the credit request. A follow-on credit must be requested within 60 days of the authorization.To process stand-alone credits, contact your account representative to find out if your processor supports stand-alone credits. |
256 | DINVALIDDATA | Credit amount exceeds the maximum allowed for your account. | Contact customer support or your acquirer for details. |
257 | DINVALIDDATA | Gift card account or prepaid card account is already active. | No action required. |
259 | DINVALIDDATA | Reload limit for the gift card or prepaid card was exceeded. | Correct and resend the request. |
260 | DINVALIDDATA | Requested amount conflicts with the minimum or maximum amount allowed on the gift card or prepaid card. | Correct and resend the request. |
261 | DINVALIDDATA | Decline. The merchant account set up is either invalid or missing on the acquirer’s gateway. |
|
262 | DINPROGRESS | Request is still in progress. | Wait for a response from Cybersource. |
263 | DCAPTUREPOSSIBLE | Mass transit transaction (MTT) was declined. | When the transaction amount is less than the transit chargeback threshold, and the other mandated checks are performed, you can capture the authorization. Your acquirer can provide information about mandated checks and transit chargeback thresholds. |
264 | DINVALIDDATA | Processor missing field. |
|
268 | ETIMEOUT | Transaction error. Unable to confirm. Contact Barclays help desk. Do not reprocess. | Contact Barclays to understand the payment status and to determine if the consumer received their funds. Do not reprocess. |
400 | DSCORE | Soft decline. Fraud score exceeds threshold. | You can capture the authorization, but consider reviewing the order for the possibility of fraud. |
403 |
| Communication error. This can be caused by HTTP errors or using incorrect or outdated API keys for validation. | Check the HTTP transmission and API validation keys. |
428 | DAUTHENTICATE | Your request for a strong customer authentication (SCA) exemption was declined. | SCA is required for this transaction. Resubmit using SCA. |
450 | DINVALIDADDRESS | Apartment number missing or not found. | Ask the customer to verify the address information and resend the request. |
451 | DINVALIDADDRESS | Insufficient address information. | Ask the customer to verify the address information and resend the request. |
452 | DINVALIDADDRESS | House/box number not found on street. | Ask the customer to verify the address information and resend the request. |
453 | DINVALIDADDRESS | Multiple address matches were found. | Ask the customer to verify the address information and resend the request. |
454 | DINVALIDADDRESS | P.O. Box identifier not found or out of range. | Ask the customer to verify the address information and resend the request. |
455 | DINVALIDADDRESS | Route service identifier not found or out of range. | Ask the customer to verify the address information and resend the request. |
456 | DINVALIDADDRESS | Street name not found in postal code. | Ask the customer to verify the address information and resend the request. |
457 | DINVALIDADDRESS | Postal code not found in database. | Ask the customer to verify the address information and resend the request. |
458 | DINVALIDADDRESS | Unable to verify or correct address. | Ask the customer to verify the address information and resend the request. |
459 | DINVALIDADDRESS | Multiple address matches were found (international). | Ask the customer to verify the address information and resend the request. |
460 | DINVALIDADDRESS | Address match not found. No reason given. | Ask the customer to verify the address information and resend the request. |
461 | DINVALIDADDRESS | Unsupported character set. | Verify the character set that you are using to process transactions. |
465 | DAUTHENTICATE | Encountered a Payer Authentication problem. Payer could not be authenticated. | Authenticate the cardholder before continuing with the transaction. |
475 | DAUTHENTICATE | The cardholder is enrolled in Payer Authentication. | Authenticate the cardholder before continuing with the transaction. |
476 | DAUTHENTICATIONFAILED | Encountered a Payer Authentication problem. Payer could not be authenticated. | Authenticate the cardholder before continuing with the transaction. |
478 | DAUTHENTICATE | Strong customer authentication (SCA) is required. | Resubmit using SCA. |
480 | DREVIEW | The order is marked for review by Decision Manager. | Depending on your permissions, you can:
|
481 | DREJECT | The order was rejected by Decision Manager. | Depending on your permissions, you can:
|
490 | DAGGDENIED | Your aggregator or acquirer is not accepting transactions from you at this time. | Contact your acquirer or payment technology partner. |
491 | DAGGREJECTED | Your aggregator or acquirer is not accepting this transaction. | Contact your acquirer or payment technology partner. |
520 | DSETTINGS | Soft decline. The authorization request was approved by the issuing bank but was declined based on your Smart Authorization settings. | Do not capture the authorization without further review. Review the ccAuthReply_avsCode, ccAuthReply_cvCode, and ccAuthReply_authFactorCode fields to determine why the request was rejected. |
700 | DRESTRICTED | The customer matched the Denied Parties List. | Reject the customer's order. |
701 | DRESTRICTED | Export bill_country/ship_country match. | Reject the customer's order. |
702 | DRESTRICTED | Export email_country match. | Reject the customer's order. |
703 | DRESTRICTED | Export hostname_country/ip_country match. | Reject the customer's order. |