#recipe.p

1 messages · Page 1 of 1 (latest)

winged egretBOT
pale meadow
drowsy sapphire
#

I have tested custom account and it was successfully done. Why can't I do the same with express account?

pale meadow
#

custom accounts are fully managed by you (the platform)

#

Express accounts have their own Dashboard and are expected to manage any required information themselves.

#

You can prefill most of the required information, but the Express account holder is expected to accept the tos themselves

drowsy sapphire
#

Ohhh that was what I missed!

#

Then I may have to 1. create express account with api
2. then make account link
3. login as a user( express) account and fill the info!

#

Is it possible to do this process in test mode as well?

pale meadow
#

yes, it's possible, you can test that out

drowsy sapphire
#

Thanks!
I'll try it out!

drowsy sapphire
#

It worked!

#

I have one more question about the payout parameters

#
  1. If I set the delay days "minimum(assume1~2days)", and inverval "weekly" then is the payout happens 8~9days after I sent the money?

  2. Is the delay_days controllable(can I set this like 10 days?)
    If we set the delay days like 4 days, and we transferred overly by mistake, is there any way(api or platform function) we can get the money back during the delay days?

  3. What happens when the user's bank account is not working due to some reasons like account closure?

pale meadow
#

what charge type are you using - direct charges or destination charges?

drowsy sapphire
#

checkout session?

pale meadow
drowsy sapphire
#

Oh

#

Then destination charge is the one. Buyers pay to us, and we pay to Sellers

pale meadow
#

https://stripe.com/docs/connect/manage-payout-schedule
The delay_days property reflects how long it takes for on_behalf_of charges (or direct charges performed on the connected account) to become available for payout. Express and Custom accounts support editing this property.

If you're using destination charges (without on_behalf_of) then delay_days won't have any effect at all

drowsy sapphire
#

To make it clear, We sell buyers some kind of point they can use in our platform, and we calculate and transfer the money to sellers
So the sales data that sent to Stripe will be like this

  1. Buyer -> Us Purchase
  2. We -> Seller Transfer
#

not like Buyer -> Us -> Seller

#

Is it still a destination charge?

pale meadow
#

is it one seller, or multiple sellers?

drowsy sapphire
#

multiple!

pale meadow
#

that'll be separate charges and transfers then

drowsy sapphire
pale meadow
#

because delay_days only apply to charges that use the on_behalf_of parameter or direct charges

#

if you're using separate charges and transfers, then delay_days will have no effect on how long the funds take to become available to payout for your connected accounts

drowsy sapphire
#

Okay then it will not have any effect for us!

#

then can you answer for just 2, 3 question?

  1. If we transferred overly by mistake, is there any way(api or platform function) we can get the money back during the delay days?

  2. What happens when the user's bank account is not working due to some reasons like account closure?

#

additional question for question 3, can Stripe detect if the bank account is active or not?

pale meadow
#
  1. If we transferred overly by mistake, is there any way(api or platform function) we can get the money back during the delay days?

You can reverse the transfer : https://stripe.com/docs/api/transfer_reversals

  1. What happens when the user's bank account is not working due to some reasons like account closure?

The payout will fail

#

3, can Stripe detect if the bank account is active or not?

No, we wouldn't know if the bank account is active until we make the attempt to payout

drowsy sapphire
#

then how can user payout? if I did not set the manual payout? is there any way user can cnage their bank account and try payout again?

pale meadow
#

The Express user can view the failed payouts and update their bank account via the Express Dashboard