#AntonKotov

1 messages · Page 1 of 1 (latest)

mossy robinBOT
tardy fable
spare plume
#

Yes, that's the issue - here's how the process unfolds:

  1. A request is sent to Stripe to search for a user.
  2. 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.
  3. 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."
tardy fable
#

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

spare plume
#

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?

tardy fable
#

Hmm, we shouldn't be? Do you have an example GET /v1/customers/:id request that returns a deleted object?

spare plume
#

I'll be back with a request soon.

tardy fable
#

I can't see any GET requests to lookup cus_P77qeUEaPiuU8y on your logs