#Joe A - charges-error
1 messages · Page 1 of 1 (latest)
Can I get the request ID for this request to /v1/chargs?
req_LxyqioNaHyjurB
Thanks!
Okay so the issue is the /v1/charges API is looking for an account ID acct_ not a customer ID.
Well it looks like you are using destination charges so you're collecting on behalf of someone. It would be the account ID of that someone.
Here are the docs for destination charges: https://stripe.com/docs/connect/destination-charges
Okay, I see. This is a test environment. Do you know if there's a test account_id I can use?
Never mind, I found the information on creating connected accounts. I believe that's the route I want to go down. Feel free to correct me otherwise, I'll attempt this. Thank you so much!
What are you trying to build (in general)?
Connect is a powerful but complicated system and we want to make sure you are using the right products for your business.
My company uses the v1/charge endpoint to handle customer-to-customer transactions. I'm just testing our code
I am trying to hit the endpoint we use in postman, and our repo is poorly documented so I wasn't sure what account id meant
Okay so you have some customers who are paying other customers?
Yes
Okay so here's a good overview of Stripe Connect: https://stripe.com/docs/connect
Secondly I want to strongly recommend you avoid the Charges API and instead utilize our Payment Intents API: https://stripe.com/docs/payments/payment-intents
It is much more robust with better handling of authentication, retries, and other useful workflows
I will make the suggestion I am a lowly junior dev lol
I know we intend to move away from our current payment handling. I really appreciate your help though.
Well hopefully you can suggest these alternatives, seem exceptionally smart, and avoid a lot of technical debt on your end.