#battbot
tacit lichen
The event id is
evt_1NS1ovJ93KfFVesbqnBz3Ib4
finite oak
Can you share the example webhook event ID and/or payment intent id?
tacit lichen
the payment intent is:
pi_3NS1oaJ93KfFVesb0dngE79A
finite oak
ah thanks
tacit lichen
this resulted in us reporting to the customer that his payment wasn't successful. so he tried again and ended up doing double payment
he call to complaine the next day that the first payment was charged and asked us to refund but we cannot refund since it's interac payment and he's no longer present at the store with his card
finite oak
Looking at the logs for the reader now
tacit lichen
We don't know how the Stripe cloud server got the payment information from the reader and processed the payment but then went ahead and sent us a webhook call telling us it failed. There must be a bug in your server code somewhere. When this happens it's making our payment handling extremely unreliable
finite oak
We're looking into this currently -- will share when I have more or any further questions
tacit lichen
ok thank you
finite oak
Ok, this is possible and ~normal where a reader has intermittent connectivity issues
When you get that connection error event, you need to explicitly check the Payment Intent status to see if it succeeded before retrying
This is explained here:
https://stripe.com/docs/terminal/payments/collect-payment?terminal-sdk-platform=server-driven#payment-timeout
tacit lichen
our code does check, but at that time the payment_intent status wasn't successful
and there's no other webhooks which updates us on a successful status for this particular reader/payment intent
finite oak
our code does check
Can you explain more or how this is done?
tacit lichen
when the reader tells us successful or failed event, we get the payment intent and check its status to verify
tacit lichen
in our logs, when we checked, the status of the payment_intent did not == "succeeded"
tacit lichen
if the payment_intent status isn't succeeded and the webhook told us it failed, we interprete it as a failure
we will add code to try and recover from this scenario then, thank you for the help
spare vortexBOT
finite oak
webhook told us it failed
The webhook says that the reader action failed with a communication error, which is different and more specific
Are you reattempting payment with the same payment intent, or a new one?
You can also cancel the payment intent to ensure its not successful
tacit lichen
I'm trying to check the developer logs the GET method for this payment intent when we called it
but your filters doesn't work very well
when i use the API filter
/v1/payment_intents/pi_3NS1oaJ93KfFVesb0dngE79A
it gets no results
we reattempt using a new payment intent
finite oak
we reattempt using a new payment intent
I would not recommend that. You should generally retry with the same one, which would avoid a duplicate charge (it would error if already successful when you try again)
If you do want to use a new one, you should first cancel the initial PI