Payflow Pro (Verisign) Error Codes

CCP610 may return errors for various reasons. For more information, please see Handling Errors from CCP610.

Gateway error descriptions are stored in VeriSignError.xml, which is bundled together with Personify360 application server files. These descriptions can be changed. However, processor error codes are specific to the processor and there is no easy way to customize them.

The following Payflow Pro (Verisign) errors are delivered by default. These errors can be modified or additional error codes can be added as necessary to meet your association’s needs.

Error Code

Description

-11

Proxy authorization failed.

12

Declined.

13

Referral. Transaction was declined but could be approved with a verbal authorization from the bank that issued the card. Submit a manual Voice Authorization transaction and enter the verbal authorization code.

19

Original transaction ID not found. The transaction ID you entered for this transaction is not valid.

22

Invalid American Bankers Association (ABA) number.

23

Invalid account number.

24

Invalid expiration date.

50

Insufficient funds available in account.

105

Credit error.

111

Capture error. Either an attempt to settle a transaction that is not an authorization transaction type, or an attempt to settle an authorization transaction that has already been settled.

On the CCP610 report, this error will display, “ Transaction Already Captured - Receipt has not been reversed - No further attempt will be made to process this transaction.” This is considered a “good error” because the receipt was not reverse. This error is letting you know that the receipt was settled, but not through Personify.

When this error is combined with a Processor Reason Code, further investigation is required.

112

Failed Address Verification Service (AVS) check. Address and ZIP code do not match. An authorization may still exist on the cardholder’s account.

113

Merchant sale total will exceed the sales cap with current transaction. Automated Clearing House (ACH) transactions only.

114

Card Security Code (CSC) mismatch. An authorization may still exist on the cardholder’s account.

122

Merchant sale total will exceed the credit cap with current transaction. Automated Clearing House (ACH) transactions only.

125

Declined by Fraud Protection Services Filter.

126

Flagged for review by Fraud Protection Services Filter.

Result code 126 indicates that a transaction triggered a fraud filter. This is not an error, but a notice that the transaction is in a review status. The transaction has been authorized but requires you to review and to manually accept the transaction before it will be allowed to settle. This result occurred due to that fact that all new Payflow accounts include a “test drive” of the Fraud Protection Services at no charge. The filters are on by default, and a suspicious transaction triggered Result code 126. You can modify these settings based on your business needs. Result code 126 is intended to give you an idea of the kind of transaction that is considered suspicious to enable you to evaluate whether you can benefit from using the Fraud Protection Services.

127

Not processed by Fraud Protection Services Filter.

128

Declined by merchant after being flagged for review by Fraud Protection Services Filter.

1041

Buyer Authentication Service - Validate Authentication failed: missing or invalid Payment Authentication Response (PARES).

1043

Buyer Authentication Service - Validate Authentication failed: Cannot find successful Verify Enrollment.

1044

Buyer Authentication Service - Validate Authentication failed: Signature validation failed for Payment Authentication Response (PARES).

1045

Buyer Authentication Service - Validate Authentication failed: Mismatched or invalid amount in Payment Authentication Response (PARES).

1046

Buyer Authentication Service - Validate Authentication failed: Mismatched or invalid acquirer in Payment Authentication Response (PARES).

1048

Buyer Authentication Service - Validate Authentication failed: Mismatched or invalid card number in Payment Authentication Response (PARES).

1052

Buyer Authentication Service - Validate Authentication failed: This Payment Authentication Response (PARES) was already validated for a previous Validate Authentication transaction.

CVV-N

Card Verification Value (CVV) validation failed.

AVS-ZN

Address Verification Service (AVS) zip code validation failed.

AVS-AN

Address Verification Service (AVS) street address validation failed.

AVS-AX

Cardholder's bank does not support Address Verification Service (AVS).

AVS-ZX

Cardholder's bank does not support Address Verification Service (AVS).