#daniele-connect-applepay
1 messages · Page 1 of 1 (latest)
daniele-connect-applepay
@raw maple When you use Standard Connect, you usually also use our Direct Charges flow (https://stripe.com/docs/connect/direct-charges) where the payment is created on the connected account. In that case, the ApplePayDomain must also be registered on that connected account. See https://stripe.com/docs/stripe-js/elements/payment-request-button?client=html#html-js-using-with-connect
Did you do that step?
Yep! Domain connected on the connected account
in fact, it works on embed.sellix.io but not on his
this is a screen from the connected account
you can test the whole flow by going to
https://futura-services.com/
scroll down
click buy on any plan
choose Stripe (Apple Pay / Cards)
use catch@sellix.io and Demo Demo as name/surname
an invoice with the production mode of Stripe will appear
in fact, it works on embed.sellix.io but not on his
I don't understand what that could mean I'm sorry. I'm going to need a bit more than this to go on. Like do you see the button? If not it's definitely a configuration issue on the account where you need to make sure that
- You register the domain on the connected account
- You initialize Stripe.js with the right connected account in the
stripeAccountoption as documented on https://stripe.com/docs/connect/authentication#adding-the-connected-account-id-to-a-client-side-application
you see the button
no, the button does not appear on his domain (https://futura-services.com/) but it does on embed.sellix.io, which is another domain
You initialize Stripe.js with the right connected account in the stripeAccount option as documented on
yes we did
You register the domain on the connected account
yes we did
Can you share your exact code + the exact account id you're passing + the error you see in the Safari JS console and any error in the network tab?
so, very simply
this is futura-services.com, where Apple Pay does not appear
this is embed.sellix.io, where Apple Pay appears
futura-services.com uses an iframe to insert embed.sellix.io into its site as a payment page, but even if Apple Pay appears on the standalone embed page, it doesn't when the embed is inserted into futura-services.com
this is the fully scrolled console.log, though i think many of those console logs are unrelated
the code here is not important, as it works on embed.sellix.io but not on futura-services.com
the connected account is acct_1NbM88EqvvIFljS8
there are no errors in the network tab
Sorry you keep talking about "embedded" what does that mean? Like an iframe?
when i click the Purchase button, a window appears (like a modal), that's the embed
it's embed.sellix.io inserted into futura-services.com as an iframe
futura-services.com uses an iframe to insert embed.sellix.io into its site as a payment page
Yeah sorry you shared a ton of pictures and tons of words, I'm struggling to follow most of it while helping a lot of other people
Is this the first time you're using an iframe? Or have you made the iframe work before with Apple Pay in another context?
I'm struggling to follow most of it while helping a lot of other people
yeah yeah no worries, we're not rushing this; take your time
Is this the first time you're using an iframe
no, it's not the first time
we've never received such a report on thousands of customers, though i have no confirmation it also working before that i can clearly remember
the issue is that i don't really know how we could debug this, could it be the iframe? could it be something else?
the site is also serving the association at https://futura-services.com/.well-known/apple-developer-merchantid-domain-association
Yes it can absolutely be the iframe because they have to be on the same domain. That's why I'm asking really. If you have never tested this before it likely never worked in the iframe
See https://stripe.com/docs/stripe-js/elements/payment-request-button?client=html#html-js-testing
When using an iframe, its origin must match the top-level origin. Two pages have the same origin if the protocol, host (full domain name), and port (if specified) are the same for both pages.
the thing is that Stripe itself works
like, the SDK to get and use credit card payments, that works with no problems
only Apple Pay doesn't
also, if we could keep this open as i'm also loaded with other things to do ahah, will get to reply when possible
"Stripe itself works"
I mean it's all Stripe, just some features come with different restrictions. That restriction I quoted is specific to Apple Pay
So yeah if you have a website on example.com and then load an iframe from anotherwebsite.com then Apple Pay can not work
ok, makes sense
we'll see how to work that out, thank you