#hoyong_01835
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. 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.
- hoyong-connect-onboarding, 2 days ago, 20 messages
Account IDs aren't sensitive, there's nothing a malicious actor can do with just an account ID
Thanks!
I have a couple questions about webhook
-
does webhook send us events based on paymentIntent id? or something else?
-
does webhook give the same information i'd get if we just queries the paymentIntent status ourselves (meaning using the API)?
I don't quite follow question # 1. Can you rephrase?
As for question # 2, not exactly. Say you listen for payment_intent.updated events. When you receive this event, the payload will include a PaymentIntent object at the time when that event was triggered. If some other action updates that PaymentIntent again (say, if its status changes to canceled) before you retrieve the PaymentIntent yourself via the API, the response you get for the retrieve call won't match the PaymentIntent object details in that first payment_intent.updated event. Does that make sense?
I think #2 actually kinda explains my #1.
I was wondering how I know which paymentIntent is sending me the webhook, and it sounds like it gives the entire paymentIntent object.
And your answer makes sense for #2. I found a doc for the API response for completing a payment using API. But, I am going to use iframe and webhook. I wanted to see which information I will get to architect my database table. Could you send me the link that shows the webhook's payload?
maybe this is the one? https://docs.stripe.com/connect/webhooks
I recommend referencing a couple of docs:
https://docs.stripe.com/webhooks#example-event-payload - you can see the full event payload; note that the data hash contains the subscription object relevant to the customer.subscription.updated event