Reason Codes and Reply Flags

A transaction response contains either a reason code or SCMP reply flag, depending on the
integration method used. The Reason Codes and Reply Flags table shown below lists reason
codes, corresponding reply flags, descriptions of the values, and possible follow-up actions that
you can take.
Reason Codes
A
reason code
is the response from the servers for production transactions that are submitted using these
methods:
 Simple Order API

 Virtual Terminal

 Secure Acceptance
–
Hosted Checkout Integration
 Secure Acceptance
–
Checkout API
 SOAP Toolkit API

 Offline Transaction File Submission

The reason for a code might be determined by systems upstream such as your payment
processor. Further investigation may be required in order to learn the root cause.
Reply Flags
A
reply flag
is the transaction response value for the SCMP integration method that corresponds to a reason
code.

Reason Reply Flag (SCMP) Description Possible Action

Code

100 SOK Successful transaction. No action required.

101 DMISSINGFIELD Declined. The request is See the response fields

missing one or more fields. missingField_0...N
for which fields are
invalid. Resend the request
with the correct
information.

102 DINVALIDDATA Declined. One or more See the response fields

fields in the request invalidField_0...N
contains invalid data. for which fields are
invalid. Resend the request
Reason Reply Flag (SCMP) Description Possible Action
Code

with the correct

information.

104 DDUPLICATE Declined. The merchant Resend the request with a

reference code sent with unique merchant reference
this authorization request code.
matches the merchant
reference code of another
authorization request that
you sent in the past 15
minutes.

105 DDUPLICATE Merchant transaction Resend this request with a

identifier (MTI) sent with unique MTI.
this request has already
been used in the past 60
days.

110 SPARTIALAPPROVAL Partial amount was See "Partial

approved. Authorizations" in Credit
Card Services Using the
Simple Order API

150 ESYSTEM Error. General system You must design your

failure. A system error transaction management
occurred. 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.
Reason Reply Flag (SCMP) Description Possible Action
Code

151 ETIMEOUT Error. The request was To avoid duplicating the

received, but a server transaction, do not resend
timeout occurred. This the request until you
error does not include review the transaction
timeouts between the client status in the Business
and the server. 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 To avoid duplicating the

received but a service did transaction, do not resend
not finish running in time. 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 Contact customer support

enabled for the OCT to have your account
service. enabled for this service.

154 ESYSTEM Bad MAC key. The payout The merchant is safe to
failed due to MAC retry the payout as it was
validation failure. 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,
Reason Reply Flag (SCMP) Description Possible Action
Code

merchants using payouts

should be boarded with
multiple TIDs.

200 DAVSNO Soft decline. The You can capture the

authorization request was authorization, but consider
approved by the issuing reviewing the order for the
bank but was flagged possibility of fraud.
because it did not pass the
Address Verification
Service (AVS) check.

201 DCALL Decline. The issuing bank Call your processor to

has questions about the possibly receive a verbal
request. You do not authorization. For contact
receive an authorization phone numbers, refer to
code programmatically, your merchant bank
but you might receive one information.
verbally by calling the
processor.

202 DCARDEXPIRED Decline. Expired card. You Request a different

might also receive this payment card or other form
code or flag if the of payment.
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.

203 DCARDREFUSED Decline. General decline of Request a different

the card. No other payment card or other form
information provided by of payment.
the issuing bank.
Reason Reply Flag (SCMP) Description Possible Action
Code

204 DCARDREFUSED Decline. Insufficient funds Request a different

in the account. payment card or other form
of payment.

205 DCARDREFUSED Decline. Stolen or lost Refer the transaction to

card. your customer support
center for manual review.

207 DCARDREFUSED Decline. Issuing bank Wait a few minutes and

unavailable. then resend the request.

208 DCARDREFUSED Decline. Inactive card or Request a different

card not authorized for payment card or other form
card-not-present of payment.
transactions.

209 DCARDREFUSED Decline. Card verification Request a different

number (CVN) did not payment card or other form
match. of payment.

210 DCARDREFUSED Decline. The card has Request a different card or

reached the credit limit. other form of payment.

211 DCARDREFUSED Decline. Invalid Card Request a different

Verification Number payment card or other form
(CVN). of payment.

