#emiljonssom12344321
vagrant peak
when selecting klarna and goes to the next step they try to open a link but it is impossible
serene grail
Is this in live or test mode?
vagrant peak
it is in testmode.
serene grail
Okay can you provide a link where we can reproduce what you are seeing?
And do you see any Console errors?
Oh actually
vagrant peak
no console errors
serene grail
@vagrant peak we do call this out: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=embedded-checkout#mount-checkout
Avoid placing Checkout within another iframe because some payment methods require redirecting to another page for payment confirmation.
So yeah you can't use a payment method type like Klarna if you are going to put Checkout in an iframe here.
serene grail
We don't recommend doing that, no.
vagrant peak
ok do you know if there is any other payment methods that will have the same issue? the most important ones working for us is card payment- apple pay and google pay
serene grail
Any payment methods that require a redirect. Card payment methods do not require a redirect.
So you are fine for Card (which includes Apple Pay and Google Pay).
The most important thing is that you test each payment method type that you are going to support.
vagrant peak
yes
crimson geodeBOT
vagrant peak
is it a complete new integration to switch to custom payment flow or can parts from checkout integration be reused?
and will we have the same issue there?
clear brook
Hello 👋
It will be a new integration for the most part as the custom payment flow relies on PamyentIntents API vs Checkout Sessions API
I'm taking over for bismark so haven't had a chance to read through the whole thread yet, what's the issue you're currently seeing?
is it related to payment methods that require full page redirect?
vagrant peak
yes exactly
clear brook
If so yeah, PaymentElement (custom payment flow) also would see the same constraints
https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements#:~:text=Avoid placing the Payment Element within another iframe because some payment methods require redirecting to another page for payment confirmation
Avoid placing the Payment Element within another iframe because some payment methods require redirecting to another page for payment confirmation. If you do choose...
vagrant peak
we use the embedded checkout in an iframe
ok got it, are you looking at adding any support for redirecting from an iframe any time soon?
clear brook
Not that I am aware of unfortunately. You can certainly file a feature request using
https://support.stripe.com/?contact=true
Just for curiosity, is there a reason you're putting embedded checkout in another iframe?
You could just directly use the embedded component, no?
vagrant peak
we are a saas company providing a bookingsystem that can be integrated on any website using a script and a div.
that is why
here you can see how it works
klick the top one
clear brook
I see, got it
vagrant peak
we switched from hosted page for better control over if customer exits the payment step so we can drop the pending.
clear brook
We do have a doc about recovering abandoned carts with Hosted Checkout Page
https://stripe.com/docs/payments/checkout/abandoned-carts
vagrant peak
i think we will go for embedd, will you add a feature request to fix the issues we have or do i have to do that?