#_nerder
winter cometBOT
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.
- nerder-customerdelete-event, 2 days ago, 32 messages
- _nerder, 3 days ago, 49 messages
- _nerder, 6 days ago, 5 messages
silent dragon
You can use this guide: https://stripe.com/docs/payments/handling-payment-events
dry crypt
The main problem I have is that if multiple developers are working on the code, every other local listener also receives it
every developer should have is own separate account?
silent dragon
Yep
dry crypt
what's the best practice here?
silent dragon
Yeah just have each dev create their own test stripe account
And have a main stripe account that's totally separate
dry crypt
Ok I see, so each dev has their personal one configure that webhook an connect to their local listener
silent dragon
Yeah if you need to keep events separate, that would be the way to handle
dry crypt
and with connect?
they should also have their own new connected account?
or can everyone use the same connected account?
dry crypt
our app mainly work with connect
so most of the tests each dev should do revolves around doing things in the app and see how they play out in the connected account
silent dragon
Are these direct charges?
silent dragon
Gotcha
Yeah I mean if it's a requirement that each dev not receive all the connect events, then they'll need to each create their own platform and connect accounts
dry crypt
ok, probably we should be able to script this creation E2E right? Sounds quite painful tbh
silent dragon
No they'd need to go to stripe.com to create their platform
Why do you need to keep events separate though in the first place?
dry crypt
for instance in this scenario we've faced today
we have an orchestration between the 2 webhooks, platform and connected
basically what we want to do is to keep in sync payment methods from the platform and clone them in the various connected account in which our user is a customer of
so for instance, for a payment_method.attached received in the platform we trigger several updates in the various connected accounts
now since 2 devs have the local listener up and running, when dev A attach a payment method on the platform, in the connected account we see 2 payment methods attached instead of only 1
silent dragon
Ok. Why not have a deployed test environment that is used by several devs? Then if devs also want to test things locally, then they should create their own stripe accounts. But the deployed test webhook can be in a shared account.
dry crypt
yes we actually have that, but while working on the webhook I think that having it locally is way more convinient (faster feedback loop, hot reload, etc)