#rpoulose - webhook events

1 messages · Page 1 of 1 (latest)

meager cliff
#

hey there! Which client do you use?

#

Those events are not interchangeable, no, as the underlying objects are of different types

feral moat
#

Thank you for the response. Do you mean which client I use for accessing Stripe - it is the Stripe dashboard. Our application uses both web and IOS clients (respective Stripe client libraries). We also use Stripe APIs extensively

#

So looks like we have to use payment_method.automatically_updated or its earlier version (Payment_method.card.automatically_updated )?

meager cliff
#

The pervious name was payment_method.card_automatically_updated and if your endpoint API version corresponds to that name then we'd adapt the event to send that version

feral moat
#

Our API version is 2019-02-19. Hence I don't see a way to select payment_method.automatically_updated when creating webhooks. I can select payment_method.card_automatically_updated when creating webhooks. That is in line with the documentation about which events are supported in 2019-02-09. However, what is confusing is that in the actual events listed for a customer who has had his card details updated by the network, I see only payment_method.automatically_updated (not payment_method.card_automatically_updated ) events. I would have thought since our version is 2019-02-19 I should see only payment_method.card_automatically_updated.

meager cliff
#

The docs refer to the latest name and don't take your API version into account

#

The delivered events will consider the configured endpoint API version, though

feral moat
#

That does not seem to be what is happening. Per the documentation here https://stripe.com/docs/upgrades#2020-08-27 payment_method.card_automatically_updated should be available for versions before 2020-08-27. Our version is 2019-02-19 but I don't see payment_method.card_automatically_updated events.

meager cliff
#

Can you share your account id, or one of your endpoint IDs?

feral moat
#

Do you mean the webhook id? I can also share the event id, if that suffices. Not sure if any of these is confidential data

meager cliff
#

Sure, any of those work and are safe

#

Nobody can do anything with object IDs without your keys (never share your secret keys, even test mode keys)

feral moat
#

evt_1Js6FpD4siJYPQuY0MnVsX7C is the event for a
payment_method.automatically_updated . I didn't see a
payment_method.card_automatically_updated which I thought should have happened since we are on v2019-02-19.

sleek finch
#

taking over, let me look

#

The Dashboard always shows the latest API version, so it will always show the new name, but you would have received payment_method.card_automatically_updated since you're on an older API version

feral moat
#

oh do you mean to say that if we had a webhook configured to listen for the payment_method.card_automatically_updated event, it would have sent that event even though it won't show on the dashboard?

sleek finch
#

Correct. It would show in the Dashboard if you had one less than 15 days old. You'd see the exact raw JSON we sent your webhook endpoint and could confirm it has the right type

feral moat
sleek finch
#

it's right there though

#

if you look at it, the event was delivered to 3 separate webhook endpoints, the 3rd one is on a 2019 API version and saw the old version

#

the middle one (yours) is explicitly configured to listen to events based on the API version 2020-03-02 so it has the newer version

feral moat
#

Thank you! I do see the old payment_method.card_automatically_updated now.

sleek finch
#

Perfect!

#

@feral moat are you all set or do you want me to keep this thread open?

feral moat
#

We are all set. Thank you for your help