#lucas-caldas_error
1 messages Β· Page 1 of 1 (latest)
π 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/1389341042414981194
π Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello, do you have the ID of a checkout session that saw this error? I don't think that that error relates to your webhooks but will double check
Is this what you need:
cs_test_b19kH3yz2PKPeuC5FnQFppBYpKiWnfPE6oqLL46f44UYOzgO60YbFZmIEQ
Yes thank you, looking in to this error.
Quick question: do you get this error when trying to pay with any PM or just boleto?
Only Boleto. Credit Card payments are ok.
Interesting, it looks like the error is happening because it thinks the tax ID is invalid but you are using our test CNPJ tax ID
https://docs.stripe.com/payments/boleto/accept-a-payment?payment-ui=stripe-hosted#test-integration
Can you try the CPF one to see if that has the same issue?
Same error:
Using CLI. Webhooks returns payment_intent.payment_failed and charge.failed
Gotcha. So the reason you are seeing these errors as opposed to the async ones is because the payment is erroring out before it is truly initiated. The reason for the async errors is that at a point Stripe is waiting on the bank to signal a success or failure. This is failing before that part, so it is a synchronous failure. Not sure why this is erroring this way here, but that is why there are two different error shapes
Could that be on my side of implementation? I'm using the Java SDK version 29.2.0. Do you have any suggestions on how I might troubleshoot or handle this kind of synchronous failure?
π stepping in for my teammate. Give me a few more minutes to catch up please
In your Dashboard, is there a tax ID under Settings > Business > Tax Details? Is it 000000000 ?
No. No number actually.
Got it, okay
It looks like a workaround in this case is to create a new sandbox account in BR and test with that account instead. In your existing sandbox, it looks like we're passing some placeholder tax ID that is resulting in this error
I've followed up with my team about this so we can prevent this kind of error going forward. Could you follow the steps I'm about to share to open a support case? I'll make sure details about our conversation are linked to that support case
Hello @worn mirage, we have sent you a direct message, please check it at https://discord.com/channels/@me/1389360110739914874
- πThe message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.