#clyver_financial-account-last4-discrepancy

1 messages · Page 1 of 1 (latest)

rustic pathBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1457776889115443330

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

fresh mica
#

Hi, please let me know if I can add any detail or clarify anything

#

much appreciate your help

civic thicket
#

Hello 👋

Just so I'm clear, the last4 property of the Payment Method object created does not match the actual account number?

fresh mica
#

that's correct

#

As far as my observations go, this appears to only be impacting Chase accounts

civic thicket
#

Okay I found the case and some internal comments. It looks like some banks, and Chase is one of them, do not share the actual raw account numbers. They tokenize the account on their end. So Stripe cannot display the correct number because we never receive it.

fresh mica
#

We've had this integration established since 2023. We are assustomed accustomed to receiving tokenized account numbers, but could always rely on the last4 being the true last4 of the user's account number

#

This field shows the last four digits of the real account number, regardless of whether the institution uses TANs or real account numbers.

#

We have relied on this ☝️ , and this is what is no longer working as expected

#

I can confidently say this is a new issue

civic thicket
#

Unfortunately this isn't an integration issue that we can assist with direcly here. However, my colleague and I are filing this internally to flag the change in behavior you have noticed and will be updating your support ticket with this information.

fresh mica
#

okay, thank you for your help. Can you please escalate this on your end? I genuinely believe this is a serious issue, that is impacting operations at my organization (EquityZen), and could very well be more widespread.

civic thicket
#

Can you please escalate this on your end

That is what we are doing by filing this with the team in charge of this behavior.

fresh mica
#

Understood. Are you able to put me in contact with a case manager for this issue?

civic thicket
#

No I am not, I'm sorry to say. I realize that you have not heard back in 5 days but the original support case is still the best avenue for support in this

fresh mica
#

Is there anything else you'd recommend? This is a high severity issue and we haven't heard abck

#

back

civic thicket
#

Did you just notice this impact roughly a week ago? Or did it start earlier?

fresh mica
#

Yes we first noticed this the day we opened the support ticket (DEC 31 2025)

#

Presumably it started around then, as this is sensitive information and our clients immediately began writing in with concern that they are seeing bank account information linked to their profile that they don't recognize

#

(ie, the last4 did not reflect the actual last four digits of their real account number)

civic thicket
#

Okay and just to be clear, you are retrieving a FInancial Account object and displaying that object's last4 property?

fresh mica
#

that's correct

civic thicket
#

Okay thanks for clarifying

#

I have refined our internal case and flagged this via multiple approaches.

fresh mica
#

thank you very much

rustic pathBOT
#

clyver_financial-account-last4-discrepancy