#Darby-checkout
main flare
cloud ivy
hey @rugged root - what do you mean by transaction here? a payment intent? or the actual stripe account "balance transaction"?
rugged root
Hi @cloud ivy . I was looking fot the tx_ transaction? that look it's the root transaction in the stripe system? where all charges/refunds/disputs refer back to?
cloud ivy
Gotcha, and is this a one time payment session or a subscription start?
rugged root
one time payment
cloud ivy
ok in that case the session object in the event has a payment_intent attribute that you can use to retrieve the payment intent
then using expansion you can get the balance transaction via the charge
See the first example here for how to use that expansion: https://stripe.com/docs/expand/use-cases#stripe-fee-for-payment
(its looking at the fees, but you get the whole balance transaction object)
rugged root
great, ty!
cloud ivy
NP!
rugged root
so i think stripe has changed it model sense i last looked at it
is every single payment now associated with the payment intent? will refunds/disputes point back to the original payment intent/
cloud ivy
sorry missed this message @rugged root - can you clarify?
when you create refunds you can refer to the payment intent or the charge it uses under the hood, both work
but yes the payment intent would be noted as refunded even if you used the charge id, for example
We still have legacy endpoints for the Charges API, which do not use payment intents, though i dont recommend doing any new development work suing these