#luc_checkout-error
hardy horizonBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1303478370205696163
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
undone jolt
luc_checkout-error
@shrewd nymph the error message associated with that request you shared has nothing to do with an API version change. You seem to be mixing up your customer ids and using one that doesn't exist on the account
shrewd nymph
I see that the customer was deleted https://dashboard.stripe.com/logs?object=cus_QpR06IzVjC9Or4&starting_after=1730443673-req_Nh8SOgQA5FaXYc
is it possible to know if the customer was deleted via the stripe dashboard or via api?
undone jolt
You can load that Customer in the Dashboard and then see the logs for example and checked what caused the deletion
As far as I can tell this was deleted manually in the Dashboard by someone deleting multiple Customers at once back in September
undone jolt
You can't really see it sadly because it used the "batch" delete feature in the Dashboard. But it's what happened.
shrewd nymph
https://dashboard.stripe.com/logs?showIP=false&method[0]=delete&dashboard=false
I'm using this, but the filter is set to API... does the batch delete feature uses the API behind the scenes?
i see now
undone jolt
yes it does and shows StripeBatchAPI/1.0 which is how I knew what happened
shrewd nymph
so the only way to use the stripeBatch api is via the dashboard, right?
undone jolt
yes
shrewd nymph
req_4taNkSm84igAKG about this request error, it seems that it's as easy as adding this customer_update[
customer_update[address]=auto on the api call*
undone jolt
possibly!
Sorry you just dumped a request id and a picture with no context at all on your question 😅
shrewd nymph
about this request error, it seems that it's as easy as adding this customer_update[address]=auto on the api call to fix it?
undone jolt
Sorry this is the exact same sentence right?
I'm happy to help you, but can you try to provide clear details about your questions? Sure I can load the request, try to figure out what you were doing, what caused it and then explain, but I think the first step is for you to ask a clear question
hardy horizonBOT
shrewd nymph
ok, so I have this request id that returned an error. but I want to understand why it just returned an erro after oct 26 (that was when the last successful checkout/sessions occurred)
most of the errors are because the customer was deleted, but this one is not
cursive salmon
👋 Stepping in for my teammate
shrewd nymph
this is the customer https://dashboard.stripe.com/customers/cus_R8lD2G2tchoNXN
cursive salmon
Can you copy/paste that request ID (begins with req_... in your screenshot) and share it here?
shrewd nymph
req_w6YpXWierb5MM4
i know the error message is clear and it should be okay if I add the customer_update[address]=auto to the call, but I'd like to understand why it worked before
cursive salmon
Do you have an example of where it worked before?
shrewd nymph
req_vLUQs6Bobn4FA1
this one worked
cursive salmon
Right, the issue with this particular request is that, in order to enable tax_id_collection, the customer used needs to have an address (or the Session needs to be created in such a way as to allow the customer to update their address)
Thanks!
Okay, so I see the customer in the request that worked (cus_QuwnZc48FlveX8) has a saved address
shrewd nymph
but both requests had the tax_id_calculation enabled
cursive salmon
The address for customer cus_QuwnZc48FlveX8 was added back in September so we were able to pull that address and use it for the tax ID collection
shrewd nymph
I see now, it seems that the customer cus_R8lD2G2tchoNXN was added via the dashboard and no address was given
it seems that we have 2 customers with the same email cus_MX4JBrNOCcSr39 and cus_R8lD2G2tchoNXN
cursive salmon
Hm, I see those two customers have different email addresses in Stripe
shrewd nymph
you are correct, I saw another email and got confused..sorry about that
but the issue was that cus_R8lD2G2tchoNXN was created via the stripe dashboard and doesn't have an address...that's why the api call faled
one last question, is there an easy way to pull all those customers ids? the deleted ones https://dashboard.stripe.com/logs?showIP=false&method[0]=delete&dashboard=false
just from september 24
cursive salmon
No, there's no programmatic way to pull these IDs
The list all customers and search customers endpoints don't allow you to filter for deleted customers
shrewd nymph
is there an API to get the logs? haha
cursive salmon
No, unfortunately