monove-terminal

[west star]

@steel holly I think we'd need a lot more context:

• the reader type(P400/WisePOS E/something else) and is it using the current firmware and region configuration(https://stripe.com/docs/terminal/readers/bbpos-wisepos-e#reader-software-version)
• the PaymentIntent ID pi_xxx you're using
• which SDK you're using JS/iOS/SDK and which version

[steel holly]

P400
pi_3JjmOMB26iHaRoZC0XWE5lBO
Javascript SDK latest

[west star]

thanks

to clarify, that PaymentIntent succeeded fairly normally from what I see

so what you're saying is that reader didn't seem to update the screen and the promise didn't resolve?

[steel holly]

ch_3JjmOMB26iHaRoZC0ShhzJIJ did not succeed

[west star]

yep but that's an internal charge, you don't get that returned explicitly

it's like the reader attempts the payment, that decline happens, the reader prompts for a PIN, the customer enters it and the charge processes, and then you get a resolved Promise with the outcome, all that handling is within processPayment I believe. Maybe that's the confusion.

[steel holly]

the reader did not prompt for a pin as I explained above

[west star]

did you insert the card yourself anyway?

just so I understand, since the PaymentIntent did succeed a minute later with a contact payment

[stray belfry]

👋 Just want to hop in for a question about the PIN issue you're describing - is the location of your terminal in the US?

[west star]

(it is)

and yep I was going to say that, likely it's the regional config on the reader, perhaps.

[steel holly]

yes

[steel holly]

yes

but processPayment request never resolves

we found the issue. sorry and thank you for your time

[stray belfry]

Out of curiosity, what was it?

[steel holly]

miscommunication by tester. it had indeed requested the user insert or swipe.

until the Promise is resolved we are showing loader on our kiosk so it is confusing for the customer who may have looked away from the terminal

[stray belfry]

Ahhh, gotcha!