#.iameugene
crimson muralBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- .iameugene, 23 hours ago, 8 messages
- .iameugene, 6 days ago, 7 messages
fading wasp
Hello there
To be clear, the transfer_group is arbitrary and just used for your own tracking of Transfers
It isn't required nor has any real impact
If you want to make two transfers after a Subscription payment, then you just create two Transfers and you don't set transfer_data on the Subscription itself
Or, you could use transfer_data to transfer a certain amount to one account and then create a separate Transfer to another account
Up to you
But yes, this is all totally possible
vagrant nimbus
If you want to make two transfers after a Subscription payment, then you just create two Transfers and you don't set transfer_data on the Subscription itself
Yes, that's exactly the question. Because to create two Transfers, we need some parameter that associates them with a specific payment. And Stripe suggests using transfer_group for this purpose. However, I don't understand how to apply it in the case of a subscription. And if we don't use it at all, what parameter can we rely on?
fading wasp
You can update the transfer_group on the PaymentIntent that is created from the Sub using https://stripe.com/docs/api/payment_intents/update#update_payment_intent-transfer_group
If you want to go that route
The other option is to use metadata instead of transfer_group to tie this stuff together
Up to you, really.
vagrant nimbus
Super, thanks. this is exactly what we need 