Phones that are compatible with the Chase App

masonic

Yellowman said:

Yet app-only banks such as Atom, Tandem and Zopa (and the PayPal app) work perfectly and securely on my 'old' (Android 8.0 max) mobile phone.

All of those banks you mention developed their apps a couple of years before Chase UK (and none of them offer a current account, which requires a higher level of security due to the ability to transfer money anywhere at any time). As mentioned above, the cut-off is generally made at the point of release, and has to be made somewhere. The Chase app runs fine on my 2017 vintage Android 8.1 sub-£100 phone, though I use it on my 2 year old Android 11 device. Based on the standard 2 year support window, we're talking about the exclusion of devices made in 2015 and earlier, to not have been upgraded from incompatible 8.0 to compatible 8.1. It would be unwise to do online banking on such a vulnerable OS. It is equivalent to using Windows XP and Internet Explorer, which most banks won't let you do now. However, if an app just lets you monitor and apply for fixed term savings accounts, and move money to a preset linked account, then the risk is obviously a lot lower.

Ian601256

I had the same problem with the Chase app. I asked them if it would work on a Samsung A13 and they said yes. When it didn't I raised a complaint and they have given me £75. What they haven't done is update their web site and call handler training to explain that the App requires a 64 bit phone. Bearing in mind all their competitors' apps work on 32 bit phones, and phone manufacturers are still introducing 32 bit phones (the A13 came out this year), it seems a poor decision from Chase.

400ixl

Yellowman said:

Yet app-only banks such as Atom, Tandem and Zopa (and the PayPal app) work perfectly and securely on my 'old' (Android 8.0 max) mobile phone.

Not really a true statement. There are zero day exploits out there for Android 8.0 which have not been and will not be patched, with more being found all of the time. One of these exploits or a future unpatched exploit could be the one that can be used to compromise your account.

Being on an unsupported operating system with financial applications is not a sensible thing to be doing. Personally I believe banks should be protecting users from themselves and if the OS is no longer in support the app should no longer work.

400ixl

refluxer said:

ericlered7 said:

Is it possible to use the Chase app on one phone, but for two accounts? By logging in and out? Sorry if this is a stupid question, but my girlfriend's phone is only 8.0 and she can't set up an account.

I don't think so because there is no log in and out option - logging in to the app takes you straight to your account and the app is only going to accept the log-in credentials of the customer who set up the account.

Android phones (at least recent versions) support multiple user profiles. Whether this could be used I haven't tried, don't think it will as they are usually sandboxed environments, but may be worth an experiment.

TELLIT01

The concerns about the Chase app have come at the right time for me.  I'm looking at savings accounts and many are managed by Chase.  Despite my phone only being 2 years old Samsung I'm inclined to avoid anything linked to Chase.  I have no idea whether the version of Android on my phone 16, 32, 64 bit or whatever, and I suspect most for most phone users that isn't high on their list of priorities when purchasing.

Suggestions that somebody pay out £150 for a 'cheap' phone is crazy.  If it's cheap it will probably also not run the app in 12 months time.  What then - another £150 up in smoke?

Beddie

masonic said:

Yellowman said:

Yet app-only banks such as Atom, Tandem and Zopa (and the PayPal app) work perfectly and securely on my 'old' (Android 8.0 max) mobile phone.

All of those banks you mention developed their apps a couple of years before Chase UK (and none of them offer a current account, which requires a higher level of security due to the ability to transfer money anywhere at any time). As mentioned above, the cut-off is generally made at the point of release, and has to be made somewhere. The Chase app runs fine on my 2017 vintage Android 8.1 sub-£100 phone, though I use it on my 2 year old Android 11 device. Based on the standard 2 year support window, we're talking about the exclusion of devices made in 2015 and earlier, to not have been upgraded from incompatible 8.0 to compatible 8.1. It would be unwise to do online banking on such a vulnerable OS. It is equivalent to using Windows XP and Internet Explorer, which most banks won't let you do now. However, if an app just lets you monitor and apply for fixed term savings accounts, and move money to a preset linked account, then the risk is obviously a lot lower.

I was going to write something similar, but you saved me the effort!

Olinda99

ericlered7 said:

Is it possible to use the Chase app on one phone, but for two accounts? By logging in and out? Sorry if this is a stupid question, but my girlfriend's phone is only 8.0 and she can't set up an account.

yes if you have a samsung galaxy S phone eg S21 etc

2010

TELLIT01 said:

The concerns about the Chase app have come at the right time for me.  I'm looking at savings accounts and many are managed by Chase.  Despite my phone only being 2 years old Samsung I'm inclined to avoid anything linked to Chase.  I have no idea whether the version of Android on my phone 16, 32, 64 bit or whatever, and I suspect most for most phone users that isn't high on their list of priorities when purchasing.

Suggestions that somebody pay out £150 for a 'cheap' phone is crazy.  If it's cheap it will probably also not run the app in 12 months time.  What then - another £150 up in smoke?

I`m with you on this.

People are buying new phones (whatever the cost) just to open a current bank account to then open a savings account to get the great rate of 1.5%, which will soon be caught up with by others who make it easier to open an account.
And how much are they putting in this Chase account after jumping through hoops to get it?
I would guess not enough to justify the hassle and cost involved.

masonic

Ian601256 said:

I had the same problem with the Chase app. I asked them if it would work on a Samsung A13 and they said yes. When it didn't I raised a complaint and they have given me £75. What they haven't done is update their web site and call handler training to explain that the App requires a 64 bit phone. Bearing in mind all their competitors' apps work on 32 bit phones, and phone manufacturers are still introducing 32 bit phones (the A13 came out this year), it seems a poor decision from Chase.

Chase certainly has a case to answer regarding being too slow to respond to the revelation that some device manufacturers are still loading an inappropriate 32-bit operating system on their 64-bit phones. It has come as a surprise to all concerned, but Chase has continued to give unclear information to customers and potential customers who have queried this. However, the main fault lies with the device manufacturers who appear to be deliberately limiting some of their cheaper devices, the only rational explanation for which is that they want to push people towards a higher price point. The A13 has 64-bit hardware, so can run 64-bit Android. Some versions of it do run 64-bit Android. It is a deliberate choice by Samsung to load the OS designed for the wrong architecture, thereby forcing the hardware to drop into 32-bit compatibility mode.

Olinda99

As I understand it, it was (is) difficult / impossible to get 32bit processors so they installed 64 bit processors on the cheaper phones as these were plentiful

What WERE easily available (and cheap) were / are 32 bit peripherals (modems, screen drivers etc) ie bits other than the cpu.

Building with them made the phone cheaper, but of course it meant a 64 bit operating system could not be used even though there was a 64 bit processer.