Got it. Thanks for chiming in. By how precise and technical your answer was may I assume that your are a Software Developer?
Are we talking about the transaction processing rules bellow?
Funds are 100% being refunded “instantly” to my NatWest Account (i.e., the balance including pending transactions matches as well). But let’s simplify things by keeping NatWest out of the equation for now.
What I can still not understand is why different Monzo users are getting different behaviour when buying something from the same merchant (Uber).
By what you typed above I assume that Uber:
- Is not sending the authorisation reversal message 100% of the time
- Has agreed (or opted in to a default) of 30 days for auto reversal of unclaimed auth holds with MasterCard.
Did I get it right? If so, any clues on why Uber may be failing to send the authorisation reversal message?
This doesn’t seem to be just randomly dropped messages. Some users are reporting that they always receive immediate refunds while others, like me, are consistently waiting for the auto reversal.
My theory is that Uber is probably sending the authorisation reversal message and Monzo is properly handling it for most payment flows (e.g., the Apple Pay crowd above). But then again, this is not working properly for other kinds of payment flows / or maybe it’s working for all payment flows but not under certain specific conditions. The problem may still be on Uber’s side, or Uber may actually be doing the right thing and Monzo may be missing some specific corner case when handling reversals.
I understand that one doesn’t simply bring unverified issues into the backlog, but it would be great to check with backend / QA folk if:
- Authorisation Reversal is working for users paying with Google Play.
- Authorisation Reversal is working for Monzo Plus and Monzo Premium users paying with Virtual Cards.
I’m a Software Developer myself and I happen to have a Monzo Premium account with Open Banking API access to a NatWest Bank account. I’m happy to provider further details and volunteer to “test in production” if any Monzo insiders feel like investigating the issue. Feel free to DM me.
The truth is: Regardless of the root cause of the problem, the issue is very inconvenient, and at the moment it’s only affecting my Monzo account (mine, and from at least 3 other users so far).
I would be very grateful if someone from engineering could have a look at it.