#wchiquito_sepa-fingerprint
1 messages ¡ Page 1 of 1 (latest)
đ 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/1483585842772447232
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there,
just to clarify, are you asking why the finger print for a SEPA DD payment method changes?
Since SEPA DD is async, Stripe creates a temporary fingerprint when creating the Payment Method, but then validates IBAN etc. with the bank and computes the final fingerprint. After that, the fingerprint should not change again.
There are two questions: 1) Why does the fingerprint change? (your previous answer would explain this) and 2) Why isn't the webhook payment_method.updated fired due to the fingerprint change?
Let me do some more digging. I might have been a been hasty with my response. Let me actually investiagte a bit more.
Is this a connect setting?
No, it's not a connect setting.
Got it.
Can you share your account ID where you see the fingerprints changing?
For security reasons, I'm not allowed to provide this type of information, which is considered sensitive.
I understand the concern but without sharing the ID, I am not fully able to support. Can you share a different ID, like a Payment Method ID of a SEPA DD for that account? In general there shouldn't be any concerns sharing those IDs since they are useless for third parties.
It might be easier to chat with support directly to via https://support.stripe.com/contact they can look up the object(s) involved and clarify what's causing this
wchiquito_sepa-fingerprint
I'll try to start a chat with support directly to discuss the issue. @blazing bison, thank you so much for all your help.
Sounds good! Hopefully they can clarify quickly!