Transactional payment operations
If it's necessary to identify every operation, it is possible to use commands cardAsync identified by an identifier from add-on application (e.g. UUID). This approach is convenient when the payment terminal uses multiple applications. Executed commands are stored in a separate database, and it is possible to access them based on UUID (commands are independent of other commands).
Error codes for cardAsync and cardGetTransactionInfo commands
Processing error codes are derived from PegasFM error codes extending them with error 04:
Code | Description |
|---|---|
00 | OK |
04 | Data unavailable / Command processing in progress |
32 | Incorrect number of items in the command |
96 | Parameter error in command / non-existent UUID |
41 | Duplicate UUID for ASYNC commands |
-48 | The file does not exist - The receipt does not exist (commands cardPrintTransaction, cardPrintLastTransaction…) |
-1 | The command was not processed |