Skip to main content

Error Codes

Standard Error Codes

CodeDescription
1005Invalid message type The Monek message type (e.g. ESALE_KEYED) is invalid.
1008No TIDs available, using primary The number of active concurrent transactions exceeds the number of Terminal Identifiers (TIDs) allocated to the merchant. The primary TID will be reused.
1022Invalid track 2 data The track 2 data supplied for a CHIP or SWIPE transaction is not valid.
1026Unrecognised Card Type The card number supplied has not been recognised against the active card ranges.
1052Merchant not set up for supplied currency The merchant is not set up for the currency specified.
1063Merchant or Entity Type not found Merchant configuration error, please contact Monek Support.
1300Response sequence error The transaction response from the acquiring bank was not properly formatted.
1301Response Message Type: HOLD The bank could not process the transaction on this attempt. Depending on the acquirer this can indicate a long running authorisation or an issue with the supplied card details. This is entirely at the discretion of the acquiring bank so it is recommended that under these circumstances the card details should be checked and resubmitted.
1303Unexpected response code for acquirer 'xx' The acquiring bank returned an unknown transaction response code.
1309PSF card data malformed The Payment, Store or Fuel card line item data supplied was malformed.
1314Invalid Monek merchant number The specified Monek merchant number is invalid.
1323Unable to extract stored card data The system was unable to resolve card data for a Cross Reference transaction.
1350Cannot submit swiped card details for KEYED transaction method Card details were provided in Track2 format against a keyed card transaction type.
1367Connection timed out The authorisation connection to the acquiring bank timed out.
1374Client closed socket before response sent. Acquirer request sent. The calling client closed the transaction socket before the transaction could be completed. The authorisation request was sent to the acquiring bank but the transaction will NOT be settled.
1380Merchant IP address not found A refund or Cross Reference transaction was received from an IP address not registered against the merchant.
Note: This functionality is deprecated in favour of Validity ID. See: Payments API Additional Fields
1381Validity ID or API Key incorrect A refund or Cross Reference transaction was received with a missing or invalid API Key.
1384Client closed socket before response sent. Acquirer request NOT sent. The calling client closed the transaction socket before the transaction could be completed. The authorisation request was not sent to the acquiring bank.
1401Internal timeout An internal timeout occurred processing the transaction.
1403Internal timeout An internal timeout occurred processing the transaction.
1487No TIDs available, TID Limited The number of active concurrent transactions exceeds the number of Terminal Identifiers (TIDs) allocated to the merchant. TID usage is limited to unique available TIDs.
1488Malformed card details The card details supplied are not in a recognisable format.
1491Card Type Not Supported by 3-D Secure 3-D Secure details were supplied for a card type that does not support 3-D Secure.
14923-D Secure CAVV conversion failed The CAVV supplied for a 3-D Secure transaction is invalid.
14933-D Secure Enrolled character not valid The Enrolled value supplied for a 3-D Secure transaction is invalid.
14943-D Secure Authenticated character not valid The Authenticated value supplied for a 3-D Secure transaction is invalid.
1495Internet or Keyed Maestro transaction in which no 3DS data has been submitted Internationally issued Maestro cards processed over the internet must use 3-D Secure.
1500Merchant not set up for Streamline settlement country [Streamline Only] The transaction specified a country code not allowed for the merchant.
1501Invalid operation performed using Cross Reference in lieu of card details A cross reference can be used to settle, recharge or refund a previous transaction. It cannot be used to perform a sale against a refund or to reprocess authorisation only requests.
1509VERIFY not supported by acquirer The acquirer for this merchant does not currently support the Zero Auth transaction type.
1510Monek Merchant Closed The Monek merchant has been closed at the request of the merchant or their acquiring bank.
2152Connection timed out The authorisation connection to the acquiring bank timed out.
2155Connection timed out The authorisation connection to the acquiring bank timed out.
2157Authorisation rejected by host The connection to the acquiring bank was established but the authorisation host refused to accept the transaction.
2166Authorisation rejected by host The connection to the acquiring bank was established but the authorisation host refused to accept the transaction.
2180Internal timeout An internal timeout occurred processing the transaction.
3073Invalid request string The transaction message was invalid.
3074Invalid request string The transaction message was invalid.
3501No matching transaction for refund No suitable transaction could be found to match the refund request

Dynamic Error Codes

Monek request message validation generates dynamic codes to represent field validation failures. Dynamic codes follow the format 4xyy where:

  • 4 – Indicate a field validation error
  • X – Indicates the type of problem
  • Y – Indicates the field that failed validation

X - Problem Types

The following table details the codes for each validation problem type.

CodeDescription
0MISSING
1EMPTY
2TOO SHORT
3TOO SMALL
4TOO FEW FIELDS
5TOO LARGE
6TOO LONG
7TOO MANY FIELDS
8NOT INTEGER
9NOT NUMERIC

YY - Field Numbers

The following table details the 2-digit codes used to represent the field failing validation.

CodeDescription
00MISSING
02TERMINAL IDENTIFIER
03TRANSACTION IDENTIFIER
04TERMINAL TYPE
05MESSAGE TYPE
07Monek MERCHANT ID
08CARD DETAILS
09AMOUNT
10CASHBACK AMOUNT
11CURRENCY CODE
12COUNTRY CODE
13DISPATCH
14AUTHORISATION CODE
15CUSTOMER DETAILS
16CARD SECURITY CODE (CV2)
17DESCRIPTIVE DATA
18PURCHASE/STORE/FUEL CARD LINE ITEM DETAIL
19RESERVED
20TRANSACTION TIME & DATE
21EMV TERMINAL TYPE
22REASON ONLINE CODE
23ICC TRANSACTION REQUEST DATA
24CARD NUMBER
25ISSUE NUMBER
26EXPIRY MONTH
27EXPIRY YEAR
28START MONTH
29START YEAR
37SERVICE CODE
56CUSTOMER NAME
57CUSTOMER ADDRESS
58CUSTOMER POSTCODE
59CUSTOMER TELEPHONE
60CUSTOMER EMAIL
71RESERVED
87CROSS REFERENCE
94START DATE
95EXPIRY DATE