#je-lunchbox-support_unexpected
obsidian cosmosBOT
👋 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/1351464056967663658
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
frail karma
Please look at this 2 transaction screenshots
refund created in seconds after processing, the source is automatic. why does this happen?
blazing root
can you share the corresponding PaymentIntent id?
obsidian cosmosBOT
subtle lintel
Is it just these 2 PaymentIntents? Or is it a recurring issue?
It's Terminal payments, right?
What's the customer experience in this case? Does it look like the payments were successful on the device?
frail karma
for now we only captured this 2 paymentintents
it's terminal payments
it is showing as payment successful on device
subtle lintel
It seems like the refund was initiated via the Terminal...
frail karma
How do we see that the refund was initiated via terminal?
subtle lintel
I don't think it's visible in the Dashboard, unfortunately. I am investigating internally.
I see you used the same card for the both transactions. Perhaps the issue is with the card, e.g. the card was rejected.
Captured+refunded is just the form in which the rejection was implemented in this case.
I don't think there's an issue with your Stripe API integration.
subtle lintel
You need to listen to payment_intent.succeeded Event in this case, and that Event never appreared.
These 400 errors are because you seem to have called the same endpoint multiple times.
frail karma
can I also know why terminal shows as successful?
subtle lintel
Yeah, this is bad customer experience, unfortunately. I guess the card was rejected later in the process, for some reason. You can try to reach out to Stripe Support, maybe they will be able to tell why this happened in your case specifically.
However, this is not the usual behavior though, and I wouldn't expect this to happen a lot.
As I said, given you're processing a lot of successful transactions, I don't think you have any issues with your Stripe integration.
frail karma
is this a successful message?
subtle lintel
The PaymentIntent status was never succeeded. The low-level Charge succeeded briefly and then refunded, but it shouldn't be a concern. You should only check the status of the PaymentIntent.