PayJunction will return a standardized response code for each of your transactions.

In general, "00" is the only approval code our system will return (the rest are all decline codes).

A "05" decline is the most common and general decline code.

Our approval and decline codes are structured so that you can quickly determine the type of decline code:

CodeDescription
2-digit numeric response codesA "00" approval response -or- a decline response code generated from the credit card processing networks and the customer's issuing credit card bank.  This cannot be overridden without contacting the issuing bank or correcting a problem at the processor level.
2-digit alpha character response codesA decline response code generated by the PayJunction system.  This usually indicates something is configured incorrectly with the merchant's terminal or file. This can also be a PayJunction specific decline.

Approval Codes

ResponseDescription
00Approval
85Approval
(generally not used anymore)

Decline Codes

ResponseDescription
01Declined - Call Issuer
04Declined - Pick Up Card
05Declined - Do Not Honor
See: What is a "05" Do Not Honor decline code?
12Declined - Invalid Transaction
13Declined - Card Amount Invalid
14Declined - Card Number Invalid
15Declined - No Such Issuer
19Declined - Re-Enter
51Declined - Insufficient Funds
54Declined - Card Expired
57Declined - Service Not Allowed
61Declined - Customer Exceeds Withdrawal Limit
62Declined - Restricted SIC Code
63Declined - Restricted
65Declined - Customer Exceeds Activity Limit
78Declined - No Account
97Declined - CVV MisMatch 

PayJunction Specific Decline Codes

ResponseDescription
AADeclined - AVS No Match: Address
AIDeclined - AVS International AVS Not Supported
ANDeclined - AVS Not Supported
AUDeclined - AVS Unavailable
AWDeclined - AVS Not Working
AXDeclined - AVS: No Match: Address and Zip
AYDeclined - AVS: No Match: Address or Zip
AZDeclined - AVS: No Match: Zip
BC

Declined - Card Brand Not Supported
See: What is a "BC" Card Brand Not Supported decline code?
Contact PayJunction to assist in activating this type of card brand on your account.
See: How do I accept American Express?

BD

Declined - Merchant Deactivated
Contact your merchant account provider, ISO, or sales representative.  Your account appears to be turned off.

BT

Declined - Terminal File Configuration Error
Contact PayJunction to resolve a configuration error.

BMDeclined - Merchant File Configuration Error
Contact PayJunction to resolve a configuration error.
CEDeclined - No Match: CVV
Trinity 1.0 Response
CNDeclined - CVV Not Supported
CVDeclined - No Match: CVV
Trinity 2.0 Response
DT

Declined - Duplicate Transaction
The same transaction amount, invoice number, and credit card charge account has been attempted within the last 10 minutes.
This is most likely a mistake, change the invoice number or wait 10 minutes and try again. 
See: What is a "DT" Duplicate Transaction decline code?

FBDeclined - Fraud Card Blacklisted  - Account blocked by merchant.
FFDeclined - Fraud Engine
FGDeclined -  Account blocked by PayJunction for fraud.
GBDeclined - General Bank Error
GFDeclined - General Format Error
GLDeclined - General Login Error
GSDeclined - General System Error
GKDeclined - General System Unknown Error
GUDeclined - General Upstream Error
There was a problem connecting to the processing networks.  Try again in one minute.
LDDeclined - Merchant Daily Limit Exceeded
See: How do I increase my processing limits?
LMDeclined - Merchant Monthly Limit Exceeded
See: How do I increase my processing limits? 
LTDeclined - Merchant Per Transaction Limit Exceed
See: How do I increase my processing limits? 
NRNacha Reject
OLDeclined - Merchant Over Processing Limit
See: How do I increase my processing limits? 
PPDeclined - Purged Payment
PayJunction has deleted an old, unused, or expired payment from the system.
Obtain an updated form of payment from your customer.
RCDeclined - Stop Recurring
The customer has specifically requested that the issuer block your recurring transactions from processing again. 
Obtain an updated form of payment from your customer, or have the customer remove the block.
SRDeclined - Transaction Rejected at Settlement
For an unknown reason, this transaction was deemed unacceptable at settlement time.
In this case, the authorization code has been canceled and funds have not been transferred.
Contact the customer and the customer’s issuer to resolve the issue.
UC

Declined - Refund Cannot Exceed Charge Amount
A refund amount cannot be more than you have charged a customer's card within the last 12 months.
If you just refunded this transaction, please try to Void the original charge instead.
See: What is a "UC" Uncharged Refund decline code? 

QuickLink Unique Response Codes

Icon

The following tables indicate possible responses in our QuickLink API service to submitted transactions. These response codes will be returned by our service via the "dc_response_code" POST field.

