#Félix

1 messages · Page 1 of 1 (latest)

long monolithBOT
radiant spear
#

👋 happy to help

#

you have really good Qs, I'm not sure I have the answers for them yet

#

could you please bear with me while I try asking my colleagues?

normal fern
#

Sure no problem, thank you

upper fulcrum
#

Hi! I'm taking over this thread.

#

Do you have any request ID (req_xxx) where you saw that error message?

normal fern
#

req_VBcwe0UfPS9zCs

#

I created this location for testing purposes (and then updated it with a French address)

upper fulcrum
#

So to make sure I understand your setup correctly:

  • You are a platform in France
  • And you have a custom connected account in Ireland
  • You created the PaymentIntent on your platform with a Destination Charge
  • And you get an error when trying to confirm the PaymentIntent: req_VBcwe0UfPS9zCs
  • Later you switched the country of the custom account to France, and this time you managed to confirm the PaymentIntent: req_rGRrZyVw5KCJrC
    Is this correct?
normal fern
#

This is correct except the last point: I updated the location tml_E0SbbAuMeXUBix with a French address, and this time the request was successful (req_rGRrZyVw5KCJrC).

upper fulcrum
#

Got it. But the custom account you used (acct_1Hvn8r2RIwqbgtJT) is actually a French account, not Ireland.

normal fern
#

Indeed, I tried to replicate the error from this connected account, by using a terminal location based in Ireland

vestal shore
#

not too familiar with this but it sounds like your reader needs to be in the same location as your account since it didn't work when it wasn't.

normal fern
#

Got it, do you see any problems that could arise by associating a reader geographically located in Ireland to a terminal location based in France ?

vestal shore
#

yes, that wouldn't be allowed

normal fern
#

Thank you for your answers 🙏 , just a small last one :). Why this wouldn't be allowed (I mean for two coutnries sharing the same firmware configuration), are there some specific legal reasons behind it ?