#Luís Jesus
1 messages · Page 1 of 1 (latest)
👋 Give me a few to take a look
Thank you!
Sorry server is a bit busy.
I think this is happening due to regional restrictions on terminal payments
https://stripe.com/docs/terminal/payments/regional?integration-country=PT#:~:text=In order to process Terminal payments%2C both the Stripe account receiving the funds and the location associated with the reader must be in the same country%2C accepting local currency only.
Hi there, no problem
Well in that page it says that the Tap to Pay is in Beta in Portugal
Do you think it has to do with this: "In order to process Terminal payments, both the Stripe account receiving the funds and the location associated with the reader must be in the same country, accepting local currency only."
The thing is that I'm able to create the payment intent on_behalf_of a Portuguese Connected Account, but this error happens beforehand, when I'm connecting to the reader, it's not when processing the payment.
"To accept Terminal charges in Portugal, either your platform account or connected account must be in Portugal." -> I'm fine with this, we have a connected account in Portugal
But this happens when connecting to the reader
I've tried creating the Location in the Connected Account instead, but then it says that the API Key doesn't have access to that location
What is the proposed way to do payments with the Terminal SDK when doing payment intents on behalf of another connected account? How should the connection to the reader be made, and to which location?
I'm seeing that I can potentially associate a location with a Connected Account using Metadata: https://stripe.com/docs/terminal/design-multiparty-platform?locale=pt-BR#express-or-custom-connect is this the way to go? If so, what should I put on the metadata?
Sorry, give me a couple minutes to catch up.
Server got super busy
No problem, sorry for the information overload 😆
Appreciate your patience
The thing is that I'm able to create the payment intent on_behalf_of a Portuguese Connected Account, but this error happens beforehand, when I'm connecting to the reader, it's not when processing the payment.
I see. So you're seeing the error when you callprocessPayment?