#TheMechanic
vast nexus
Hi there 👋 I'm not sure offhand what could be causing that error specifically. Do you have a publicly accessible test site where you're seeing this behavior that I could take a closer look at? Also, since it sounds like you're at the testing stage, can you confirm that you are not using an a private Safari window to test this?
nova masonBOT
azure plinth
I cannot share url, but i'm using Safari Preview v17 (as your doc says, Payment in iframe cross-domain works only for Safari >=17), not in private mode. I've add the domain to payment_method_domains list on dashboard, in test mode and normal mode
vast nexus
And your iframe and top level domain both have the same origin?
Oh, wait, I see, that's the requirement that chaned in Safari 17
azure plinth
no, it's cross-domain, and I've followed your doc : "When using an iframe, its origin must match the top-level origin (except for Safari 17 when specifying allow="payment" attribute). Two pages have the same origin if the protocol, host (full domain name), and port (if specified) are the same for both pages."
vast nexus
Hm, it's a bit trickky to think of what could be causing this without being able to see what's happening. Are you using Stripe Connect, and if so are you using Direct Charges?
vast nexus
Gotcha, Direct Charges are one of the three charge types we have available for use with Connect, where payments happen directly on the Connected Accounts.
https://stripe.com/docs/connect/charges#types
When you initialize stripe.js in your frontend, are you using the stripeAccount option?
azure plinth
we are using :
const stripePromise = loadStripe(process.env.NEXT_PUBLIC_STRIPE_KEY!);
an then :
<Elements stripe={stripePromise} options={{ locale: message?.language ?? 'fr', fonts: [ { cssSrc: 'https://marketing-assets.vercel.app/Beausite.css', }, { cssSrc: 'https://marketing-assets.vercel.app/Brice.css', }, ], }} >
vast nexus
Okay, so looks like you're initializing your frontend for a destination charge flow (or separate charges and transfers). Which menas the payment method domain would have needed to be registered for your platform account. When you were registering that domain, did you use the stripeAccount parameter there at all?
azure plinth
I registered the iframe domain :https://dashboard.stripe.com/test/settings/payment_method_domains?enabled=true
vast nexus
I'm trying to stand up a test site to test what you're describing.
Hm, it's working for me, but I registered the top level domain earlier also, let me see if removing that causes what you're describing.
Still seems to work after that registration is removed.
azure plinth
ok really weird
you are testing with safari preview Release 175 (Safari 17.0, WebKit 18617.1.1.2) ?
vast nexus
No, I don't think I'm on a preview build:
Version 17.0 (18616.1.27.111.22, 18616)
azure plinth
i try with le latest
vast nexus
Does it work on a non-preview version of Safari for you?
azure plinth
no as my "normal" version is below v17
so i try to reinstall the preview, maybe the latest will fix it
vast nexus
I'm not too familiar with the preview version of Safari, so I don't know much about what if offers. I don't know if it does, but my fear would be that they may disable more sensitive features until the build is deemed stable, which is why I was thinking checking with a non-preview build may help.
azure plinth
still the same issue
vast nexus
Were non-apple-pay payments working before you started trying to add Apple Pay?
azure plinth
yes everything else working fine (card and googlePay too)
i gonna see if I can update mac os to have normal safari in v17
vast nexus
Sounds good. I'm still not sure what could be causing that behavior, and think it would be beneficial if I could see what's happening to see if anything jumps out at me, if it's possible to share a test site.
azure plinth
I check this safari stuff, then if still issues I try to give you a test url !