#Joe A - charges-error

1 messages · Page 1 of 1 (latest)

soft kiln
#

Hi! I'm taking a look right now

wheat iris
#

Thanks!

#

I can provide the real customer id, I didn't post it here

soft kiln
#

Can I get the request ID for this request to /v1/chargs?

wheat iris
#

req_LxyqioNaHyjurB

soft kiln
#

Thanks!

#

Okay so the issue is the /v1/charges API is looking for an account ID acct_ not a customer ID.

wheat iris
#

Okay, would that be a stripe account?

#

Like, my own stripe account?

soft kiln
#

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.

wheat iris
#

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!

soft kiln
#

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.

wheat iris
#

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

soft kiln
#

Okay so you have some customers who are paying other customers?

wheat iris
#

Yes

soft kiln
#

It is much more robust with better handling of authentication, retries, and other useful workflows

wheat iris
#

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.

soft kiln
#

Well hopefully you can suggest these alternatives, seem exceptionally smart, and avoid a lot of technical debt on your end.