Apple Pay We could not complete your purchase

[HDFan]

For the past week or so the message "We could not complete your purchase. cancelled" has been popping up on my iMac screen once a day.



I have seen it before when using Apple Pay to purchase something via a web browser and the transaction fails for some reason. However I haven't purchased anything that way in weeks, and the message comes when I am not at my iMac. I filed a feedback request to Apple as there is no information about the purchase request - who made it, where, using what method, etc.

Talked with the Apple Cash people and one suggestion was to change the passwords on my accounts, which I did. We looked at my Apple subscriptions and none are due, so didn't come from there. Got the message again today.

Wondering if anyone else has had this problem, or has any ideas.

 

[jinxcat3]

This just started happening to me on my laptop yesterday, and happened again today. I never open the app store or even use it on my laptop, so I'm not sure what's happening either. I guess I'll change my passwords as well, but I wonder why it's happening to more than one person.

 

[7H3M4573R]

Yup. Started with me this week as well on Mojave, now several times a day.

 

[Eric Idle]

Any chance this is a fake dialogue box from a hacked browser?

 

[derfel]

I had this also, but I noted couple days back that I had a DayOne application update on the App Store and as I clicked for that to update the dialog immediately appeared. Also I have not gotten the dialog after I turned off automatic updates for the App Store.

 

[jinxcat3]

It's starting to happen more often to me now. I changed my apple id password, but it's still occurring even a few weeks after that.

 

[HDFan]

It had stopped and has now returned after Apple support guided me in removing some caches. Got 5 in a row in the early am. As soon as I dismissed one another one appeared.

 

[markwackojacko]

I have the same problem... i was/am worried it could be a virus trying to make unauthorised purchases.... has anyone actually resolved this yet?