#Reid-token-errors
trim wyvern
Do you have any request IDs I can look at?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
devout marten
req_WYBD1Ej9DEguoY
trim wyvern
At first glance, that sounds like the wrong API key is being used to create charges. Did you roll them recently? Or did someone accidentally add the test-mode-only API key to the production server?
devout marten
That was my first thought, but the keys seem right to me. We did have a big infra change last night moving up to node 14 and updating some elastic beanstock instances to support, but the keys seem fine. Unfortunately, none of us are dev ops experts so its all kind of sorcerers apprentice type knowledge.
trim wyvern
Ah okay. How long has it been going ong?
devout marten
Apparently all day, but we only recently noticed what is happening when a customer reached out to let us know they could not pay.
trim wyvern
Let me dig on this for a moment. Be right back
It looks like the token creation is happening with the test-mode publishable API key
Can you roll back the changes you made? Something appears to have changed the API key you were using to tokenize cards as far as I can tell
Here's an example of the request whose key is test-mode: https://dashboard-admin.stripe.com/test/logs/iar_eFmyKFpoaxvcnG
devout marten
I think we found the issue! Thanks for your insight!