#raimund_docs
open stirrupBOT
👋 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/1341892118330871870
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
analog dust
Hi there. When you say 'automated' payouts, do you mean that your platform is, in fact, creating the Payouts via the API?
(but abstracting this from your connected accounts)
warped grotto
That's the plan, because AFAIU what we're planning to do is something that the Stripe-builtin automated payout mechanism doesn't support.
We're already using "regular" payouts, but are changing our pricing model.
The idea is that the recipients can choose between weekly and monthly payouts. Monthly payouts will be free, weekly ones will incur a fixed fee.
analog dust
Gotcha. It looks like the Application Fees feature that is referenced in https://docs.stripe.com/connect/instant-payouts#monetization-and-fees rely on some conditional logic you set in the dashboard and don't seem to offer the kind of flexibility that you're looking for
warped grotto
Exactly. Plus it's only applicable to Instant payout methods (unless I misunderstand something).
analog dust
No I think you're correct. I think this is a newer feature.
You may find the simplest approach under the circumstances would be to just debit your accounts at intervals based on the payout feature they're accessing
It requires you to keep track of some state on your end, but should achieve the effect you want
The docs for that are here: https://docs.stripe.com/connect/account-debits
warped grotto
Yeah, I came across that. Am I correct in assuming that the transfer method is preferred over the charge approach?
analog dust
I think it makes the most sense for the scenario you're describing
warped grotto
I kind of thought so, but was looking for confirmation. Thanks. 🙂 We're already using transfers anyway, so that doesn't sound like too much of an issue.
analog dust
Awesome! It is a fairly common use-case
warped grotto
In that case, may I suggest to mention that in the documentation? The main reason I was a bit doubtful was this sentence:
"This approach is best for making adjustments within a platform (for example, correcting a payment mistake or recovering any fees you paid to Stripe)."
It just didn't sound like our use case.
analog dust
That's understandable; I'll be happy to pass the feedback on
analog dust
Sometimes things are simple 🥲
warped grotto
Tell me about it. 😆