Apple iOS 13 Security Issue: iTunes Payment Method Leaking Credit Card Information

Apple’s credit card service on the iOS 13 is facing a major bug which puts all of its users at risk. Potentially, some users could end up getting access of credit card details of wholly different person. Meanwhile, the company has yet to address the issue on their end.

As seen on the iPhone subreddit, some users are already giving light into this issue that could affect anybody with a credit card tied to their Apple device. According to Reddit User Thanamite, the picture feature for registering the credit card to the iPhone was faulty.

Instead of registering the user’s own credit card, the device read it as a wholly different person complete the stranger’s full name, billing address, and last four digits of their credit card. This leak is dangerous not only for the user’s money security but also their privacy. Other users in the Reddit thread have advised each other to change their Apple passwords for security.

Meanwhile, the issue has already been forwarded to Apple and the company is working on the fix. The fix for this credit card issue could be on the release of the iOS 13.1 update which would be released on September 25.

The company has yet roll out a fix to prevent this from happening as of the moment. This credit card issue also hurts on the company’s end as Apple has also ventured into the credit card business with the Apple Card.

As of now, Apple users will just have to wait until the credit card problem gets sorted out. Many users notice that the iOS 13 is still buggy as of its release. Prior to its release this month, Apple had many public beta tests to iron out any bugs and problems it’ll have once it arrives on its user’s devices.

The credit card issue was found on one of the iOS 13 betas a year prior its release. According to Reddit User helpkilbananas, his wife would sometimes get a Chinese credit card payment method from Siri prior to the iOS 13 update. While it wasn’t as dangerous as getting their details leaked, Apple was not able to explain how this issue was occurring.