#jmung_dev
1 messages ยท Page 1 of 1 (latest)
๐ happy to help
I wanted to use Destination charges https://stripe.com/docs/connect/destination-charges. I'm wondering if I'll be able to hold the funds in the platform account while waiting for the client to confirm that he's been served so that we can proceed to seller payment
Hi @fading brook
in that case you need to use separate Charges and Transfers
Ohh thank you
And do you have some samples I can use to integrate quickly ?
What are the steps to integrate with seperate charges and transfers ?
it's all explained in the link I shared
I don't understand this part. In my case, the money will be sent to only one seller. Here there are two conntect accounts involved in the transaction
How can I get the expected feature by following this guide ?
you don't need to send to multiple sellers
it's just an example to show that you can create multiple transfers
but you don't have to if you don't need to
By doing so ?
How do I hold funds on the platform while waiting for use to confirm that he's been served ?
user*
you don't create the transfer
once you want to move the funds to the connected account
then you create the transfer
I'm using booking.id as transfer group because it's the main relationship between users and sellers
Now when user confirms payment, Can I use it to fetch the details about the stripe payment and then send the money to the seller ?
sorry I need to step away, my colleague will be with you shortly
Hi! I'm taking over from my colleague. Please, give me a moment to catch up.
Hi @graceful pike. Thanks for joining
Now when user confirms payment, Can I use it to fetch the details about the stripe payment and then send the money to the seller ?
Can you use the PaymentIntent ID instead?
So I'll need to save the payment intend id in my db using the webhook ?
Maybe you can search via transfer_group, let me check.
No, unfortunately only these fields are supported for search: https://stripe.com/docs/search#query-fields-for-payment-intents
But you can also put it in metadata then!
And then search by metadata["booking_id"]:"value"
Yeah that's what I'm doing
Let me share the steps I need for the project so that I get the most from your assistance @graceful pike
- User books a service, we associate the payment intent with booking id in the meta data as well as the transfer_group identifier
- Then seller is notified using the webhook for payment intend succeeded
- When seller confirms a service completion, user is contacted to confirm that he's been served or ask for a refund
- If user confirms, we create a transfer on behalf of seller connected account
- Finally if user wants to be refunded, the admin takes care of the situation by discussing with both parties, then he can whether confirm the seller payment or refund the client.
Could youl help me with step by step insights to achieve that logic ?
This looks like a common flow. What exact parts are you having doubts about?
Then you query the PaymentIntent by metadata and refund it: https://stripe.com/docs/api/refunds/create
Or, create a transfer to your Connected Account: https://stripe.com/docs/connect/separate-charges-and-transfers
That's great thanks! I'm now getting a clear vision
Happy to help!