#Kamon
barren leaf
nova moon
Hello 👋
For grouping multiple SCP charges into one transfer and using transfer_group, is there a problem with having all charges for a customer being under the same transfer group?
I don't think so, are you thinking of any specific ones?
pearl goblet
Howdy!
No, just wondering if it'd be problematic like, for say, 1000 charges ranging over 5 years were all part of the same transfer group 😂
Rubeus also mentioned that I could use metadata to do that, which I can't find anywhere in the docs.
The docs mention a group needs to represent "one business action"
What does that even mean?
And, what would happen if I didn't even have a transfer group?
nova moon
Good question, thinking..
pearl goblet
No worries, take your time!
I'm in no rush, just want a solid confirmation 🙂
(even if it takes a day or two, haha)
nova moon
No, just wondering if it'd be problematic like, for say, 1000 charges ranging over 5 years were all part of the same transfer group 😂
I don't think that would be a problem really. Thetransfer_groupallows you to group charges under one umbrella. I don't think there should be any issues as such.
Rubeus also mentioned that I could use metadata to do that, which I can't find anywhere in the docs.
I believe Rubeus was referring tometadataproperty on the PaymentIntent object
https://stripe.com/docs/api/errors#errors-payment_intent-metadata
You can technically store any information (in key: value format) as metadata
The docs mention a group needs to represent "one business action"
I'm not sure but I'm interpreting the doc as if you use a certain string fortransfer_groupon PaymentIntent then you should use the same one on the transfer. So like if you use stringtransfer_group: 'xyz'for PaymentIntent then use the same string on transfer object, nottransfer_group: 'abc'
And, what would happen if I didn't even have a transfer group?
I don't believe it would have any effect on the API operation.
It just wouldn't associate the transfer to any group
nova moon
NP! 🙂 Happy to help
Good Luck