#fm0
marble dragon
magic sleet
Does the terminal where you run stripe listen produce something?
magic sleet
It should have forwarded already
Any chance your middleware is after some layer stopping the log?
crimson sail
my app seems to not be receiving anything though I think the problem is with the hop between the forwarding and my server
magic sleet
What happen without --skip-verify?
Ah wait
that`s forward-connect
That only forward Connect related event
you want --forward-to
magic sleet
np, happy to help 😄
crimson sail
ok so now, have a signature error not sure how to fight this
The python exception that maps to this would be:
```stripe.error.SignatureVerificationError````
Any leads?
Code that sets-up stuff
event = stripe.Webhook.construct_event(
payload, sig_header, endpoint_secret
)
Okie are you sending with --skip-verify?
magic sleet
No just confirming
This SignatureVerificationError is a common one
When you do stripe listen it will output a secret, correct?
Did you set it into endpoint_secret?
crimson sail
yep, logged it temporarily and confirmed it matches what the cli says
do you think the STRIPE_API_KEY part could be the part thats breaking it?
I am using the production version of my stripe app's api key here
(by stripe app I mean this one)
magic sleet
Hmm so this webhook is for a Stripe App?
crimson sail
My Stripe app's main functionality is for listening to my customers webhooks on their behalf and doing actions on their behalf based on the webhooks i receive from stripe
magic sleet
Umm is there a Doc/guide you are following?
I am not sure I follow your setup, that is you seem to setup a webhook onbehalf of a merchant who uses your app
crimson sail
context:
magic sleet
Thanks. So you were looking at backend-only Stripe App and came that far to have a div to setup authentication
But I am not sure if that could let you listen to your user webhook event on behalf of them
Those kind of structure only works if you are a Platform and they are Standard Connected Accounts to you, but again with limited events, not everything, and only if you create Direct Charge with them
Imagine you have 1000 merchants uses your app, you can't have 1000 different endpoints listen to each of their events. 1 endpoint can only listen to events of 1 account
crimson sail
oh
magic sleet
Also that 1000 is dynamic, you wouldn't know how many users of your app
crimson sail
i thought i can listen to 1000 merchants as long as each one has my app installed
magic sleet
No, each endpoint requires an endpoint secret, which is bounded to 1 account
crimson sail
this seems to show that I can listen for events from my customer as long as my app has the perms in my maniifest
stripe apps grant permission "PERMISSION_NAME" "EXPLANATION"
Public listing on App Marketplace
magic sleet
Hey you may be right! Let me confirm this a bit further with my colleague
crimson sail
ya np, i feel stripe apps a bit weird since they are so new
so not super clear what the patterns are
appreciate the help!!!!
magic sleet
Hey yes I think here it mentions the steps https://stripe.com/docs/stripe-apps/build-backend?public-private=public#receive-events
So yes you can! Sorry please disregard my previous assessment. You can setup a Connect Webhook Endpoint and listen to all of your installed user events
That brings back the forward-connect-to parameter 😅
But in order to test it, you will need to trigger an event on an account which installed your app
stripe trigger will only trigger event on your own account
crimson sail
Gotcha makes sense, so is there a way to stripe trigger on a connect account?
also I installed my own app on my account, so this should work but we are back to square 1
where my server isnt getting anything
using stripe listen --forward-connect-to localhost:4000/stripe-webhook --skip-verify
magic sleet
Let's install on a different account, to avoid confusion
crimson sail
make a second stripe account?
