#.iameugene

1 messages · Page 1 of 1 (latest)

vivid lilyBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

marsh oxide
#

Hi there 👋 I'm not too familiar with the specifics around Payout timing, as those can fluctuate on a per-country basis. Can you describe your desired outcome a bit more? I'm wondering if Manual Payouts would be a better fit than delay days, since you mentioned wanting to be able to process Payouts on request.
https://stripe.com/docs/connect/manual-payouts

gusty portal
#

We are focusing our efforts on attracting Sellers in the US, so the maximum period of 2 years for this country allows us to set a hold period of 60 days. When creating a test account, I also added the parameter "settings.payouts.schedule.interval: manual" and encountered the error described above (cannot set delay more than 31 days).

The complete payout scenario is as follows:

  1. The customer makes a purchase (in our case, it's a subscription).
  2. We transfer 70% of the subscription cost to the Seller Custom account in Stripe.
  3. We place this amount on hold for 60 days (for security purposes).
  4. After 60 days, we notify the Seller that they can initiate a payout to their external account.
  5. The Seller clicks the Payout button in their account on our Marketplace, and the previously frozen amount can be transferred to their account/card.
marsh oxide
#

You don't need delay days if you're doing Manual Payouts, you control the entire Payouts process then and would initiate a Payout for the appropriate amount and the desired time.

gusty portal
#

ok, so we program the hold period on our side and trigger the payout API after 60 days, right?

marsh oxide
#

Yup, exactly