sg-pushpaveni_webhooks | Stripe Developers | Page 1

drifting geyserBOT Jul 11, 2024, 11:32 AM

#

versed chasmBOT Jul 11, 2024, 11:32 AM

#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

sg-pushpaveni_webhooks, 18 hours ago, 25 messages
sg-pushpaveni_code, 2 days ago, 31 messages

drifting geyserBOT Jul 11, 2024, 11:32 AM

#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1260921763559247955

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

grim sandal Jul 11, 2024, 11:33 AM

#

Tried to listen to paymentintent.succeeded, the json properties are different
Seems expected given that the event type is for an entirely different API object

#

What's the question/ask?

vagrant jetty Jul 11, 2024, 11:36 AM

#

here it is mentioned that , it is not required to listen to the new events
will charge.succeeded ad charge.failed work after migration to the latest stripe.net.dll 45.1.0 towards the migration of sources API to paymentIntent API

grim sandal Jul 11, 2024, 11:40 AM

#

Then I'm not understanding the issue. What exactly is unexpected with the webhook events you're receiving?

vagrant jetty Jul 11, 2024, 11:50 AM

#

Im working on the migration process by following the steps listed in the link
https://docs.stripe.com/payments/payment-intents/migration

I have completed 3 steps
and now working on the step4 for webhooks

we need to know whether we have to proceed with listening to the webhooks of - charge.succeeded and charge.failed after the migration process also???

Migrating to the Payment Intents API

grim sandal Jul 11, 2024, 11:51 AM

#

No, they're replaced by payment_intent.succeeded and payment_intent.payment_failed event as the doc outlines

vagrant jetty Jul 11, 2024, 11:52 AM

#

ok

#

but is the below link is not valid now - I mean after the migration process??
https://docs.stripe.com/payments/payment-methods/transitioning#webhooks

Transition to the Payment Intents and Payment Methods APIs

Learn how to transition from the Sources and Tokens APIs to the Payment Methods API.

grim sandal Jul 11, 2024, 11:55 AM

#

What about it? It basically states you can continue to listen for charge.* events if you wish as they're still sent

vagrant jetty Jul 11, 2024, 12:01 PM

#

does it mean, even though paymentIntent API is implemented, we can listen to charge.* events in the webhooks for the payment calls?
kindly confirm me that my understanding is correct ???

scenic rune Jul 11, 2024, 12:06 PM

#

hi! I'm taking over this thread.

#

yes that's correct. a PaymentIntent will create a Charge object, so you will receive a charge.created event as well.

vagrant jetty Jul 11, 2024, 12:10 PM

#

ok, one more question

#

When updating stripe.net.dll to 45.1.0, below error comes.

what needs to be done???

Error CS1061 'PaymentIntent' does not contain a definition for 'Charges' and no accessible extension method 'Charges' accepting a first argument of type 'PaymentIntent' could be found (are you missing a using directive or an assembly reference?)

scenic rune Jul 11, 2024, 12:15 PM

#

the PaymentIntent no longer has a charge property. Instead it's lastes_charge https://docs.stripe.com/api/payment_intents/object#payment_intent_object-latest_charge

vagrant jetty Jul 11, 2024, 12:22 PM

#

kindly clarify me the below file contains the data which is received for the paymentIntent.succeeded event through webhooks
it has charges property?? why ???

📎 stripe.json

#

this data doesn;t have latest_charge property. why? what is missing to get it out ?

scenic rune Jul 11, 2024, 12:24 PM

#

because this is using an old API version (2022-08-01). but we changed this on version 2022-11-15 as mentioned here https://docs.stripe.com/upgrades#2022-11-15

#

so it depends which API version and SDK you are using.

vagrant jetty Jul 11, 2024, 12:34 PM

#

is the below one indicate our API version currently configured???

scenic rune Jul 11, 2024, 12:35 PM

#

the API version used in your events depends on the API version set on the webhook endpoint itself.

vagrant jetty Jul 11, 2024, 12:40 PM

#

kindly answer me the following questions??

do I need to update the webhook API version?
if so, what version do I need to change??
how to change? kindly share any reference link to update web hook api version??????
what will it happen if Im not updating the webhook api version

scenic rune Jul 11, 2024, 12:40 PM

#

it depends. what exactly are you trying to do and what is the issue?

vagrant jetty Jul 11, 2024, 12:42 PM

#

is it possible to have call ??

scenic rune Jul 11, 2024, 12:43 PM

#

on Discord we can only help by chat here. if you need a call, you can try asking Stripe support: https://support.stripe.com/contact

vagrant jetty Jul 11, 2024, 12:48 PM

#

I have submitted my question on audio/video call

versed chasmBOT Jul 11, 2024, 12:50 PM

#

vagrant jetty Jul 11, 2024, 12:51 PM

#

vagrant jetty kindly answer me the following questions?? 1. do I need to update the webhook AP...

all these questions are related to the migration process mentioned in the link https://docs.stripe.com/payments/older-apis#deprecation-of-the-sources-api

Older payment APIs

Information about our older APIs and the newer APIs that replace them.

#

kindly share your replies on all 5 points

#

do I need to update the webhook API version?
if so, what version do I need to change??
how to change? kindly share any reference link to update web hook api version??????
what will it happen if Im not updating the webhook api version
will the charges API calls initiated SEPA payment before the version update work after upgrading to latest version also

