#onur_ece-klarna
lyric cloakBOT
đ 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/1438963093832073348
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
wary dune
It is not clear which method to use on FE side to confirm this next action too.
Right now we use confirmPayment(clientSecret)
some docs say => const {error, paymentIntent} = await confirmPayment(clientSecret, {
paymentMethodType: 'Klarna'
},
});
some say => use confirmKlarnaPayment(clientSecret)
But the root problem is we can't even test. Because we can't get this next action to trigger which is comparable easy with Credit cards using 3184 card.
left flume
onur_ece
I have never heard of something like this ever being possible with Klarna
onur_ece-klarna
wary dune
If you are able to see intent info
pi_3STRawEilDfETi8Y03pr48TW -> no next action
pi_3STS7t4iU67VQe1Z1rWNjtpj -> action required
in the next action url I see something like
"https://pm-redirects.stripe.com/authorize/***/***?useWebAuthSession=true&followRedirectsInSDK=true"```looking
wary dune
thanks. In klarna docs; it only mentions approve/decline cases; but nothing related to next action:
left flume
I don't get your examples, they seem completely different
One confirmed with a ConfirmationToken and succeeded
The other one confirmed without one, though you seem to have done an Update PaymentIntent and passed a PaymentMethod before?
Can you try to explain what is happening and why they are different? They are on differnet accounts too (one for your own and one for a connected account)
Did both use ECE? Why did one use ConfirmationToken and not the other one if so?
wary dune
our web and mobile implementation is different; web uses confirmation tokens. mobile doesn't at the moment.
I was just looking at the latest transactions for Klarna; that is probably why they are from different accounts. Our company have multiple accounts for multiple gateways.
I see another intent pi_3STRTL4iU67VQe1Z1cttaKlS
left flume
Like that second PaymentIntent (pi_3STS7t4iU67VQe1Z1rWNjtpj) to me looks like someone said "I want to pay with Klarna" on your mobile app but haven't done anything yet and then you confirm the PaymentIntent so we send them to Klarna to sign in/sign up and pay -> next action
That first one (pi_3STRawEilDfETi8Y03pr48TW) uses ECE so they log into Klarna upfront and then when you confirm the PI it has already had the payment mostly approved so no next action
wary dune
do we need to change anything with the confirmPayment call for mobile then? Stripe AI docs suggesting:
React Native: use confirmPayment() with paymentMethodType: 'Klarna'
left flume
Not really, to me it all seems to be working totally as expected
ECE is just a different integration path
On Mobile you confirm -> then go to Klarna
On web with PaymentElement you confirm -> then go to Klarna
On web with ExpressCheckoutElement -> you pick klarna and enter all the details -> then confirm
Let me know if that doesn't make sense
wary dune
I am checking with our mobile dev right now
left flume
sounds good
lyric cloakBOT