#mebezac_platform-intent-modifications
reef roostBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1465399815343964261
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
radiant elk
Hello 👋
Since the Payment Intent was created (request as a Direct Charge, it exists on and belongs to the Connected Account. The particular connected account has multiple platform connections, each with the same access.
Unfortunately, as it stands, you would need to ask the connected account to modify their connection to the other platform. As you and the other platforms are currently connected, there isn't a way to restrict actions on Payment Intents your platform creates on this Account from being acted on by other Platform accounts.
For this type of connection, that behavior is for the Connected account to manage.
Each Platform is a service the Connected Account has connected to and it's up to them to manage their services
That being said, I can file a feature request for something like this. I cannot say whether or not it would be selected for development or when such a feature might be rolled out but I could at least make your interest known internally
mint plover
Thanks for confirming, and yes I'd like that as a feature request.
Can you confirm by looking at those requests that it at least looks like to you that Lopay shouldn't be capturing those payments, we've been having the non-dev Stripe support tell us that we are at fault since we have failed requests after (since we try to capture and then cancel an already captured payment).
radiant elk
Lopay shouldn't be capturing those payments
I think you need to re-frame the way you consider this. Both Lopay and Clinko are services the Connected Account is using. Both of you have read_write access and make requests on behalf of the Connected Account. Essentially, if the Connected Account has connected with Lopay specifically to capture un-captured funds, that is up to them.
While I understand this means things are happening to Payment Intents your Platform created that you do not expect, your integration should check the status of the Payment Intent prior to attempting to capture to ensure it is in the correct state. I realize it's more overhead for you but the Payment Intents don't "belong to you". They belong to the Connected Account.
You could also make the Connected Account aware of how their integration with Lopay is causing problems with payments you are generating for them.
mint plover
Ok, thanks
radiant elk
I filed this feature request. If you want to stay up to date on future changes as we roll them out, I recommend you sign up for the Developer Digest
mint plover
Thanks, I think the thing I would want to make absolutely sure of is that other integrations aren't charging an application_fee on payments we initiated on behalf of the customer, since we don't charge those.