#matty-charges-sct
regal stirrup
viscid sequoia
matty-charges-sct
👋 @vital void ! If you have enough money in your own Stripe account's balance then the Transfer creation at step #2 will succeed. And at that point the connected account will have enough funds in its balance and let you create a Payout (assuming it's on manual Payouts)
vital void
thanks that is good to know. sorry about all the questions over the past few days. the event timings and context sensitive rules are hard/sometime impossible to test in testing mode.
viscid sequoia
all good!
vital void
dumb how am I suppose to use it question. is there a difference between doing a charge and a transfer separate vs a payment intent and a transfer without a fee.
halcyon trellis
i'm a bit confused over where the fee that you're mentioning comes from
a Transfer shouldn't have a fee
vital void
sorry. in the docs. you mention that linking payment intents and transfers through transfer groups is how you should do market place like transfers (https://stripe.com/docs/connect/charges-transfers#transfer-availability) like if you are facilitating connected_account a -pays-> connected account b and you want to keep some of that transfer as a fee which is collected into the general account
halcyon trellis
ah, so it's an application fee. Sorry, whenever a fee is mentioned, my mind tends to go to Stripe fees
vital void
np. so say we are facilitating a charge but there is no fee. what is the difference between the payment intent way. vs just calling stripe:charge to connected account a and stripe::transfer for connected account b
halcyon trellis
you shouldn't be using the Charge API anymore - it's considered as deprecated. PaymentIntents (which ideally you should now use instead) create a Charge object when payment is attempted. There's technically no difference in terms of how the Transfer works.
actually the transfer group parameter is optional. you can think of it as labelling / tagging to make it easier to identify associated objects
vital void
ok. we are talking about the same kind of charge right(https://stripe.com/docs/api/charges). I dont see it marked as depricated
halcyon trellis
yes, that's the API. It still works, just that new features and functionalities are not built on it. That's probably why we don't mark it as deprecated. But we recommend you migrate to PaymentIntents and PaymentMethods to support new features and functionality - https://stripe.com/docs/payments/payment-intents/migration
vital void
thanks for pointing that out. easy to miss 🙂