#literatelapellabel_best-practices
static pagodaBOT
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.
- literatelapellabel_webhooks, 5 days ago, 27 messages
wind sapphireBOT
đ 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/1247854581275295744
đ Have more to share? Add details, code, screenshots, videos, etc. below.
light stirrup
hi! that's expected yes, a new account is created so that data is not shared between platforms. The accounts are all under the same Stripe 'user' as the merchant. https://support.stripe.com/questions/security-permissions-and-access-levels-when-connecting-your-stripe-account-to-a-third-party-platform#:~:text=During the onboarding flow
coral pendant
In summary of the previous dicsussion, we were advised connect onboarding and a connect enabled webhook would be adeqaute, however it seems that it onboards them as new accounts so we don't have access to the events when they cancel
So if we need to get notified of their existing account subscription activity, how should we best proceed?
light stirrup
what's the use case of your platform listening to subscription cancellation events on existing connected accounts? revenue protection/churn handling?
if you don't need write access to accounts, consider building a Stripe App, or signing up as an 'extension' and using read_only OAuth. https://docs.stripe.com/connect/oauth-standard-accounts But if you need write access, what I said above applies in terms of having multiple accounts-per-user
coral pendant
We don't require write access, our customers use our platform to calculate commission points for their partners, currently we award these until manually stopped by our customer in our platform, however we wish to automate stopping if their is a customer.subscription.deleted event in their stripe account.
The idea being that, we would receive the webhook event, check if the customer cancelling was for an ongoing commission and stop calculating it
light stirrup
hmm, not sure overall how that works, you're not the one creating/controlling the payments on the accounts but are giving some commission?
but overall if you need read access to existing accounts then Stripe Apps or an Extension with read_only OAuth are the options.
coral pendant
Perhaps I'm over-complicating my request,
Say Acme Inc, uses our platform, and are referred a business lead. If they mark the lead as won in our platform (they then handle billing the new customer via their own stripe) we calculate commission points for the referrer, and need to stop doing so, if that customer later cancels.
It sounds like from what you've said we can use a stripe app, would we just point the users to the stripe marketplace to install our app?
light stirrup
yes
coral pendant
Thank you. Does the stripe app require any UI if its just registering a webhook
light stirrup
coral pendant
Thank you thats a great help