XavierV-connect-transfer | Stripe Developers | Page 1

acoustic spire Oct 26, 2021, 12:40 PM

#

tulip hawk Oct 26, 2021, 12:59 PM

#

Hi, can I provide more information ?

acoustic spire Oct 26, 2021, 12:59 PM

#

Hey, thank you for your patience, it is a busy day. Just catching up on this, one moment.

tulip hawk Oct 26, 2021, 1:00 PM

#

no worries ! thanks for your help

acoustic spire Oct 26, 2021, 1:21 PM

#

Unfortunately there isn't really a way to re-reverse the transfer as far as I can tell. Looking in to if there is a way to do this and still have it connected to the original charge

#

Do you simply want to know what charge it was originally a part of? Or is there some functionality you are looking to use after?

tulip hawk Oct 26, 2021, 1:24 PM

#

long story short, we save some of the stripe IDs for each transaction in our systems so that our clients and support can figure out what step each transaction is at
so the charge ID is something we like to be consistent through the process so that we can, for example, tell that this particular transaction was paid out

#

I totally understand how this very peculiar case might be outside the scope of 99.9% of transactions and there might not be an easy way to keep that re-transfer tied to the original charge. but I figured I would ask!

#

Do you know if there would be issues including the source_transaction to the transfer (assuming there i already another transfer tied to the same source_transaction)
I presume not, because we do use multiple transfers with the same source_transaction for an in-house eCard implementation
I'm just wondering if it might be different for disputes ?

untold pendant Oct 26, 2021, 3:15 PM

#

Apologies for the delay, I think the biggest concern with trying to use source_transaction is this limitation:

You may create multiple transfers with the same source_transaction, as long as the sum of the transfers doesn’t exceed the source charge
https://stripe.com/docs/connect/charges-transfers#transfer-availability

The transfer_group parameter may be a better fit as it's just intended to be able to group transfers and doesn't have the same limitations as source_transaction since it isn't actually altering the flow the of the transfers.
https://stripe.com/docs/api/transfers/create?lang=python#create_transfer-transfer_group

The 'metadata' field that exists on most objects is also a good place to stick identifies that are important to your flows that don't directly impact how Stripe should handle things.
https://stripe.com/docs/api/metadata?lang=python

#XavierV-connect-transfer