#VoodooPrawn

1 messages · Page 1 of 1 (latest)

storm gorgeBOT
fresh veldt
#

👋 happy to help

umbral cypress
#

Cheers

fresh veldt
umbral cypress
#

Oh this looks very useful

#

Thank you

#

I'll give this a go and let you know if I have any issues

#

So that opens up the source, which has a "py_" ID

#

but my payment intent has a "pi_" id and the charge on it has a "ch_" id

#

so I'm still not sure how I tie the PaymentIntent to the BalanceTransaction

#

I should probably mention I'm using Connect

fresh veldt
umbral cypress
#

it's the other way around, the BalanceTx has a "py_" that I can't match up with my "PaymentIntent"

#

I think the reason is that I'm pulling the PaymentIntent, which is on our side (as in, the Platform side) and trying to match it to BalanceTx from the Connected account side

#

which is probably wrong

fresh veldt
#

Oh yeah that makes sense now

#

yes you're right

umbral cypress
#

I guess the question is, how do I get the corresponding payment from the connected account side from the platform side payment intent

#

I know it has a Transfer attached to it

#

to make it more confusing, we have some clients which we use OBO and some not 😄

#

(but I can deal with that my side)

fresh veldt
#

expand: ['data.source.source_transfer.source_transaction']

umbral cypress
#

on the PaymentIntent call, right?

#

let me try that, I think that will do the trick

fresh veldt
#

no

#

this is instead of just expanding on data.source when listing balance transactions

umbral cypress
#

ah

fresh veldt
#

if you read the second paragraph in the link I sent earlier

umbral cypress
#

gotcha

fresh veldt
#

If you’re using Connect with destination charges, you can retrieve the same information on behalf of your connected accounts. One difference is that destination charges involve both a transfer and a linked payment (in the form of a Charge object) to move funds to a connected account. So when listing the balance transactions bundled in your connected account’s payouts, each balance transaction’s source is linked to the transfer’s payment rather than the originating Charge. To retrieve the originating Charge, you need to expand a payment’s linked transfer through the source_transfer property; and from there, expand the transfer’s source_transaction property:

umbral cypress
#

perfect, leave it with me, pretty sure you've cracked the case

fresh veldt
#

let me know if you need any more help

umbral cypress
#

working perfectly

#

thanks so much for your help

fresh veldt
#

would you mind if I closed the thread?