When I try to top up using Apple Pay, I consistently get an error:
"Sorry, your payment did not go through. Please check your card ddetails entered, check with your bank, or try another card."
This error appears when tapping on the Apple Pay button in the app, before being asked which Apple Pay card to use. So it's nothing to do with a particular card issuer, but a bug in the app.
It also doesn't like my manually-entered card number with an error that the format is wrong. Therefore how can I top up?
Hey @NFH thanks for posting this here. When you are making the top up and select Apple Pay are you getting the above error before you select continue?
When you are entering your card details what error are you receiving about the format?
@Three_Niall With Apple Pay, you don't enter card details. You select the card from your Apple Wallet, but it doesn't get as far as asking me to select a card, instead taking me to an error page with the above message.
Thank @NFH I understand you won't be asked to enter card details using Apple Pay however I can see you were also speaking about difficulties with using your card separately?
Is the error happening immediately when you hit Apple Pay or are you able to select continue and is this in the app?
@Three_Niall It says "Card number is incorrect", even though I have double-checked that it is definitely correct.
I'd love to look into this for you, can you try screen recording the process and pop it through to me here on PM so I can have a further look at what is happening.
I reproduced the issue on multiple devices with multiple Three accounts, but I later found a solution. I went to Top Up (tab at the bottom), then Payment Methods, and then deleted Apple Pay as a payment method. I then tried again, and the My3 app took me to Apple Pay instead of to an error message. It appears that the My3 app had incorrectly cached some corrupt data for Apple Pay, and this caused the My3 app to send a malformed message to Apple instead of taking the user to Apple Pay to choose a card and authorise a payment. So in summary, it's definitely a bug in the My3 app, but there's a solution.