#prabu17
1 messages · Page 1 of 1 (latest)
No, platform can't implement restrictions on connected account's Dashboard
Programmatically, I perform calculations for application fees at the time of capture. However, the issue arises when a connected user directly clicks the 'Capture' button within their dashboard.
Can you describe the problem that you are facing?
I initiated a payment that is set to be held for a duration of 7 days. Upon receiving the status confirming the delivery, I proceeded to initiate the capture process. This capture involves calculating application fees that are dynamic and contingent on the transaction amount. However, a complication arose when a connected user independently performed the capture action directly from their account's dashboard. Consequently, this direct capture bypassed the application fee calculation.
I'm wondering if there's a way to go back and adjust transactions that were manually captured.
I would really appreciate your advice on how to address this situation.
Do you have the PaymentIntent ID?
You can set a higher application_fee when creating a PaymentIntent, so that you can still collect it even if the connected account capture the PaymentIntent.
I will share
Once the Payment is completed, you can optionally create an application fee refund (https://stripe.com/docs/api/fee_refunds/create#create_fee_refund) to adjust if needed.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
https://stripe.com/docs/connect/account-debits-stripe-managed-risk#transferring-from-a-connected-account for now you can create a transfer to move some funds the connected account to cover your uncollected application fee.
pi_3NjyimIJbJroK8xx0mHeF3qT
captured is $197.92
Application should be $121.19
Manual captured $108.19 only.
I need to collect extra $3 from the connect account to application account.
Sure, refer to the link that I sent earlier to transfer from a connected account