#jason02012023
1 messages · Page 1 of 1 (latest)
Hello, happy to help look in to this. Can you provide the ID of the card? And did you get an event for this update? Or did you just notice that the fingerprint had changed when retrieving the card again?
We got an update for the customer source being updated. We're not listening to any related events for Connect account.
The fingerprint didn't change, it was an update of the expiration date of the card
@ruby mantle is it fine to send card ids on a public channel? Or should I DM them to you
Safe to send the ID here
It is your API keys and live secrets that are the sensitive ones
card_1NIjuQJ7xI3N7Avq11CKKghj
and card_1NIjuSQtIiXUlKGoqcKt2Tq2
First is on Customer, second is on Connect
Same card (fingerprints are the same), but the first one on the Customer was automatically updated for expiration date (evt_1NTrMbJ7xI3N7Avqt8GoMDeM) but the second one on Connect was not
Gotcha, thanks for the IDs, checking in to them.
Thanks!
evt_1NTrMbJ7xI3N7Avq2oTXSUIA is the automatic update event on the customer sorry
Actually for card updates and connect, I think our support team would be better suited to help you. It may be a platform or connected account setting that prevented the card from being updated properly on the connected account https://support.stripe.com/?contact=true
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.