Reference list of error codes returned by the STPI (SecureTable POS Interface) gateway, including the terminal message, technical details, and suggested action for each code.
Contents
Many codes in the 802–954 range are generic POS-side errors (labelled “May occur with some POS systems” in the source document) and are not specific to STPI. For these, contact the POS provider for support.
| Code | Terminal Message | Technical Details | Suggested Action |
|---|---|---|---|
| 101 | Fatal error | Unexpected error | Contact PayFacto Support. |
| 201 | License error | This can happen when we are using the older CA license files during the communication with the license server. (Not license tokens) This shouldn’t happen now because we are using license tokens rather than the old CA license files. | Contact PayFacto Support. |
| 401 | Invalid server socket | This will only happen when STPI cannot establish a connection to the POS. | Check the gateway_sm.properties in the STPI install location for the pos.listen.port property. By default, this is set to port 4999. Make sure that port is not already in use. |
| 402 | Socket init failed | Could not open the connection to the POS. | Check that the POS is listening on the correct IP address and port specified by the properties pos.server.ip and pos.server.port in the gateway_sm.properties file in the STPI install location.Or, due to conflicting ports. STPI will try to open a socket for printing purposes on port 600xx where xx is the first two digits of the check number. If this happens, check the POS. |
| 403 | IP send failed | Could not send message to the POS. (The socket was already successfully opened) | This means that even though the socket was opened to the POS, that there was a problem in sending messages to the POS. Check any network issues (if POS is on another machine), or POS side, or try another transaction. |
| 404 | IP receive failed | Could not receive response message from POS. (The socket was already successfully opened, and a request message was already successfully sent to POS) | This means that even though we sent a message to the POS already, that there was a problem in receiving a response from the POS. Check any network issues (if POS is on another machine), or POS side, or try another transaction. |
| 601 | Invalid tag values | This issue typically happens when STPI receives a request message from the terminal which is expected to be a number but was not. | If this happens, report the issue to the PayFacto Support. Try to downgrade the version of the SecureTablePay app. It could be that the latest version could cause this. If that doesn’t work, also try a downgrade of the STPI client. |
| 602 | Invalid value for format | This issue will happen when certain configuration in the gateway_sm.properties file are expected to be numbers, but aren’t. | Check the values in the gateway_sm.properties file. Possible properties to check may be (but not limited to) the following:1. pos.server.ip 2. pos.server.ip2 3. pos.server.port 4. pos.read.timeout 5. pos.termid 6. pos.servicetype 7. pos.response.limit 8. pos.close.check 9. pos.pass.tk2.apply.pay |
| 801 | Invalid server ID | This happens when the server id does not exist in the POS database. | Check that you are using the correct server ID in the POS. |
| 802 | Invalid SQL server | This happens when we cannot connect to the POS database. | Check that the following properties in the gateway_sm.properties file match the setup in the POS.1. pos.server.ip 2. pos.server.database.port 3. pos.server.database.instance.name 4. pos.server.database.connection.type • the value for this is 1 or 2. • value 1 means that we connect to the database using IP address (1) and database port (2). • value 2 means that we connect to the database using IP address (1) and the instance name (3). Check that the sq.conf file also exists in the STPI install location. |
| 803 | Invalid POS server | ||
| 804 | Invalid response | A. This can happen when STPI does not receive enough bytes from the POS. Or, B. When the POS database does not have the specific check or any checks. Or, C. Cannot get a response from the hello1.dll. | A. 1. If the POS is running on a different machine, this could be potentially packet loss. Try it again. 2. If the issue persists, it could be that the POS has an issue when sending a response back to STPI. Contact POS support. B. Contact POS support. C. Check with PayFacto Support about this or contact the POS provider for support. |
| 805 | Invalid XML response | Invalid XML response. Or, Cannot get print data from POS. | 1. If the POS was recently updated, try downgrading the version. 2. If STPI was recently updated, try downgrading the version. 3. If 1 & 2 fails, contact PayFacto Support to examine the XML response from POS. May need to contact the POS provider for support. |
| 807 | Invalid amount | This can happen if the check number, purchase amount or tax amount from the POS is not a number. | 1. If the POS was recently updated, try downgrading the version. 2. If STPI was recently updated, try downgrading the version. 3. If 1 & 2 fails, contact PayFacto Support to examine this issue. May need to contact the POS provider for support. |
| 808 | No tables | This can happen when there are no tables available. | 1. Open some tables on the POS and try again. 2. If that fails, check if STPI has been updated lately and downgrade it and try again. |
| 810 | Check does not exist | This can happen if the check does not exist. | 1. Check that the check number is correct. 2. If the POS was recently updated, try downgrading the version. 3. If STPI was recently updated, try downgrading the version 4. Contact PayFacto Support to examine this issue. May need to contact the POS provider for support. |
| 816 | Invalid payment slip | This can happen when applying the payment. | 1. If the POS was recently updated, try downgrading the version. 2. If STPI was recently updated, try downgrading the version. 3. If 1 & 2 fail, contact PayFacto Support to examine this issue. May need to contact the POS provider for support. |
| 817 | Invalid payment response | This can happen when there is an issue packing the apply payment response to return to the POS | 1. If STPI was recently updated, try downgrading the version. 2. If 1 & 2 fails, contact PayFacto Support to examine this issue. |
| 819 | Invalid type of service | Config issue on POS | Make sure that the pos.servicetype property in the gateway_sm.properties file is correct. Expected value is TS |
| 820 | Invalid terminal ID | Config issue on POS | Make sure that the pos.termid property in the gateway_sm.properties file is correct. |
| 821 | Invalid DLL response | May occur with some POS systems | Contact PayFacto Support |
| 822 | DLL load failed | Config issue on POS | 1. Make sure the hello1.dll exists 2. Contact PayFacto Support |
| 823 | Too many tables | May occur with some POS systems | Contact PayFacto Support |
| 824 | Invalid server name | May occur with some POS systems | Contact the POS provider for support. |
| 825 | Invalid table count | May occur with some POS systems | Contact PayFacto Support |
| 826 | Invalid server ID | May occur with some POS systems | Contact the POS provider for support. |
| 829 | Unauthorized COM term | May occur with some POS systems | Contact the POS provider for support. |
| 830 | Someone already logged in | May occur with some POS systems | Contact the POS provider for support. |
| 831 | Could not find employee from ID | May occur with some POS systems | Contact the POS provider for support. |
| 832 | Invalid employee password | May occur with some POS systems | Contact the POS provider for support. |
| 833 | Invalid manager card | May occur with some POS systems | Contact the POS provider for support. |
| 834 | Employee logged in on another terminal | May occur with some POS systems | Contact the POS provider for support. |
| 835 | No one logged in | May occur with some POS systems | Contact the POS provider for support. |
| 836 | Already clocked in | May occur with some POS systems | Contact the POS provider for support. |
| 837 | Too many shifts today | May occur with some POS systems | Contact the POS provider for support. |
| 838 | Invalid jobcode for employee | May occur with some POS systems | Contact the POS provider for support. |
| 839 | Unknown employee clock in error | May occur with some POS systems | Contact the POS provider for support. |
| 840 | Not clocked in | May occur with some POS systems | Contact the POS provider for support. |
| 841 | Need to checkout first | May occur with some POS systems | Contact the POS provider for support. |
| 842 | Unknown employee clock out error | May occur with some POS systems | Contact the POS provider for support. |
| 843 | No checkout | May occur with some POS systems | Contact the POS provider for support. |
| 844 | Already checked out | May occur with some POS systems | Contact the POS provider for support. |
| 845 | Invalid queue | May occur with some POS systems | Contact the POS provider for support. |
| 846 | Invalid table | May occur with some POS systems | Contact the POS provider for support. |
| 847 | Open checks on table | May occur with some POS systems | Contact the POS provider for support. |
| 848 | Table is closed | May occur with some POS systems | Contact the POS provider for support. |
| 849 | Only one check per table allowed | May occur with some POS systems | Contact the POS provider for support. |
| 850 | Invalid check | May occur with some POS systems | Contact the POS provider for support. |
| 851 | Check has unordered items | May occur with some POS systems | Contact the POS provider for support. |
| 852 | Check not fully tendered | May occur with some POS systems | Contact the POS provider for support. |
| 853 | Invalid payment | May occur with some POS systems | Contact the POS provider for support. |
| 854 | No local printer | May occur with some POS systems | Contact the POS provider for support. |
| 855 | Invalid tender | May occur with some POS systems | Contact the POS provider for support. |
| 856 | Check is closed | May occur with some POS systems | Contact the POS provider for support. |
| 857 | Check is empty | May occur with some POS systems | Contact the POS provider for support. |
| 858 | Employee not assigned to drawer | May occur with some POS systems | Contact the POS provider for support. |
| 859 | Employee drawer not local | May occur with some POS systems | Contact the POS provider for support. |
| 860 | Table active on another terminal | May occur with some POS systems | Contact the POS provider for support. |
| 861 | Invalid item | May occur with some POS systems | Contact the POS provider for support. |
| 862 | No entry | May occur with some POS systems | Contact the POS provider for support. |
| 863 | Invalid order mode | May occur with some POS systems | Contact the POS provider for support. |
| 864 | Invalid void reason | May occur with some POS systems | Contact the POS provider for support. |
| 865 | Invalid entry | May occur with some POS systems | Contact the POS provider for support. |
| 866 | Unavailable item | May occur with some POS systems | Contact the POS provider for support. |
| 867 | Invalid mod code | May occur with some POS systems | Contact the POS provider for support. |
| 868 | Mod not authorized for parent item | May occur with some POS systems | Contact the POS provider for support. |
| 869 | Mod requirements not met | May occur with some POS systems | Contact the POS provider for support. |
| 870 | Item is not open item | May occur with some POS systems | Contact the POS provider for support. |
| 871 | Need more CC info | May occur with some POS systems | Contact the POS provider for support. |
| 872 | Employee drawer not confirmed | May occur with some POS systems | Contact the POS provider for support. |
| 873 | Jobcode cannot close checks | May occur with some POS systems | Contact the POS provider for support. |
| 874 | Bad CC track info | May occur with some POS systems | Contact the POS provider for support. |
| 875 | Illegal declared tips amount | May occur with some POS systems | Contact the POS provider for support. |
| 876 | Illegal declared cash amount | May occur with some POS systems | Contact the POS provider for support. |
| 877 | Table not found | May occur with some POS systems | Contact the POS provider for support. |
| 878 | Table in use | May occur with some POS systems | Contact the POS provider for support. |
| 879 | No local cashier | May occur with some POS systems | Contact the POS provider for support. |
| 880 | Employee cannot tender cash | May occur with some POS systems | Contact the POS provider for support. |
| 881 | Check is missing items from reqdcat | May occur with some POS systems | Contact the POS provider for support. |
| 882 | Check has pending payments | May occur with some POS systems | Contact the POS provider for support. |
| 883 | Check is full | May occur with some POS systems | Contact the POS provider for support. |
| 884 | Could not print back off gift cert | May occur with some POS systems | Contact the POS provider for support. |
| 885 | Too many checks on table | May occur with some POS systems | Contact the POS provider for support. |
| 886 | Entry already selected | May occur with some POS systems | Contact the POS provider for support. |
| 887 | Invalid special message | May occur with some POS systems | Contact the POS provider for support. |
| 888 | Invalid menu | May occur with some POS systems | Contact the POS provider for support. |
| 890 | No pivot seating | May occur with some POS systems | Contact the POS provider for support. |
| 891 | Too many seats | May occur with some POS systems | Contact the POS provider for support. |
| 892 | Not supported in quick service | May occur with some POS systems | Contact the POS provider for support. |
| 893 | Not supported in table service | May occur with some POS systems | Contact the POS provider for support. |
| 894 | Cannot adjust finalized gift card | May occur with some POS systems | Contact the POS provider for support. |
| 895 | Finalizing gift card | May occur with some POS systems | Contact the POS provider for support. |
| 896 | Check is from previous shift | May occur with some POS systems | Contact the POS provider for support. |
| 897 | Employee is checked out | May occur with some POS systems | Contact the POS provider for support. |
| 898 | Invalid exception modifier group | May occur with some POS systems | Contact the POS provider for support. |
| 899 | Not in exception modifier group | May occur with some POS systems | Contact the POS provider for support. |
| 900 | No entries selected | May occur with some POS systems | Contact the POS provider for support. |
| 901 | No entries moved | May occur with some POS systems | Contact the POS provider for support. |
| 902 | Invalid comp type | May occur with some POS systems | Contact the POS provider for support. |
| 903 | Invalid promotion | May occur with some POS systems | Contact the POS provider for support. |
| 904 | Invalid comp | May occur with some POS systems | Contact the POS provider for support. |
| 905 | Invalid promo | May occur with some POS systems | Contact the POS provider for support. |
| 906 | FOHCOM currently busy | May occur with some POS systems | Contact the POS provider for support. |
| 907 | FOHCOM server exception | May occur with some POS systems | Contact the POS provider for support. |
| 908 | Check has payments pending signature verification | May occur with some POS systems | Contact the POS provider for support. |
| 909 | Invalid parameter | May occur with some POS systems | Contact the POS provider for support. |
| 910 | eFrequency invalid request | May occur with some POS systems | Contact the POS provider for support. |
| 911 | eFrequency invalid card number | May occur with some POS systems | Contact the POS provider for support. |
| 912 | eFrequency invalid prefix | May occur with some POS systems | Contact the POS provider for support. |
| 913 | eFrequency requires manager override | May occur with some POS systems | Contact the POS provider for support. |
| 914 | eFrequency unknown error | May occur with some POS systems | Contact the POS provider for support. |
| 915 | Manager not clocked in | May occur with some POS systems | Contact the POS provider for support. |
| 916 | Illegal break type for shift | May occur with some POS systems | Contact the POS provider for support. |
| 917 | Illegal combo of break and paid for shift | May occur with some POS systems | Contact the POS provider for support. |
| 918 | Employee cannot break with open tables | May occur with some POS systems | Contact the POS provider for support. |
| 919 | Employee on break | May occur with some POS systems | Contact the POS provider for support. |
| 920 | Invalid break type for employee | May occur with some POS systems | Contact the POS provider for support. |
| 921 | Employee is not on a break | May occur with some POS systems | Contact the POS provider for support. |
| 922 | Enforced break times not met | May occur with some POS systems | Contact the POS provider for support. |
| 923 | Password has non-numeric chars | May occur with some POS systems | Contact the POS provider for support. |
| 924 | System not setup to use passwords | May occur with some POS systems | Contact the POS provider for support. |
| 925 | Password is less than min length | May occur with some POS systems | Contact the POS provider for support. |
| 926 | Password is greater than max length | May occur with some POS systems | Contact the POS provider for support. |
| 927 | Employee is magcard only | May occur with some POS systems | Contact the POS provider for support. |
| 928 | Manager must clockout | May occur with some POS systems | Contact the POS provider for support. |
| 929 | Magcard already in use | May occur with some POS systems | Contact the POS provider for support. |
| 930 | No clear password rights | May occur with some POS systems | Contact the POS provider for support. |
| 931 | Employee is terminated | May occur with some POS systems | Contact the POS provider for support. |
| 932 | Employee is locked on another terminal | May occur with some POS systems | Contact the POS provider for support. |
| 933 | Employee currently clocked in | May occur with some POS systems | Contact the POS provider for support. |
| 934 | Employee cannot delete clockout employee has no shift | May occur with some POS systems | Contact the POS provider for support. |
| 935 | Employee not scheduled for work | May occur with some POS systems | Contact the POS provider for support. |
| 936 | Employee cannot work another shift | May occur with some POS systems | Contact the POS provider for support. |
| 937 | Employee cannot clock out yet | May occur with some POS systems | Contact the POS provider for support. |
| 938 | Cannot find drawer for employee | May occur with some POS systems | Contact the POS provider for support. |
| 939 | Drawer currently assigned to another employee | May occur with some POS systems | Contact the POS provider for support. |
| 940 | Employees password was cleared but password provided | May occur with some POS systems | Contact the POS provider for support. |
| 941 | Employee is checked in | May occur with some POS systems | Contact the POS provider for support. |
| 942 | Need manager to checkout employee | May occur with some POS systems | Contact the POS provider for support. |
| 943 | No delete clockout rights | May occur with some POS systems | Contact the POS provider for support. |
| 944 | No delete checkout rights | May occur with some POS systems | Contact the POS provider for support. |
| 945 | Invalid reset password state | May occur with some POS systems | Contact the POS provider for support. |
| 946 | Set expired password required | May occur with some POS systems | Contact the POS provider for support. |
| 947 | Set cleared password required | May occur with some POS systems | Contact the POS provider for support. |
| 948 | Set uninit password required | May occur with some POS systems | Contact the POS provider for support. |
| 949 | COM error | May occur with some POS systems | Contact the POS provider for support. |
| 950 | POS INIT failed | May occur with some POS systems | Contact the POS provider for support. |
| 951 | Table does not exist | May occur with some POS systems | Contact the POS provider for support. |
| 952 | Too many print requests | May occur with some POS systems | Contact the POS provider for support. |
| 953 | Read password error | May occur with some POS systems | Contact the POS provider for support. |
| 954 | Write password error | May occur with some POS systems | Contact the POS provider for support. |
| 1001 | Insufficient terminal info | This can happen if any of the following tag request values were not submitted by the Terminal request, or have a 0 value: 1. TSN 2. SEQ | 1. Report this to PayFacto Support 2. Try to downgrade SecureTablePay version to see if the issue is resolved. |
| 1002 | Invalid transaction type | This can happen if the TTYPE in the terminal request was incorrect. | 1. Report this to PayFacto Support 2. Try to downgrade SecureTablePay version to see if the issue is resolved. |
| 1003 | Invalid server information | This can happen if the CLERK in the terminal request was invalid. The CLERK must be all numeric characters. This should not be possible because the SecureTablePay app should not allow the user to punch in non-numeric characters for the CLERK. | 1. Report this to PayFacto Support 2. Try to downgrade SecureTablePay version to see if the issue is resolved. |
| 1004 | Insufficient pos information | This can happen if the terminal request is missing required information. | 1. Report this to PayFacto Support 2. Try to downgrade SecureTablePay version to see if the issue is resolved. |
| 1005 | Insufficient payment information | This can happen if the terminal request is missing required payment information. | 1. Report this to PayFacto Support 2. Try to downgrade SecureTablePay version to see if the issue is resolved. |
| 1006 | Invalid amount information | This can happen if the terminal request is missing valid amounts in the payment information. | 1. Report this to PayFacto Support 2. Try to downgrade SecureTablePay version to see if the issue is resolved. |
| 1007 | Invalid purchase amount | This can happen if the purchase amount in the terminal request is 0 | 1. Report this to PayFacto Support 2. Try to downgrade SecureTablePay version to see if the issue is resolved. |
| 1008 | Invalid STPI property | Invalid value for property pos.server.mode The expected value for this is 2 when working with real POS. The expected value for this is 1 when working with the POS4 server (POS simulator). | Ensure the property value is correct in the gateway_sm.properties file. |
| 1009 | Invalid tender value | This can happen when the terminal request contains an invalid card type for the payment request. | 1. Report this to PayFacto Support 2. Try to downgrade SecureTablePay version to see if the issue is resolved. |
| 1011 | STPI property file in use or lost | This can happen if the gateway_sm.properties file is missing | 1. Check that the file exists 2. Reinstall STPI |
| 1013 | Insufficient batch information | This can happen for non-cash payments where the terminal request is missing parameters required for batching. These parameters can be: 1. MID 2. TID 3. DATE 4. TIME 5. BATCH 6. PTYPE 7. TRESP | 1. Report this to PayFacto Support 2. Try to downgrade SecureTablePay version to see if the issue is resolved. |
| 1014 | Incorrect batch information | The BATCH parameter in the terminal request must be a number | 1. Report this to PayFacto Support 2. Try to downgrade SecureTablePay version to see if the issue is resolved. |
| 1019 | Invalid date | The DATE parameter in the terminal request must be of the yyMMdd format | 1. Report this to PayFacto Support 2. Try to downgrade SecureTablePay version to see if the issue is resolved. |
| 1021 | Invalid terminal request | The DEST parameter in the terminal request must be one of the following: 1. STPI 2. STPICLIENT 3. STP This logic was added to restrict TGI devices from using STPI. | 1. If you absolutely need to use this for testing purposes, you can get around this by setting the property stpi.allow.tgi=1 in the gateway_sm.properties file.2. Otherwise, contact PayFacto Support for support. |