wary bolt Jul 11, 2024, 12:55 PM

#

👋 stepping in here as soma needs to step away

#

Catching up

vagrant jetty Jul 11, 2024, 12:56 PM

#

ok fine

wary bolt Jul 11, 2024, 12:56 PM

#

Which of our SDKs are you using?

vagrant jetty Jul 11, 2024, 12:56 PM

#

thanks for stepping in here to support me

vagrant jetty Jul 11, 2024, 12:57 PM

#

wary bolt Which of our SDKs are you using?

stripe.net.dll

wary bolt Jul 11, 2024, 12:57 PM

#

And what version of that SDK?

#

Oh you are looking to move to the latest version?

#

If you are going to use 45.* then you do need to upgrade your Webhook version to using 2024-06-20 as the SDK pins to certain versions. See: https://github.com/stripe/stripe-dotnet/blob/master/CHANGELOG.md#4500---2024-06-24

#

If you don't upgrade then you could have potential errors involving data deconstruction

#

To upgrade you want to follow our process here: https://docs.stripe.com/webhooks/versioning

vagrant jetty Jul 11, 2024, 1:01 PM

#

40.1.0 was there, couple of days before, I have upgraded to 45.1.0 towards the migration process
https://docs.stripe.com/payments/payment-methods/transitioning

wary bolt Jul 11, 2024, 1:01 PM

#

Yep gotcha then see the above

vagrant jetty Jul 11, 2024, 1:03 PM

#

can I upgrade to lower version instead of 45.1.0 so that the migration process will work with less impact/less changes in the already implemented code

wary bolt Jul 11, 2024, 1:03 PM

#

Sure, that's up to you and whatever features of our SDK you need in terms of the newer versions

#

You should review the Changelog to see what version your integration will require

vagrant jetty Jul 11, 2024, 1:05 PM

#

I need the below features only

Credit card - payment
credit card - authorization for recurring payments
SEPA direct debit - payment
SEPA direct debit - authorization for recurring payments

wary bolt Jul 11, 2024, 1:06 PM

#

Don't think you need to upgrade at all in that case

vagrant jetty Jul 11, 2024, 1:06 PM

#

kindly suggest which version I can choose for the above features need to work in our product

wary bolt Jul 11, 2024, 1:06 PM

#

Pretty sure SEPA Debit works just fine on 40.1.0

#

Your next step is to test it out

vagrant jetty Jul 11, 2024, 1:08 PM

#

wary bolt Pretty sure SEPA Debit works just fine on 40.1.0

if that is the scenario, why we are getting this alert on migration to paymentIntent API instead of sources API????

wary bolt Jul 11, 2024, 1:08 PM

#

Do you use the Sources API right now?

#

If so, then you need to update your integration to use the PaymentIntents/PaymentMethods API. That doesn't necessarily mean updating your SDK or your Webhook endpoint version

vagrant jetty Jul 11, 2024, 1:09 PM

#

I want to clarify everything with you so that I can share all the details to my management team on the volume of work needs to be done

wary bolt Jul 11, 2024, 1:09 PM

#

There is nothing left to really clarify. Your current SDK and API version is compatible already. All you should need to do is update the actual APIs you are using in your integration.

#

And to confirm that 100% you need to test this out in test mode via your integration, as I have no insight into what your integration specifically does.

vagrant jetty Jul 11, 2024, 1:11 PM

#

wary bolt There is nothing left to really clarify. Your current SDK and API version is com...

does it mean that 40.1.0 can still be used to migrate from sources API to paymentIntent API??

wary bolt Jul 11, 2024, 1:11 PM

#

Yes

vagrant jetty Jul 11, 2024, 1:21 PM

#

one more questions, kindly clarify this

how long can we use the 40.1.0 version???
can we continue to use the 40.1.0 version for 2 or 3 years more??

#

just high level info is enough...

wary bolt Jul 11, 2024, 1:22 PM

#

Yes, there are no plans to deprecate past versions. If that were to ever happen you would be sent communication with plenty of heads up.

vagrant jetty Jul 11, 2024, 1:23 PM

#

oh ok thanks for your support by clarifying all my questions

wary bolt Jul 11, 2024, 1:23 PM

#

Happy to help

vagrant jetty Jul 11, 2024, 1:25 PM

#

in one of the documentation page, it was information to update the library version as the first step
may be that is leading us update to the latest version of stripe.net.dll which has lots of changes over the 40.1.0 version

wary bolt Jul 11, 2024, 1:27 PM

#

Which documentation page was that?

#

I'm happy to provide feedback internally to improve it

vagrant jetty Jul 11, 2024, 1:32 PM

#

Im not able to get that link for now, sorry

wary bolt Jul 11, 2024, 1:33 PM

#

Alrighty well if you do find it let us know

vagrant jetty Jul 11, 2024, 1:33 PM

#

here it is

#

https://docs.stripe.com/payments/payment-intents/migration?web-migration=elements#api-version

Migrating to the Payment Intents API

wary bolt Jul 11, 2024, 1:34 PM

#

Ah okay thanks -- it does just say "recommend" there, which we do indeed recommend that you use the latest API version. But it isn't mandatory.

#

I'll file feedback about this though

vagrant jetty Jul 11, 2024, 1:34 PM

#

oh ok fine

#sg-pushpaveni_webhooks