Josh_FloralFrog | Stripe Developers | Page 1

mint valveBOT Mar 15, 2023, 2:29 PM

#

ruby yarrow Mar 15, 2023, 2:29 PM

#

Can you send the ID of the payment intent (pi_123) or request (req_123) that you saw this error on?

outer canyon Mar 15, 2023, 2:30 PM

#

sure: req_H77reTdRHcBMCU

ruby yarrow Mar 15, 2023, 2:32 PM

#

That looks like a different request, the error we sent back for that one was:

The card_present source type with currency usd is not supported in GB.
https://dashboard.stripe.com/logs/req_H77reTdRHcBMCU

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

outer canyon Mar 15, 2023, 2:33 PM

#

that's odd, let me check something

#

sorry, my mistake, it's req_7T54NVYhkcaPjM

ruby yarrow Mar 15, 2023, 2:37 PM

#

So the API path that I am seeing for that request is /v1/test_helpers/terminal/readers/tmr_FA1ypgTvIGR3mH/present_payment_method https://dashboard.stripe.com/logs/req_7T54NVYhkcaPjM
Which is this call for simulating presenting the payment method on the reader
https://stripe.com/docs/api/terminal/readers/present_payment_method
Do you know where in your code you are making that call? Looks like it is intended to be a test mode only API method

outer canyon Mar 15, 2023, 2:40 PM

#

Ahh, we suspected it may be something loke that but the coder responsible said this hadn't been done. so without diving into the docs, if we removed the /test_helpers/ section, would I be correct to assume this would correct the issue?

#

The payments do actually go through using a seperate PI so perhaps this testing code was left running along-side by mistake

ruby yarrow Mar 15, 2023, 2:46 PM

#

Not quite but if that is in a live code path there is likely something else your integration is trying to do like pass the payment intent to the reader. I think I'd need more information on what your code is trying to do at that point to say what it can be replaced with

outer canyon Mar 15, 2023, 2:48 PM

#

Looking at the logs, i can see 2 requests being sent to stripe, one for the simulated terminal, and the one that works okay, in this case, the other request is
req_qyqTNoWL9kHuSU

ruby yarrow Mar 15, 2023, 2:55 PM

#

So it actually looks like that method is entirely used for simulated readers https://stripe.com/docs/terminal/payments/collect-payment?terminal-sdk-platform=server-driven&reader=simulated#simulate-a-payment

Collect payments

Prepare your application and backend to collect payments using Stripe Terminal.

#

That other call is for actually sending payment data to your terminal, so that would be expected in this flow in live mode

#

So it is sounding more like some test code is accidentally getting called here. I think the next step would be to debug on your side, unfortunately I am not getting enough context from these logs to know for sure why that call is being made

outer canyon Mar 15, 2023, 2:59 PM

#

No that's okay, it sounds like the type of issue this coder has created in the past (ie forgetting to disable test code) but thank you for your help! if there's any other issue's I'll be sure to let you guys know

ruby yarrow Mar 15, 2023, 3:11 PM

#

Ah, yeah that makes sense then. Glad I could help, definitely let us know

#Josh_FloralFrog