Full List of Approval Codes and Decline Codes

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 declined 05 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 you're dealing with:

Code

Description

Two-digit numeric response codes

A 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.

Two-digit alpha character response codes

A 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.

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?

FB

Declined - Fraud Card Blacklisted

Account blocked by merchant.

FF

Declined - Fraud Engine

FG

Declined - Account blocked by PayJunction for fraud.

GB

Declined - General Bank Error

GF

Declined - General Format Error

GL

Declined - General Login Error

GS

Declined - General System Error

GK

Declined - General System Unknown Error

GU

Declined - General Upstream ErrorThere was a problem connecting to the processing networks. Try again in one minute.

There was a problem connecting to the processing networks. Try again in one minute.

PayJunction has deleted an old, unused or expired payment from the system. Obtain an updated form of payment from your customer.

RC

Declined - 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.

SR

Declined - 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 ran this transaction, please try to void the charge instead.

API Unique Response Codes

The following table provides possible responses for transactions that are submitted via the PayJunction API service. These codes are found in the transaction response in the "response" object along with a corresponding message.

Response

Description

FE

There was a format error with your Trinity Gateway Service (API) request.

NL

Aborted because of a system error, please try again later.

AB

Aborted because of an upstream system error, please try again later.

80

Declined because of an invalid date.

13

Declined because the amount is invalid.

14

Declined because the card number is invalid.

93

Declined because there is a violation (the transaction could not be completed).

96

Declined because of a system error.

N7

Declined because of a CVV2/CVC2 mismatch.

M4

Declined.

N4

Declined because the amount exceeds issuer withdrawal limit.

RE

Address verification failed because Address Verification System is not working.

SE

Address verification failed because Address Verification System is unavailable.

EE

Address verification failed because the ZIP transaction is not a mail or phone order.

GE

Address verification failed because international support is unavailable.

Declined because there is a violation (the transaction could not be completed).

ACH (NACHA) Return Status Codes

Status values starting with the letter R are NACHA-specification rejects 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 two to four business days of payment submission.

Code

Description

Detail

R01

Insufficient funds

Available balance is not sufficient to cover the amount of the debit entry.

R02

Bank account closed

Previously active account has been closed by the customer of RDFI.

R03

No bank account or unable to locate account

Account number does not correspond to the individual identified in the entry or the account number designated is not an open account.

R04

Invalid bank account number

Account number structure is not valid.

R05

Unauthorized debit

Unauthorized debit to consumer account using corporate SEC code.

R06

Returned per ODFI request

ODFI requested the RDFI to return the entry.

R07

Authorization revoked by customer

Receiver has revoked authorization.

R08

Payment stopped

Receiver of a recurring debit has stopped payment of an entry.

R09

Uncollected funds

Collected funds are not sufficient for payment of the debit entry.

R10

Customer advises not authorized

Receiver has advised RDFI that originator is not authorized to debit his bank account.

R11

Check truncation entry return

To be used when returning a check truncation entry.

R12

Branch sold to another RDFI

RDFI unable to post entry destined for a bank account maintained at a branch sold to another financial institution.

R13

RDFI not qualified to participate

Financial institution does not receive commercial ACH entries.

R14

Representative payee deceased or unable to continue in that capacity

The representative payee authorized to accept entries on behalf of a beneficiary is either deceased or unable to continue in that capacity.

R15

Beneficiary or bank account holder

(1) the beneficiary entitled to payments is deceased or (2) the bank account holder other than a representative payee is deceased.

R16

Bank account frozen

Funds in the bank account are unavailable due to action by RDFI or legal order.

R17

File record edit criteria

Fields rejected by RDFI processing (identified in return addenda).

R18

Improper effective entry date

Entries have been presented prior to the first available processing window for the effective date.

R19

Amount field error

Improper formatting of the amount field.

R20

Non-payment bank account

Entry destined for non-payment bank account defined by regulation.

R21

Invalid company ID number

The company ID information not valid (normally CIE entries).

R22

Invalid individual ID number

Individual ID used by receiver is incorrect (CIE entries).

R23

Credit entry refused by receiver

Receiver 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.

R24

Duplicate entry

RDFI has received a duplicate entry.

R25

Addenda error

Improper formatting of the addenda record information.

R26

Mandatory field error

Improper information in one of the mandatory fields.

R27

Trace number error

Original entry trace number is not valid for return entry; or addenda trace numbers do not correspond with entry detail record.

R28

Transit routing number check digit error

Check digit for the transit routing number is incorrect.

R29

Corporate customer advises not authorized

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