You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We regularly have double transactions and thought that the users are impatient. This is from a user who made 3 double transactions in a row (on multiple days, so with big time intervals between them):
The issue I am encountering is not the delay in the transaction processing. It is rather once the transaction gets completed and then it says "finish your payment..." on the purchases tab where you see the "add money money" option. This gives me the perception that the transaction has not gone through successfully and that's why I have to go ahead with finishing the payment for the transaction. When that happens, it charges twice.
To Reproduce
No idea, but hopefully the above is useful for locating the code where something has to change.
The text was updated successfully, but these errors were encountered:
There was a support request from a user who didn't try to pay the second time. Impersonating the user indeed I saw the message about finishing the purchase (which actually was not possible without adding more money to the account, maybe the calculation was off because of pending charges) or cancelling it. Trying to finish the purchase asked for payment information again.
Describe the bug
We regularly have double transactions and thought that the users are impatient. This is from a user who made 3 double transactions in a row (on multiple days, so with big time intervals between them):
The issue I am encountering is not the delay in the transaction processing. It is rather once the transaction gets completed and then it says "finish your payment..." on the purchases tab where you see the "add money money" option. This gives me the perception that the transaction has not gone through successfully and that's why I have to go ahead with finishing the payment for the transaction. When that happens, it charges twice.
To Reproduce
No idea, but hopefully the above is useful for locating the code where something has to change.
The text was updated successfully, but these errors were encountered: