#BIG STEVE
small grail
pulsar tinsel
Hey there, are these connect-related payments?
loud gazelle
Yes
pulsar tinsel
the py_123 are charge objects with a different prefix for <waves hands> reasons
So you can retrieve them from the Charge api
using connect headers, if needed
(you typically see them for the "payment" related to a destination charge transfer, but also for legacy ACH charges)
pulsar tinsel
then, assuming it was a card payment, you can get the last4 inside the payment_method_details.card:
https://stripe.com/docs/api/charges/object#charge_object-payment_method_details-card-last4
loud gazelle
Ok that makes sense
that's what I first thought but the sample charge has an id starting with ch_xxx so was thrown off
Getting Error: No such charge: 'py_XXXX'
pulsar tinsel
The ID prefixes are meant to be helpful hints, but are subject to change
Can you share the request ID? https://stripe.com/docs/api/request_ids
I suspect the connect context is missing
loud gazelle
Looking into how I can get that, since the Stripe library just throws an error
looking via dash 1 sec
req_qYOYH32FaeshWQ
pulsar tinsel
Yea, you need to include the connected account context: https://stripe.com/docs/api/connected_accounts?lang=node
{ stripeAccount: 'acct_123' }
pulsar tinsel
NP!