212 DCARDREFUSED EMV transaction was Resubmit the request with

rejected. 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 Request a different

data was invalid (CVV, payment card or other form
expiration date, card of payment.
number, name on card).

220 DCHECKREFUSED Decline. Generic decline. Request a different form of

payment.

221 DCHECKREFUSED Decline. The customer Review the order and

matched an entry in the contact the payment
processor's negative file. processor.
Reason Reply Flag (SCMP) Description Possible Action
Code

222 DCHECKREFUSED Decline. The customer's Review the order or request

account is frozen. a different form of
payment.

230 DCV Soft decline. The You can capture the

authorization request was authorization, but consider
approved by the issuing reviewing the order for the
bank but was flagged possibility of fraud.
because it did not pass the
Card Verification Number
(CVN) check.

231 DINVALIDCARD Decline. Invalid account Request a different

number. payment card or other form
of payment.

232 DINVALIDDATA Decline. The card type is Contact your merchant

not accepted by the bank to confirm that your
payment processor. account is set up to accept
the card type.

233 DINVALIDDATA Decline. General decline Request a different

by the processor. payment card or other form
of payment.

234 DINVALIDDATA Decline. There is a Do not resend the request.

problem with your Contact your customer
merchant configuration. support to correct the
configuration problem.

235 DINVALIDDATA Decline. The requested Issue a new authorization

amount exceeds the and capture request for the
originally authorized new amount.
amount. For example, this
occurs when you try to
capture an amount larger
than the original
authorization amount.

236 DINVALIDDATA Decline. Processor failure. Wait a few minutes and

then resend the request.

237 DINVALIDDATA Decline. The authorization No action required.

was already reversed.

238 DINVALIDDATA Decline. The transaction No action required.

was already settled.
Reason Reply Flag (SCMP) Description Possible Action
Code

239 DINVALIDDATA Decline. The requested Correct the amount and

transaction amount must resend the request.
match the previous
transaction amount.

240 DINVALIDDATA Decline. The card type sent Confirm that the card type
is invalid or does not correlates with the credit
correlate with the credit card number specified in
card number. the request, and then resend
the request.

241 DINVALIDDATA Decline. The referenced No action required.

request ID is invalid for all
follow-on transactions.

242 DNOAUTH Decline. The request ID is Request a new

invalid. authorization, and if
You requested a capture, successful, proceed with
but there is no the capture.
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.

243 DINVALIDDATA Decline. The transaction Correct and resend the

was already settled or request.
reversed.

244 DINVALIDACCOUNT Account number did not Correct and resend the
pass a verification check. request.

246 DNOTVOIDABLE Decline. The capture or No action required.

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.
Reason Reply Flag (SCMP) Description Possible Action
Code

247 DINVALIDDATA Decline. You requested a Correct and resend the

credit for a capture that request.
was voided.

248 DBOLETODECLINED Decline. The Boleto Correct and resend the

request was declined by request.
your processor.

250 ETIMEOUT Error. The request was To avoid duplicating the

received, but a timeout transaction, do not resend
occurred at the payment the request until you
processor. review the transaction
status in the Business
Center.

251 DCARDREFUSED Decline. The PINless debit Request a different

card's use frequency or payment card or other form
maximum amount per use of payment.
was exceeded.

254 DINVALIDDATA Decline. Account is Submit a follow-on credit

prohibited from processing by including a request ID
stand-alone refunds. 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 Contact customer support

maximum allowed for your or your acquirer for details.
account.

257 DINVALIDDATA Gift card account or No action required.

prepaid card account is
already active.

259 DINVALIDDATA Reload limit for the gift Correct and resend the
card or prepaid card was request.
exceeded.

260 DINVALIDDATA Requested amount Correct and resend the

conflicts with the request.
Reason Reply Flag (SCMP) Description Possible Action
Code

minimum or maximum
amount allowed on the gift
card or prepaid card.

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 When the transaction

(MTT) was declined. 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 Contact

to confirm. Contact Barclays
Barclays to understand the payment
help desk. Do not status and to determine if
reprocess. the consumer received their
funds. Do not reprocess.

400 DSCORE Soft decline. Fraud score You can capture the
exceeds threshold. authorization, but consider
reviewing the order for the
possibility of fraud.

