#AntonKotov
1 messages · Page 1 of 1 (latest)
You're passing cus_P77qeUEaPiuU8y which was deleted ~last week by this API call: https://dashboard.stripe.com/test/logs/req_UiFAtQTEeiQ6W4
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Yes, that's the issue - here's how the process unfolds:
- A request is sent to Stripe to search for a user.
- If the user is not found, a request is made to create the user, and Stripe returns the user's id, for example, cus_xxxxxx.
- We then send a request to create an order in Stripe, specifying the user id obtained in the second step. At this point, we receive an error from Stripe stating "cus_xxxxxx not found."
Yeah, because it can't be found as you deleted it last week
See the link I just shared. That's an API request to delete the cus_P77qeUEaPiuU8y object
I understand that it has been deleted. However, on our end, we don't store the customer_id; we obtain it from you. So the question is, why does Stripe return a customer_id that has been deleted?
Hmm, we shouldn't be? Do you have an example GET /v1/customers/:id request that returns a deleted object?
I'll be back with a request soon.
I can't see any GET requests to lookup cus_P77qeUEaPiuU8y on your logs