Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
When the CLI doesn’t give the answer you expect.
| What happens | Why | What to do |
|---|---|---|
| No result file at all | appsettings.json is missing or unreadable, or the action is misspelled (actions are case-sensitive). | Put appsettings.json beside the program; check the -a= spelling. |
The API request was not successful. | The gateway couldn’t be reached, or answered with an HTTP error (for example 401: a wrong or revoked key). | Check the machine’s internet access to posgateway.paymentsmojo.com on port 443, and the key in the POS. |
The request to /Links/… timed out. | No answer for 10 minutes. | For a sale, look it up by its order id before trying again. |
A gateway message in <Message> or RespMessage | The gateway’s answer: see Errors. | As listed there. |
-d to a command (or set "runMode": 1 in appsettings.json) and the CLI writes a log of the run to Logs\
beside the program. Logs never contain card data or the key’s secret. Send the log with your question to
hello@paymentsmojo.com.