#vamsi_api
old questBOT
đ 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/1250969335237705760
đ Have more to share? Add details, code, screenshots, videos, etc. below.
sharp plinth
Which events did you expect to receive?
sharp plinth
In https://dashboard.stripe.com/test/webhooks/we_1O0JbtEJx1LumFjqn13gyv3b, the Webhook endpoint is set as Connect type, i.e. only receive the events on the connected account.
However, the subscription is created on the platform account itself.
You'd need to create a Webhook endpoint with Account type for your own platform account: https://docs.stripe.com/webhooks#add-a-webhook-endpoint
sharp plinth
I'm afraid that's not possible. You can only create a new Webhook endpoint with Account type
keen bramble
if a connected account creates a subscription all events related to subscription and the payment intents are posted on which webhook type - Account or Connect
sharp plinth
If the subscription is created on the connected account, the events will be sent to Webhook endpoint with Connect type
keen bramble
how to make sure the subscription created is on connected accout through api ?
currently I'm consuming customerid which i believe is not mapped to connected account.
sharp plinth
What type of connected account are you using? Standard, Express or Custom?
keen bramble
Custom
sharp plinth
If you use Custom connected account, Destination Charges or Separate Charges & Transfer should be used. This means that the payments and subscription should be created on the platform.
keen bramble
we create accounts through api's for every user maintained at the platform
sharp plinth
You shouldn't need to use Webhook endpoint with Connect type for subscription in such a case
keen bramble
I see
sharp plinth
Webhook endpoint with Account type should be used
keen bramble
Thanks that helps.