Citizens Bank CC application - "Unable to verify identity" despite all CRs unfrozen

[Onetime91]

Just chiming in to say I have the same problem.

[jefeporsche6pm]

The only way I see this being resolved is if we all write a letter to their CEO or Corporate office and get some attention looked into their system. 

[northway]

Just a slight update. After trying about 30 times over the last few months, all of a sudden I reached a new page that said I didn't have any pre-qualified offers but I could select one of the 4 cards to apply for with a hard pull. I continued and the app went pending.

3 days later, I get a hard pull at 6am on EXP, and after chdcking the portal, I was approved for the Summit Reserve for $40K. Not sure if being Private Bank had anything to do with the approval amount.

[smcj]

---

@northway wrote:

Just a slight update. After trying about 30 times over the last few months, all of a sudden I reached a new page that said I didn't have any pre-qualified offers but I could select one of the 4 cards to apply for with a hard pull. I continued and the app went pending.

3 days later, I get a hard pull at 6am on EXP, and after chdcking the portal, I was approved for the Summit Reserve for $40K. Not sure if being Private Bank had anything to do with the approval amount.

---

Good to hear -- I guess they can un-break it at least some of the time.

No change at this end.  Still "unable to verify identity" no matter what I unfreeze.

Perhaps one day Citizens will grow up and learn some systems administration - but for now, not worth my time to chase around; that their people are no help deciphering this thing is already a known quantity.

[GalactiCC]

i am having the same issue. i have tried 10 times already. which credit bureau did you have unfrozen at the time it went through?

[northway]

---

@GalactiCC wrote:

i am having the same issue. i have tried 10 times already. which credit bureau did you have unfrozen at the time it went through?

---

They pulled Experian, but I've had everything unfrozen either way.

One thing that may have occurred is this time, it autocorrected the address to a different city within my ZIP code that's still valid, but I'm pretty sure I've tried that previously.

[smcj]

---

@northway wrote:

---

---

They pulled Experian, but I've had everything unfrozen either way.

One thing that may have occurred is this time, it autocorrected the address to a different city within my ZIP code that's still valid, but I'm pretty sure I've tried that previously.

---

I didn't try the autocorrect address this time, but "a different address" (meaning a variant -- though definitely not a different city or base street name or zip code) was the first thing the rep asked about waaaaay back when I first encountered this issue.  In my locality there are a couple of variants on my address -- the USPS-official one doesn't match the autocorrect one, for example.  I believe the autocorrect pulls from Google or some other shared-by-a-bunch-of-entities database.  When I was chasing my tail on this I tried multiple variants, including the autocorrect one, and none made a difference.

But this last time, I went with the USPS-official one, since it's, well, official, and it also matches my CRs.  FWIW.  I agree that it isn't likely the issue in play.  Honestly feels like a straight-up data access fail, probably with whatever DB (or subcomponent of same) is used for the "verify".