#TicketMan
crude slate
👋 how can I help?
opal cairn
Hi! My college opened this thread but has not had any support. We have been going back and forth over email however the person replying has not replied to the correct question/gotten the thread mixed up with a different one.
can you please reopen that thread
crude slate
I can't reopen the thread but we can chat here
opal cairn
okay. .. can you see the contents of the thread @wild wharf was asking about?
crude slate
Handling declines with Card Present transactions?
opal cairn
yes, specifically triggering the decline. Currently the payment intent stays as pending despite an error on the terminal
crude slate
PaymentIntent seems to be in requires_payment_method status, no?
wild wharf
Hi hanzo, yes it is has requires_payment_method status, but how can we get the latest error?
For example for the case where user tap expired card we would like to display this error in our POS application, but we can't due to the field LastPaymentError of payment intent object is null
opal cairn
Example (card present transaction - invalid expiration): https://dashboard.stripe.com/test/payments/pi_3Np8JKIbSH5OzC5G2CaZTcmM
crude slate
I feel like this error is categorized differently by our APIs somehow. Let me check
Ideally you should rely on the terminal.reader.action_failed webhook events for this
https://stripe.com/docs/terminal/payments/collect-payment?terminal-sdk-platform=server-driven&process=immediately#payment-failures
If you had a webhook endpoint, you'd have received this event
https://dashboard.stripe.com/test/events/evt_1Np8JXIbSH5OzC5GWlh14Sh6
@wild wharf @opal cairn wanna make sure you saw my message above
wild wharf
Thank you for the information hanzo, unfortunately we don't have webhook listener in our integration
crude slate
With Server Driven SDK, we'd highly recommend that you build one.
opal cairn
is there any way to produce the same result without the webhook listener?
crude slate
I don't think there's a way to reproduce it without the webhook as far as I can tell.
It seems like for some reason this error isn't classified as payment related decline but just card read error instead. I'll flag and check with our terminal team but the best way to resolve this issue would be to rely on webhook events instead
runic socketBOT
wild wharf
Can we see list of errors we can retrieve using this approach? - https://stripe.com/docs/error-handling?lang=dotnet#use-stored-information
Or vice versa - list of errors we can't get using approach above
crude slate
We don't have a list that calls that out explicitly, also not saying that the expiry error not showing up under LastPaymentError is expected.
We'd need to talk to our terminal team in order to confirm that
wild wharf
Got it. Thank you!
crude slate
NP! 🙂
opal cairn
@crude slate with regards to the email thread I mentioned at the beginning of this conversation... do you have any suggestions on how we can get the support team to answer the correct questions? They have been replying to @wild wharf with someone else's information/request.
crude slate
Can you DM me the email @wild wharf has been using for correspondence? I will try to find the ticket and see if I can flag it internally
wild wharf
ok
crude slate
thanks, looking
opal cairn
Thanks @crude slate for all your help
crude slate
No worries. Looks like the person helping you accidentally sent a response meant for a different user.
Their latest response was to ask if you were retrieving the PaymentIntent using your Publishable key or Secret API key (which is accurate)
I'll just grab the ticket for now and respond as soon as I hear back from terminal team around the expected behaviour. Apologies for the confusion.
opal cairn
sounds good, thank you!