donna_terminal-reactnative

[oblique sequoia]

👋 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/1303057475078979595

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[elfin harness]

@fossil harness yes the expectation is that you do try again on the reader since the payment got declined

donna_terminal-reactnative

[fossil harness]

Yes, I figured that I have to apply action on reader, but is there any way to indicate that the payment was declined with offline_pin_required or online_or_offline_pin_required? I can't find any errors or events that show this.

Payments declined for other cases, such as generic_decline or incorrect_pin, work as expected. I receive the error, and I can successfully cancel the payment using the SDK or the reader.

[wheat bramble]

Hi 👋

I'm stepping in to offer some assistance with your Terminal integration.

[fossil harness]

Hi Snufkin

[wheat bramble]

So you are looking for error classes that specify the offline_pin_required error?

[fossil harness]

yes, and just for more information , I am using WisePad 3 and it's a ios application

[wheat bramble]

How are you testing your integration? Do you have a physical test card?

[fossil harness]

yes i have a physical test card, here are the steps and what I am seeing when I am testing:

1. create a payment with amount 10.03
2. send to the terminal, tap the test card (credit card)
3. reader display ' try card again' , there is no message and logs showing payment declined
4. reader showing 10.03 again, tried to cancel payment by cancelPaymentIntent SDK, app freeze

[wheat bramble]

For your error handling, can you add a default clause to catch any unspecified exceptions and log both the state of the reader object and the execption?

Can you tell me exactly which step you are on when the app freezes here: https://docs.stripe.com/terminal/references/testing#physical-test-cards

[fossil harness]

for error handling, I am using try catch for all the SDK call, and here is where it freeze:

1. send payment with 03 decimal to the terminal.
2. tap the card, pament doesn't go through, the SDK collectPaymentMethod doesn't give any errors back
3. trying to clear the reader screen with cancelCollectPaymentMethod() and cancel the payment with cancelPaymentIntent(), no error and it freeze

so for any other cases, such as deimal 05, 01, 55, it's working as expect

[wheat bramble]

Okay so your cancelPaymentMethod function is getting called? Can you add a log at the start?

App freezing sounds to me like some long-running process is running on the main (UI) thread in your app. It happens to me sometimes in Android. I'm trying to identify what call is hanging here.

Can you provide the serial number for your WisePad 3?

[fossil harness]

yea i can confirm the cancelPaymentMethod is getting called, but the reader is not cleard, so it's not been called properly, I can cancal payment method at any cases except when it's end with decimal 03,

and I am working with ios app, here is the serial number: WPC323225038220