Skip to main content
August 5, 2024
Question

Coop Bank feed, no OTP codes!

  • August 5, 2024
  • 1 reply
  • 0 views

I seriously can't remember the last time QBSE worked properly!

There's an open banking issue between QB and the Coop Bank that's been rumbling on for years now.

For a while now, EVERY time I log in to QBSE or open the QB app, Coop Bank sends me an OTP. As much as this is annoying, I need it to download the transaction history.

Now, Coop Bank have stopped sending QB the codes. They work if I'm banking normally but nothing is coming through for the QB app or QB login online.

Downloading csv files is laborious and not efficient especially when QB has problems importing or even uploading them.

 

Why am I paying full price each month for something that doesn't work?

1 reply

August 5, 2024

Hi EddieDelag Thanks for reaching out to us here on the Community. We sincerely appreciate your frustrations in relation to not being able to connect your bank. When you login to your account using an incognito/private window on a computer/browser select accounts > fix now are you receiving any type of error message or code?

August 5, 2024

Hi John,

    in an incog window I get:

"Something kept us from connecting to get transactions here. Let's fix that. (103)

Fix this now"
 
This takes me to the "Update your connection" window. When I enter my details, the "Fix your connection" window pops up and I get:
 
"For your security, The Co-operative Bank (UK) - Personal and Credit Card requires additional verification info. (185)
Kindly enter your OTP code"
 
Nothing happens. So I hit the "Get new code" button. After several attempts, a code appears on text and after a bit of waiting I get:
 
"That didn’t work. Try signing in again. (103)"
 
..and into a loop of misery we go. The details I'm entering are definitely correct.
 
August 5, 2024

Hi EddieDelag Thanks for trying, I really appreciate it. I'd be grateful if you can select the cog/gear icon, from the main page > connect bank and attempt to connect the same account/entering the same credentials do you experience the same error?