#EzequielCalcanat-connect-transfers

1 messages ยท Page 1 of 1 (latest)

drowsy pendant
#

Hi ๐Ÿ‘‹ starting a thread for this and will be with you in just a moment.

junior cobalt
#

yeah, transfers

drowsy pendant
#

Gotcha, thank you for that. Do you have examples of a transfer that is associated with a payment and one that is associated with one of your extra charges?

#

I need to get an understanding of how these transfers are being created in order to see if there is a field that can be used as a differentiator between the two types.

junior cobalt
#

do you need the JSONs?

drowsy pendant
#

The ID of the Transfers (tr_XXX) would be most beneficial.

junior cobalt
#

ok, so you only need the ID of the transfer of the both transfers?๐Ÿง

drowsy pendant
#

Yes please, I can then pull them up on my end.

junior cobalt
#

even if they are generated in test mode?

drowsy pendant
#

Yes

junior cobalt
#

woow, give me a sec pls

#

this one is consider like an extra charge:
tr_3L6e86GsGs3VcMtU0KCj3zUJ
and this other one is consider as a payment:
tr_1L6czMGsGs3VcMtUuAQkLeLs

we need to add a field, maybe a metadata and then filter by that field, what do you suggest?

drowsy pendant
#

Thank you for those details. So it looks like the the transfers associated with payments, are being created as part of our Destination Charges flow. I believe this means you have a couple options.

  1. You could look into leveraging metadata to store a flag on the relevant transfers to indicate if they were created as part of your extra charge process.
  2. I believe (but please double check) that since the Transfers associated with payments are being created from Payment Intents, that they'll contain a value in the source_transaction field.
    https://stripe.com/docs/api/transfers/object#transfer_object-source_transaction
    It doesn't look like your extra charge Transfers have a value here, though it is worth noting that they could if your flow that creates them begins passing values into the creation request for the source_transaction field.
junior cobalt
#

ok ok I'll check that information and I'll be back as soon as I got an answer, thanks a lot toby

drowsy pendant
#

๐Ÿ‘ sounds good, happy to help!