#shaz_api
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/1435715596913217560
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi, can you share a PaymentIntent id or a CheckoutSession id where you did not see these payment methods?
Thanks for the ID, taking a look
The reason being, these payment methods do not support recurring payments: https://docs.stripe.com/payments/afterpay-clearpay
When you created the PaymentIntent, https://dashboard.stripe.com/acct_1SNvAfGdcwcGIozO/logs/req_xTYOgrpzU5eoRh you passed setup future usage
If you take away setup_future_usage, these should show up
Hmm I see but we use setup_future_usage as an upsell feature so that the customers card details are saved and can more easily purchase other products from the same business
Is there any other way we can persistat that functionality while also enabling the payment method?
Can you tell me more about what you mean my persist that functionality?
I meant that as far as I know, the only way to ensure a users card details are saved on their stripe customer (on a non recurring payment) is to provide setup_future_usage: 'off_session', so that after payment at any later date if the customer revisits a new offering/product their payment method is already there, so checkout out is essentially one click
But you mentioned that setup_future_usage must be removed to enable the payment method, but then we lose the ability to keep the users card on the stripe customer?
If you want to offer a mix of PMs that can be saved an ones that can't, payment intents have a property called payment_method_options that lets you set settings per payment
So you can set payment_method_options.afterpay_clearpay.setup_future_usage to none and that should let affirm show up even if setup_future_usage is set for the overall intent https://docs.stripe.com/api/payment_intents/create?api-version=2025-10-29.preview#create_payment_intent-payment_method_options-afterpay_clearpay-setup_future_usage
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Ah great, so can I set setup_future_usage: 'off_session', at the payment intent level, and then specifically set it to none for some to make it show?
Correct!
Awesome, thank god it's possible haha
Appreciate it!
Also one other question
when you download the accounts list e.g:
Does requested_active mean it is enabled?
Yep that means enabled!
Awesome, thanks all done ๐