#tyler-pi-webhook-applypay
1 messages ยท Page 1 of 1 (latest)
thanks for creating this thread @maiden dove
Hello Tyler, please allow me to read through your problem and assist you ๐
sure thing!
I was wondering if you could provide the request id for your PaymentIntent please?
give me a sec
I will double check your webhook settings to ensure everything is setup correctly, thank you.
this is the one that missing application pi_3K6oXtJYxzz9q9i90VQItAwd
this is the webhook we_1JXdlxJYxzz9q9i9kkxIhn9C ๐
Thank you
The webhook you have created is currently listening to events from Connected accounts.
As the PaymentIntent is an event generated by the Platform account, you would need a new webhook to listen to events that are specific to this account.
The Type should be defined as Direct instead of Connect.
right, so we need to create a new webhook, which maybe can point to the same destination?
Is there a way to complete this integration without creating a new webhook?
sorry, I'm not familiar with Connect and Platform
one part I'm not sure, PaymentIntent for Web and App were both created by the same endpoint and payload
Unfortunately there is not a way to change a webhook to listen to events from Connect to Direct and vice versa.
A new webhook would have to be created to listen to events specific to the Platform account (Direct).
If you would like to learn more about the difference between the Direct and Connect webhooks, please refer to https://stripe.com/docs/connect/webhooks
The definition of Connect Account are the different Standard, Express or Custom Stripe accounts that has been created independently from your Platform account [0].
It is not related to how Apple Pay has been implemented. Rather via native app or Web, as long as these are using the secret key defined within your Platform account, these PaymentIntent are tied to this account.
Hope you find this useful ๐
apologise for dumb question ahead. But we are creating the PaymentIntent in the same backend API endpoint with the same payload, the same API key. Wondering how to explain the difference in this case
our backend simply calls stripe.paymentIntents.create
I see, you are trying to listen to the payment_intent.succeeded events and would like to be able to tell rather the event was fired via app or Web?
There is nothing within the PaymentIntent event itself that could expose this information, however you could make use of metadata when creating the PaymentIntent [0], this can be any information you would like to parse in. This metadata will be displayed in the PaymentIntent webhook event.
yeah, thats what we are doing atm
and from what we can see, content in metadata matches in these two different cases
is the application injected after the PaymentIntent is created?
would like to be able to tell rather the event was fired via app or Web? we don't need to know where does the event coming from
now the problem is that paymentintent does not trigger webhook
even when it was created the same way as other places
I wonder what do you mean by
We can see PaymentIntent created by our iOS app can be successfully created and completed,
PaymentIntent should always be created on server: like this specific steps on our Apple Pay/iOS: https://stripe.com/docs/apple-pay?platform=ios#create-automatic-payment-intent
Either Web or iOS, aren't the calls to create PaymentIntent the same?