#ivaaaan
lavish lynx
fading wraith
Hello 👋
A quick question, is there a reason you're creating a connected account for users instead of a customer object? A customer object can have a credit balance which can be applied to the next finalized invoice
https://stripe.com/docs/invoicing/customer/balance
The transfer settlement is dependant on when the original charge settles and all, so there's no way to have the transfer amount instantly available.
While you could technically create a manual transfer by calling the API and using the source_transaction parameter while the funds are pending
https://stripe.com/docs/connect/charges-transfers#transfer-availability
However, the transfer itself only occurs once the charge's funds become available (after they move from pending to available) so that won't work either
shell summit
Thanks, I will take a look to the customers. What we do is something like this: users topup their wallet, then do something after what funds can be transferred to other users, who can withdraw their money to the bank accounts. Do you think customers flow would be better here?
The transfer settlement is dependant on when the original charge settles and all, so there's no way to have the transfer amount instantly available.
I think the original transfer was captured immediately. We use test mode so far
fading wraith
Hmm I don't think withdrawing would be something customer objects can support unfortunately. So you'd need to use connected accounts for this.
shell summit
Maybe we should create customer object for users who buy services on the platform, just to track the balance. And connect accounts for users who can withdraw their money?
fading wraith
Yeah that could work yes. I was about to ask for more context on how exactly are you charging these connected accounts for the services and all.
The simplest way would be to the way you described, customer object for services and connected account for withdrawals
shell summit
That makes sense, thanks for your help
fading wraith
NP! 🙂 Happy to help