Stripe transfer insufficient funds, used together with stripe checkout

[samtjong23]

Hi I am using stripe transfer in my own personal project where I am making a marketplace kind of application to provide sellers with a platform to sell their products. How I envision the payment system to work is that buyers will make payment to the platform (me) and once payment is completed I will make transfers to sellers accordingly. I am using stripe checkout also and when I want to charge buyers, it will create a paymentintent object. The problem is, once I receive the update that the buyer has made payment, it will be added to my stripe balance but I cannot transfer the funds straightaway as it seems that I will have to wait a few days before I can actually use the it. As such, I cannot transfer the money to sellers straightaway. I also found out that theres this source transaction field which when I provide with id of the charge object used to charge the buyer, will help to transfer the funds immediately when it becomes available regardless of whether my balance is sufficient or not at the time the transfer object is created. However im not using charge object, I am using paymenintent object instead since stripe checkout tells me to use paymentintent. May I know if theres a similar method as source transaction but for paymentintent? Or any other alternative solution that can help me to make transfer to sellers immediately when the buyer makes payment? Any help is greatly appreciated thanks!

[ljharb]

This has nothing to do with npm; ask stripe.

[darcyclarke]

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

[darcyclarke]

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.