ResponseDescription
FEThere was a format error with your Trinity Gateway Service (API) request.
NLAborted because of a system error, please try again later.
ABAborted because of an upstream system error, please try again later.
80Declined because of an invalid date.
13Declined because the amount is invalid.
14Declined because the card number is invalid.
93Declined because there is a violation (the transaction could not be completed).
96Declined because of a system error.
N7Declined because of a CVV2/CVC2 mismatch.
M4Declined.
N4Declined because the amount exceeds issuer withdrawal limit.
REAddress verification failed because address verification system is not working.
SEAddress verification failed because address verification system is unavailable.
EEAddress verification failed because transaction is not a mail or phone order.
GEAddress verification failed because international support is unavailable.
CEDeclined because CVV2/CVC2 code did not match.
FGFraud Engine General
XEAddress verification failed because zip and address did not match.
YEAddress verification failed because zip and address did not match.
OEAddress verification failed because address or zip did not match.
UEAddress verification failed because cardholder address unavailable.
ZEAddress verification failed because zip did not match.
93Declined because there is a violation (the transaction could not be completed).

 

NACHA Return Status Codes

Status values starting with the letter R are NACHA specification reject and return reason codes that indicate that the consumer portion of the payment has been returned (typically a closed bank account, invalid bank account, insufficient funds, or dispute). If a payment is unsuccessful, PayJunction usually gets the return message from the ACH network within 2 to 4 business days of payment submission.

Code DescriptionDetail
R01Insufficient fundsAvailable balance is not sufficient to cover the amount of the debit entry
R02Bank account closedPreviously active amount has been closed by the customer of RDFI
R03No bank account/unable   to locate accountAccount number does not correspond to the individual identified in the entry, or the account number designated is not an open account.
R04Invalid bank account numberAccount number structure is not valid
R05Unauthorized DebitUnauthorized Debit to Consumer Account Using Coprorate SEC Code
R06Returned per ODFI requestODFI requested the RDFI to return the entry
R07Authorization revoked by customerReceiver has revoked authorization

R08Payment stoppedReceiver of a recurring debit has stopped payment of an entry
R09Uncollected fundsCollected funds are not sufficient for payment of the debit entry
R10Customer advises not authorizedReceiver has advised RDFI that originator is not authorized to debit his bank account
R11Check truncation entry returnTo be used when returning a check truncation entry
R12Branch sold to another RDFIRDFI unable to post entry destined for a bank account maintained at a branch sold to another financial institution
R13RDFI not qualified to participateFinancial institution does not receive commercial ACH entries
R14Representative payee deceased or unable to continue in that capacityThe representative payee authorized to accept entries on behalf of a beneficiary is either deceased or unable to continue in that capacity.

R15Beneficiary or bank account holder(Other than representative payee) deceased* - (1) the beneficiary entitled to payments is deceased or (2) the bank account holder other than a representative payee is deceased
R16Bank account frozenFunds in bank account are unavailable due to action by RDFI or legal order
R17File record edit criteriaFields rejected by RDFI processing (identified in return addenda)
R18Improper effective entry dateEntries have been presented prior to the first available processing window for the effective date.
R19Amount field errorImproper formatting of the amount field
R20Non-payment bank accountEntry destined for non-payment bank account defined by reg.
R21Invalid company ID numberThe company ID information not valid (normally CIE entries)
R22Invalid individual ID numberIndividual id used by receiver is incorrect (CIE entries)
R23Credit entry refused by receiverReceiver returned entry because minimum or exact amount not remitted, bank account is subject to litigation, or payment represents an overpayment, originator is not known to receiver or receiver has not authorized this credit entry to this bank account
R24Duplicate entryRDFI has received a duplicate entry
R25Addenda errorImproper formatting of the addenda record information
R26Mandatory field errorImproper information in one of the mandatory fields
R27Trace number errorOriginal entry trace number is not valid for return entry; or addenda trace numbers do not correspond with entry detail record
R28Transit routing number check digit errorCheck digit for the transit routing number is incorrect
R29Corporate customer advises not authorized

RDFI has bee notified by corporate receiver that debit entry of originator is not authorized

Click Here to learn how to resolve this issue.

R30RDFI not participant in check truncation programFinancial institution not participating in automated check safekeeping application

R31Permissible return entry (CCD and CTX only)RDFI has been notified by the ODFI that it agrees to accept a CCD or CTX return entry
R32RDFI non-settlementRDFI is not able to settle the entry
R33Return of XCK entryRDFI determines at its sole discretion to return an XCK entry; an XCK return entry may be initiated by midnight of the sixtieth day following the settlement date if the XCK entry
R34Limited participation RDFIRDFI participation has been limited by a federal or state supervisor
R35Return of improper debit entryACH debit not permitted for use with the CIE standard entry class code (except for reversals)