#monove

1 messages · Page 1 of 1 (latest)

vagrant meadowBOT
ember holly
#

Can you share the request id for creating this payment intent?

ancient coyote
#

heres the event id: evt_3No5SA2aA6B7Coa30WkriaFZ

#

does that work?

ember holly
#

Yes

#

One moment

#

OK I see. Well when you tapped the card, payment failed because you need to insert the card

#

So it's expected you'd get a payment_intent.payment_failed event in that scenario as well

#

This was the error message: This transaction requires chip and PIN. In testmode, using a physical test card with designated amount ending values produce specific decline responses. See https://stripe.com/docs/terminal/references/testing#physical-test-cards for details.

ancient coyote
#

correct, but why the cancel

#

event

#

perhaps related: take a look at req_VDFldRfLKc0OES. the terminal still shows "insert to pay". we were advised that a when a payment intent is cancelled, the screen is cleared

ember holly
ancient coyote
#

in Live mode, does the payment_intent become cancelled before they have a chance to dip their card to enter their pin?

ancient coyote
#

if it came from our API it is because the flow is/used to be that there was no second chance if the pin needed to be entered. has that changed?

ember holly
#

Yeah shows it came from your backend. PHP

ancient coyote
#

ok

ember holly
#

Oh hm I thought that as well

#

Let me ask a colleague

#

Which reader do you have?

#

Since you're using our server driven integration, you need to call cancelAction

ancient coyote
ember holly
#

Oh yikes I see the same hmm

#

Looking

ancient coyote
#

next question: on the payment_intent level, how can we know if the reader is still waiting for more info, ie pin

vagrant meadowBOT
ember holly
ember holly
ancient coyote
#

i guess i'll get it from the reader