403 Communication error. This Check the HTTP

can be caused by HTTP transmission and API
errors or using incorrect or validation keys.
outdated API keys for
validation.
Reason Reply Flag (SCMP) Description Possible Action
Code

428 DAUTHENTICATE Your request for a strong SCA is required for this
customer authentication transaction. Resubmit using
(SCA) exemption was SCA.
declined.

450 DINVALIDADDRESS Apartment number missing Ask the customer to verify

or not found. the address information and
resend the request.

451 DINVALIDADDRESS Insufficient address Ask the customer to verify

information. the address information and
resend the request.

452 DINVALIDADDRESS House/box number not Ask the customer to verify

found on street. the address information and
resend the request.

453 DINVALIDADDRESS Multiple address matches Ask the customer to verify

were found. the address information and
resend the request.

454 DINVALIDADDRESS P.O. Box identifier not Ask the customer to verify
found or out of range. the address information and
resend the request.

455 DINVALIDADDRESS Route service identifier not Ask the customer to verify
found or out of range. the address information and
resend the request.

456 DINVALIDADDRESS Street name not found in Ask the customer to verify
postal code. the address information and
resend the request.

457 DINVALIDADDRESS Postal code not found in Ask the customer to verify
database. the address information and
resend the request.

458 DINVALIDADDRESS Unable to verify or correct Ask the customer to verify

address. the address information and
resend the request.

459 DINVALIDADDRESS Multiple address matches Ask the customer to verify

were found (international). the address information and
resend the request.

460 DINVALIDADDRESS Address match not found. Ask the customer to verify
No reason given. the address information and
resend the request.
Reason Reply Flag (SCMP) Description Possible Action
Code

461 DINVALIDADDRESS Unsupported character set. Verify the character set that
you are using to process
transactions.

465 DAUTHENTICATE Encountered a Payer Authenticate the cardholder

Authentication problem. before continuing with the
Payer could not be transaction.
authenticated.

474 DAUTHENTICATE PIN data is required. Ask the customer to enter

their PIN in the terminal
and resend the request with
PIN data.

475 DAUTHENTICATE The cardholder is enrolled Authenticate the cardholder

in Payer Authentication. before continuing with the
transaction.

476 DAUTHENTICATIONFAIL Encountered a Payer Authenticate the cardholder

ED Authentication problem. before continuing with the
Payer could not be transaction.
authenticated.

478 DAUTHENTICATE Strong customer Resubmit using SCA.

authentication (SCA) is
required.

480 DREVIEW The order is marked for Depending on your

review by permissions, you can:
Decision Manager  Accept, reject, or settle
. the order.
 Void or reverse the
authorization.
 Take no action. If no
action is taken, the
order will be rejected
after 30 days.
Reason Reply Flag (SCMP) Description Possible Action
Code

481 DREJECT The order was rejected by Depending on your

Decision Manager permissions, you can:
.  Convert the order to an
Accepted status.
 If the authorization has
not been sent to the
payment processor for
settlement, it can be
voided.
 If the authorization has
been sent to the
payment processor for
settlement but is not yet
settled, it can be
reversed.
 If the transaction has an
authorization code, it
can be settled.

490 DAGGDENIED Your aggregator or Contact your acquirer or

acquirer is not accepting payment technology
transactions from you at partner.
this time.

491 DAGGREJECTED Your aggregator or Contact your acquirer or

acquirer is not accepting payment technology
this transaction. partner.

520 DSETTINGS Soft decline. The Do not capture the

authorization request was authorization without
approved by the issuing further review. Review the
bank but was declined ccAuthReply_avsCode
based on your Smart ,
Authorization settings. ccAuthReply_cvCode
, and
ccAuthReply_authFactorC
ode
fields to determine why
the request was rejected.

700 DRESTRICTED The customer matched the Reject the customer's order.
Denied Parties List.
Reason Reply Flag (SCMP) Description Possible Action
Code

701 DRESTRICTED Export Reject the customer's order.

bill_country/ship_country
match.

702 DRESTRICTED Export Reject the customer's order.

email_country
match.

703 DRESTRICTED Export Reject the customer's order.

hostname_country/ip_coun
try
match.

Reason Codes and Reply Flags