Thanks for the reports! We think this is happening because of a timeout somewhere in the process (hence why it often works the second time) and are going to look into why this is happening and see what we can do about it. I’ll keep this topic updated when we make progress
I had this too - I wonder whether there are two separate things here:
why is the timeout occurring (likely out of mondo control though - this could be a Wirecard issue (the prepaid issuer of mondo cards)
is it right for the transaction history to show a decline and refund in the case of a timeout (I dont think this is how transaction history behaves in ‘traditional’ banks) - this would come down to whether mondo could differentiate from the messages that come through (a timed out auth and a reversal message)0
If the authorisation message didn’t get back to the terminal before the timeout then you should expect to see an authorisation followed by an auth reversal (which will appear in your feed as a payment followed by a refund).
We have no way of telling that the initial authorisation didn’t get to the terminal until the auth reversal comes in as the messages are all asynchronous. A traditional bank only shows you transactions after they have settled (much later) and therefore would never show the first auth as it would never be presented for settlement. Some terminals are poorly configured and don’t even send an auth reversal and for these the auth will expire (usually in 7 days).
There are two things we can do:
Investigate the cause of these “declines”
Display it to the user in a more helpful way when it happens.
I think Mondo could improve its behavior lot in a few cases which currently result in multiple transactions. Mutating existing transactions to correct the actual outcome should happen in a lot of cases, in my opinion.
Thanks for all the reports! @anon73816237 is planning to look into this first thing on Monday morning so hopefully we’ll have more answers later next week
This also happened to me. It was because the merchant’s card machine was playing up. But because of the delay between it appearing as having gone through on the phone, and then showing as being refunded it did cause a minor argument. The merchant was showing it as having declined, while I was showing them it went through on the phone…
Don’t know how much use this is, but it’s happened to me twice now…once in a fast food restaurant with a big M logo where it seemed to cause the ingenico card reader to malfunction and crash and another today on a portable Great Western Railway card machine, however the portable card machine just didn’t like the card.