Technical Error

[hennaboy]

Expected Behavior

Payment Accepted

Current Behavior

Random occurrence. Payment will be processing for a longer period of time and then return Technical Error Payment Cannot be Processed.

If you check in the Zettle account sometimes the payment will have been taken. Other times the payment has not been taken.

Steps to Reproduce

Happens at random so unable to state.

Context

Kotlin, Android 10, Latest SDK

[bobzettle]

Hi @hennaboy,

Sincere apologies for the delay in getting back to you!
We are working on a solution to this timing problem that we hope will remove this deviation.

[To0m]

We have exactly the same problem. I am looking forward to a solution.

[To0m]

Hi @bobzettle ,

are there any news regarding this issue?

[hennaboy]

For those following this, the only way I have managed to resolve this is by purchasing a new card reader.

The error seemed to then disappear. Not an ideal solution at a cost of £79 per reader but perhaps it will give the devs a heads up where they should be looking.

[bobzettle]

Hi @To0m,

We are still working on this issue. We have had another big thing as our top priority to fix first, but now this is in our spotlight.
There are a lot of different parts involved in this issue, ordering a new reader might improve the situation.
Also making sure the wifi/data is stable, no disturbance in bluetooth etc.

But we know that it's not always possible to control the environment, and the disturbance can come from other non-controllable parts, so from the SDK we are focusing on getting it more fault tolerant for all different hiccups and adding ways to recover if we end up in this state.

Hope to have more news in the coming weeks.

[fparmak]

Hi, now we have a new version out that we think will mitigate the false "Technical error" that still completes the payment, often resulting in a double payment situation.

Please give it a go and reach out during migration if there's something we can help with. A full migration guide can be found here.

[hennaboy]

Tested with 2.1.4

The same technical response was received and the only way to check is to log in to the admin area to see if payment has actually gone through.

[hennaboy]

Just having a Technical error it may or may not have gone through is basically stating we are not checking so do it yourself!

Why is there no check in the technical error response. There is a transaction ID for the payment surely if it looked to see if that was present in the database of payments then it would be able to return a better response.

Check if transaction id present in case of technical error

Present -> respond with Technical error payment was taken
Not Present -> respond with Technical error payment was not taken

Far more informative and as a merchant I do not need to request the customer to try again or risk upsetting the customer charging them again and having done so twice.

[Rubiksrls]

Hi, any updates about this?

[hennaboy]

The issue is still present and I believe the card reader is faulty.

Replacing the card reader resolves the issue. So if you have this issue and your reader is within 12 months contact Zettle sales for a replacement.

[Rubiksrls]

HI, I tried with different card reader. THe issue is present with the official Zettle Go Android app and when do a payment with Apple Wallet (everthing works well with simple credit/debit card)
I obtain a techincal error and reader show PLEASE WAIT ... I must kill the Zettle Go App and restart it to do a new connection and payment

[stigssonfabian]

We are suffering from this issue as well. The API works fine for card payments but for Apple pay we receive errors frequently.

[mfareed-pp]

Hello!
We have identified the issue and that we are working on providing a solution as soon as possible.