santhosh-kumar-r_api

[dim mason]

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

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

[hushed mason]

My stripe sdk logs

I called the paymentmethod colleciton.

but it is cancelled with "user cancelled" message but user does not cancel actually

and tries to connect again

and it is conected

My query is why it is logged as "user cancelled transaction" ( red alert in the image) when the reader is trying to connect

[errant vault]

hello

What you describe doesnt really make sense, those are separate steps

you wouldnt be able to call collect payment method before connecting to a reader

[hushed mason]

yes. let me clarify .

what happens is that it is automatically reconnect when we try to call the payment method colleciton in our app

we have setup with autoReconnect: true

Further payment calls are worked correctly.
i need to understand why it is logged as "user cancelled transaction" when it is cancelling the payment method

[errant vault]

I'm not sure, do you have the actual logs from the reader? Whats the SN of the reader here?

[hushed mason]

logs are here.
we are added as toast as it is a remote device

[hushed mason]

let me check if i can get SN

[hushed mason]

will it help ?

[errant vault]

Those look like logs from event handlers on various event types, not the raw logs which includes potential errors etc.

Sorry i mean terminal SDK logs from the app host POS device

[hushed mason]

how do i get this ?

what logs do you need ?

[hushed mason]

it wont happening always.
only when reader disconnected during payment method call

[hushed mason]

can we get the SN from the transaction ?

[errant vault]

If you have an example payment I can check, sure

[errant vault]

You get this by capturing eg logcat on an Android device or device console logs from an ios device

[errant vault]

Ok, and this recovers following the reconnection and you can reattempt payment collection?

[hushed mason]

i am not maintaining the reader connection status.
so i am calling payment method colleciton when user clicked the rent button

Sometimes it is trying to reconnect so it cancelled the payment method at that time.
and followed by reconnect automatically.

[hushed mason]

yes. what do we need to capture ?

[errant vault]

The SDK logs emitted

But in the case of unexpected disconnected, I suspect this is normal/expected that the transaction is also cancelled/aborted as a result of that

And you can use the reconnect event to indicate to your customer that the reader had an issue and is reconnecting

[errant vault]

When the SDK sends onDidStartReaderReconnect to your app, display a message announcing that the reader lost connection and reconnection is in progress.
https://docs.stripe.com/terminal/payments/connect-reader?terminal-sdk-platform=react-native&reader-type=bluetooth#handle-disconnects
(event is the same or USB disconnect/reconnect)

[hushed mason]

if i provide reader serial number, will it help ?

[errant vault]

We can look at logs received our side and see if anything stands out

[hushed mason]

WPC323225003608

[hushed mason]

yes. we can. we are arleady setup the event handlers.
My doubt it that is why it logged as "user cancelled transaction" error in the payment collection method coincidentally when the reconnect is also happening automatically