#Eugene Bakhmetiev

1 messages · Page 1 of 1 (latest)

gloomy folioBOT
astral sapphire
#

Hey, catching up

#

The Payment Element will limit the PMs offered based of geographic location of the customer (according to session IP)

upbeat burrow
#

Thanks for the response! Does it take into account the fact that merchant is US based ? What I mean is that BNPL methods, i.e. Klarna, are supported in EU countries, but only for EU merchants, so they should be filtered out for all EU sessions

astral sapphire
#

Well, Klarna is also supported for US merchants

#

But only on USD payments

upbeat burrow
#

Yes, but Klarna is supported only if both customer and merchant are either in EU or US, so if merchant is in US, but customer's session is in EU, it should not be displayed, but it still is. Only if I change the currency of the paymentIntent to euro -- then Klarna and other unsupported methods are filtered out of the list

astral sapphire
#

I'm not sure that's true – my understanding is it only depends on the presentment currency (i.e. US merchants can only offer Klarna payments in USD)

#

So what you're describing seems accurate

upbeat burrow
#

I found this in the docs, and I interpreted it to mean that both currency and country are taken into account

astral sapphire
#

So maybe EU customers can use Klarna for USD payments as you're a US merchant? Unclear. Did you try and complete a test Klarna payment?

upbeat burrow
#

Yes, it results in this error:

The customer's billing address country is NL which is outside the countries you can accept Klarna payment from. billing_details[address][country] must be one of: US.

astral sapphire
#

Hmm, let me think about this

#

Yeah I'm not sure this is possible right now with AutoPM, in that you can't re-compute the available PMs once you've collected some billing details for example

#

My guess is we don't exclude Klarna on an IP basis in this scenario as in theory you could have a qualifiying billing address outside of your IP locale (i.e. you may be on vacation)

#

I think having the Payment Element re-compute available PMs based on billing details collected in the Address Element seems reasonable, and is something I'll relay internally

upbeat burrow
#

Okay, makes sense, thanks. What would be the best approach to control the list of PMs in this case then? Disable automatic PM list, and populate it manually based on the address?

gloomy folioBOT
digital sparrow
#

that's an option, you could geoIP-locate the customer or ask them upfront for a location, and then pass a customised payment_method_types . But yeah, not ideal.