#danieledebenedetto_78910
1 messages · Page 1 of 1 (latest)
Hi there 👋 this sounds sort of familiar, but I'm struggling to recall the specifics offhand, I'm asking a teammate to double check that.
Double checking, you're running Checkout Sessions in payment mode and are referring to using payment_intent_data.setup_future_usage?
this is my configuration
basically i'm creating a checkout session with mode:payment with payment intent data.setup_future_usage: 'off_session'
Gotcha, yeah, that aligns with what I was thinking. My teammate has confirmed that it is expected for Apple Pay to not be offered in that scenario.
why that ?
gpay works well, which is the limitation here?
(also i suggest to add it in doc)
I totally agree this should be documented. My understanding is it is intended to be a temporary limitation as we adapt to changes that Apple is rolling out.
so for my understanding, it's something that can became availavle in the future ? or it' something that was available but apple have blocked ?
It's something that was available, which we hope to reintroduce once we've finished adapting our flows to handle Apple's new requirements.
perfect, there is an estimate date ? because it's annoying to offer only GPay and not apple pay to our customers
Sorry, no, I don't have that.
ok, where i can track the development, so that i can know if there is fix?
also you know how long has this problem been there?
I would recommend reaching out to our Support team to try to be updated on this matter.
https://support.stripe.com/?contact=true
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
I believe this has been the case since Oct of last year