Miran

[worldly osprey]

Hi 👋 nothing happens with the source_transaction parameter unless you provide a value for it.

You can read about how to use that parameter here:
https://stripe.com/docs/connect/charges-transfers#transfer-availability

[ancient steppe]

I am sorry, we are sending the id of the charge object as the source_transaction parameter.

Does this mean, when our balance gets the money we captured, the transfer gonna succeed then?

[worldly osprey]

Gotcha, so then the Transfer's lifecycle is tied to the Charge's lifecycle. The Transfer won't be triggered until the Charge's funds settle, to ensure they are available to cover the Transfer. Once the Charge settles, the Transfer proceeds and should succeed.

[ancient steppe]

Charge settles means there is no dispute right?

[worldly osprey]

Disputes could occur later

[ancient steppe]

Okay.. in that case the Transfer is not rolled back right?

Aside from insufficient balance, is there any other situations where transfer could fail?

[worldly osprey]

Yes, that is my understanding.

[worldly osprey]

Insufficient funds is the big one, the only other thing that comes to mind is if the Connected Account has been restricted and isn't allowed to accept transfers.

[ancient steppe]

Let's say the transfer could not be made for some reason, will stripe let me know about it through events?

[worldly osprey]

I'm pretty sure if you're able to create the Transfer object, then it will succeed, and that if there are going to be problems they'll be surfaced in the response to create the Transfer.

[ancient steppe]

Okay, many many thanks for your help sir. I got the answer that I was looking for.