nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Chase - OL-393-A Errors [Edited]

CaveCreek

Quicken is unable to update your accounts.

Find more posts tagged with

Online Banking

Add/Edit Transactions

Windows

Accepted answers

[Deleted User]

What I have found is that this error usually means you have Online Billpay set to "Yes" for an account that is not eligible for Billpay at your financial institution. Go to Account Details and check all of your accounts at Chase. If any accounts are not accounts you use billpay for, you need to change the appropriate billpay option to "No".

Quicken Jasmine

Hello All,

We do now have a New Active Alert regarding OL-393-A Errors with Chase. You may follow this link to bookmark the alert in order to remain up to date on any new information, ETAs, or resolutions that may occur.

We do apologize for the inconvenience this causes and we appreciate your support and patience.

All comments

DetroitRick

@Chris_QPW Thanks for the explanation. Yes, that appears to be exactly what is going on now for me. And my Chase account does have the "Bank Online Bill Pay" turned on in Quicken (and Quicken Bill Pay Manager off). At least, even with this error showing, I am still getting the correct transaction downloads and account balances through Quicken. So I can probably ignore error message for now. Worst case, I can shut of bank bill pay in Quicken - inconvenient but not a big deal for me. And I'm following that announcement that you referenced in the interim. Thanks.

[Deleted User]

@Lewis Bernstein - this error is totally in the hands of Chase. It is not a Quicken error. Quicken can only alert Chase and give us updates on Chase's progress, but again, it is Chase's error. Quicken is helping Chase to get the issue resolved.

weshough

For the past several days I am receiving error message 393-A after my online update for one financial institution (Chase Bank). Although the error message states the accounts with Chase are not updating, it appears that they actually are being updated. However, at the top of the account transaction window, where normally it shows the date and time of the most recent update, this is empty.

DKNY

@CaveCreek your solution totally worked for me thanks for taking the time to post it

Chris_QPW

@bobandsherry82 I have observed that when you setup a Chase checking account for Direct Connect, the Bill Pay option is automatically turned on. You don't have to do anything to turn it on.

Jerry Pederson

This is a screenshot of my Chase account detail->Online Services Tab

I have used Chase's Bill Pay for years and never got this 393 error. strange, my Chase accounts all update properly, but since 5/09/22 I get this 393 error message. Like I said earlier, disconcerting.

Chris_QPW

@Jerry Pederson for the people that are actually using the Chase Bill Pay the best you can do is report the problem as this announcement states.

https://community.quicken.com/discussion/7913242/updated-5-10-2022-chase-ol-393-a

Since this broke only for Chase Bill Pay, and for users no matter what version, and it is Direct Connect, which means that Quicken talks directly to Chase for this, the problem is on the Chase side, and they will have to fix it. But it seems that Quicken Inc might be gathering the information from users logs to help Chase identify the problem. (Or maybe just to satisfy people that they are "doing something", when in reality they can't do anything, because it is out of their control).

Ps56k2

Just tried the usual OSU for Chase - today Wednesday 5/11/22 - and it WORKED.... as it normally should.

Downloaded any transactions, and uploaded a Bill Payment - NO Error - and checked on the Chase website for the Bill pending...

SO... at least for me - as I didn't change the Online Setup, just waited a few days - and for me, it is working again -

Ps56k2

Lewis Bernstein said: [Removed - Disruptive] The error is OL-393-A

There is an ongoing Chase OL-393 thread AND Alert - and have suggested this posting be merged into that one...

William Fee

How can I fix the connection?

Ps56k2

And …. It’s back - to the OL-393 error.
So - no error this morning, and was just waiting for dust to settle - made NO changes -
and now in the afternoon the error message is back,
but with complete upload/download of transactions.

Weird - I get the downloaded banking transactions,
along with the uploaded Bill Payments - and then also get the OL-393 error message.

Chris_QPW

William Fee said:

How can I fix the connection?

See this announcement:
https://community.quicken.com/discussion/7913242/updated-5-10-2022-chase-ol-393-a

Cyril

Deactivating Bank Bill Pay restored my direct download without error. I don't use it and do my payments from Chase website. It was frustrating when I couldn't get my transactions for several days. Now it works!

unknown

This content has been removed.

Charlie236

No issue with TD bank since Mondo update a couple weeks back. Chase did perform Bill Pay and Transfers between Checking & Savings, as usual, BUT, there is still the OL-393-A Error persists.

Yoramariel

I am receiving OL-393-A error upon downloading Chase data when "Bring My Payment Information Up To Date" is checked. When unchecked, no error. Transactions are downloaded in either case.

Chris_QPW

Yoramariel said:

I am receiving OL-393-A error upon downloading Chase data when "Bring My Payment Information Up To Date" is checked. When unchecked, no error. Transactions are downloaded in either case.

Read @Quicken Janean answer, and click the link "here".

MarcStone

Problem still exists several days later. Transactions download, but the error messages continues to display. It's as if Quicken software doesn't see the data downloading.

DRMick

Getting Chase 393A error. But transactions were downloading OK. Turned off "Bank Bill Pay" . No more error. Thanks

bartsot

I've been getting the OL-393 for 4 days now, BUT I just set up a payment using the (Quicken) online center as I normally do, and the payment instruction went through to Chase even though I got the error message. Checked that it arrived at Chase using the Chase web site.

ssc2755

:/ For the last week, I have been unable to sync my bank info with CHASE. Please fix this soon or I will have to end my subscription. :/

ssc2755

I cannot continue using Quicken if I cannot get access to my bank accounts at Chase.

Sherlock

If you haven't already, you may want to review: https://community.quicken.com/discussion/7913242/updated-5-10-2022-chase-ol-393-a

Quicken Janean

Hi @MarcStone,

I am sorry that this issue is still happening. Can you clarify if you are using Direct Connect Bill pay? If you do not use Direct Connect Bill pay, then we suggest that you disable it. This should resolve the error.

However, if you do use Direct Connect, then please do not disable Direct Connect Bill pay. We ask that you go to Help > Report a problem to send us your logs files and add 'Attn: CTP-3750' to the title/subject line.

I am sorry for the trouble caused.

Quicken Janean

cheez1950

Thank you. Deactivating Bill Pay worked for me.

Dayzee

How can I stop getting OL-393-A error message on my Chase account? Everything was working fine until a few day ago.

Jerry Pederson

Granted deactivating Bill Pay puts a bandaid on a problem that still needs to be resolved. It is time for Quicken to step up to the plate and resolve this problem.

Chris_QPW

Jerry Pederson said:

Granted deactivating Bill Pay puts a bandaid on a problem that still needs to be resolved. It is time for Quicken to step up to the plate and resolve this problem.

They can't. It is a Chase problem.

Jerry Pederson

Then Quicken should contact Chase. Quicken is our service provider. We pay for the service to be error-free (for the most part). It is Quicken's software that needs to interface with Chase's programs/software. Quicken s/b leading the way and getting this resolved.

Chris_QPW

Jerry Pederson said:

Then Quicken should contact Chase. Quicken is our service provider. We pay for the service to be error-free (for the most part). It is Quicken's software that needs to interface with Chase's programs/software. Quicken s/b leading the way and getting this resolved.

I'm sure that has already been done. But after contacting them and pointing it out, which many Chase customers have already done. What do you expect? Quicken Inc and dictate to Chase on when they should get something fixed.