Chase 1.5% Easy Access

jamei305

RedImp_2 said:

masonic said:

I've made dozens of contactless payments via Google Pay over several months, and many online payments using the virtual card details, and not once been required to use the physical card. I may one day encounter a retailer that doesn't support contactless or Google Pay specifically, which is when the card would be needed.

But you've not used your physical card?  My Santander card required a PIN usage before allowing contactless & indeed for 'security ' reasons every so often I'm required to enter a PIN now.

Google and Apple Pay obviate the need to use the physical card and enter the PIN occasionally. You only need to do that if you're using the physical card as contactless.

Google and Apple add the extra layer of security of authenticating your device, so using the card PIN isn't necessary.

inspectorperez

inspectorperez said:

First experience this morning of transferring money out of new Savings account.

Needed a 4 figure sum to cover credit card payment from main bank current account (not Chase) having already set up that account as a "payee" in the Payments section of the app. This account also happened to be the source of the initial deposits into Chase Savings.

The payment process was interrupted by an alert on the app telling me that the payment had been flagged up as "unusual" and to navigate to the "support" section of the app and ring the telephone number listed there.

Duly followed this instruction and ended up speaking to Chase validation team who took me through security and once satisfied that everything was bona fide, allowed the payment to proceed (which it did immediately).

This was all quite novel to me in as much as I was having to speak to someone on my mobile, as well as receive and respond to a text message, and navigate round the app at the same time. This will have been very straightforward to many, but not to me as I am used to doing one thing at a time on my smartphone.

So anyway, it was a useful learning curve, and if anything has enhanced my view of the Chase app now understanding better how these things work.

Posted this comment as it might just be of some help to others who may not be too proficient in using the features of their smartphone.

First negative experience with Chase this morning following my previous post several days ago.

Having scheduled an outgoing payment from my Savings account on Saturday, due to go out today, I received a text message at 5.00am this morning asking me to telephone "Support".

This payment was going to the same bank account destination as the deposit source for the savings account.

Following my subsequent converation with the Support line, I was informed that this was merely a precautionary measure for security purposes.

Whilst I have no problem with anything that is going to protect customers and indeed the bank from fraudulent activity, I think the fact that the payment had been scheduled in the first place and indeed the funds were going to a payee which had been properly set up in the app and to whom a previous payment had been made, I think this is OTT and will be unhappy if it happens again for no good reason!

Daliah

inspectorperez said:

Whilst I have no problem with anything that is going to protect customers and indeed the bank from fraudulent activity, I think the fact that the payment had been scheduled in the first place and indeed the funds were going to a payee which had been properly set up in the app and to whom a previous payment had been made, I think this is OTT and will be unhappy if it happens again for no good reason!

I have said this before and I say it again.

As utterly annoying as those checks are, banks make them for good reason (to reduce the APP fraud risk). If they were to carry out these checks with a set pattern, e.g. just once when a payment is made to a new payee, the fraudster would be having a ball, setting up a "good" payment , and then subsequently use that payee to launder away to their heart's content. 

inspectorperez

Daliah said:

inspectorperez said:

Whilst I have no problem with anything that is going to protect customers and indeed the bank from fraudulent activity, I think the fact that the payment had been scheduled in the first place and indeed the funds were going to a payee which had been properly set up in the app and to whom a previous payment had been made, I think this is OTT and will be unhappy if it happens again for no good reason!

I have said this before and I say it again.

As utterly annoying as those checks are, banks make them for good reason (to reduce the APP fraud risk). If they were to carry out these checks with a set pattern, e.g. just once when a payment is made to a new payee, the fraudster would be having a ball, setting up a "good" payment , and then subsequently use that payee to launder away to their heart's content. 

Don't disagree with what you say.

But, the whole purpose of having an easy access savings account is to enable same day access for whatever purpose.Typically in my case to cover any payments leaving by bank current account which aren't covered by the lowish balance I maintain within that account to maximise interest on savings etc.

I will certainly be watching this space now with Chase as it certainly increases the risk from my perspective of payments due to leave my current account being frustrated by a failed transfer from Chase Savings.

If there were to be a security intervention, it would have been better to do this at the time that the schedule was set up rather than wait for the payment due date imo!

jaypers

I would imagine that they have a huge amount of payment activity at present and it will take time for their systems and algorithms to settle down. 

Daliah

inspectorperez said:

If there were to be a security intervention, it would have been better to do this at the time that the schedule was set up rather than wait for the payment due date imo!

