Yes I don’t think it’s a bug. I think there’s some sort of update that will happen in the future. Right now, I have no more information. Please keep checking the blog for updates on it!
It was a quick reply so i don’t think she actually knew what she was on about.
What’s great is often the actual Devs read threads and reply with info you wouldn’t get anywhere else but that’s usually on feedback threads to new products.
Hopefully one of the staff will read this and get a proper answer.
But I can’t think which staff to tag who would know best.
Yeah Ive had grumpy feedback from people having to enter it all manually. I think its short sighted as friends before were impressed at how easy it was and enquired more about what Monzo is all about.
The options seem to be either make them get a monzo account so you can do it the monzo way, or switch to starling or an epayment type service that does offer Apple/google pay.
It is a shame that there’s been no official response yet to say this feature is dead or just a screwup.
We disabled the apple and google pay integrations on monzo.me last month. This is because we had to upgrade the version of the Stripe integration that powers it, in order to be compliant with the new Strong Customer Authentication regulations. The Stripe update requires more work on our side to make Apple and Google pay compatible with it again.
The team that owns monzo.me (the one I work on ) is currently laser-focused on shipping our in-house Faster Payments gateway - to replace an unreliable third party. The only slot Faster Payments themselves have available in their release schedule is in early November. It was a tough prioritisation call to make, but we can’t afford to distract ourselves with other work until it is complete.
Hmm… I’m re-reading that blog post, and I’m wondering… was it possible (mathematically) for a very unlucky person to have their payment not go through for a long time, as despite the chances, pretty much every request was corrupted? I mean, they would have to have been very unlucky, but it was technically possible?
Which leaves me to add, do you have a record of how long the longest transaction took to finally go through? I’m curious.
I remember calculating this at the time, when we were asking ourselves how you’d feel if given the advice “just keep trying and it’ll eventually work”… not great to hear when you’re worried about your payment.
With a 25% failure rate if you re-try 4 times you have a 99% chance of succeeding – ((0.25^4)*100) = 0.39% failure rate. As we re-try outbound payments automatically ad infinitum every 30 seconds this meant that all outbound payments completed within a few minutes.
For inbound, it’s complicated. The sending bank might just give up and not send the payment on getting a declined response. In that case, it’d be up to the sender to send it again. Some banks automatically re-send as an asynchronous payment for this kind of decline, meaning it’ll get queued in the middle and re-tried infinitely, in which case it would have come through shortly after recovery (you can see a graph of this towards the end of that post).
Out of interest, are you able and/or allowed to say how often such chances come around?
The long term benefits of the new FPS connection far outweigh the short term hit on monzo.me (and I am sure that I am not alone in having my browser populate card details from Google anyway), but would be interesting to know just how up against you are timewise
I know all too well from work what it is like to have a fixed end date or window to hit while often seeing the start date drift, so understand the laser focus!
Thank you for the update on this. It’s good you’re so open about decisions you’ve had to make in the background.
This really is a great feature and I do hope you have time to develop this soon. It’s so much easier for people to pay me this way rather than entering details etc.
I am just wondering whether you’ve actually scheduled it to start in early November for you to start working on this? Hopefully it won’t take too long to re-implement!