#reyanshsharma-terminal-sdi
granite garnet
olive valve
Hi! Let me help you with this.
limber canyon
Sure thanks
olive valve
Could you please share more context about the error? Any screenshots/PaymentIntent ID
limber canyon
ReaderId in question is: tmr_FAmNAVKxdN8kvc
I don't have any screenshots etc though steps:
- Check if the reader is online if so proceed.
- Create a PI.
- Send the request using endpoint [process_payment_intent]
I belive the exception is being thrown from Stripe with the prompt mentioned above [Reader is not capable of processing this action]
olive valve
On what exact action does it fail?
What type of integration do you have?
limber canyon
Server-driven implementation and exception are being thrown when calling action[process_payment_intent].
olive valve
Do you get the error in your response, or on the device?
limber canyon
Response
olive valve
Could you please share the Request ID req_xxx? https://support.stripe.com/questions/finding-the-id-for-an-api-request
limber canyon
Dont have access to the requestID
olive valve
I will need to to be able to investigate properly. Where do you see the error? You should see the req_ in the response header
limber canyon
I don't have access to the Stripe account at the moment got the details of the excerption through email which includes the PI & reader ID information only.
olive valve
Could you share the PI ID please?
eternal stump
reyanshsharma-terminal-sdi
Hi there 👋 jumping in as my teammate needs to step away. I see the error messages you're referring to, and am trying to see if I can spot why they're being thrown.
limber canyon
Sure thanks
eternal stump
Can you check what software version your reader is running, and whether it satisfies the requirement mentioned here?
https://stripe.com/docs/terminal/payments/regional?integration-country=CA#reader-software-version
eternal stump
Hm, that doesn't seem to match what I'm seeing, taking another look.
eternal stump
I'm seeing that the reader is on an older 2.15.5.0 version, did you update the reader recently? And if so has it successfully communicated with our service since the update?