#guedes233_api
fossil hedgeBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question. Thank you for your patience!
⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1214502415953436682
📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.
sinful kestrelBOT
teal sinew
hi! seems like the answer is no
heady mural
no as in not possible?
teal sinew
as in it's not possible
heady mural
😢
teal sinew
transfer_group isn't really important though IMO
you'd just pass the payment_intent.latest_charge to source_transaction when creating a Transfer
https://docs.stripe.com/connect/separate-charges-and-transfers#transfer-availability
Stripe automatically creates a transfer_group for you
heady mural
i was planning on using transfer group to know how much budget there was within a project to later distribute between freelancers...
i can have multiple charges before i start payout
so if i keep setting latest charge when creating invoice theyu will get grouped?
teal sinew
well to be clear it would be actually doing the transfer
when you create a transfer you can/should be using source_transaction to link the transfer to an incoming payment and part of that is that each transfer created that way creates a transfer_group
If the source charge has a transfer_group value, Stripe assigns the same value to the transfer’s transfer_group. If it doesn’t, then Stripe generates a string in the format group_ plus the associated PaymentIntent ID, for example: group_pi_2NHDDD589O8KAxCG0179Du2s. It assigns that string as the transfer_group for both the charge and the transfer.
heady mural
so what would be a better way to collect invoiced money that i keep track of to later distribute? is there like a common way to do this? i thought it was the transfer_group...
because i will have multiple transfers (from multiple invoices)
teal sinew
transfer_group would work well but not possible when using Invoices directly
so instead I guess I'd just store the IDs of things in my database on my end
heady mural
or metadata?
teal sinew
you could also add metadata to the PI and use the search API yes but that has it's own caveats
heady mural
since i was thinking metadata what would be caveats to be aware of?
teal sinew
e.g. searching PIs for certain metadata might not return all of them depending on timing, but it might not be an issue if you don't need them immediately after the payment completes
heady mural
ah right... i guess it's indexed so there is lag... but i would be doing this a days after payments are delivered (on project conclusion)
teal sinew
you can also use the normal /v1/payment_intents List API and do the search in your own code