Error Codes
Standard Error Codes
Code | Description |
---|---|
1005 | Invalid message type The Monek message type (e.g. ESALE_KEYED) is invalid. |
1008 | No 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. |
1022 | Invalid track 2 data The track 2 data supplied for a CHIP or SWIPE transaction is not valid. |
1026 | Unrecognised Card Type The card number supplied has not been recognised against the active card ranges. |
1052 | Merchant not set up for supplied currency The merchant is not set up for the currency specified. |
1063 | Merchant or Entity Type not found Merchant configuration error, please contact Monek Support. |
1300 | Response sequence error The transaction response from the acquiring bank was not properly formatted. |
1301 | Response 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. |
1303 | Unexpected response code for acquirer 'xx' The acquiring bank returned an unknown transaction response code. |
1309 | PSF card data malformed The Payment, Store or Fuel card line item data supplied was malformed. |
1314 | Invalid Monek merchant number The specified Monek merchant number is invalid. |
1323 | Unable to extract stored card data The system was unable to resolve card data for a Cross Reference transaction. |
1350 | Cannot submit swiped card details for KEYED transaction method Card details were provided in Track2 format against a keyed card transaction type. |
1367 | Connection timed out The authorisation connection to the acquiring bank timed out. |
1374 | Client 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. |
1380 | Merchant 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 |
1381 | Validity ID or API Key incorrect A refund or Cross Reference transaction was received with a missing or invalid API Key. |
1384 | Client 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. |
1401 | Internal timeout An internal timeout occurred processing the transaction. |
1403 | Internal timeout An internal timeout occurred processing the transaction. |
1487 | No 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. |
1488 | Malformed card details The card details supplied are not in a recognisable format. |
1491 | Card Type Not Supported by 3-D Secure 3-D Secure details were supplied for a card type that does not support 3-D Secure. |
1492 | 3-D Secure CAVV conversion failed The CAVV supplied for a 3-D Secure transaction is invalid. |
1493 | 3-D Secure Enrolled character not valid The Enrolled value supplied for a 3-D Secure transaction is invalid. |
1494 | 3-D Secure Authenticated character not valid The Authenticated value supplied for a 3-D Secure transaction is invalid. |
1495 | Internet 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. |
1500 | Merchant not set up for Streamline settlement country [Streamline Only] The transaction specified a country code not allowed for the merchant. |
1501 | Invalid 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. |
1509 | VERIFY not supported by acquirer The acquirer for this merchant does not currently support the Zero Auth transaction type. |
1510 | Monek Merchant Closed The Monek merchant has been closed at the request of the merchant or their acquiring bank. |
2152 | Connection timed out The authorisation connection to the acquiring bank timed out. |
2155 | Connection timed out The authorisation connection to the acquiring bank timed out. |
2157 | Authorisation rejected by host The connection to the acquiring bank was established but the authorisation host refused to accept the transaction. |
2166 | Authorisation rejected by host The connection to the acquiring bank was established but the authorisation host refused to accept the transaction. |
2180 | Internal timeout An internal timeout occurred processing the transaction. |
3073 | Invalid request string The transaction message was invalid. |
3074 | Invalid request string The transaction message was invalid. |
3501 | No 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.
Code | Description |
---|---|
0 | MISSING |
1 | EMPTY |
2 | TOO SHORT |
3 | TOO SMALL |
4 | TOO FEW FIELDS |
5 | TOO LARGE |
6 | TOO LONG |
7 | TOO MANY FIELDS |
8 | NOT INTEGER |
9 | NOT NUMERIC |
YY - Field Numbers
The following table details the 2-digit codes used to represent the field failing validation.
Code | Description |
---|---|
00 | MISSING |
02 | TERMINAL IDENTIFIER |
03 | TRANSACTION IDENTIFIER |
04 | TERMINAL TYPE |
05 | MESSAGE TYPE |
07 | Monek MERCHANT ID |
08 | CARD DETAILS |
09 | AMOUNT |
10 | CASHBACK AMOUNT |
11 | CURRENCY CODE |
12 | COUNTRY CODE |
13 | DISPATCH |
14 | AUTHORISATION CODE |
15 | CUSTOMER DETAILS |
16 | CARD SECURITY CODE (CV2) |
17 | DESCRIPTIVE DATA |
18 | PURCHASE/STORE/FUEL CARD LINE ITEM DETAIL |
19 | RESERVED |
20 | TRANSACTION TIME & DATE |
21 | EMV TERMINAL TYPE |
22 | REASON ONLINE CODE |
23 | ICC TRANSACTION REQUEST DATA |
24 | CARD NUMBER |
25 | ISSUE NUMBER |
26 | EXPIRY MONTH |
27 | EXPIRY YEAR |
28 | START MONTH |
29 | START YEAR |
37 | SERVICE CODE |
56 | CUSTOMER NAME |
57 | CUSTOMER ADDRESS |
58 | CUSTOMER POSTCODE |
59 | CUSTOMER TELEPHONE |
60 | CUSTOMER EMAIL |
71 | RESERVED |
87 | CROSS REFERENCE |
94 | START DATE |
95 | EXPIRY DATE |