Quicken Community is moving to Single Sign On! Starting 1/22/21, you'll sign in to the community with your Quicken ID. For more information: http://bit.ly/CommunitySSO
Error w/Direct Connect and Wells Fargo

This discussion was created from comments split from: One Step Update Error: Sorry! An unexpected error has occurred.
0
This discussion has been closed.
Comments
I spoke w/ Wells Fargo support team about this Quicken OneStepUpdate issue. As of Thurs Apr 4, 2019 you are not allowed to enter anything in the MEMO of your online payment.
RESOLUTION: Edit you online payment and REMOVE any characters in the MEMO column of the payment. Then try OneStepUpdate again. (I did not have to reboot. I did not have to close/re-open Quicken)
Wells Fargo is actively working to resolve this issue!!
Thank you for taking the time to share the details of this issue and the steps to resolve it with the Community!
Sarah
Any suggestions?
Cheryl63
Details:
If I attempt to setup a NEW online payee by issuing a check with text in the memo field, the bank rejects the command with an error. I have tried removing commas, dashes, and any sort of non-alpha characters from the memo. No luck.
Workaround: I can setup the new payee with a completely blank memo field, issue a "Send Online Payment" command and the bank (in this case, Wells Fargo) will accept the command and issue a check number in response, as it has done for years. Then, I can come back with a new transaction that has text in the memo field and successfully transmit a "Send Online Payment" command... it works as it always has in this second case.
This appears to be a bug.
It also appears to have been reported before in this thread:
https://community.quicken.com/discussion/7857341/adding-new-online-payees-payments-will-not-send