#Krunal-WisePOS-E
1 messages · Page 1 of 1 (latest)
@junior perch let's use the thread here. Can you explain more why you want to timeout or reset in mobile app?
yes
Actually we have case
when some one is not doing payment after initiating the payment and Amount display on reader will be there -0 in this case it's stuck
on next discovery it's failed
Re initalization is not allowed in Mobile app sdk
Hi @junior perch can you send me the payment intent ID?
give me some more time sorry for delay busy with something else
I am giving you payment intent id
pi_3L3xwTBTDnqJlDMT0Yhl0kUz
payment intent d
Hey
Are you there ?
now if i kill my mobile app terminal stuck there with amount screen
Hi @junior perch yes I'm here
I only see a PaymentIntent creation request from you backend, there's no subsequent confirmation request from the Terminal reader
yes that's the question
if i am not swiping card on terminal and kill my mobile app
then when terminal will clear or reset existing request
is there any way ?
we tried reset reader api but it is not working
giving error like - Reader is currently processing a transaction from a different integration mode.
i have raised query in chat section of stripe as well
for the same case
What's your Terminal code like?
means you need serial number ?
No, you Android or iOS code.
You are using an mobile app connecting to a bluetooth reader right?
no internet reader method
i am using terminal sdk for iOS & android both
{"terminals":[{"label":"new Terminal","serial":"WSC513124019824","terminalId":"tmr_EkuHVwBVPTuxjP"}]}
This is my terminal
we have server oriented payment process
OK, so you are using server-driven integration
Our web app is already live
yes
Client name is adit - it is live on
https://app.adit.com/
Now we are doing the same for mobile app
So basically your mobile app talks to your server and you are making API call from your server to Stripe Terminal, is it the correct understanding?
yes
just token call is from mobile app to sdk running
discovering and selecting terminal is also from mobile app
so far I can see your server is making the paymentIntent creation https://stripe.com/docs/terminal/payments/collect-payment?terminal-sdk-platform=server-driven#create-payment
just collecting payment and processing payment is from server end
anything blocking it from processing the payment? https://stripe.com/docs/terminal/payments/collect-payment?terminal-sdk-platform=server-driven#process-payment
no positive case of payment is working fine
we can proceed for payment and it is working
Use Case 1 :User initiate payment for In office payment using terminalSearch for Terminal ( Discover )
Select Terminal Request for Payment and confirm for proceed furtherTerminal will display amount for payment User kill app or back any how or not responding to terminal for any reason
Issue - Terminal will goes into Standby mode and not resetting on new request Restart terminal is only solution for next payment in this case.
Did you also make the request to capture the payment? https://stripe.com/docs/terminal/payments/collect-payment?terminal-sdk-platform=server-driven#capture-payment
no i am not doing capture payment request
and killing mobile app without it
You need to capture the payment after processing it
my question for same Negative case - how to reset terminal display
that is ok payment is proceed and working fine
I want to clear terminal display from server end
is it possible ?
or from mobile sdk end
Use Case 2 :
- User request payment from mobile app for Customer A
- Wait for 1-2 min to swipe card and meanwhile some one initiate payment from web
- web is resetting that mobile app request and clear terminal display and requesting new amount on top of that existing request for Customer B
- If Mobile App user doesn't know about it - it will swipe customer's card and payment will cut on that customer A for the request of Customer B
https://stripe.com/docs/terminal/payments/collect-payment?terminal-sdk-platform=server-driven#request-cancellation Here is how you can reset the reader
yeah but that's not the ask @fiery tendon ,they want to cancel it from the mobile side, they are using the same reader from the server-driven integration and also in a mobile SDK integration at the same time
correct
@junior perch ultimately I don't think there's a good solution here since the SDKs don't really expect to be used simultaneously like that. I would just catch the error you get in the app(that "Reader is currently processing a transaction" one you mentioned) and handle it robustly by letting the cashier know the payment didn't go through
that's ok but in real time scenario with mobile app is like kill app or internet down case
what's the default session timeout for terminal
I don't know I'm afraid
And how can we customize it ?
not sure you can!
so our issue is terminal stuck
in above case user's need to restart the terminal
after that works for next payment
is it an option to not use both integrations here?
no that's not possible
we probably intended that you only use either the server-driven integration or the mobile SDK integrations
not both at the same time
we are only using server driven method here but reset is must in any case
as in mobile app re-intialization is not allowed like in web sdk have
anyway you're also talking to our main support team you said so I'm not going to duplicate effort, they can help and escalate the issue for you and you can write a detailed email if needed
i have already chatted with support team in website they must have created support ticket with my transcript email
sounds good
but no reply from any team member yet
it's been 5 minutes
ok
you're asking a complicated question about an edge case in an advanced way of using Terminal so it will take time to understand the use case and get you the best answer
you can reply back to your email thread and ask that
k
i have sent it from our beta registered account
aditpay15@gmail.com
can you give me ticket id for future conversation
if possible