#bigyankball_apple-pay-cross-browser
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/1366414917313364112
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- bigyankball_api, 5 days ago, 10 messages
Hi, we document some of the requirements for ApplePay here, https://docs.stripe.com/apple-pay and here, https://docs.stripe.com/elements/express-checkout-element#supported-browsers
Right - so was the first dev who helped me mistaken? The thread I opened last week left me with the impression that this was achievable with the express checkout element on PC
And if it is not, is there a timeline for this to be implemented through stripe?
It sounds like you're asking if we support ApplePay on iOS 18 via scanning a sort of QR code?
Is that right?
Yes - the first docs link you sent points to this Apple support page which says Apple Pay is supported on Windows with that method
If so, Apple Pay is available on non-Safari browsers on Mac and browsers on Windows/other OS platforms using Express Checkout Element. They are able to pay using their phone to scan a QR code.
Find out which iPhone, iPad, Apple Watch, Apple Vision Pro and Mac models are compatible with Apple Pay and where you can use them for your purchases and payments.
Oh good - but that’s not working for me, would it help if I shared my code?
Is it working for others and not working for some?
document.addEventListener("load", () => {
// Create and mount the Stripe Elements express checkout button
const publishableKeyContainer = document.getElementById("stripePublishableKeyContainer") as HTMLInputElement;
if (window.Stripe == undefined) {
throw new Error("Stripe is not loaded!");
}
const stripe = window.Stripe(publishableKeyContainer.value);
const elements = stripe.elements({
mode: "payment",
currency: "gbp",
paymentMethodTypes: ["card"],
amount: 1099,
appearance: {
theme: "flat"
}
});
const expressCheckoutElement = elements.create('expressCheckout', {
paymentMethods: {
applePay: "always",
googlePay: "always"
}
});
expressCheckoutElement.mount('#express-checkout-element');
})
no, I am unable to get Apple Pay to show on windows using Firefox or Google Chrome
this is still in development, I have not published this change
I am able to get Google Pay to show which suggests to me that the element is working correctly, and perhaps there is a change that needs to be made in my stripe configuration
my domains are set up correctly
Can you share the URL where we can attempt to reproduce this on our end? Did you properly register the full domain, https://docs.stripe.com/apple-pay?platform=web#web-integration-considerations ?
I should note also that it doesn’t appear to be my browser, as I am able to get the QR code on other sites
this is a dev site so you will have to bear with me, I can set up credentials for you
I am setting up the credentials and will have them shortly, though it might be worth mentioning that I am looking at the stripe docs, this page https://docs.stripe.com/testing/wallets?ui=express-checkout-element
and the express checkout element will not render at all on windows, chrome or Firefox
please let me know when you are done, whilst this is a local db I will need to delete the user once you’ve looked
and you will need to add a product to your basket and go to the basket page to see the issue
also, I have a meeting in 20 minutes, so please excuse me if I do not reply after 4 for a little while
can you confirm receipt of these credentials please
I didn’t realise these threads were publicly visible, I am keen to delete the message
Hi taking over here
Deleted messages
Give me a bit to catch up on context fully
Then I'll test
thanks a lot, no problem at all, appreciate the help
and the express checkout element will not render at all on windows, chrome or Firefox
What did you mean by this? You don't see the Express Checkout Element rendered at all?
Earlier you said I am able to get Google Pay to show which suggests to me that the element is working correctly,
the express checkout element on this page https://docs.stripe.com/testing/wallets?ui=express-checkout-element won’t render, I mean
I can get it to render on my page, but the example on the docs won’t render, it gets stuck like this
Oh I see interesting
Sorry for the delay on this
I chatted with some folks internally on this as well
This qr code implementation isn't fully rolled out yet. It's only being surfaced to some customers at this time. That's why it's not documented publicly in our docs yet. It probably shouldn't have been suggested to you.
Apologies for the confusion on this
I see - do you have a timetable for when it will be fully rolled out? I need something I can report back to my client if at all possible - doesn’t have to be a hard date, but knowing if we’re talking weeks months or years would help a lot
Unfortunately I don't have a timeline, so I don't want to guess
These things can change due to internal priorities
I see - is there anything I can do to try and either get a timeline or advance the surfacing of the feature to my client? I understand that’s unlikely, but I wouldn’t be doing my job if I didn’t ask
Hi đź‘‹
I'm stepping in as my colleague needs to go. Unfortuantely we cannot offer any timeline or guidance at this point.