#taylor-brooks-simple_api
austere mountainBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1296476387036758160
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
random shard
Charges can have both prefixes for various reasons
Most commonly, ACH payments can start with py_xxx along with transfers associated with connect accounts
This is not an important difference and both are charge objects
You ignore that and handle them both as charges
The ID prefixes are meant only to be helpful queues as to object types and machine readable pointers, they can and will change so you should not over index on them
austere mountainBOT
random shard
Stripe considers the following changes to be backwards-compatible:
- Changing the length or format of opaque strings, such as object IDs, error messages, and other human-readable strings.
- This includes adding or removing fixed prefixes (such as ch_ on charge IDs).
jovial sparrow
You're saying that if I remove the prefix, the Ids will match?
random shard
I don't think I'm saying that at all. WHat do you mean?
py_123 and ch_456 are different payments/charges
both are charge objects, which can have different prefixes for various internal/historical reason that should not affect your integration
jovial sparrow
py_1Q4p95If6mA6tQKcwV3W0bnG
spice talon
Hi taking over here as synthrider has to step away soon
Id's that start with py_ and id's that start with ch_ are both charges
I know it's a little confusing, but they represent the exact same object in our api
jovial sparrow
Are these pointing to the same resource? ch_3Q4p94LMHLcGMW3Q0zGUL2la <> py_1Q4p95If6mA6tQKcwV3W0bnG
spice talon
Kind of. ch_3Q4p94LMHLcGMW3Q0zGUL2la is the charge created on your platform account. py_1Q4p95If6mA6tQKcwV3W0bnG is the portion transferred to the connect account
Since this was a destination charge
jovial sparrow
Assuming I've only got the ID of "ch_" how do I get to the "py_"?
When I export transactions from Stripe, I only have py_ resource ids.
In my system, I've got ch_ resource ids.
It's hard for me to reconcile, when things don't match
spice talon
You're looking at payments on the connect accounts above, so this is totally expected
py_ would be the payment made on the connect account when you do a destination charge
In destination charges, you make the charge on the platform account
So that's where the ch id will exist
Then a portion is transferred to the connect account
Which is a py
But to get the py from the ch, you need to expand the transfer on the charge: https://docs.stripe.com/api/charges/object#charge_object-transfer
That transfer will have a destination payment: https://docs.stripe.com/api/transfers/object#transfer_object-destination_payment
That's the py_ id