#Capruce
1 messages ยท Page 1 of 1 (latest)
Hi there!
Can you share request IDs (req_xxx) for each error that you mentioned (the old one and the new one)?
Sure just give me a few minutes! Thanks ๐
New request card_error that returned a charge: req_miGXtdxqC6N5w6
Old request that was invalid_request_error and no charge: req_p6AQ1rhWWK1STG
Thanks! Give me a few minutes to look into this.
Yes it looks like the API response is different due to some internal changes.
Is this change causing issues for your Stripe integration?
Thanks for looking into it ๐
Well the first case did cause us some issues as we weren't expecting the change.
We have a fix ready but I wanted to check the change was intentional before we merged it!
A final question, the new error type is card_error but the response's status code is still 400. Can we expect it to be a 402 in the future to match the other card_errors ?
That's a good question, but I don't know. I would recommend to just react to what you see the API returning.
And when you see something changing, please let us know (like you did today).
Okie doke, no worries. Thanks for your help ๐
Have a nice day!