05-19-2017 12:07 PM
We are buildling a mobile checkout app.
We have everyting working now except can't seem to get the signature image back from the transaction response.
We need access to that image to add to our POS record of the transaction.
We passed "true" to the startEMVTransaction call.
EMVTransactionManager.startEMVTransaction(emvTransaction, emvTransactionListener, this, true);
But signature attribute in response continues to be blank.
Also, is there a way to get the signature later through transaction API?
05-22-2017 08:22 AM
05-22-2017 09:46 AM
Hi Richard -
Thanks for your reply.
The SDK documentation tells that the signature image is available in the transaction response. But we are not seeing it in the response. is this a bug? if so, how do we escalate it? We need to get it from the SDK so we can store it.
From SDK overview:
Step 4.The SDK returns "end of transaction" data to the POS application, including success/failure, authorization code, signature image, and EMV tags.
05-22-2017 10:01 AM - edited 05-22-2017 10:04 AM
The signature image should be returned in the transaction response from the SDK, but you cannot query for it later as it is not stored.
Is this occuring in the sandbox or production. Which mobile device are you using with the reader?
05-24-2017 09:37 AM
We are using Anywhere Commerce C2X, purchased from auth.net POS portal.
I am using a Samsung Galaxy Tab E. It's a new tablet purchased around christmas time.
The problem occurs in both sandbox and production (I have 2 C2X devices, one for each).
My developer in Vietnam has run the app in the debugger and claims that the response object contains no signature (value is blank or null). He also added an alert to display the value and it shows blank.
How can I get help to debug this? Is there any way to escalate this issue and get live development support?
05-24-2017 09:54 AM
I've made additional inquiries regarding your issue and am waiting for a response. I would also suggest opening a case with customer support since you are experiencing this with your production account. If you send me the case # via private, I can ensure it's routed properly to our mobile specialist.
05-24-2017 06:37 PM
Could you please try the updated SDK at https://github.com/AuthorizeNet/inperson-sdk-android/tree/QuickChip and let us know if this solves your issue. If it does, we'll merge into the main branch.