#Reyansh Sharma
dusk glen
supple swan
Hello! Can you provide more details? Are you seeing errors?
patent vapor
No error but was talking to someone from the support so we needed the readerIDs and PI's for the paymen intents with issues;
Conversation summery:
*I looked at telemetry for that serial number and all I really see is that the reader has a few connections/disconnections from the internet in the last day, the last time it was used fully was on March 21st when you ran test mode SetupIntent seti_1Mo8CjK8SGfgbRnhItQ8tFJX on your 'National - Dev Test' account on it and got an error about Interac.
what we need to investigate this really is concrete information so we know exactly where to look and see if there is anything to find.
- exact serial number of the device
- exact Payment/SetupIntent ID involved in a failure, and/or the exact UTC timestamp of when you had a problem
- any logs from your app about what exact SDK functions it's calling and what responses it gets*
I needed to request the reader S/N etc so that thread got closed 🙂
supple swan
You were talking to Stripe support? If so they should be able to assist. Did they send you here?
patent vapor
So sorry my falt, I was talking to someone here actually 🙂
and the last part of the conversation is as above.
Device S/N: WSC513142092851
supple swan
Okay, what about the other info requested? Do you have a Setup Intent or Payment Intent ID? Do you have error logs from your POS integration?
patent vapor
Setupintent is only from test mode (We are not having issues in test mode at all). Must be something related to the multiple devices we have.
We don't have proper POS logs at the moment implimented in the app we built though following are the PI's:
pi_3MoqB1BAWeA01Zfu0exYmnYq: Failed
pi_3MoqAsBAWeA01Zfu0SegIq8P: Intentionally cancelled
supple swan
The logs from your POS integration are the single most important piece of information in a situation like this. Do you know when you'll be able to update your app to add more logging?
patent vapor
Assuming you meant tracking all the request/response in our application locally for reference (We are planning to start working on that as soon as possible)
Also something from earlier:
Implimentation is mix of stripe SDK/API's & terminal JS. Steips are as follow:
- Discovering and connecting to a reader(terminalJS).
- Generating a connection token using [ConnectionTokenService] & using the Secret in terminalJS.
- Creating a PI on stripe account (Only amount needed initially).
- Using [PI.ClientSecret] from above created PI in terminalJS.collectPaymentMethod ==> response is PI object.
- Response from above is used in TerminalJS.processPayment
- Then finally supposed to capture the payment as PM is attached to PI after card tap/swipe.
I belive point 1,2,3 are working fine all the time but 4,5,6 only working for more than half of the transactions/payments
supple swan
To clarify, how does this issue manifest from your customer's point of view?
For 4/5/6, when it fails, what exactly happens? How does it fail?
patent vapor
In 1,2,3 we create a payment intent & then (in 4,5,6) trying to use that secret in the terminalJS to collect PM then process payment:
- After successfully creating the PI using the ClientSecret for collectPaymentMethod as input (Will tap or swipe the card on a card reader)
- Response from above is being used in terminals processPayment endpoint to process payment.
So customer select a amount --> App is waiting for customer to swipe or tap the card(Its only working once every two tries).
happened again with PI: pi_3Mor7zBAWeA01Zfu0B0z4C4s
On reader with S/N WSC513142028951
Do you think this is something related to connection token we generating through [ConnectionTokenService]?
supple swan
Right, but there must be an error being thrown somewhere on your end. From our perspective we're not seeing any activity on that Payment Intent beyond it being created.
Looking at the logs for that reader it seems like you should be seeing multiple errors in your POS code. Looks like you're trying to use a reader you're not connected to, and it looks like you're trying to use a Connection Token that's already been used.