Native integrations: diagnose the root cause of an issue

ISVs building their own app on top of the Handpoint Android SDK might encounter issues with their own software preventing transactions to be started or processed. In those cases diagnosing if the problem is with the ISV software or the Handpoint SDK might be difficult. Fortunately, there are a couple of steps that will help narrow down the problem.

If the ISV (or one of their merchant) reaches out saying that they are unable to process a transaction and they have built their own application on top of the Handpoint Android SDK, then the first step is to ask them to download the Handpoint Payments application on the terminal from the PAX Store and process a transaction (https://handpoint.atlassian.net/wiki/spaces/PD/pages/3858300936 / https://handpoint.atlassian.net/wiki/spaces/PD/pages/3858169881 ). This simple step will allow you to narrow down if the issue is on the Handpoint side or the ISV side.

If the same issue happens with the Handpoint application then the next step would be to download the application logs from the PAX Store and forward them to Handpoint (https://handpoint.atlassian.net/wiki/spaces/PD/pages/3858333726 ), in this case there might be some important issue that will require Handpoint to investigate. Please ask for the date/time at which the issue was reproduced to be able to easily pinpoint which part of the logs should be reviewed.
If the transaction is processed successfully with the Handpoint application then the issue is narrowed down to a problem with the ISV application. In this case it is still possible to help the ISV troubleshoot by downloading the application logs from the PAX Store and forward them to the ISV and Handpoint ( ). In this case though the ISV really is the one who will need to diagnose the issue, possibly with help from Handpoint. Please ask for the date/time at which the issue was reproduced to be able to easily pinpoint which part of the logs should be reviewed