agree, checking at set-up time, and if amount of SO gets changed (if that's possible),  would be much smarter.

Ian601256

masonic said:

The key takeaways are:

• >4 GB RAM must be 64-bit
• Kernel information may be printed on the box if you get the chance to physically shop for your device

Just want to check I've got this right:
if the phone RAM is over 4 GB, this means that the OS must be 64 bit as well as the hardware?
Many thanks

Wheres_My_Cashback

inspectorperez said:

inspectorperez said:

First experience this morning of transferring money out of new Savings account.

Needed a 4 figure sum to cover credit card payment from main bank current account (not Chase) having already set up that account as a "payee" in the Payments section of the app. This account also happened to be the source of the initial deposits into Chase Savings.

The payment process was interrupted by an alert on the app telling me that the payment had been flagged up as "unusual" and to navigate to the "support" section of the app and ring the telephone number listed there.

Duly followed this instruction and ended up speaking to Chase validation team who took me through security and once satisfied that everything was bona fide, allowed the payment to proceed (which it did immediately).

This was all quite novel to me in as much as I was having to speak to someone on my mobile, as well as receive and respond to a text message, and navigate round the app at the same time. This will have been very straightforward to many, but not to me as I am used to doing one thing at a time on my smartphone.

So anyway, it was a useful learning curve, and if anything has enhanced my view of the Chase app now understanding better how these things work.

Posted this comment as it might just be of some help to others who may not be too proficient in using the features of their smartphone.

First negative experience with Chase this morning following my previous post several days ago.

Having scheduled an outgoing payment from my Savings account on Saturday, due to go out today, I received a text message at 5.00am this morning asking me to telephone "Support".

This payment was going to the same bank account destination as the deposit source for the savings account.

Following my subsequent converation with the Support line, I was informed that this was merely a precautionary measure for security purposes.

Whilst I have no problem with anything that is going to protect customers and indeed the bank from fraudulent activity, I think the fact that the payment had been scheduled in the first place and indeed the funds were going to a payee which had been properly set up in the app and to whom a previous payment had been made, I think this is OTT and will be unhappy if it happens again for no good reason!

Banking systems are not programmed to cross check incoming/outgoing payments and automatically authorise if the same. That in itself would be a security risk.

I assume this was your first outgoing payment to that a/c? If so I would have expected a check if this was more than a very small amount.

For ref all outgoing scheduled automatic payments are first attempted at 0500 which is far later than most other banks, who do it between 0030-0300 generally. Should the first not succeed it will automatically be attempted again at 1430 if no manual intervention.

eskbanker

Wheres_My_Cashback said:

inspectorperez said:

inspectorperez said:

First experience this morning of transferring money out of new Savings account.

Needed a 4 figure sum to cover credit card payment from main bank current account (not Chase) having already set up that account as a "payee" in the Payments section of the app. This account also happened to be the source of the initial deposits into Chase Savings.

The payment process was interrupted by an alert on the app telling me that the payment had been flagged up as "unusual" and to navigate to the "support" section of the app and ring the telephone number listed there.

Duly followed this instruction and ended up speaking to Chase validation team who took me through security and once satisfied that everything was bona fide, allowed the payment to proceed (which it did immediately).

This was all quite novel to me in as much as I was having to speak to someone on my mobile, as well as receive and respond to a text message, and navigate round the app at the same time. This will have been very straightforward to many, but not to me as I am used to doing one thing at a time on my smartphone.

So anyway, it was a useful learning curve, and if anything has enhanced my view of the Chase app now understanding better how these things work.

Posted this comment as it might just be of some help to others who may not be too proficient in using the features of their smartphone.

First negative experience with Chase this morning following my previous post several days ago.

Having scheduled an outgoing payment from my Savings account on Saturday, due to go out today, I received a text message at 5.00am this morning asking me to telephone "Support".

This payment was going to the same bank account destination as the deposit source for the savings account.

Following my subsequent converation with the Support line, I was informed that this was merely a precautionary measure for security purposes.

Whilst I have no problem with anything that is going to protect customers and indeed the bank from fraudulent activity, I think the fact that the payment had been scheduled in the first place and indeed the funds were going to a payee which had been properly set up in the app and to whom a previous payment had been made, I think this is OTT and will be unhappy if it happens again for no good reason!

I assume this was your first outgoing payment to that a/c?

OP addressed that in the post you quoted (see bolded wording)!

inspectorperez

Wheres_My_Cashback said:

inspectorperez said:

inspectorperez said:

First experience this morning of transferring money out of new Savings account.

Needed a 4 figure sum to cover credit card payment from main bank current account (not Chase) having already set up that account as a "payee" in the Payments section of the app. This account also happened to be the source of the initial deposits into Chase Savings.

The payment process was interrupted by an alert on the app telling me that the payment had been flagged up as "unusual" and to navigate to the "support" section of the app and ring the telephone number listed there.

Duly followed this instruction and ended up speaking to Chase validation team who took me through security and once satisfied that everything was bona fide, allowed the payment to proceed (which it did immediately).

This was all quite novel to me in as much as I was having to speak to someone on my mobile, as well as receive and respond to a text message, and navigate round the app at the same time. This will have been very straightforward to many, but not to me as I am used to doing one thing at a time on my smartphone.

So anyway, it was a useful learning curve, and if anything has enhanced my view of the Chase app now understanding better how these things work.

Posted this comment as it might just be of some help to others who may not be too proficient in using the features of their smartphone.

First negative experience with Chase this morning following my previous post several days ago.

Having scheduled an outgoing payment from my Savings account on Saturday, due to go out today, I received a text message at 5.00am this morning asking me to telephone "Support".

This payment was going to the same bank account destination as the deposit source for the savings account.

Following my subsequent converation with the Support line, I was informed that this was merely a precautionary measure for security purposes.

Whilst I have no problem with anything that is going to protect customers and indeed the bank from fraudulent activity, I think the fact that the payment had been scheduled in the first place and indeed the funds were going to a payee which had been properly set up in the app and to whom a previous payment had been made, I think this is OTT and will be unhappy if it happens again for no good reason!

Banking systems are not programmed to cross check incoming/outgoing payments and automatically authorise if the same. That in itself would be a security risk.

I assume this was your first outgoing payment to that a/c? If so I would have expected a check if this was more than a very small amount.

For ref all outgoing scheduled automatic payments are first attempted at 0500 which is far later than most other banks, who do it between 0030-0300 generally. Should the first not succeed it will automatically be attempted again at 1430 if no manual intervention.

This was not the first outgoing payment to that account. Previous payment was to same account (held in a UK registered bank and of many years longstanding)  in a similar (but not the same) sum and validated by Chase intervention. I also noted that Chase had looked at my Linkedin profile within the same timeframe which I don't have a problem with, but will be ears to the wall for customers reporting similar occurrences on this forum.