Gateway Response Codes
The current (at the time of this release) response codes for the supported Gateways are listed below. Please see the individual specifications for each Gateway (available from the Gateway itself) for an updated list of these codes.
3DSI EC-Linx:
ResponseCode | Description |
0 | Transaction succeeded |
1 | The Total Amount must be a numeric value |
2 | The Tax Amount must be a numeric value |
3 | The Freight Amount must be a numeric value |
4 | The Duty Amount must be a numeric value |
5 | The Order Number is a required field |
6 | The Response URL is a required field |
7 | The Transaction Type is a required field |
8 | Unrecognized Transaction Type |
9 | The Debit/Credit indicator is a required field |
10 | Invalid Debit/Credit indicator |
11 | The Original Order Number is a required field |
12 | The Cardholder Name is a required field |
13 | The Expiration Month is a required field |
14 | Invalid Expiration Month |
15 | The Expiration Year is a required field |
16 | Invalid Expiration Year |
17 | Credit Card Number is a required field |
18 | Credit Card Number must contain only numbers |
19 | Credit Card Number is invalid |
20 | The number of line items must be a numeric value |
21 | The Quantity field is not numeric for line item X |
22 | The Amount field is not numeric for line item X |
25 | Authorization Code is required for a Forced Transaction |
30 | Original Order Number does not exist |
31 | The Credit Card Number passed for the credit does not match Credit Card Number of the original transaction |
32 | The credit amount cannot exceed the original transaction amount |
33 | The original order has not been processed by the bank |
34 | The original order is not a debit therefore it cannot be credited |
35 | An unknown error has occurred. Retry your request. |
36 | Order Number does not exist |
37 | The Credit Card number authorized does not match the capture Credit Card Number |
38 | The total amount to capture cannot be more than was authorized |
39 | The order has not been authorized. You must authorize the order before requesting a capture |
40 | The requested credit amount must equal the original transaction amount |
48 | The transaction amount exceeds the bank's limit of {#########.##}. Please split the transaction so that the transaction amount for each transaction is less than this amount. |
49 | DetailLevel must be one of the following values: 1, 2, 3. |
50 | User locked out |
51 | Unable to validate user |
52 | Order Number entered already exists |
53 | Card rejected. Verify it is a card that you accept |
54 | Message returned from bank (reason for decline-not always populated) |
55 | Not a valid user for external processing. (This error usually occurs when using an EC-Zone User Id and Password). |
56 | Merchant is not certified for external processing |
59 | User is temporarily locked out due to too many consecutive password failures. |
60 | Currency must be one of the following values: CAD, USD. |
61 | The Invoice Date must be a valid date value in the form 'YYYYMMDD'. |
70-74 | An error occurred processing the request. Retry your request. |
75 | An error occurred while processing your request. Object 'GetMaxTransLimit' failed. |
76 | The Canadian GST Tax must be a numeric value |
77 | The Canadian PST Tax must be a numeric value |
78 | The Canadian QST Tax must be a numeric value |
79 | The Canadian HST Tax must be a numeric value |
80 | An error occurred while processing your request. Object 'IsValidSENum' failed. |
81 | Valid service establishment number does not exist for credit card. |
-1:-14 | An error occurred processing the request. Retry your request. |
-15 | The Credit Card Number failed account number validation |
-16 | The Expiration Date failed validation |
-17 | The Amount field failed validation |
-18 | The AddressVerifyZip field failed validation |
-19 | The AddressVerifyState field failed validation |
-20 | The ShipToZip field failed validation |
-21 | The SalesTaxAmount1 field failed validation |
-22 | The SalesTaxAmount2 field failed validation |
-23 | The SE Number field failed validation |
-24 | The SE Number was not provided |
-25 | The SE Number was provided but is not used for this card company |
-26 | The CVV2 Indicator field failed validation |
-27 | The CVV2 Value field failed validation |
-28 | The CVV2 Value was not provided |
-29 | The CVV2 Value was provided but is not required |
-30:-99 | An error occurred processing the request. Retry your request. |
5th Dimension Logistics:
ResponseCode | Description |
1 | Approved |
520 | Approved |
A | Approved |
00 | Approved |
100 | Approved |
2 | Declined |
530 | Declined |
540 | Declined |
D | Declined |
05 | Declined |
500 | Declined |
3 | Error |
550 | Error |
X | Error |
ER | Error |
ResponseCode | Description |
A | Approved |
D | Declined |
E | Error |
ResponseCode | Description |
A | Approved |
D | Declined |
E | Error |
ResponseCode | Description |
Authorised | Authorization approved |
Refused | Declined, possibly due to fraud. |
Error | An error occurred. |
[refund-received] | Credit transaction approved. |
[cancel-received] | Void transaction approved. |
[capture-received] | Capture transaction approved. |
ResponseCode | Description |
1 | Approved. |
2 | Declined. |
3 | Error. |
4 | Held for review. (Approved is set to 'True', so transaction is assumed to be successful) |
ResponseCode | Description |
I00001 | The request was processed successfully. |
I00003 | The record has already been deleted. |
E00001 | An unexpected system error occurred while processing this request. |
E00002 | The only supported content-types are text/xml and application/xml. |
E00003 | This is the result of an XML parser error. |
E00004 | The name of the root node of the XML request is the API method being called. It is not valid. |
E00005 | Merchant authentication requires a valid value for transaction key. |
E00006 | Merchant authentication requires a valid value for name. |
E00007 | The name/and or transaction key is invalid. |
E00008 | The payment gateway or user account is not currently active. |
E00009 | The requested API method cannot be executed while the payment gateway account is in Test Mode. |
E00010 | The user does not have permission to call the API. |
E00011 | The user does not have permission to call the API method. |
E00013 | One of the field values is not valid. |
E00014 | One of the required fields was not present. |
E00015 | One of the fields has an invalid length. |
E00016 | The field type is not valid. |
E00019 | The customer tax ID or driver's license information (driver's license number, driver's license state, driver's license DOB) is required for the subscription. |
E00027 | An approval was not returned for the transaction. |
E00029 | Payment information is required when creating a subscription or payment profile. |
E00039 | A duplicate of the customer profile, customer payment profile, or customer address was already submitted. |
E00040 | The profileID, paymentProfileId, or shippingAddressId for this request is not valid for this merchant. |
E00041 | All of the fields were empty or missing. |
E00042 | The maximum number of payment profiles for the customer profile has been reached. |
E00043 | The maximum number of shipping addresses for the customer profile has been reached. |
E00044 | The payment gateway account is not enabled for Customer Information Manager (CIM). |
E00045 | An error exists in the XML namespace. This error is similar to E00003 |
E00051 | If the customer profile ID, payment profile ID, and shipping address ID are included, they must match the original transaction. |
ResponseCode | Description |
1 | Approved. |
3 | Referred. Transaction was declined by the authoriser, but it might receive voice approval. This is also known as a soft decline. |
50 | Declined. Transaction was declined by the authoriser and it is unlikely that it would receive voice approval. This is also known as a hard decline. |
- | Error. There is something wrong with the transaction which prevents it from processing. See ErrorText for more information. |
ResponseCode | Description |
1 | Transaction approved. |
0 | Transaction declined. |
ResponseCode | Description |
0 | Declined |
1 | Approved |
ResponseCode | Description |
0 | Declined |
1 | Approved |
E | Error |
ResponseCode | Description |
1 | Transaction Approved. |
2 | Transaction Declined. |
3 | Error in transaction data or system error. |
ResponseProcessorCode | Description |
100 | Transaction was approved (Approved). |
200 | Transaction was declined by Processor. |
201 | Do Not Honor. |
202 | Insufficient Funds. |
203 | Over Limit. |
204 | Transaction not allowed. |
220 | Incorrect Payment Data. |
221 | No such card issuer. |
222 | No card number on file with Issuer. |
223 | Expired card. |
224 | Invalid expiration date. |
225 | Invalid card security code. |
240 | Call Issuer for further information. |
250 | Pick up card. |
251 | Lost card. |
252 | Stolen card. |
253 | Fraudulent card. |
260 | Declined with further instructions (see response text). |
261 | Declined - Stop all recurring payments. |
262 | Declined - Stop this recurring program. |
263 | Declined - Updated cardholder data available. |
264 | Declined - Retry in a few days. |
300 | Transaction was rejected by gateway. |
400 | Transaction error returned by processor. |
410 | Invalid merchant configuration. |
411 | Merchant account is inactive. |
420 | Communication error. |
421 | Communication error with issuer. |
430 | Duplicate transaction at processor. |
440 | Processor format error. |
441 | Invalid transaction information. |
460 | Processor feature not available. |
461 | Unsupported card type. |
ResponseCode | ResponseText | Description |
0 | APPROVED | Transaction approved. |
1 | (Custom server response) | Declined or error condition. See ResponseText for additional information. |
[Empty] | [Empty] | See ErrorCode and ErrorText for error information. |
ResponseCode | Description |
0 | Approved |
- | Anything other than an approved transaction will return no code. However, the ResponseText property will contain the error message. |
ResponseCode | Description |
-1 | Incorrect Matching Code. |
-5 | TransType not valid. |
-8 | No Authorization to Capture. |
-9 | Capture Error. |
-10 | No Capture To Refund. |
-11 | Refund Error. |
-12 | Duplicated OrderId. |
-13 | Invalid Credit Card Number. |
-14 | Too Many transactions from the same card within 24 hours. |
-15 | Too much money cleared from the same card within 24 hours. |
-16 | Amount cleared exceeds the max ticket price. |
000 | Success From Processor/3DSecure Authentication Successful. |
001 | Missing or wrong MerchantId. |
004 | Wrong or empty SecretCode. |
005 | No Processing Available. |
006 | Access Error!!!. Restricted by Ip-Address. |
007 | Illegal characters in InputField. |
008 | OwnerCountry is not valid. |
009 | TransType are not supported by this Clearing-Gateway. |
010 | Error From Processor/3DSecure Authentication Failed. |
011 | HTTP_GET are not supported. Use HTTP_POST instead. |
012 | OwnerState is not valid. |
015 | The AmountCleared should be at least 100. |
016 | Hello I am Online (PHP). |
017 | Hello I am Online (Perl). |
019 | CashServer is down for Maintainment. |
020 | Required Fields. |
022 | The Character backslash detected in Key. Invalid input. |
023 | Cannot find at Authorize/Capture to process. |
024 | Terminal Unique Id Failure. |
026 | Aquirer UserId is not valid. |
029 | The creditcard expiredate is not valid. |
030 | CurrencyCode is not valid. |
031 | Illegal Currency. |
032 | Illegal Internal Currency. |
033 | Currency Convertion Failed. |
036 | Length of InternalOrderId exceeded. |
041 | CreditCardCVC code is required. |
042 | RefundLimit is exceeded. |
043 | CreditCards from "country" is Blocked. |
048 | The following 3DSecure parameter is missing "parameter". |
050 | 3DSecure is not activated for this account. |
061 | 3D Secure is only supported in the API version 2 or higher. |
062 | 3D Secure not enrolled. |
070 | Invalid state code. |
071 | CardNumber or IP is Blacklistet. |
072 | CurrencyCode was not found. |
073 | Illegal character in "input field". |
074 | Cannot make another recurring transaction before "date". |
ResponseCode | Description |
ACCEPT | Transaction approved. |
REJECT | The request was rejected. Check the ResponseText for the reason why. |
ERROR | There was a system error. |
ResponseCode | Description |
1 | Success - Transaction accepted and logged. |
2 | Socket write error - Communication was interrupted. The argument is e.g. 523/555 (523 bytes written but 555 expected). |
3 | Timeout - A timeout occurred while we were reading the transaction details. |
5 | Edit error - A field was specified twice, you sent us too much or invalid data, a pre-auth lookup failed during a fulfill transaction, the swipe field was incorrectly specified, or you omitted a field. The argument will give a better indication of what exactly went wrong. |
6 | Comms error - Error in communications link; resend. |
7 | Not authorised - Transaction declined. The arguments are as return code 1, except the first argument is the bank's reason for declining it (e.g. REFERRAL, CALL AUTH CENTRE, PICK UP CARD etc.) or the result from a failed fraud check (e.g. FRAUD DECLINED reason code) |
9 | Currency error - The currency you specified does not exist. |
10 | Authentication error - The vTID or password were incorrect. |
12 | Invalid authorisation code - The authcode you supplied was invalid. |
13 | Type field missing - You did not supply a transaction type. |
14 | Database server error - Transaction details could not be committed to our database. |
15 | Invalid type - You specified an invalid transaction type. |
19 | Cannot fulfill transaction - You attempted to fulfill a transaction that either could not be fulfilled (e.g. auth, refund) or already has been. |
20 | Duplicate transaction reference - A successful transaction has already been sent using this vTID and reference number. |
21 | Invalid card type - This terminal does not accept transactions for this type of card (e.g. Diner's Club, American Express if the merchant does not take American Express, Domestic Maestro if multicurrency only). |
22 | Invalid reference - Reference numbers should be 16 digits for fulfill transactions, or between 6 and 30 digits for all others. |
23 | Expiry date invalid - The expiry dates should be specified as MM/YY or MM-YY. |
24 | Card has already expired - The supplied expiry date is in the past. |
25 | Card number invalid - The card number does not pass the standard Luhn checksum test. |
26 | Card number wrong length - The card number does not have the expected number of digits. |
27 | Issue number error - You did not supply an issue number when we expected one, or the issue number you supplied was non-numeric or too long. |
28 | Start date error - The start date was missing or malformed (must be MM/YY). |
29 | Card is not valid yet - The supplied start date is in the future |
30 | Start date after expiry date. |
34 | Invalid amount - The amount is missing, is not fully specified to x.xx format. |
40 | Invalid cheque type - Must be either "business" or "personal". |
41 | Invalid cheque number - Cheque number was missing or was not 6 digits. |
42 | Invalid sort code - The sort code was missing or was not 6 digits. |
44 | Invalid account number - The account number was missing or was not 8 digits. |
51 | Reference in use - A transaction with this reference number is already going through the system. |
53 | No free TIDs available for this vTID - There are matching TIDs available, but they are all in use. |
56 | Card used too recently. |
57 | Invalid velocity_check value - The velocity_check value must be numeric and between 0 and 120. |
59 | This combination of currency, card type and environment is not supported by this vTID. |
60 | Invalid XML - The XML Document is not valid with our Request schema. The reason is detailed in the "information" element of the Response document. |
61 | Configuration error - An error in account configuration caused the transaction to fail. Contact DataCash Technical Support. |
62 | Unsupported protocol - Please use the DataCash XML API. |
63 | Method not supported by acquirer - The transaction type is not supported by the Acquirer. |
104 | APACS30: WRONG TID - Error in bank authorization, where APACS30 Response message refers to different TID to that used in APACS30 Request message; resend. |
105 | APACS30: MSG SEQ NUM ERR - Error in bank authorization, where APACS30 Response message refers to different message number to that used in APACS30 Request message; resend. |
106 | APACS30: WRONG AMOUNT - Error in bank authorization, where APACS30 Response message refers to different amount to that used in APACS30 Request message; resend. |
190 | No capture method specified - Your vTID is capable of dealing with transactions from different environments (e.g. MoTo, e-comm), but you have not specified from which environment this transaction has taken place. |
271 | Cannot query transactions of this kind. |
274 | Cannot locate transaction to query. |
280 | Unknown format of datacash reference - The datacash reference should be a 16 digit number. The first digit (2, 9, 3 or 4) indicates the format used and whether the txn was processed in a live or test environment. |
281 | Datacash reference fails Luhn check - The new format of datacash reference includes a luhn check digit. The number supplied failed to pass the luhn check. |
282 | Mismatch between historic and current site_id - The site_id extracted from the datacash reference does not match the current environment. |
283 | Mismatch between historic and current modes - The mode flag extracted from the datacash reference does not match the current environment. |
425 | ISO8583 - message corrupted - Encoded characters are not supported. |
440 | Payment Gateway Busy - Out of external connections. |
470 | Maestro txns for CNP not supported for clearinghouse - Maestro transactions for Card Holder not present are not supported for the given clearinghouse. |
471 | 3-D Secure Required - This transaction must be a 3dsecure transaction. |
472 | Invalid capturemethod - International Maestro is not permitted in a Mail order / telephone order environment. |
473 | Invalid transaction type - Keyed International Maestro transaction not permitted. |
480 | Invalid value for merchantid - The Merchant Id provided is invalid . |
481 | Element merchantid required - The merchant is expected to provide a Merchant Id with each transaction. |
482 | Invalid element merchantid - The merchant is not set to provide Merchant Id for a transaction. |
510 | GE Capital: Inappropriate GE Capital card number - The merchant attempted to use a GE Capital card with a BIN that does not belong to them. |
1100 | No referenced transaction found. |
1101 | Only referred transactions can be authorised. |
1102 | Only pre or auth transaction can be authorised. |
1103 | Must supply updated authcode to authorise transaction. |
1104 | Transactions cannot be authorized after time limit expired - The default timeout value is set to 6hours but can be amended per Vtid by contacting DataCash Support. |
1105 | Fraud challenged transactions cannot be authorized. |
1106 | Historic reference already in use |
12001 | vtidconfiguration - There are more than one active passwords already registered against your vTID at the time the txn was received. |
12002 | vtidconfiguration - The IP address of the system submitting the vtidconfiguration request is not registered against your vTID. |
eProcessing:
ResponseCode | Description |
0 | Approved. |
1 | Declined. |
2 | Error. |
ResponseCode | Description |
True | Transaction authorized. |
Anything else | Transaction declined. |
ExPay Response Codes for the ExPayGetMethods call:
ResponseCode | Description |
200 | The request has been successfully processed |
401 | Invalid request hash |
402 | Invalid Payee ID key |
404 | Mandatory attribute is missing |
405 | Invalid format of the attribute |
500 | Internal server error |
ExPay Response Codes for the AuthOnly method:
ResponseCode | Description |
204 | Payment is rejected |
206 | Waiting for payment by the payer |
401 | Invalid request's hash |
402 | Invalid Payee ID Key |
404 | Required attribute is missing |
405 | Invalid format of the attribute |
406 | The amount of payment is less than the minimum possible at a selected payment method |
407 | The amount of payment larger than the maximum possible in a selected payment method |
413 | The amount of payment is less than commission |
479 | This payment ID already exists in the system |
483 | This payment method is not available |
500 | Internal server error |
545 | This merchant is blocked, contact support |
583 | The payment system provides payment method is blocked |
999 | Unknown status, contact support |
ExPay Response Codes for the ExPayGetStatus call:
ResponseCode | Description |
201 | Payment is in the processing queue |
203 | Payment in the processing |
204 | Payment is rejected |
205 | Payment has been successfully completed |
206 | Waiting for payment by the payer |
207 | Payment is returned |
401 | Invalid hash of request |
402 | Invalid Payee ID Key |
404 | Mandatory attribute is missing |
405 | Invalid attribute format |
474 | Payment with the specified parameters is not found |
500 | Internal server error |
999 | Unknown status, contact support |
Fast Transact/Net Billing:
ResponseCode | Description |
I (letter I) = Incomplete | These are transactions that are successful, but may fail at a later date, ie: An ACH transaction is approved, but then is later denied due to NSF. |
1 (number 1) = Approved, Good | This is a transaction that is approved and charged. |
R = Refunded | This transaction has been refunded. It is extremely unlikely you will ever see this return code in this context, although you may see it when browsing old transactions in the NetBilling database (via the Admin tools). |
T = Ticket | This is returned when an Authorize-Only or AVS-Only transaction is good. |
F or 0 = Failure | The number zero "0" or the letter "F" indicates that the transaction failed. A more detailed message will be available in the ResponseText property. |
Other Code | Any other non-zero, non-null codes should be interpreted as success for compatibility with future response codes. |
ResponseCode | Description |
1 | Approved |
2 | Declined |
3 | Error |
ResponseCode | Description |
00 | Transaction Normal |
08 | CVV2/CID/CVC2 Data not verified |
10 | Invalid Transaction Description |
11 | Invalid Sequence No |
12 | Message Timed-out at Host |
14 | Invalid Gateway Id |
15 | Invalid Transaction Number |
16 | Connection Inactive |
17 | Unmatched Transaction |
18 | Invalid Reversal Response |
19 | Unable to Send Socket Transaction |
20 | Unable to Write Transaction to File |
21 | BCE Function Error |
22 | Invalid Credit Card Number |
23 | Invalid Response from First Data |
24 | Unable to Void Transaction |
25 | Invalid Expiry Date |
26 | Invalid Amount |
27 | Invalid Card Holder |
28 | Invalid Authorization No |
30 | Invalid Date From Host |
31 | Invalid Verification String |
32 | Invalid Transaction Code |
40 | Unable to Connect |
41 | Unable to Send Logon |
42 | Unable to Send Trans |
43 | Invalid Logon |
44 | Address not Verified |
52 | Terminal not Activated |
53 | Terminal/Gateway Mismatch |
54 | Invalid Processing Center |
55 | No Processors Available |
56 | Database Unavailable |
57 | Invalid Reference No |
58 | Invalid AVS String, The length of the AVS String has exceeded the max. 40 characters |
60 | Invalid Customer Reference Number |
61 | Socket Error |
62 | Host not Ready |
63 | Invalid Duplicate |
64 | Invalid Refund |
68 | Restricted Card Number |
70 | Transaction Placed in Queue |
72 | Data within the transaction is incorrect |
73 | Transaction Received from Bank |
76 | Reversal Pending |
77 | Reversal Complete |
79 | Reversal Sent to Bank |
93 | Invalid authorization number entered on a pre-auth completion |
F1 | Address check failed - Fraud suspected |
F2 | Card/Check Number check failed - Fraud suspected |
F3 | Country Check Failed - Fraud Suspected |
F4 | Customer Reference Check Failed - Fraud Suspected |
F5 | Email Address check failed - Fraud suspected |
F6 | IP Address check failed - Fraud suspected |
ResponseCode | Description |
Unknown | |
Success | Request was received and successfully processed. Returned on API calls which don't involve executing a payment or payment cancellation. |
Payment_Success | Specific to Make a Payment. Indicates the payment was accepted and successfully issued for authorization. |
Cancel_Success | Specific to Cancel Payment. Indicates the request to cancel a payment was received and successfully issued to the processor. |
Error | Indicates an error occurred in processing your request. Any number of problems could produce an error condition. ResponseText will contain the further error details. |
Declined | Indicates that a payment authorization has been denied by the processor. ResponseText may contain further details. |
Verification_failed | Indicates that the consumer identity information did not match the processors records. |
Communication_Error | Indicates that the PayPoint system is experiencing issues communicating with in its internal systems. |
Settled | Indicates that the transaction was issued for Settlement and was successfully accepted. |
Settlement_Error | Indicates that when the payment action was issued for settlement an error occurred. If a payment action receives a Settlement Error you should contact PayPoint Support personnel for additional details. |
Network_Error | Indicates that the PayPoint system is experiencing issues communicating with third party processing. |
Processor_Mismatch | There is a processor mismatch in the internal systems. |
CreditCards_Disabled | Indicates that the application you are attempting to issue a credit card payment action against is currently not enabled for Credit Cards. If you wish to start accepting credit cards contact PayPoint Support personnel. |
Unaccepted_Card_Type | Indicates the Make A Payment request was rejected because the card type used is not valid for this application. PayPoint enables only cards being accepted by your Payment Processor. |
Payment_Exceeds_System_Limit | PayPoint has the ability to set a daily limit on payments received and processed for a given account. This limit is determined at the time you fill out your PayPoint application. The default setting is unlimited. Unless you explicitly request a limitation on your PayPoint application you will never see this return code. |
Payment_Exceeds_Card_Limit | PayPoint has the ability to set a single payment limit on payments received and processed for a given card. This limit is determined at the time you fill out your PayPoint application. The default setting is unlimited. Unless you explicitly request a limitation on your PayPoint application you will never see this return code. |
Possible_Duplicate_Payment | PayPoint has the ability to track duplicate payments received and can reject them as a part of the Make A Payment request. This feature is determined at the time you fill out your PayPoint Application. The default setting is set to not check for duplicates. Unless you explicitly request a duplicate payment check option on your PayPoint application you will never see this return code. |
Unresolved_Cancellation | A cancellation was not resolved on the internal systems. |
Undefined_Item | Prior to processing a request within PayPoint the data you send is run through a data validation process. This process checks to ensure that your request conforms to the specification. For example that you have provide all required data elements in your request, or that you are passing proper data types (i.e. not passing characters in numeric values). If your request fails this validation process PayPoint will reject your request with this return code. The Result Message will provide more specific details on what data failed validation. |
Chargeback | Indicates that the payment was successfully charged back. |
Chargeback_Reversal | Indicates that a charge back request was successfully reversed. |
Settlement_Incomplete | Catch all error for technical problems encountered during settlement processing. You should never see this result code. If this error is ever seen contact PayPoint Support personnel. |
Partial_Settlement | Anytime there are multiple payments actions under a single transaction where one payment is settled but the other has not you will see a Partial_Settlement Result Code. For example if you have a primary payment and a convenience fee payment under the same transaction and only the primary payment has been issued for settlement. Another possible example is a E-Check payment which is refunded, the original payment would be settled but the refund may not have settled yet. |
Settlement_Pending | This result code is specific to E-Check payments which have a longer settlement process than Credit Cards. This result code means a payment has been sent off for settlement, but we have not received back confirmation of the settlement result. Settlement results within ACH are typically updated as a result of no negative activity within the first 6 days from the settlement issuance. |
eChecks_Disabled | Indicates that the application you are attempting to issue a E-Check payment action against is currently not enabled for E-Checks. If you wish to start accepting E-Checks contact PayPoint Support personnel. |
Missing_Identification | The result code is specific to E-Checks. PayPoint provides fraud detection services. PayPoint provides the ability to enable identity verification services for an additional cost. These services are offered to allow clients to be NACHA compliant with consumer identity requirements. If enabled this result code indicates that the payment is being rejected because you did not provide the required identity data such as Driver's License Number or SSN. |
Waiting_On_PreNote | This result code is specific to E-Checks. PayPoint supports the ability to require the issuance of Pre-Notes for registered accounts. If your application is enabled to require Pre-Notes it may also be set to require a successful pre-note before accepting payments. You will receive this result code for any payments received prior to completion of the pre-note process for a given registered account. |
PreNote_Failed | This result code is specific to E-Checks. PayPoint supports the ability to require the issuance of Pre-Notes for registered accounts. If your application is enabled to require Pre-Notes it may also be set to require a successful pre-note before accepting payments. Indicates that the Pre-Note request for a registered account has failed. No Payments can be applied against the registered account until the account information is updated and a new pre-note is issued by PayPoint. You will receive this result code for any payments received prior to correcting the registration information and successful issuance of the pre-note. |
Stop_Payment_Issued | This result code is specific to E-Checks. Consumers have the right to issue a stop payment up to 60 days after making an original payment. This result code indicates that we received a stop payment request through the ACH network and have reversed the original payment transaction within PayPoint and a reversal has been issued against the merchants account. |
Non_Sufficient_Funds | This result code is specific to E-Checks. This indicates that a E-Check which was issued for settlement resulted in a Non-Sufficient Funds return. Depending on your configuration the payment will be re-presented through the ACH network up to 2 additional times. If you see this message it indicates 1 of 2 possible attempts. If after re-presentment the payment still results in Non-Sufficient funds in the consumers account a Final_Non_Sufficient_Funds result code is returned. |
Final_Non_Sufficient_Funds | This result code is specific to E-Checks. This indicates that the consumers account has insufficient funds to process the original payment request. As a result PayPoint will reverse the transaction. In addition a reversal of the original payment request will be issued against the merchants account. |
Account_Invalid | This result code is specific to E-Checks. When a E-Check payment request is received PayPoint will perform a basic check of the account and routing numbers provided against known data sources such as Thomson account files to ensure the account number is valid. However after a payment is issued for settlement there can be other conditions that result in invalidating the use of the account number. One example is consumers who may have debit blocks on their accounts which would result in a denial by the consumers back to allow the debit to take place. If an Invalid account result is received PayPoint will reverse the transaction within PayPoint. In addition a reversal of the original payment request will be issued against the merchants account. |
Payment_Pending | Indicates that the original Payment was issued with a postdated payment. PayPoint only support postdated transactions for E-Check payments. Once the payment date is reached the payment request will be sent through the normal payment authorization and settlement processing. |
Post_Date_Too_Large | This result code is specific to E-Checks. This result indicates that at the time the Make A Payment request sent the payment was posted dated beyond the acceptable limits. PayPoint can support postdated payments up to 365 days. The default value is to not accept postdated payments. When you fill out your PayPoint Application form you must identify the number of days your application will accept posted dated payments. |
Refund_Settlement_Pending | E-Check Only result code. This result code indicates that a E-Check Payment which is currently in Settlement_Pending status was refunded. (i.e. before the original payment fully settled through ACH). The refund stays in a Refund_Settlement_Pending status until the original payment fully settles and the refund can be settled against the original payment. |
Pre_Auth_Success | This result code is specific to Credit Card payments and is only seen when PayPoint is responsible for doing account verifications when new registrations are created. Account Verification is a feature that can be enabled on your PayPoint account to make a verification request of the account data associated with the registration data being created or updated. To verify a credit card a Pre-Authorization for $1.00 is made to verify account is valid. |
Eligible | Result code is specific to PINless debit cards. The result is returned as a result of a call to the PinlessDebitCheck API call. This result code indicates that the card is eligible to be processed through the PINless debit network. |
Not_Eligible | Result code is specific to PINless debit cards. The result is returned as a result of a call to the PinlessDebitCheck API call. This result code indicates that the card is NOT eligible to be processed through the PINless debit network. |
PINLessDebit_Disabled | Result code is specific to PINless debit cards. This result is returned when your PayPoint account is not enabled to process PINless debit transactions. |
PINDebit_Disabled | Result is specific to PIN based debit cards. This result is returned when your PayPoint account is not enabled to process PIN debit transactions. |
ResponseCode | Description |
00 | Successful |
101 | Declined by Issuing Bank |
102 | Referral by Issuing Bank (treat as decline in automated system such as internet) |
103 | Card reported Lost or Stolen |
106 | AUTH FAILED CONTACT AUTH CENTRE |
107 | FAILS REALSCORE FRAUD CHECKS |
108 | USING TEST SYSTEM. PLEASE USE PREAPPROVED TEST CARDS ONLY |
109 | COMMS ERROR SCHEDULED Issuing BANK MAINTENANCE |
200 | UNSPECIFIED BANK ERROR |
202 | NETWORK ERROR: CANNOT CONNECT TO EpoS. |
205 | Comms error Bank connection error. |
301 | Cannot connect to Database. |
302 | Configuration error with your bank details acquiring bank). Please contact Global Iris. |
303 | Error in configuration, merchant has more than one config for this currency/card combination. |
304 | Can't find transaction details in database. |
305 | HSBC Merchant Services are currently updating the system. We apologise for the inconvenience. |
501 | This transaction has already been processed. |
502 | Compulsory field not present, cannot continue. |
503 | Request type not allowed for this merchant. |
504 | There is no merchant id. Please contact Global Iris Support Team if you continue to experience this problem. |
505 | Sha1hash incorrect. |
506 | Bad XML formation. |
507 | Currency/Card combination not allowed. |
508 | Invalid request data. |
509 | Invalid credit card data. |
510 | That amount is greater than the max allowed. |
511 | Unable to connect to the merchant response URL. |
512 | Original transaction not found. |
513 | Can't void a settled transaction. |
514 | Can't settle the transaction. |
600 | "INTERNAL PROBLEM" Application has identified an issue with a resource dependency and cannot process the request. |
601 | "INVALID REQUEST" Request Format does not conform and cannot be parsed. |
603 | "INTERNAL EXCEPTION" Application has encountered an unknown error and cannot process the request. |
666 | This account has been deactivated. Please contact Global Iris Support Team for further details. |
ResponseCode | Description |
00 | Transaction was Approved |
01 | Error - invalid request. |
02 | Error - invalid credentials. |
03 | Error - internal GPG Error. |
05 | Merchant processing network error - timeout. |
20 | Declined - Exceeds Maximum Ticket. |
21 | Declined - CVV No Match. |
22 | Declined - AVS No Match. |
23 | Declined - Fraud Prevention. |
24 | Declined - Test Card. |
25 | Declined - Transaction Not Allowed. |
26 | Declined - Prepaid Card Not Allowed. |
27 | Declined - Transaction Not Allowed. |
28 | Declined - Transaction Not Allowed. |
200 | Transaction was declined by processor. |
201 | Do not honor. |
202 | Insufficient Funds. |
203 | Over Limit. |
204 | Transaction not allowed. |
220 | Incorrect payment data. |
221 | No such card issuer. |
222 | No card number on file with issuer. |
223 | Expired card. |
224 | Invalid expired date. |
225 | Invalid card security code. |
240 | Call issuer for further information. |
250 | Pick-up card. |
251 | Lost card. |
252 | Stolen card. |
253 | Fraudulent card. |
260 | Declined with further information available. |
261 | Declined - stop all recurring payment. |
262 | Declined - stop this recurring program. |
263 | Declined - update cardholder data available. |
264 | Declined - retry in few days. |
300 | Transaction was rejected by gateway. |
400 | Transaction error returned by processor. |
410 | Invalid merchant configuration. |
411 | Merchant account is inactive. |
420 | Communication error. |
421 | Communication error with issuer. |
430 | Duplicate transaction at processor. |
440 | Processor format error. |
441 | Invalid transaction information. |
460 | Processor feature not available. |
461 | Unsupported card type. |
ResponseCode | Description |
0 | Error |
1 | Transaction successful |
2 | Transaction declined |
ResponseCode | Description |
0 | Normal Termination |
20978 | A required transaction field is invalid/missing |
20979 | A required transaction field is missing |
20988 | Merchant is not approved for service |
20989 | Both Card and Check services are turned off |
20995 | Invalid transaction type |
20996 | Missing transaction type |
20997 | Invalid server (potential security violation) |
20998 | Could not validate Merchant Id |
20999 | Missing or invalid Merchant Id |
30998 | Internal software error |
ResponseCode | Description |
-2 | Invalid license |
-3 | Inactive license |
-4 | Expired license |
-5 | Invalid site |
-6 | Inactive site |
-7 | Expired site |
-8 | Invalid device |
-9 | Inactive device |
-10 | Expired device |
-11 | Invalid user |
-12 | Invalid user password |
-13 | Inactive user |
-14 | Expired user |
-15 | Invalid service |
-16 | Inactive service |
-17 | Expired service |
-18 | Invalid device service |
-19 | Inactive device service |
-20 | Expired device service |
-21 | Unauthorized |
0 | OK |
1 | Gateway system error |
2 | Duplicate transactions |
3 | Invalid original transaction |
4 | Transaction already associated with batch |
5 | No current batch |
6 | Transaction not associated with batch |
7 | Invalid report parameters |
8 | Bad track data |
9 | No transaction associated with batch |
10 | Empty report |
11 | Original transaction not CPC |
12 | Invalid CPC data |
13 | Invalid edit data |
14 | Invalid card number |
15 | Batch close in progress |
16 | Invalid Ship Date. |
17 | Invalid encryption version. |
18 | E3 MSR Failure. |
19 | Invalid Reversal Amount. |
20 | Database operation time out. |
23 | An error was returned from the tokenization service when looking up a supplied token. |
24 | A token was supplied in the request but tokenization is not yet supported for the requested service type. |
25 | A token value was both supplied and requested. |
30 | POS Gateway did not receive a response from the back end systems. POS Gateway is not sure if the transaction was successful or not. |
32 | Missing KTB error. |
33 | Missing KSN error. |
ResponseCode | Description |
A | Approved. |
D | Declined. Transaction was declined by the authoriser and it is unlikely that it would receive voice approval. This is also known as a hard decline. |
R | Referred. Transaction was declined by the authoriser, but it might receive voice approval. This is also known as a soft decline. |
E | Error. There is something wrong with the transaction which prevents it from processing. |
ResponseCode | Description |
0 | Transaction Approved |
* | All other codes should be considered as declined. |
ResponseCode | Description |
A | Approved. The purchase has been authorized by the issuer. |
S | Same. The DTS has detected a possible duplicate transaction. You can treat this as a decline, or you can send the transaction again after adding the following special field with the AddSpecialField method: AddSpecialField("DUPEOK", "Y");. |
D | Declined. The authorizer has declined the purchase request. |
X | Expired. The card has expired. |
E | Error. A data entry error of some kind has occurred. |
U | Unknown. An unknown processor or issuer error has occurred. |
F | Failure. A system failure of some kind has occurred. |
ResponseCode | Description |
G | Approved |
D | Declined |
C | Cancelled |
T | Timeout waiting for host response |
R | Received |
ResponseCode | Description |
0 | Approved. |
1 | Declined or error condition. |
ResponseCode | Description |
000 | Approved |
001 | Refer to card issuer. |
002 | Refer to card issuer, special condition. |
003 | Pick up card. |
005 | Do not honor. |
006 | Error. |
007 | Pickup card, special condition. |
014 | Invalid account number (no such number). |
015 | No such issuer. |
025 | Record cannot be found. |
041 | Pick up card (lost card). |
043 | Pick up card (stolen card). |
051 | Insufficient funds. |
052 | No checking account. |
054 | Expired Card. |
057 | Transaction not permitted to cardholder. |
062 | Restricted card. |
100 | Do not honor. |
103 | Invalid manual Entry 4DBC. |
104 | New card issued. |
105 | Account Canceled. |
107 | Please Call Issuer. |
109 | Invalid merchant. |
110 | Invalid amount. |
111 | Invalid account. |
115 | Service not permitted. |
122 | Invalid card (CID) security code. |
125 | Invalid effective date. |
181 | Format error. |
182 | Please wait. |
183 | Invalid currency code. |
188 | Expiration date required. |
189 | Canceled or Closed Merchant/SE. |
200 | Pick up card. |
400 | Reversal accepted. |
913 | Merchants who do not accept certain credit card types. |
917 | Expired card. |
981 | Merchant accounts that are configured to reject transactions based on AVS results. |
992 | Decline/Timeout. |
900 | XML syntax error. |
ResponseCode | Description |
APPROVED | The transaction was approved. |
DECLINED | the transaction was declined. |
FRAUD | Fraudulent transaction detected. |
ResponseCode | Description |
000 | Approved |
010 | Partially Approved |
100 | Processing Network Unavailable |
101 | Issuer Unavailable |
102 | Re-submit Transaction |
110 | Insufficient Funds |
111 | Authorization amount has already been depleted |
120 | Call Issuer |
121 | Call AMEX |
122 | Call Diners Club |
123 | Call Discover |
124 | Call JBS |
125 | Call Visa/MasterCard |
126 | Call Issuer - Update Cardholder Data |
127 | Exceeds Approval Amount Limit |
130 | Call Indicated Number |
140 | Update Cardholder Data |
191 | The merchant is not registered in the update program. |
301 | Invalid Account Number |
302 | Account Number Does Not Match Payment Type |
303 | Pick Up Card |
304 | Lost/Stolen Card |
305 | Expired Card |
306 | Authorization has expired; no need to reverse |
307 | Restricted Card |
308 | Restricted Card - Chargeback |
310 | Invalid track data |
311 | Deposit is already referenced by a chargeback |
320 | Invalid Expiration Date |
321 | Invalid Merchant |
322 | Invalid Transaction |
323 | No such issuer |
324 | Invalid Pin |
325 | Transaction not allowed at terminal |
326 | Exceeds number of PIN entries |
327 | Cardholder transaction not permitted |
328 | Cardholder requested that recurring or installment payment be stopped |
330 | Invalid Payment Type |
335 | This method of payment does not support authorization reversals |
340 | Invalid Amount |
346 | Invalid billing descriptor prefix |
349 | Do Not Honor |
350 | Generic Decline |
351 | Decline - Request Positive ID |
352 | Decline CVV2/CID Fail |
353 | Merchant requested decline due to AVS result |
354 | 3-D Secure transaction not supported by merchant |
355 | Failed velocity check |
356 | Invalid purchase level III, the transaction contained bad or missing data |
360 | No transaction found with specified litleTxnId |
361 | Authorization no longer available |
362 | Transaction Not Voided - Already Settled |
363 | Auto-void on refund |
365 | Total credit amount exceeds capture amount |
370 | Internal System Error - Call Litle |
400 | No Email Notification was sent for the transaction |
401 | Invalid Email Address |
500 | The account number was changed |
501 | The account was closed |
502 | The expiration date was changed |
503 | The issuing bank does not participate in the update program |
504 | Contact the cardholder for updated information |
505 | No match found |
506 | No changes found |
601 | Soft Decline - Primary Funding Source Failed |
602 | Soft Decline - Buyer has alternate funding source |
610 | Hard Decline - Invalid Billing Agreement Id |
611 | Hard Decline - Primary Funding Source Failed |
612 | Hard Decline - Issue with Paypal Account |
701 | Under 18 years old |
702 | Bill to outside USA |
703 | Bill to address is not equal to ship to address |
704 | Declined, foreign currency, must be USD |
705 | On negative file |
706 | Blocked agreement |
707 | Insufficient buying power |
708 | Invalid Data |
709 | Invalid Data - data elements missing |
710 | Invalid Data - data format error |
711 | Invalid Data - Invalid T&C version |
712 | Duplicate transaction |
713 | Verify billing address |
714 | Inactive Account |
716 | Invalid Auth |
717 | Authorization already exists for the order |
ResponseCode | Description |
0 | Approved |
1 | Declined |
ResponseCode | Description |
000 | Transaction Approved. |
085 | No reason to decline (Response to an AVS Only transaction) |
0xx | Transaction declined. xx = decline reason code. |
101 | Invalid Profile ID or Profile Key. |
102 | Incomplete Request. |
103 | Invoice Number Length Error. |
104 | Reference Number Length Error. |
105 | AVS Address Length Error. |
106 | AVS Zip Length Error. |
107 | Merchant Name Length Error. |
108 | Merchant City Length Error. |
109 | Merchant State Length Error. |
110 | Merchant Zip Length Error. |
111 | Merchant Category Code Length Error. |
112 | Merchant Phone Length Error. |
113 | Reference Number Must Be Numeric. |
114 | Missing Card Holder Account Data. |
115 | Invalid Card Number. |
116 | Credits Not Allowed. |
117 | Card Type Not Accepted. |
118 | Currency Type Not Accepted. |
119 | Retry ID length error. Must be 16 characters or less |
120 | An invoice number is required for a 3D enrollment check |
121 | MOTO/e-Commerce indicator length error. |
122 | Non-USD offline transaction are not supported |
123 | Client Reference Number length error |
124 | Batch Number Required |
125 | Invalid Batch Number |
201 | Invalid Transaction ID. |
202 | Invalid Transaction Amount. |
203 | Void Failed. |
204 | Transaction Already Settled. |
205 | Transaction Already Voided. |
206 | Transaction Already refunded. |
207 | Refund failed. |
208 | Failed to receive a response from auth host. |
209 | Invalid tax amount. |
210 | AVS result is declined by user. |
211 | CVV2 result is declined by user. |
212 | Refund amount must be between zero and the original amount. |
213 | Only sale transactions can be refunded. |
214 | Only one type of card data allowed per request. |
215 | Invalid Card ID. |
216 | Failed to load card data, retry request. |
217 | Failed to store card data, retry request. |
218 | Card ID parameter cannot be included in this type of transaction. |
219 | Offline transactions requires an authorization code |
220 | Failed to delete card data, retry request |
221 | Invalid Card ID |
222 | Card ID required |
223 | Retry Request ID Lookup Failed |
224 | FX rate ID invalid. |
225 | FX rate has expired. |
226 | FX rate lookup failed, retry request. |
227 | FX rate ID required for foreign currency transactions. |
228 | Base and consumer amounts are inconsistent with the FX rate. |
229 | Failed to find currency code for the requested country code. |
230 | Failed to post transaction the FX service. |
231 | FX amount in base currency is required. |
232 | FX transactions not accepted for this account. |
233 | Request currency code must match FX rate currency code |
234 | Pin debit transactions require track 2 swipe data. |
235 | Invalid pin debit transaction type. |
236 | Non-USD pin debit transactions are not supported. |
237 | Batch Close Failed |
238 | Quit Duplicate Batch |
300 | Failed to capture International transaction. |
301 | Failed to void International transaction. |
302 | Failed to refund International transaction. |
303 | Card Verify not supported. |
304 | Failed to reverse International authorization. |
400 | VBV/MSC Enrollment Check |
401 | VBV/MSC Verification Failed. |
999 | Internal Error. |
ResponseCode | Description |
Declined | Transaction declined. |
Approved | Transaction accepted. |
ResponseCode | Description |
AUTH | Transaction authorized/approved. |
CALL | Call processor for authorization. |
DENY | transaction denied, permanent denial, not likely to succeed on further attempts. |
DUPL | Duplicate transaction. |
PKUP | Confiscate card. |
RETRY | Temporary error, retrying the transaction may yield a different result. Typically these are clerk-initiated retries, not automated. |
SETUP | Setup error. |
TIMEOUT | Transaction not processed in allocated amount of time. |
ResponseCode | Description |
0 | Declined or incomplete. |
1 | Approved. |
ResponseCode | ResponseText | Description |
0 | APPROVED | Transaction approved. |
1 | (Custom server response) | Declined or error condition. See ResponseText for additional information. |
[Empty] | [Empty] | See ErrorCode and ErrorText for error information. |
ResponseCode | Description |
ACCEPTED | The transaction was processed. |
DECLINED | The transaction was declined before it was sent for processing. |
ERROR | The transaction was attempted but failed. |
ResponseCode | Description |
1 | Accepted |
2 | Declined |
3 | Error |
ResponseCode | Description |
0 | Incomplete or invalid |
1 | Cancelled by client |
2 | Authorization refused |
4 | Order stored |
41 | Waiting client payment |
5 | Authorized |
51 | Authorization waiting |
52 | Authorization not known |
55 | Stand-by |
59 | Authoriz. to get manually |
6 | Authorized and cancelled |
61 | Author. deletion waiting |
62 | Author. deletion uncertain |
63 | Author. deletion refused |
64 | Authorized and cancelled |
7 | Payment deleted |
71 | Payment deletion pending |
72 | Payment deletion uncertain |
73 | Payment deletion refused |
74 | Payment deleted |
75 | Deletion processed by merchant |
8 | Refund |
81 | Refund pending |
82 | Refund uncertain |
83 | Refund refused |
84 | Payment declined by the acquirer |
85 | Refund processed by merchant |
9 | Payment requested |
91 | Payment processing |
92 | Payment uncertain |
93 | Payment refused |
94 | Refund declined by the acquirer |
95 | Payment processed by merchant |
99 | Being processed |
ResponseCode | Description |
0 | Decline. |
1 | Approved. |
2 | Message/System error. |
ResponseCode | Description |
0 | Failed Transaction |
1 | Successful Transaction (for Charge and Settle) |
2 | Voided or Refunded Transaction |
5 | Pending Credit for First Data |
7 | Successful Authorization Transaction |
9 | Pending Transaction |
10 | Successful Pending E-Check Transaction |
21 | eCheck NSF |
22 | eCheck NSF |
23 | eCheck Return |
24 | eCheck Return |
ResponseCode | Description |
00 | Approved. |
85 | Approved. |
FE | There was a format error with your Trinity Gateway Service (API) request. |
LE | Could not log you in (problem with dc_logon and/or dc_password). |
AE | Address verification failed because address did not match. |
ZE | Address verification failed because zip did not match. |
XE | Address verification failed because zip and address did not match. |
YE | Address verification failed because zip and address did not match. |
OE | Address verification failed because address or zip did not match.. |
UE | Address verification failed because cardholder address unavailable. |
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 transaction is not a mail or phone order. |
GE | Address verification failed because international support is unavailable. |
CE | Declined because CVV2/CVC2 code did not match. |
NL | Aborted because of a system error, please try again later. |
AB | Aborted because of an upstream system error, please try again later. |
04 | Declined. Pick up card. |
07 | Declined. Pick up card (Special Condition). |
41 | Declined. Pick up card (Lost). |
43 | Declined. Pick up card (Stolen). |
13 | Declined because of the amount is invalid. |
14 | Declined because the card number is invalid. |
80 | Declined because of an invalid date. |
05 | Declined. Do not honor. |
51 | Declined because of insufficient funds. |
N4 | Declined because the amount exceeds issuer withdrawal limit. |
61 | Declined because the amount exceeds withdrawal limit. |
62 | Declined because of an invalid service code (restricted). |
65 | Declined because the card activity limit exceeded. |
93 | Declined because there a violation (the transaction could not be completed). |
06 | Declined because address verification failed. |
54 | Declined because the card has expired. |
15 | Declined because there is no such issuer. |
96 | Declined because of a system error. |
N7 | Declined because of a CVV2/CVC2 mismatch. |
M4 | Declined. |
ResponseCode | Description |
-100 | Transaction NOT Processed; Generic Host Error |
0 | Approved |
1 | User Authentication Failed |
2 | Invalid Transaction |
3 | Invalid Transaction Type |
4 | Invalid Amount |
5 | Invalid Merchant Information |
7 | Field Format Error |
8 | Not a Transaction Server |
9 | Invalid Parameter Stream |
10 | Too Many Line Items |
11 | Client Timeout Waiting for Response |
12 | Decline |
13 | Referral |
14 | Transaction Type Not Supported In This Version |
19 | Original Transaction ID Not Found |
20 | Customer Reference Number Not Found |
22 | Invalid ABA Number |
23 | Invalid Account Number |
24 | Invalid Expiration Date |
25 | Transaction Type Not Supported by Host |
26 | Invalid Reference Number |
27 | Invalid Receipt Information |
28 | Invalid Check Holder Name |
29 | Invalid Check Number |
30 | Check DL Verification Requires DL State |
40 | Transaction did not connect (to NCN because SecureNCIS is not running on the web server) |
50 | Insufficient Funds Available |
99 | General Error |
100 | Invalid Transaction Returned from Host |
101 | Timeout Value too Small or Invalid Time Out Value |
102 | Processor Not Available |
103 | Error Reading Response from Host |
104 | Timeout waiting for Processor Response |
105 | Credit Error |
106 | Host Not Available |
107 | Duplicate Suppression Timeout |
108 | Void Error |
109 | Timeout Waiting for Host Response |
110 | Duplicate Transaction |
111 | Capture Error |
112 | Failed AVS Check |
113 | Cannot Exceed Sales Cap |
1000 | Generic Host Error |
1001 | Invalid Login |
1002 | Insufficient Privilege or Invalid Amount |
1003 | Invalid Login Blocked |
1004 | Invalid Login Deactivated |
1005 | Transaction Type Not Allowed |
1006 | Unsupported Processor |
1007 | Invalid Request Message |
1008 | Invalid Version |
1010 | Payment Type Not Supported |
1011 | Error Starting Transaction |
1012 | Error Finishing Transaction |
1013 | Error Checking Duplicate |
1014 | No Records To Settle (in the current batch) |
1015 | No Records To Process (in the current batch) |
ResponseCode | Description |
0 | Approved |
- | Anything other than an approved transaction will return no code. However, the ResponseText property will contain the error message. |
ResponseCode | Description |
0 | Approved. |
1 | User authentication failed. |
2 | Invalid tender type. Your merchant bank account does not support the following credit card type that was submitted. |
3 | Invalid transaction type. Transaction type is not appropriate for this transaction. For example, you cannot credit an authorization-only transaction. |
4 | Invalid amount format. |
5 | Invalid merchant information. Processor does not recognize your merchant account information. Contact your bank account acquirer to resolve this problem. |
7 | Field format error. Invalid information entered. |
8 | Not a transaction server. |
9 | Too many parameters or invalid stream. |
10 | Too many line items. |
11 | Client timeout waiting for response. |
12 | Declined. Please check the credit card number and transaction information to make sure they were entered correctly. If this does not resolve the problem, have the customer call the credit card issuer to resolve. |
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 auth code. |
19 | Original transaction ID (PNRef) not found. The transaction ID you entered for this transaction is not valid. |
20 | Cannot find the customer reference number. |
22 | Invalid ABA number. |
23 | Invalid account number. Please check credit card number and re-submit. |
24 | Invalid expiration date. Please check and re-submit. |
25 | Transaction type not mapped to this host. |
26 | Invalid vendor account. |
27 | Insufficient partner permissions. |
28 | Insufficient user permissions. |
29 | Invalid XML document. This could be caused by an unrecognized XML tag or a bad XML format that cannot be parsed by the system. |
30 | Duplicate transaction. |
31 | Error in adding the recurring profile. |
32 | Error in modifying the recurring profile. |
33 | Error in canceling the recurring profile. |
34 | Error in forcing the recurring profile. |
35 | Error in reactivating the recurring profile. |
36 | OLTP Transaction failed. |
50 | Insufficient funds available. |
99 | General error. |
100 | Transaction type not supported by host. |
101 | Timeout value too small. |
102 | Processor not available. |
103 | Error reading response from host. |
104 | Timeout waiting for processor response. Try your transaction again. |
105 | Credit Error. Please make sure you have not already credited this transaction, or that this transaction ID is for a creditable transaction (for example, you cannot credit an authorization.) |
106 | Host not available. |
107 | Duplicate suppression timeout. |
108 | Void error. Please make sure the transaction ID entered has not already been voided. If not, then look at the Transaction Detail screen for this transaction to see if it has settled (the Batch field will be set to a number greater than zero if the transaction has been settled.) If the transaction has already settled your only recourse is a reversal (credit a payment or submit a payment for a credit). |
109 | Timeout waiting for host response. |
111 | Capture error. Only authorization transactions can be captured. |
112 | Failed AVS check. Address and zip code do not match. |
113 | Cannot exceed sales cap. For ACH transactions only (not supported.) |
114 | CVV2 Mismatch. An authorization may still exist on the cardholder's account. |
115 | System is busy, try again later. |
116 | VPS Internal error - Failed to lock terminal number. |
117 | Failed merchant rule check. An attempt was made to submit a transaction that failed to meet the security settings specified on the VeriSign Manager Security Settings page. See VeriSign Manager User's Guide. |
118 | Invalid keywords found in string fields. |
1000 | Generic host error. This is a generic message returned by your credit card processor. The message itself will contain more information describing the error. |
ResponseCode | Description |
1 | Approved. |
2 | Referral (General). |
3 | Referral - Call bank for manual approval. |
4 | AVS request accepted. |
50 | Declined (General). |
51 | Connection timed-out. |
52 | Error connecting to processor or sending data. |
53 | Error during Payment Commit phase. |
54 | Timed out waiting for response. |
100 | Transaction failed to settle due to Soft Error. |
101 | Transaction failed to settle due to Hard Error. |
102 | Transaction failed to settle because the transaction is marked as Locked. |
500 | Declined - Transaction considered fraudulent by Fraud component. |
501 | "The transaction was Approved by the processor. However, it failed a postprocessing fraud rule and has been voided." |
502 | "The transaction was Approved by the processor. However, it failed a fraud rule and has been marked for review." |
ResponseCode | Description |
1 | Approved |
0 | Decline or error |
ResponseCode | Description |
1 | Accepted |
2 | Declined |
3 | Error |
ResponseCode | Description |
0 | Approved. |
-1 | The response from the PayTrace API was null. |
30 | Customer ID, xxxxx, was not found or is incomplete. |
35 | Please provide a valid Credit Card Number. |
36 | Customer ID, xxxxxx, does not have a valid billing address. |
37 | Customer ID, xxxxxx, does not have a valid billing ZIP. |
39 | Your PayTrace account is not set up to accept this card type. |
40 | An error occurred during the decryption process. |
43 | Please provide a valid Expiration Month. |
44 | Please provide a valid Expiration Year. |
45 | Please provide a valid Checking Account Number. |
46 | Please provide a valid Transit Routing Number. |
47 | Please provide an Amount that is less than your Sale Ceiling Amount. |
48 | Please provide an Amount that is less than your Refund Ceiling Amount. |
51 | Please provide a valid Amount. |
54 | Cash Advances may only be processed as Sales. |
55 | Cash Advances may only be processed through accounts set up in the TSYS/Vital network. |
56 | Cash Advances may not be processed to stored customers. |
57 | Your PayTrace account is not set up to process Cash Advances. |
58 | Please provide a valid Transaction ID. |
59 | Please provide a valid Check ID. |
61 | The Customer ID that you provided was not found in the PayTrace records. |
62 | Please provide a valid Photo ID. |
63 | Please provide a valid ID Expiration. |
64 | Please provide a valid Last 4 of Card. |
65 | Cash Advances may only be processed on Visa, MasterCard, and Discover cards. |
80 | The Check ID that you provided was not found in the PayTrace records. It may already be voided or settled. |
81 | The Transaction ID that you provided was not found in the PayTrace records. It may be a voided a transaction or an unsettled transaction. |
82 | Please provide a valid Batch Number. |
83 | This is not an approved transaction so it can not be captured. |
84 | This transactions approval code has expired as it was obtained more than 20 days ago. |
85 | The Transaction ID that you provided was not found in the PayTrace records. It may already be captured or settled. |
86 | The Transaction ID that you provided was not found in the PayTrace records. It may already be voided, settled, or an uncaptured authorization. |
87 | The Transaction ID that you provided was not found in the PayTrace records, and the receipt could not be emailed. |
88 | The Transaction ID that you provided was not found in the PayTrace records, and level 3 data could not be added to the Visa transaction. |
89 | The Transaction ID that you provided was not found in the PayTrace records, and level 3 data could not be added to the MasterCard transaction. |
90 | The Transaction ID that you provided was not found in the PayTrace records, and the amount was not updated. |
115 | Please provide a valid Approval Code. |
116 | Please provide a valid Transaction Type. |
117 | Please provide a valid Billing Name. |
118 | Please provide a valid Billing Address. |
119 | Please provide a valid Billing Address 2. |
120 | Please provide a valid City. |
121 | Please provide a valid State. |
122 | Please provide a valid Zip Code. |
124 | Please provide a valid Shipping Name. |
125 | Please provide a valid Shipping Address. |
126 | Please provide a valid Shipping Address 2. |
127 | Please provide a valid Shipping City. |
128 | Please provide a valid Shipping County. |
129 | Please provide a valid Shipping State. |
130 | Please provide a valid Shipping Zip Code. |
131 | Please provide a valid Shipping Country |
132 | Please provide a valid Phone Number. |
133 | Please provide a valid Source State. |
134 | Please provide a valid Source Zip Code. |
135 | Please provide a valid list of Shippers. |
136 | Please provide a valid Weight. |
137 | Please provide a valid Fax Number. |
139 | Please make sure the Shipping State and Shipping Zip are accurate. |
141 | Please provide a valid Email Address. |
148 | Please provide a valid CSC. |
149 | Please provide a valid Invoice Number. |
150 | Please provide a valid Description. |
151 | Please provide a valid Tax Amount. |
152 | Please provide a valid Customer Reference. |
153 | This customer profile does not have an email address to send the receipt. |
160 | Please provide a valid Frequency. |
161 | Please provide a valid Transaction Count. |
162 | Please provide a valid Start Date. |
163 | Please provide a valid Next Date. |
164 | Please provide a valid Repeat value. |
165 | Please provide a valid Recurring Payment ID. |
169 | No recurring payments were found with this criteria. |
170 | No approved transactions were found for this customer. |
171 | Please provide a unique customer ID. |
172 | Please provide a Customer Password that is greater than 6 characters and less than 255 characters. |
175 | Please provide a valid Start Date. |
176 | Please provide a valid End Date. |
177 | Please provide a date range. |
178 | Please provide a valid User. |
180 | No transactions were found with these criteria. |
185 | No customers were found with these criteria. |
190 | Please provide a valid National Tax Amount. |
191 | Please provide a valid Merchant Tax ID. |
192 | Please provide a valid Customer Tax ID. |
193 | Please provide a valid Commodity Code. |
194 | Please provide a valid Discount Amount. |
195 | Please provide a valid Freight Amount. |
196 | Please provide a valid Duty Amount. |
197 | Please provide a valid Additional Tax Amount. |
198 | Please provide a valid Additional Tax Rate. |
199 | Please provide a valid Additional Tax Indicator. |
200 | Please provide a valid Line Item record. |
201 | Please provide a valid Line Item Commodity Code. |
202 | Please provide a valid Line Item Description. |
203 | Please provide a valid Line Item Product ID. |
204 | Please provide a valid Line Item Quantity. |
205 | Please provide a valid Line Item Measure. |
206 | Please provide a valid Line Item Unit Cost. |
207 | Please provide a valid Line Item Additional Tax Amount. |
208 | Please provide a valid Line Item Additional Tax Rate. |
209 | Please provide a valid Line Item Discount. |
210 | Please provide a valid Line Item Amount. |
211 | Please provide a valid Line Item Additional Tax Indicator. |
212 | Please provide a valid Line Item Discount Rate. |
213 | Please provide a valid Line Item Discount Indicator. |
214 | Please provide a valid Line Item Net Gross Indicator. |
215 | Please provide a valid Line Item Debit Credit Indicator. |
230 | Batch was not initiated as no transactions are pending settlment. |
231 | Batch was not initiated as another batch is in progress or pending. |
700 | This transaction was not approved because the authorization network was not available. Please retry this transaction again. |
740 | PayTrace is unable to process this check as the check processor information is incomplete or the network returned an error. |
750 | PayTrace does not support this transaction type for this check processor. |
777 | PayTrace blocked this transaction because it is a duplicate, and it may be reprocessed in ### minute(s). |
867 | Please provide valid new passwords. |
869 | Please provide new passwords that are unique to your previous 4 passwords. |
880 | This customer is schedule for recurring payment #xxxxx and may not be deleted. |
900 | Please indicate that you agree with PayTrace's terms and conditions. |
950 | Unreferenced refunds are not permitted for Optima Payments accounts. |
951 | Forced Sales are not permitted for Optimal Payments accounts. |
952 | Swiped/card present transactions are not permitted for Optimal Payments accounts. |
973 | The processor information for xxxxxx is incomplete. |
974 | Your PayTrace account is not set up to use the PayTrace API. |
975 | Your PayTrace account is not set up to process recurring transactions. |
976 | Your account is only set up to process Cash Advances and Voids. |
978 | Your account is not set up to process checks. |
979 | Password is expired. Please log into virtual terminal to reset password. |
980~986 | Log in failed for insufficient permissions. |
987 | Please provide a valid method or request to process. |
988 | Log in failed. |
989 | Log in failed for insufficient permissions. |
990 | Please provide a properly formatted parameter string. |
991 | Log in failed. |
992 | Please ensure you have exactly one '~' between each of the name and value pairs in the parameter string. |
993 | xxxxxx is not a valid parameter name. |
994 | Please provide a valid user name. |
995 | Please provide a valid password. |
998 | Log in failed. |
999 | Log in failed for insufficient permissions. |
ResponseCode | Description |
0 | There were no errors during the execution of the operation. |
1000 | This code groups all errors related to the parameters sent. |
2000 | Groups all errors related to Payvision. |
3000 | Groups all responses related to declines. |
3100 | Groups all responses related to Referral transactions. |
3200 | Groups all errors related to the acquiring bank. |
4000 | Groups all errors regarding security issues. |
5000 | Groups all unexpected errors. |
6000 | Groups all codes different than 0 given by the business rules applied to the execution of an operation. |
PayWiser:
ResponseCode | Description |
-1 | Invalid caller |
-2 | Invalid parameters |
-3 | Duplicate ReferenceID |
-4 | Error calling bank |
-5 | Unknown card type |
-6 | Wrong format of CardExpDate |
-7 | Invalid CheckReferenceID |
-8 | Invalid PGReferenceID |
-9 | Amount is out of bounds (either 0 or not between min and max) |
-10 | Invalid ReservationReferenceID |
-11 | General processing error |
-12 | Invalid InitPaymentReferenceID |
-13 | Web payment is no longer active |
-14 | Web payment was already processed |
-15 | Invalid PaymentCheckURL response |
-16 | Invalid card region (intra) |
-17 | Invalid card region (inter) |
-18 | Hourly transaction count limit exceeded |
-19 | Daily transaction count limit exceeded |
-20 | Monthly transaction count limit exceeded |
-21 | Hourly transaction sum limit exceeded |
-22 | Daily transaction sum limit exceeded |
-23 | Monthly transaction sum limit exceeded |
-24 | Hourly card transaction count limit exceeded |
-25 | Daily card transaction count limit exceeded |
-26 | Monthly card transaction count limit exceeded |
-27 | Invalid WebFormLanguage |
-28 | Invalid TemplateID |
-29 | Invalid RecurringScheduleID |
-30 | General Moneta error |
-31 | Invalid AgreementID |
-32 | Agreement not confirmed |
-33 | 3DS error - wrong card type |
-34 | 3DS processing error |
-35 | 3DS is not set up for this account |
-36 | 3DS is not allowed for this account |
-37 | 3DS error - parameter ThreeDSecurePaRes or ThreeDSecureReferenceID is required |
-38 | 3DS error - parameter ThreeDSecureData is required |
-39 | 3DS error - ThreeDSecureReferenceID not found or not completed |
-40 | Maestro cards cannot be tokenized. Use /Reserve with card data instead. |
-41 | Merchant requires 3DS, but this card does not support 3DS |
-42 | Maestro cards processing require 3DS enabled account |
-43 | Maestro cards cannot be tokenized. |
-44 | Maestro cards require 3DS. |
-45 | 3DS error - parameter ThreeDSecureReferenceID is required |
-46 | Yearly transaction count limit exceeded |
-47 | Yearly transaction sum limit exceeded |
-48 | Yearly card transaction count limit exceeded |
-49 | Account has been temporarily suspended |
-50 | Card has already been declined by the bank. Unable to process this card for 10 minutes. |
-51 | Recurring payments or installments are not allowed with mandatory 3DS. |
-52 | Down payments, skipping payments or shitfing first payment are not alloweed with mandatory 3DS. |
-53 | Invalid RecurringPlanID |
-54 | Invalid FirstPaymentDate |
-55 | Invalid ExpiryDate |
-56 | PaymentsSkipCount cannot be greater than total number of payments |
-57 | Recurring payments cannot have Amount (use RecurringPayment.PaymentAmount instead) |
-58 | Recurring ExpiryDate must be after FirstPaymentDate |
-59 | Recurring FirstPaymentDate can not be before today |
-60 | Duplicate RecurringReferenceID |
-61 | Recurring payments are now allowed for this account |
-62 | Recurring schedule does not exist |
-63 | Recurring schedule is already terminated |
-64 | Invalid PlanPattern value |
-65 | Invalid RetryPattern value |
-66 | MaxRetryCount must be greater or equal to 0 |
-67 | Either both MaxRetryCount and RetryPattern or none of them must be specified |
-68 | PaymentHour must be between 0 and 23 |
-69 | Card with specified CardToken does not exist |
-70 | Recurring plan can not have InstallmentTotalValue |
-71 | ImmediatePaymentAmount is out of bounds (either 0 or not between min and max) |
-72 | PaymentAmount is out of bounds (either 0 or not between min and max) |
-73 | Card payments are now allowed, specifying AllowCards is not allowed |
-74 | Moneta payments are now allowed, specifying AllowMoneta is not allowed |
-75 | AdjustPlanWithStartDate is not allowed with specified recurring plan pattern |
-76 | RenewYearly is only allowed with installment type (not recurring) and for monthly plans with less than 12 installments only |
-77 | Sepa payments are now allowed for this account |
-78 | Invalid MandateSignatureDate |
-79 | Duplicate MandateID |
-80 | MandateID does not exist |
-81 | MandateID is already revoked |
-82 | Amount is out of bounds (either 0 or not between min and max) |
-83 | Invalid CheckPaymentReferenceID |
-84 | Invalid Sepa Sequence |
-85 | Invalid MandateValidFromDate |
-86 | Sepa collection date can not be before current day |
-87 | Sepa payment date is out of bounds (either to soon or too late) for bank processing, check StartDate |
-88 | Invalid CollectionDate |
-89 | MandateID is allowed only for Sepa payments |
-90 | Sepa mandate is canceled |
-91 | Currency mismatch (different currency than used for Reserve) |
-92 | Invalid Amount (larger than used for Reserve) |
-93 | Sepa mandate has already been used |
-94 | Invalid combination of CardToken, SepaMandateID and MonetaAgreementID - only one can be used |
-95 | Recurring payments require recurring mandate |
-96 | One or more itms in the list has Currency different from the payment Currency |
-97 | Either CardToken, SepaCreditorMandateID or MonetaAgreementID must be specified |
-98 | Sepa first payment date is out of bounds (either to soon or too late) for bank processing |
-99 | Sepa consecutive payment dates are out of bounds (either to soon or too late) for bank processing |
-100 | Sepa consecutive retry dates are out of bounds (either to soon or too late) for bank processing |
-101 | Sepa payments are now allowed, specifying AllowSepa is not allowed |
-102 | MonetaDO settings missing |
-103 | MonetaDO error |
-104 | MonetaDO agreement does not exist |
-105 | MonetaDO agreement is not yet confirmed by the customer |
-106 | MonetaDO agreement is canceled |
-107 | MonetaDO reservation does not exist |
-108 | Only EUR currency is allowed for Moneta payments |
-109 | AgreementID is not allowed for non-recurring payments |
-110 | AgreementID is allowed only for moneta payments |
-111 | MobileNumber does not support Moneta payments |
-113 | General Sepa error |
-114 | Invalid characters |
-115 | Sepa error - access token not available |
-116 | Payouts are not allowed for this account |
-117 | Surcharge+Cashback can not be greater than Amount |
-118 | Invalid Surcharge amount (larger than used for Reserve) |
-119 | Invalid CashBack amount (larger than used for Reserve) |
-120 | Surcharge is allowed only for card payments |
-121 | Surcharge can not be greater than Amount |
0 | Ok |
305 | 3DS is needed |
1000 | Confirmation requested |
1001 | Agreement not active |
20000 | Approved |
40000 | General input error |
40110 | Invalid card number |
40120 | Invalid CSC |
40130 | Invalid expire date |
40135 | Card expired |
40140 | Invalid currency |
40200 | Clearhaus rule violation |
40300 | 3-D Secure problem |
40310 | 3-D Secure authentication failure |
40400 | Backend problem |
40410 | Declined by issuer or card scheme |
40411 | Card restricted |
40412 | Card lost or stolen |
40413 | Insufficient funds |
40414 | Suspected fraud |
40415 | Amount limit exceeded |
50000 | Clearhaus error |
40000 | General input error |
40110 | Invalid card number |
40120 | Invalid CSC |
40130 | Invalid expire date |
40135 | Card expired |
40140 | Invalid currency |
40200 | Clearhaus rule violation |
40300 | 3-D Secure problem |
PhoeniXGate:
ResponseCode | Description |
-100 | Transaction NOT Processed; Generic Host Error. |
0 | Approved. |
1 | User Authentication Failed. |
2 | Invalid Transaction. |
3 | Invalid Transaction Type. |
4 | Invalid Amount. |
5 | Invalid Merchant Information. |
7 | Field Format Error. |
8 | Not a Transaction Server. |
9 | Invalid Parameter Stream. |
10 | Too Many Line Items. |
11 | Client Timeout Waiting for Response. |
12 | Decline. |
13 | Referral. |
14 | Transaction Type Not Supported In This Version. |
19 | Original Transaction ID Not Found. |
20 | Customer Reference Number Not Found. |
22 | Invalid ABA Number. |
23 | Invalid Account Number. |
24 | Invalid Expiration Date. |
25 | Transaction Type Not Supported by Host. |
26 | Invalid Reference Number. |
27 | Invalid Receipt Information. |
28 | Invalid Check Holder Name. |
29 | Invalid Check Number. |
30 | Check DL Verification Requires DL State. |
40 | Transaction did not connect (to NCN because SecureNCIS is not running on the web server). |
50 | Insufficient Funds Available. |
99 | General Error. |
100 | Invalid Transaction Returned from Host. |
101 | Timeout Value too Small or Invalid Time Out Value. |
102 | Processor Not Available. |
103 | Error Reading Response from Host. |
104 | Timeout waiting for Processor Response. |
105 | Credit Error. |
106 | Host Not Available. |
107 | Duplicate Suppression Timeout. |
108 | Void Error. |
109 | Timeout Waiting for Host Response. |
110 | Duplicate Transaction. |
111 | Capture Error. |
112 | Failed AVS Check. |
113 | Cannot Exceed Sales Cap. |
1000 | Generic Host Error. |
1001 | Invalid Login. |
1002 | Insufficient Privilege or Invalid Amount. |
1003 | Invalid Login Blocked. |
1004 | Invalid Login Deactivated. |
1005 | Transaction Type Not Allowed. |
1006 | Unsupported Processor. |
1007 | Invalid Request Message. |
1008 | Invalid Version. |
1010 | Payment Type Not Supported. |
1011 | Error Starting Transaction. |
1012 | Error Finishing Transaction. |
1013 | Error Checking Duplicate. |
1014 | No Records To Settle (in the current batch). |
1015 | No Records To Process (in the current batch). |
Planet Payment:
ResponseCode | ResponseText | Description |
01 | CALL | See ResponseText for issuer phone number |
02 | CALL | See ResponseText for issuer phone number |
03 | TERM ID ERROR | Invalid merchant ID |
04 | HOLD - CALL | Pick up card |
05* | DECLINE | Do not honor |
06 | ERROR | General error |
07 | PICKUP CARD | Do not honor |
08 | HONOR WITH ID | Honor with customer ID |
10 | PARTIAL APPROVAL | Partial approval for the authorized amount returned |
11 | APPROVAL VIP | approval |
12* | INVALID TRANS | Invalid transaction |
13* | AMOUNT ERROR | Invalid transaction amount |
14* | CARD NO. ERROR | Invalid card number |
15* | NO SUCH ISSUER | No such issuer |
17 | CUST CANCELATION | Customer cancellation |
19* | RE ENTER | Re-enter transaction |
21 | NO ACTION TAKEN | Unable to back out transaction |
25* | NO RECORD FOUND | Unable to locate record in file, or account number is missing from inquiry |
27* | ERROR | Issuer File Update field edit error |
28* | NO REPLY | Temporarily unavailable |
30* | CALL | Format error |
32 | PARTIAL REVERSAL | Partial reversal |
40 | NOT SUPPORTED | Requested function not supported |
41 | HOLD-CALL | Pickup card-lost |
43 | HOLD-CALL | Pickup card-stolen |
51* | DECLINE | Insufficient funds |
52 | NO CHECK ACCOUNT | No checking account |
53 | NO SAVE ACCOUNT | No savings account |
54* | EXPIRED CARD | Expired card |
55 | WRONG PIN | Incorrect PIN |
57 | SERV NOT ALLOWED | Transaction not permitted-card |
58 | SERV NOT ALLOWED | Transaction not permitted-terminal |
59 | DECLINE | Suspected fraud |
61* | DECLINE | Exceeds withdrawal limit |
62 | DECLINE | Invalid service code, restricted |
63 | SEC VIOLATION | Security violation |
65* | DECLINE | Activity limit exceeded |
68 | LATE RESPONSE | Response received late |
75 | PIN EXCEEDED PIN | tries exceeded |
76* | NO ACTION TAKEN | Unable to locate |
77* | NO ACTION TAKEN | Inconsistent data, rev. or repeat |
78* | NO ACCOUNT | No account |
79 | ALREADY REVERSED | Already reversed |
80 | DATE ERROR | Invalid date |
81* | ENCRYPTION ERROR | Cryptographic error |
82 | INCORRECT CVV | CVV data incorrect |
83 | CANT VERIFY PIN | Cannot verify PIN |
84 | BAD LIFE CYCLE | Invalid authorization life cycle |
85 | CARD OK | No reason to decline |
86 | CANT VERIFY PIN | Cannot verify PIN |
87 | DECLINE | Network unavailable |
91* | NO REPLY | Issuer unavailable |
92* | INVALID ROUTING | Destination not found |
93 | DECLINE | Violation, cannot complete |
94* | DECLINE | Duplicate transmission detected |
96* | SYSTEM ERROR | Re-send, system error |
AX | EXCEEDS AMOUNT | Amount exceeds either the minimum or maximum allowed amount |
B1 | SURCHARGE NOT ALLOWED | Surcharge amount not permitted on Visa cards or EBT food stamps |
ER | ERROR | Error-see MRC response |
N0* | FORCE STIP | Force STIP |
N3 | CASHBACK NOT AVAIL | Cash back service not available |
N4* | DECLINE | Exceeds issuer withdrawal limit |
N7 | CVV2 MISMATCH CVV2 | value supplied is invalid |
P2 | INVALID BILL INFO | Invalid biller information |
P5 | PIN CHARGE/UNBLOCK DECLINED | PIN charge/unblock declined |
P6 | UNSAFE PIN | Unsafe PIN |
Q1 | AUTHENTIC FAILED | Card authentication failed |
R0 | STOP RECURRING | Customer requested stop of specific recurring payment. |
R1 | STOP RECURRING | Customer requested stop of all recurring payments from specific merchant. |
R3 | ALL AUTH REVOKED | Revocation of All Authorizations Order SD SOFT DECLINE Transaction is declined by the Gateway based on merchant's settings for ACCOUNT_VALIDATION and CONSUMER_VALIDATION TO (Tee-oh)* TIME OUT Re-submit |
XA* | FORWARD 2 ISSUER | Forward to issuer |
XD* | FORWARD 2 ISSUER | Forward to issuer |
Z3* | UNABLE TO ONLINE | Unable to go online, declined. |
PlugNPay:
ResponseCode | Description |
A | Approved. |
C | Call Auth Center. |
D | Declined. |
P | Pick up card. |
X | Expired. |
E | Other Error. |
ResponseCode | Description |
00 | Success |
20 | Invalid username |
21 | Invalid transType |
23 | Invalid accountType |
24 | Invalid sourceEmail |
25 | Invalid firstName |
26 | Invalid mInitial |
27 | Invalid lastName |
28 | Invalid billAddr |
29 | Invalid aptNum |
30 | Invalid city |
31 | Invalid state |
32 | Invalid billZip |
33 | Invalid mailAddr |
34 | Invalid mailApt |
35 | Invalid mailCity |
36 | Invalid mailState |
37 | Invalid mailZip |
38 | Invalid dayPhone |
39 | Invalid evenPhone |
40 | Invalid ssn |
41 | Invalid dob |
42 | Invalid recEmail |
43 | Invalid knownAccount |
44 | Invalid amount |
45 | Invalid invNum |
46 | Invalid rtNum |
47 | Invalid accntNum |
48 | Invalid ccNum |
49 | Invalid expDate |
50 | Invalid cvv2 |
51 | Invalid transNum or unavailable to act on transNum due to funding |
52 | Invalid splitNum |
53 | A ProPay account with this e-mail address already exists or User has no AccountNumber |
54 | A ProPay account with this social security number already exists |
55 | The email address provided does not correspond to a ProPay account. |
56 | Recipient's e-mail address shouldn't have a ProPay account and does |
57 | Cannot settle transaction because it already expired |
58 | Credit card declined |
59 | User not authenticated |
60 | Credit card authorization timed out; retry at a later time |
61 | Amount exceeds single transaction limit |
62 | Amount exceeds monthly volume limit |
63 | Insufficient funds in account |
64 | Over credit card use limit |
65 | Miscellaneous error |
66 | Denied a ProPay account (Developer should display a descriptive message that guides a new user to fill out ProPay exceptions form and submit it.) |
67 | Unauthorized service requested |
68 | Account not affiliated |
69 | Duplicate invoice number (Transaction succeeded in a prior attempt within the previous 24 hours. This return code should be handled as a success. Details about the original transaction are included whenever a 69 response is returned. These details include a repeat of the authcode, the original AVS response, and the original CVV response.) |
70 | Duplicate external ID |
71 | Account previously set up, but problem affiliating it with partner |
72 | The ProPay Account has already been upgraded to a Premium Account |
73 | Invalid Destination Account |
74 | Account or Trans Error |
75 | Money already pulled |
76 | Not Premium (used only for push/pull transactions) |
77 | Empty results |
78 | Invalid Authentication |
79 | Generic account status error |
80 | Invalid Password |
81 | AccountExpired |
82 | InvalidUserID |
83 | BatchTransCountError |
84 | InvalidBeginDate |
85 | InvalidEndDate |
86 | InvalidExternalID |
87 | DuplicateUserID |
88 | Invalid track 1 |
89 | Invalid track 2 |
90 | Transaction already refunded |
91 | Duplicate Batch ID |
92 | Duplicate Batch Transaction |
93 | Batch Transaction amount error |
94 | Unavailable Tier |
95 | Invalid Country Code |
97 | Account created in documentary status, but still must be validated. |
98 | Account created in documentary status, but still must be validated and paid for. |
99 | Account created successfully, but still must be paid for. |
100 | Transaction Already Refunded |
101 | Refund Exceeds Original Transaction |
102 | Invalid Payer Name |
103 | Transaction does not meet date criteria |
104 | Transaction could not be refunded due to current transaction state. |
ResponseCode | Description |
APPROVED | The card issuing bank approved the transaction request. |
DECLINED | The transaction request was accepted as a valid request and was declined by the card issuing bank. |
ERROR | The transaction request encountered an error. |
ResponseCode | Description |
0 | Status Ok - Request succeeded. |
10100 | The transaction had a validation error, but could not be voided automatically. If you want to void or cancel it, you must do so manually. This is a warning and can happen if there is an incorrect street address and/or zip code. Depending on the merchant's fraud settings, QBMS may try to automatically void the transaction. If that fails, as is the case with this status code, you must void or cancel the transaction manually. |
10101 | This is a validation error warning and can be returned if the merchant's fraud settings cause some auth transactions to be rejected. In this case, even though the auth is rejected, the auth is kept on file against the customer card up to 15-30 days after the rejection. |
10200 | An error occurred while communicating with the processing gateway. Indicates a communication problem, rather than an error resulting from transaction content. |
10201 | An error occurred during login to the processing gateway. Could not log in to the QBMS processing gateway. |
10202 | An error occurred during account validation. Could not validate the QBMS account. |
10300 | A numeric value was of the wrong type. For example, some values require integers only, while others require decimals. |
10301 | This credit card number is invalid. |
10302 | An error occurred while validating a date field. Format is invalid. |
10303 | A mandatory element is missing from the request. |
10304 | A field in the request is too long. The maximum length has been exceeded. |
10305 | An error occurred during data validation. Unexpected data was found during the validation. |
10306 | You may only supply the Boolean values true or false in the indicated field. |
10307 | A field in the request is too short - The expected minimum data is not present. |
10309 | A field is not formatted correctly. |
10312 | Invalid data contained in a field. This error can occur for various reasons, for example if the value supplied in the TransactionAmount property is not formatted correctly (dollars, period, cents to two decimal places), you'll get this error. |
10314 | You can not reuse a TransactionId for a different type of transaction within a 5 minute period. The TransactionId should be unique within this time window. |
10400 | This account does not have sufficient funds to process this transaction. The attempted transaction exceeded the customer's credit limit on the credit card. The transaction failed. |
10401 | Declined: The card issuer/processor refused to authorize the transaction. For example, the account may have been closed, or activities may have been temporarily stopped for that card due to security reasons. |
10402 | The merchant bank account does not support this type of credit card. |
10403 | The QBMS account contained in the request is not valid. |
10404 | This transaction has been declined, but can be approved by obtaining a Voice Authorization code from the card issuer and then calling the Force method. |
10405 | An error occurred while attempting to void this transaction. The transaction may have already been settled. |
10406 | This capture transaction could not be processed for one of the following reasons. The transaction has been captured already, has been voided, has expired, or the capture request has used the incorrect authorization transaction ID. |
10407 | The transaction amount exceeded the per transaction limit imposed by the card issuer. |
10408 | An error occurred due to invalid data format. An incorrect format was used for a field value, such as the transaction ID. |
10409 | A validation error occurred while processing this transaction: |
10415 | This transaction has been declined because the credit card used for the original transaction has expired. For example, this error could occur if the card in question has expired between the time of authorization and the time of an attempted capture. |
10416 | This transaction was already submitted and processed. A check transaction is being duplicated. |
10417 | A particular type of check is not supported for an attempted check transaction (i.e. a Payroll Check). |
10418 | Total amount of checks submitted exceeds allowed daily maximum. |
10419 | Number of transactions exceeds allowed daily maximum. |
10420 | The check transaction was declined due to suspected fraud. |
10500 | An unknown server error occurred that prevents processing of the request. |
10501 | An unknown server error occurred that prevents processing of the request. |
Repay Gateway:
ResponseCode | Description |
-100 | Transaction NOT Processed; Generic Host Error. |
0 | Approved. |
1 | User Authentication Failed. |
2 | Invalid Transaction. |
3 | Invalid Transaction Type. |
4 | Invalid Amount. |
5 | Invalid Merchant Information. |
7 | Field Format Error. |
8 | Not a Transaction Server. |
9 | Invalid Parameter Stream. |
10 | Too Many Line Items. |
11 | Client Timeout Waiting for Response. |
12 | Decline. |
13 | Referral. |
14 | Transaction Type Not Supported In This Version. |
19 | Original Transaction ID Not Found. |
20 | Customer Reference Number Not Found. |
22 | Invalid ABA Number. |
23 | Invalid Account Number. |
24 | Invalid Expiration Date. |
25 | Transaction Type Not Supported by Host. |
26 | Invalid Reference Number. |
27 | Invalid Receipt Information. |
28 | Invalid Check Holder Name. |
29 | Invalid Check Number. |
30 | Check DL Verification Requires DL State. |
40 | Transaction did not connect (to NCN because SecureNCIS is not running on the web server). |
50 | Insufficient Funds Available. |
99 | General Error. |
100 | Invalid Transaction Returned from Host. |
101 | Timeout Value too Small or Invalid Time Out Value. |
102 | Processor Not Available. |
103 | Error Reading Response from Host. |
104 | Timeout waiting for Processor Response. |
105 | Credit Error. |
106 | Host Not Available. |
107 | Duplicate Suppression Timeout. |
108 | Void Error. |
109 | Timeout Waiting for Host Response. |
110 | Duplicate Transaction. |
111 | Capture Error. |
112 | Failed AVS Check. |
113 | Cannot Exceed Sales Cap. |
1000 | Generic Host Error. |
1001 | Invalid Login. |
1002 | Insufficient Privilege or Invalid Amount. |
1003 | Invalid Login Blocked. |
1004 | Invalid Login Deactivated. |
1005 | Transaction Type Not Allowed. |
1006 | Unsupported Processor. |
1007 | Invalid Request Message. |
1008 | Invalid Version. |
1010 | Payment Type Not Supported. |
1011 | Error Starting Transaction. |
1012 | Error Finishing Transaction. |
1013 | Error Checking Duplicate. |
1014 | No Records To Settle (in the current batch). |
1015 | No Records To Process (in the current batch). |
ResponseCode | Description |
A | Transaction approved. |
E | Front-End Error (Not approved) |
X | Gateway Error (Not approved) |
ResponseCode | Description |
OK | Process executed without error. The DEFERRED payment was released. |
MALFORMED | Input message was malformed - normally will only occur during development. |
INVALID | Unable to authenticate you or find the transaction, or the data provided is invalid. If the Deferred payment was already released, an INVALID response is returned. |
ERROR | Only returned if there is a problem at Protx. |
ResponseCode | Description |
A | Transaction authorized by bank. Approval Code available as bank reference |
N | Transaction not authorized. Failure message text available to merchant |
C | Communication problem. Trying again later may well work |
P:A | Pre-bank checks. Amount not supplied or invalid |
P:X | Pre-bank checks. Not all mandatory parameters supplied |
P:P | Pre-bank checks. Same payment presented twice |
P:S | Pre-bank checks. Start date invalid |
P:E | Pre-bank checks. Expiry date invalid |
P:I | Pre-bank checks. Issue number invalid |
P:C | Pre-bank checks. Card number fails LUHN check |
P:T | Pre-bank checks. Card type invalid - i.e. does not match card number prefix |
P:N | Pre-bank checks. Customer name not supplied |
P:M | Pre-bank checks. Merchant does not exist or not registered yet |
P:B | Pre-bank checks. Merchant account for card type does not exist |
P:D | Pre-bank checks. Merchant account for this currency does not exist |
P:V | Pre-bank checks. CV2 security code mandatory and not supplied / invalid |
P:R | Pre-bank checks. Transaction timed out awaiting a virtual circuit. Merchant may not have enough virtual circuits for the volume of business. |
P:# | Pre-bank checks. No MD5 hash / token key set up against account |
ResponseCode | Description |
Y | Transaction approved. |
N | Host decline. |
ResponseCode | Description |
0 | Transaction is not approved. |
1 | Transaction is approved. |
-1 | Error in transaction. |
ResponseCode | Description |
1 | Approved |
2 | Declined |
3 | Error / Invalid Data |
ResponseCode | Description |
Settled | The transaction has been processed AND sent to bank for settlement. |
Authorized | The Transaction was processed. |
Declined | The bank declined the transaction. |
Voided | Canceled by user. |
Canceled | Canceled by PRIGate. Usually because provided data is insufficient. |
Qued | Placed in que for later processing. Credit cards usually take 2 hours. ACH 11am next day. |
UnKnown | Unknown transaction status. |
ResponseCode | ResponseText | Description |
00 | APPROVAL | Approved and completed. |
01 | CALL | Refer to issuer. |
02 | CALL | Refer to issuer - Special condition. |
03 | TERM ID ERROR | Invalid merchant ID. |
04 | HOLD-CALL | Pick up card. |
05 | DECLINE | Do not honor. |
06 | ERROR xx | General error. |
06 | ERROR xxxx | General error. |
07 | HOLD-CALL | Pick up card - Special condition. |
13 | AMOUNT ERROR | Invalid amount. |
14 | CARD NO. ERROR | Invalid card number. |
15 | NO SUCH ISSUER | No such issuer. |
19 | RE ENTER | Re-enter transaction. |
21 | NO ACTION TAKEN | Unable to back out transaction. |
28 | NO REPLY | File is temporarily unavailable. |
39 | NO CREDIT ACCOUNT | No credit account. |
41 | HOLD-CALL | Pickup card - Lost. |
43 | HOLD-CALL | Pickup card - Stolen. |
51 | DECLINE | Insufficient funds. |
54 | EXPIRED CARD | Expired card. |
57 | SERV NOT ALLOWED | Transaction not permitted - Card. |
61 | DECLINE | Exceeds withdrawal limit. |
62 | DECLINE | Invalid service code, restricted. |
65 | DECLINE | Activity limit exceeded. |
76 | NO ACTION TAKEN | Unable to locate, no match. |
77 | NO ACTION TAKEN | Inconsistent data, rev. or repeat. |
78 | NO ACCOUNT | No account. |
80 | DATE ERROR | Invalid date. |
85 | CARD OK | No reason to decline. |
91 | NO REPLY | Issuer or switch is unavailable. |
93 | DECLINE | Violation, cannot complete. |
96 | SYSTEM ERROR | System malfunction. |
98 | VOID ERROR | No matching transaction to void. |
L2 | PASSWORD INVALID | Password is missing or invalid. |
L3 | EXPIRATION DATE INVALID | Expiration Date is not formatted correctly. |
L6 | ORDER NUMBER MISSING | The Order Number is required but missing. |
L7 | WRONG TRANSACTION CODE | Transaction Code must be either a 30 for Authorize Only, 32 for Authorize and Settle. |
L8 | NETWORK | The Network Connection timed out due to a communications error. |
ResponseCode | Description |
1 | Transaction approved. |
2 | Transaction declined. |
3 | Error in transaction data. |
ResponseCode | Description |
approved | Transaction received on-line approval (sales, auth-onlys) |
accepted | Transaction accepted for later processing (credits, captures, etc) |
error | Gateway system error |
baddata | Invalid fields sent to gateway. |
ResponseCode | Description |
Approved | Transaction approved. |
Declined | Transaction declined. |
Error | There is an error in the data received. |
This gateway is no longer in service.
Verifi:
ResponseCode | Description |
1 | Transaction approved. |
2 | Transaction declined. |
3 | Error in transaction data. |
ResponseCode | Description |
A | Transaction authorized. |
Anything else | Transaction declined. |
ResponseCode | Description |
Declined | Transaction declined. |
Approved | Transaction accepted. |
ResponseCode | Description |
AUTHORISED | Transaction authorized. (AuthOnly/Sale) |
ok | Transaction accepted (Void, Capture, Credit, and Force) |
Anything else | Transaction declined. |
ResponseCode | Description |
1 | OK. |
2 | NG. |