Just scratching my head here after a transaction I made today with a Virtual Card.
I was signing up for IFTTT Pro, and attempted to put through using a VC.
However it reported as being declined in the Monzo Feed due to an incorret Expire Date which I had indeed entered incorrect.
Now then immediately after I got the declined message, I then got a message it had gone through and indeed the IFTTT website said it had been successful also.
Both items in my feed are showing the same time also.
Now this is where I am concerned/confused… How did this get approved when the Expire date was incorrect. Is it possible for a merchant to do this? Is this possibly a freak bug? Anyone else seen this?
Thanks in advance
Any clarification would be appreciated.
Yes, I had this with Nando’s with my normal card not a virtual card
So if it is possible for a merchant to do this, why are actually allowed to do this and circumnavigate the Expire Date of the card then?
Leaving aside everything else, I would have to imagine that the merchant (IFTTT in this case) would have to take responsibility for any fraudulent transaction they put through with an invalid expiry date (similar to not using SCA)
Is this similar to how Amazon don’t bother asking for the 3 digits on the back of the card, so they take the risk?
Scarily enough I have noticed that. They either must have a way to provide its definitely you or they are taking on the risk of fraudulent transactions
Now then should banks letting through transactions like this then if they do not have the correct information, as in the Expire Date/CVC etc.
Possibly, but this does seem like a topic we need a more authoritative view about where the responsibility lies (us, merchant, Monzo) for these various combinations
Yes that would be a good call indeed, and interesting to here their view on these types of transactions.
First off, IFTTT is being super cheeky here. Sometimes you’ll see merchants doing the same where they submit a transaction with the CVC 2 code and when they get a decline, they “go f* it” and submit another one without CVC 2 - which shifts the liability on them. This usually happens outside the EU.
For expiration date, I just spent 30 min looking for proof all over Mastercard documentation that the same applies for expiration-date (as opposed to watching Selling Sunset with my girlfriend).
I am 99% certain this is the case though
Less a bat signal, more a gopher signal
Lovely, thanks for the info Arthur
We lasted only about half an episode into the follow-up “Million Dollar Beach House” before finding all the “characters” a bit grating, so Mastercard documentation is maybe not entirely without its allure
I can’t handle hearing about this Romain-Mary wedding anymore and she can’t handle hearing about Mastercard Chargeback Rules. So we’ve reached an agreement to leave each other alone
Thankyou for taking time to reply, and attempting to look through the mountain of mastercard documentation also.
That would explain then how it is possible they did this then, just concerning that companies can do this type of behavior.
If they want to take the risk of this type behavior and the included liability then its on them.
No worries. I assume you wanted to proceed with this purchase. Note that if this were fraud, you would have zero problems getting your money back - specially due to this situation.
Yeah I did want to proceed with this purchase, it just caught me a bit by surprise how it went through still with the wrong expire date on at their 2nd attempt immediately after the declined attempt.
Hadn’t seen this type of behavior before myself from a merchant.
This is one of this things I love about using Monzo, we get to see everything. Otherwise if this had been another bank in this situation most likely would not have even seen this decline, then go through immediately afterwards and thus not discovered about this type of behavior.
I think I’m more worried about the apparent exchange rate.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.