#kev12kev_error
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1476288053042483281
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there! Happy to help but I'll need some more detail. Do you have an example request where you're getting the error you mentioned above?
deferred_intent[mode]
payment
deferred_intent[amount]
8675
deferred_intent[currency]
gbp
currency
gbp
key
pk_test_51QPq3MPmF7tYOGob5Yf9VuINOJdCextI4lXv7RM4zJfCxvaMCaAyRV5w1xHRv1AIqOr4i60NOPzzARIrObZYcJWI00pHACxjuV
_stripe_account
acct_1T1YrCBAQHCEKkjN
elements_init_source
stripe.elements
referrer_host
localhost:3333
stripe_js_id
23604dcc-f533-4a78-85c8-dbb6a3001873
locale
en-GB
type
deferred_intent
That looks like after the redirect to Klarna? What's the id of the PaymentIntent?
pi_3T4m6TBAQHCEKkjN1KF9M0XG
okay so this is a direct charge from a US platform on a UK express account
Yea so we're based in the US and we want to set up a express account for a UK customer
I am in the uk and I tried purchasing and got this
are you saying this isn't possible/ allowed
I'm not immediately sure. We generally do not recommend direct charges on Express accounts (see the article below) but I'm not sure if that is playing a role here. Clearly we calculated that Klarna is available but you're running into trouble on their testmode/sandbox redirect page
https://support.stripe.com/questions/what-should-i-know-about-using-direct-charges
could you have a look at the doc while I try to reproduce? We have a bulleted list of the reasons we don't recommend this mix
ok
do you have a standard account in the UK to hand that you can try this with? The problem is, when I try to reproduce I run into errors around capabilities for accounts with the recipient service agreement, so I need to reverse-engineer what you did with this account's onboarding.
or, alternatively, can you try it with destination-charge fashion using acct_1T1YrCBAQHCEKkjN as the destination?
You'll set the connected account as transfer_data.destination when creating the PaymentIntent, but will not use the Stripe header, and then you can confirm clientside with your platform's publishable key
We do not want to use destination charge as that would cause us to have to refactor how we charge normally
every other payment type like apple pay and standard credit card already works
also klarna works with hjust US accounts
Yeah, we would expect that
I found another instance of something like this happening with Klarna/cross border where we think it is some kind of bug on klarna's sandbox site. In that case, one of my teammates was able to get around it by clearing all the site data from login.playground.klarna.com and then trying again - could you give that a try
Yes
how do we clear site data in klarna if I didn't log in
You said "I’m back in the uk" - were you recently in the US? You might have a look at the network events tab when you get the redirect to Klarna in the payment flow. My guess is that Klarna still thinks you're outside the UK and Klarna is generally local-currency settlement only
my payload has the correct locale - locale
en-GB
I'd look more for something like "buyer country"
You might have to nuke all your browsing data - I'm sure there's a way on Chrome to do it on a per-site basis but I'm not immediately sure how from a couple minutes looking
It looks like we've been in touch with Klarna about the previous instance of this that I mentioned
my klarna url has en-US in it - do you know if this could be breaking
We don't think this affects livemode at all. As I mentioned, we've been in touch with Klarna about this and it looks like they've confirmed some issues of this type with their playground site, but this is overall outside our control
when i decode the JWT I get this
{
"iss": "https://one-purchase-flow-eu.playground.c2c.klarna.net",
"session_id": "b6b56d6d-2a96-46aa-b678-79b143b25a65",
"funnel_id": "c7ebb41c-c575-4a01-9949-68365b674660",
"base_url": "https://payments.playground.klarna.com/na/opf",
"environment": "playground",
"region": "us",
"purchase_country": "US",
"locale": "en-US",
"experiments": [
{
"name": "opfc-pfcc-2738-resumable-flow",
"variate": "variate-1",
"config": {
"banktransferkob": "enabled",
"payinfull": "enabled"
}
}
],
"merchant_name": "Stripe Test MID EU",
"client_event_base_url": "https://na.playground.klarnaevt.com",
"redirect_url": "https://pay.test.klarna.com/eu/requests/f2b663b7-6752-69d4-9114-cb9daebdf2da/end",
"rf": true,
"sw": "0",
"webview": false,
"exp": 1772221168
}
region purchase country and local is US
is this due to our platform account? or me as a client
Hello, my colleague had to step out, I'm catching up. Not immediately sure if that is Klarna's token or ours, but will see what I can find. Like my colleague said, this is a known issue in Klarna's playground site, but I'm not sure if that is known to be tied to certain connect configurations or not.
does this mean if we used in production it will likely work