Response Codes
The table below lists response/result codes returned by the SDK/plugin. Handle these codes in your UI and backend reconciliation logic.
| Response Code | Message |
|---|---|
| 0 | APPROVED |
| -1 | Transaction timeout |
| -2 | Device attestation error or security flaw |
| -3 | Invalid activation code |
| -4 | Transaction connection error |
| -5 | Transaction sending error |
| -6 | Transaction receiving error |
| -7 | Transaction pack request message error |
| -8 | Transaction unpack response message error |
| -9 | Original transaction NOT exist |
| -10 | Transaction has been voided |
| -11 | Not support refund |
| -12 | Not support void |
| -13 | Host declined the transaction |
| -14 | User cancelled the transaction |
| -15 | Transaction was aborted with some reasons, please try to get device status or do warmup |
| -16 | Transaction amount exceeds the allowed contactless transaction limit |
| -17 | The transaction is declined by the card and cannot perform the transaction |
| -18 | Invalid card, please change another card and retry |
| -19 | Invalid EMV parameters, please check EMV configurations |
| -20 | Card reading incomplete, please tap and hold card steadily |
| -21 | Our service is temporarily not available to process your payment, please check the payment status in backend portal |
| -22 | Device not activated |
| -23 | Invalid request |
| -24 | Bluetooth can not detect MPOS D177 device, please check the MPOS D177 is available or not |
| -25 | Bluetooth disconnected now, please check the MPOS D177 is available or not |
| -26 | Bluetooth disabled now, please enable it |
| -27 | The location permission is missing now, please allow it |
| -100 | Unexpected error, need to restart SoftPOS application by warmup |
You can reference these numeric codes from Transactionsuccess.rspCode. Map them to user-friendly messages and retry/fallback logic in your app.