Decline Codes

For credit card and debit card declines retail swiped transactions and e-commerce transactions may be treated differently at the processing network level.

Fast Charge will always return a standardized response code for each of your transactions. For e-commerce or card not present transactions there are always 3 decline codes. Fast Charge will return the decline code with whatever description the card holder’s Bank returns.

To determine the reason for a declined transaction the following are the three decline codes for e-commerce transactions:

The first two numbers in the response code tells us where the decline comes from:

07 or 08: This decline is issued from the customer’s Bank

Example: DECLINED:0700240079

Example: DECLINED:0700560029 Declined: Call Processing Network

Note: The decline response may or my not have a reason passed back with the response. If there is no description passed back the customer will have to contact their issuing Bank for the reason they declined it.

11: A decline code that begins with “1” is issued by Fast Charge

Example: DECLINED:1101920001 “Invalid Expiration Date”:

Example: DECLINED:1103280308 “Address Does Not Match”

Note: This transaction has a reason passed back by the issuing Bank as “Invalid Expiration Date”.

30: A decline code that begins with “3” is issued by Fast Charge and is a system failure.

Example: Declined: 308741209 “Call fast Charge Support”

The retail response codes below “DO Not Always” apply to e-commerce transactions so please keep this in mind when determining the reason for a decline. We will try to match the retail response with e-commerce transactions but we have found that these can be inaccurate some of the time!

Retail Terminal Decline Codes:

For retail swiped transactions there are many more decline codes possible. Here is a list of the most common for First Data and TSYS processing networks: