#nielsen_webhooks

1 messages ¡ Page 1 of 1 (latest)

wise jasperBOT
#

👋 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/1347282176143786035

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

quaint junco
#

Hello! It's not currently possible to test that event type in test mode, unfortunately. It's a gap we're aware of, but we currently don't have an ETA for a change in this area.

slow epoch
#

ok, not even a test card that would automatically change it's information?

quaint junco
#

Nope. It's just not possible to trigger that in test mode today, period.

#

The best you can do is mock it on your end.

slow epoch
#

Ok, and to confirm. All I need is to do is listen to payment_method.automatically_updated event right?

quaint junco
#

All you need to do in order to do what?

slow epoch
quaint junco
#

Yes, if you want to be aware when a saved Payment Method is automatically updated you would listen for those events.

slow epoch
#

Does stripe have any sample code for this feature at least?

quaint junco
#

Sample code for what exactly?

slow epoch
#

how to handle the payment_method.automatically_updated webhook event

quaint junco
#

We have documentation about handling events in general. Are you asking for that or something else?

slow epoch
#

Yea I have seen that though, I was hoping for some more specific to the automatic card updates, but this is fine.

quaint junco
#

Sorry, I'm not sure I understand what you want. What problem are you trying to solve? What are you trying to build?

#

I'd love to help, I just don't quite understand what you need.

#

Like why do you want to listen for these events in the first place?

slow epoch
#

I have an integration that listens to stripe webhooks. We already handle events for payment intent updates. So I was hoping to see Stripe's "recommended" way to handle automatic card updates via the appropriate webhook event.

quaint junco
#

We don't have a recommendation. Those events are informational. If you want to know about them you can listen for those events and do whatever you want when you receive them. If you don't want to know or don't have any actions to take when a Payment Method is automatically updated there's no need to listen for those events. The thing I'm trying to understand is why you want to be notified when this happens? What action(s) do you want to take when you receive one of these events?

slow epoch
#

When our customer's credit cards expire, we would like to automatically update the credit card information, without having the customer log into our application and have them manually change it themselves

quaint junco
#

I think there might be a misunderstanding. Our card updater runs on our end, it's not something you can trigger on your end. We update cards whenever possible regardless of you listenting for these events or not.

slow epoch
#

yes, but our custoemrs dont access this from stripe directly

#

we save that info in our database as well

#

so in our app, the customer will see their credit card information is "expired" but it may not be if it was automatically updated via Stripe

quaint junco
#

Oh, okay, so you keep track of card expiration dates on your end, and you want to know when we update a card with a new expiration date so you can save that new expiration date on your end?

slow epoch
#

correct

quaint junco
#

Gotcha, that's the part I was missing. I didn't know you were storing this information on your end. So yeah, you can listen for these events, and in the payload you'll get the Payment Method object, and in there you'll see the new expiration date which you can then update on your end. We don't have sample code for this specific scenario.

slow epoch
#

Ok perfect.