#andyl_docs
worn scrollBOT
š 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/1240087324373811322
š Have more to share? Add more details, code, screenshots, videos, etc. below.
fickle fern
This should still be the case, though let me test real quick
Yep, specifying card will still automatically render GooglePay or ApplePay in Checkout
Also, as long as you have a saved card in GooglePay or ApplePay
hardy ploverBOT
prime topaz
Hi,
thank you for confirming. However another member of Stripe support wrote yesterday, when asked by one of our merchants why Apple Pay was not offered:
" Hi there,
Thank you for reaching Stripe support team and for your patience while we're checking the issue!
Taking the payment pi_3PF8SCJYX0aA0JUd0hny2UES as a sample, it seems that the PaymentIntent is being created with the parameter payment_method_types and only ācardā as a payment method is included, as you can see in the event here:
"allowed_source_types": [
"card"
"payment_method_types": [
"card"
https://dashboard.stripe.com/payments/pi_3PF8SCJYX0aA0JUd0hny2UES
Considering this, you'd need to reach out to your application (since PaymentIntents are being created on your behalf) for further assistance"
so according to what he wrote, "card" is not enough to enable Apple Pay. But according to you, it is....
shy glade
Sorry but that's definitely not correct info. I'll follow up with the relevant team to make sure they know that (with regards to that reply). i.e. To be clear, card as a payment method type encompasses both Apple and Google Pay
You say that it's not working fine, do you have a publicly accessible site with a test login that we can look at?
prime topaz
yes you can try https://bookeo.com/baytoremember/buyvoucher simply select a voucher value, input your name (or signin in with Google/Facebook) and select the "Other" button with the Apple Pay/Google Pay logos, tick the I agree checkbox and click on the Pay now button. Indeed when I do that I do not see Apple Pay as option on my phone
shy glade
you're using Checkout Sessions with payment_intent_data.setup_future_usage , Apple Pay won't be displayed as a PaymentMethod in such a case
if you omit that parameter, you'll see Apple Pay show as an option
prime topaz
mmm ok. was something changed about this?
shy glade
We made a change (it's not really recent at this point) to disable Apple Pay for setup mode and payment mode with setup future usage for Checkout Sessions. The changes were made due to the support of Apple Pay merchant tokens on Checkout and to be compliant to Apple Pay guidelines where Apple expects the merchant to always present the payment sheet for new on session payments and any price changes to an previous subscription.
Enabling Apple Pay for setup future usage for mode=payment is on the roadmap but we don't have any details to share at the point
prime topaz
mmm ok thank you for the clarification. this explains it then.
what about google pay? does it support setup_future_usage ?
prime topaz
is there a doc page where it lists which payment method types support future usage and which don't?
shy glade
the same guide which you listed in your original ask does cover setup_future_usage. I think we didn't cover the bit about Checkout and Apple Pay and setup_future_usage
If you still want to display and accept those payment methods that don't support setup_future_usage (but not save them for future usage), what you can do is to setĀ payment_method_options.<payment_method>.setup_future_usageĀ [0] specifically for those payment methods that supportĀ setup_future_usage. You'll want to omit settingĀ setup_future_usageĀ at the PaymentIntent level Ā [1] if you're setting it at the PaymentMethod level.
[0] https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_method_options
[1] https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_intent_data-setup_future_usage
prime topaz
ok thanks. PS the doc shows a green tick for "Apple Pay" under "Setup future usage 1", where the 1 footnote says "Cards and bank debit methods including SEPA debit, AU BECS direct debit, and ACSS debit support both on_session and off_session with setup future usage. All other payment method types either donāt support setup_future_usage or only support off_session" so really if one looks at the docs it is not clear if setup_future_usage=off_session is supported or not...
shy glade
I'll pass on that feedback. I think an easy way for you to find out is to check the payment_method_options and see if the payment method has setup_future_usage as a parameter
prime topaz
hi, still having problems with the same.
first of all:
If we send the request to create a checkout session with payment method types= card, apple_pay we get this error response:
Invalid payment_method_types[1]: must be one of card, acss_debit, affirm, afterpay_clearpay, alipay, au_becs_debit, bacs_debit, bancontact, blik, boleto, cashapp, customer_balance, eps, fpx, giropay, grabpay, ideal, klarna, konbini, link, oxxo, p24, paynow, paypal, pix, promptpay, sepa_debit, sofort, swish, us_bank_account, wechat_pay, revolut_pay, mobilepay, zip, or amazon_pay; request-id: req_iuqr1tnM3JnZxL
shy glade
I think we've mentioned before that you shouldn't be passing in apple_pay as a payment method type
you should omit it
prime topaz
yes I know
the reason I tried is because apple_pay is in the list of supported types, and I am trying to get setup_future_usage = of_session enabled for card and google pay at least, as you suggested
but when we send:
payment_method_types= [card]
payment_method_options
card
setup_future_usage= off_session
then google pay works (and the card is stored)
but apple pay is not even offered as option
so can you suggest a way in which setup_future_usage= off_session can be specified for card and google_pay, AND apple pay is offered as option (even without future usage)?
shy glade
To clarify, Apple Pay won't be shown if you use setup_future_usage. Now, since it's part and parcel of card, if you choose to use setup_future_usage for card, Apple Pay will not show. If you choose not to use setup_future_usage for card, then cards (including Apple and Google Pay) will not be saved for future usage. It's unfortunate but there's no solution or workaround for this right now
prime topaz
ok so essentially since all 3 fall under "card" the limitation of no future usage for apple pay means that it is not possible for card or google either (well it is, but then apple pay won't be offered)
shy glade
yep, that's right
prime topaz
... what a mess...
shy glade
sorry, totally understand it's quite confusing and it's pretty frustrating to not be able to offer Apple Pay here. I'll pass on the feedback too so that the team knows about it
prime topaz
do you have a ticket id or similar for this conversation? because now we'll have to go back to the merchant and report that we'll have to disable card storage in order to use Apple Pay, and your colleague in 1st level support (the one who told him it was our fault because we didn't specify apple_pay in the parameters! when doing so gets us an error message!) will certainly dispute our statement.
shy glade
hrm, let me try and find that support ticket
prime topaz
if it helps, it was for acct_1CMxiCJYX0aA0JUd
shy glade
so i found a recent ticket, but i don't think it explicitly mentions in the ticket that you should pass in apple_pay as a separate enum value? Or is that mentioned in another earlier ticket?
prime topaz
Alex,
no it says that "only ācardā as a payment method is included" and so "Considering this, you'd need to reach out to your application (since PaymentIntents are being created on your behalf) for further assistance: Application - Bookeo"
shy glade
i guess it's the underlying implication š¤ . Do you want me to reply on that ticket explaining what I mentioned earlier?
This Discord thread will always be here so you can also save the link
prime topaz
This is the reply I would send. Just checking with you if ok with Stripe:
Hi Tony,
sorry to see you've been "caught in the middle".
The response you received from Stripe support is unfortunately slightly misleading.
the "card" value automatically includes Apple Pay and Google Pay. In fact, it is not possible to specify apple_pay or google_pay explicitly - Stripe will return an error message if trying to do so.
This has always been the case, and just to confirm we contacted Stripe developer support today, which confirmed it:
"Yep, specifying card will still automatically render GooglePay or ApplePay in Checkout"
So that was not the issue.
However Stripe dev support also stated:
"We made a change (it's not really recent at this point) to disable Apple Pay for setup mode and payment mode with setup future usageĀ for Checkout Sessions. The changes were made due to the support of Apple Pay merchant tokens on Checkout and to be compliant to Apple Pay guidelines where Apple expects the merchant to always present the payment sheet for new on session payments and any price changes to an previous subscription.
Enabling Apple Pay for setup future usage for mode=payment is on the roadmap but we don't have any details to share at the point"
So this was the real reason why you don't see Apple Pay at checkout, because the "remember credit cards" checkbox is enabled, and Stripe no longer offers Apple Pay when card storage is requested.
After an extensive discussion with Stripe Developer support, we have come to the conclusion that due to these restrictions, from now on credit card storage will not be supported if customers choose to pay via Stripe Checkout (i.e. for the alternative methods).
This is the only way to allow Apple Pay to continue to be offered to customers.
Card storage will keep working as usual for normal credit card payments in Bookeo's dashboard and Bookeo's checkout page.
shy glade
hrm, maybe you would want to allow your users to make the selection instead?
to be specific, allow them to decide if they would like to continue saving credit cards for future usage
and put a warning that if that's the case, they won't see Apple Pay
it would probably require some engineering work on your end though
prime topaz
there is already an option to remember credit cards. it applies to direct payments (ex. from admin dashboard) and customer payments (when using the Stripe card elements and Stripe checkout). So adding a second option for checkout only would add a lot of confusion and not to mention that most merchants do want apple pay. so for now we'll disable future usage for Stripe checkout only, and wait to see if Stripe manages to support it for apple pay in the future
shy glade
ah i see, your reply looks fine to me then
prime topaz
ok. thank you for your help. having worked with many different payment gateways, your API is not perfect but better by a long mile compared to others. And definitely your tech support shines.
shy glade
glad to hear that! feel free to reach out again if you run into any issues š