#luqasn-customer
abstract hull
hi! can you clarify how you search for them, is it https://stripe.com/docs/api/customers/list#list_customers-email or something else?
untold tulip
yes, exactly that
at first I thought it was an eventual consistency issue, but adding a sleep of 6 seconds did not help. also if that was true it would be weird (though not impossible) that it works locally
abstract hull
for what it's worth I've just tried it on my account and it seems to work so I'm not sure anything is globally broken
could you share more context like
- the cus_xxx Customer ID in question
- ideally, the request ID req_xxx from the list call that was made? (https://support.stripe.com/questions/finding-the-id-for-an-api-request , but I can probably find it from just the customer ID if you don't have this)
untold tulip
I am in Stripe connect account acct_1KibWf2fXnhEYgqp
the customer the test was trying to find was cus_LPQQEGLY46Li3C
interestingly, I can't seem to be able to see the searches in the call logs
abstract hull
they'd be in the logs of the connected account
I also have to ask why you're doing Direct Charges on Custom accounts, but that's a separate discussion
so what I see if your email address has a space in it
when you created the customer, you passed email: "payment+system-*****@****.com",
but when you listed, you passed email: "payment system--*****@****.com" with a literal space character
so likely you're not encoding this value correctly in your code. That's why you get nothing, the two values are different
untold tulip
ah, mistyped the api path, that's why didn't see the request
oh, that sounds very intriguing
it should always be a +, something funny must be going on with our e2e hackery
we are proxying all stripe call through a custom python app that magically attaches a Stripe connect account via the headers in order to isolate different e2e runs from one another
abstract hull
interesting. But yeah, seems to me like the issue is with the space not getting consistently turned into a +