#sdasdq3we
pure radish
fading stream
Is each of your tenant a Connected Account of your account?
opaque pelican
yes
fading stream
You can listen to events on all Connected Account, but use the account property to determine which tenant that is
opaque pelican
let me check
Hey
In my case its not compulsory to have connected account for each tenant.
I am using destination charges.
Hello
@pure radish
@fading stream
fading stream
Sorry what did you mean by not compulsory? Isn't each tenant a Connected Account?
opaque pelican
No that is not the case, each tenant is not connected account right now.
fading stream
I am confused. Above you mentioned each tenant is a Connected Account. But okie
So then you will need someway to distinguish them
ie. Metadata on each transaction
opaque pelican
Right now what I am doing is,
I have tenant a and b
So for that db is different and url is different.
So for that I am adding webhook for both with specific url.
So with this logic I have reached max limit for webhook that I can add on stripe.
So I need a way to solve this problem.
I am think about to add one common web hook and on each event I can check that this event is for which db (tenant), and using that I will redirect that response.
I am not sure I am doing this correct or not.
fading stream
Yes that's exactly the idea. You have 1 webhook for all events, but then distinguish which tenant it is on each event, by using metadata
fading stream
It depends on how you process transaction, but generally PaymentIntent if you listen to payment_intent.succeeded, for example