#Avery246813579
1 messages · Page 1 of 1 (latest)
It's the result of a Destination Charge
So you had this Destination Charge https://dashboard.stripe.com/logs/req_I2MfpZFRALSW2f and it created a PI pi_3NBNVvAcqRxm04BK08JB3Cq5 on your Platform account, a Transfer tr_3NBNVvAcqRxm04BK0impTo0P from your Platform -> your Connected Account, and then the py_ object represents the amount arrives in your Connected Account
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Alright that makes sense
Is there any way to figure out the transfer using webhooks, or is it a lost cause?
You should received transfer.created on your Platform account
Probably your webhook endpoint wasn't listening to it
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
So it has source_transaction on the transfer
Is there any webhook transactions as well or just transfer?
You also had the regular payment_intent.succeeded https://dashboard.stripe.com/events/evt_3NBNVvAcqRxm04BK0jwYHEBK which has the transfer property
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
So that transfer will have the py_ I am looking for if I expand it during capture?
Yep!
That worked! You are a God! Thank you