#fares-helmy_api
solar mountainBOT
š 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/1486293639809339534
š Have more to share? Add more details, code, screenshots, videos, etc. below.
rose escarp
Here are the questions again:
1. What is the recommended way to detect that card details (e.g. expiry or PAN) have been updated by the network/issuer?
2. Can we rely on differences in:
ā¢ payment_method.card.exp_month / exp_year
returned in PaymentIntent / SetupIntent responses as a signal to persist updates?
3. Are webhooks (e.g. payment_method.updated or similar) the authoritative source of truth for such updates?
4. In network token (e.g. Apple Pay / Google Pay) or wallet scenarios, can the expiry returned differ from the underlying card, and how should we treat those values?
5. Are there any cases where Stripe updates card details internally for authorization purposes but does not surface those updates back to the merchant?
half knot
We talk about this here. General recommendation is to listen for the payment_method.automatically_updated event
rose escarp
So the values returned in the payment response itself should not be used?
half knot
Not sure I understand the Q
rose escarp
half knot
Well that's the payment method details at the time of the payment