_unexpected

[trail vector]

👋 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/1235449006327332878

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[unique ledge]

Can you share an example Checkout Session ID (cs_xxx) that the payment method is pre-filled?

[upper flume]

this is cs_live_a1ZQtc9kLlcyqpRZwpXOm8xDs51DaKt7tdQsn0PbSBwiD6wrRXBtWpUrNy

session id of subscription is cs_live_a1tfh6AMuHi2SJSFUY4DGZUsLErBc9wmDYkIeIiSsk4J3LlQvbuwmXjMzE

[unique ledge]

There was a successful subscription created previously. The payment method will be saved onto customer for subscription, which then be pre-filled in the future Checkout Session

[upper flume]

Does the new checkout session also apply to other subscriptions or payment modes? The document seems to mention that if the payment status is limited, it only pre-fills for the same subscription.

below

Use limited to indicate that this payment method can’t always be shown to a customer in a checkout flow. For example, it can only be shown in the context of a specific subscription.

[unique ledge]

if the payment status is limited
What does limited mean here? Checkout Session/Payment Intent doesn't have such a status.

The document seems to mention that if the payment status is limited, it only pre-fills for the same subscription.
Where did you see this information from? Can you share the doc link?

In https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-customer:

In payment mode, the customer’s most recently saved card payment method will be used to prefill the email, name, card details, and billing address on the Checkout page.

In subscription mode, the customer’s default payment method will be used if it’s a card, otherwise the most recently saved card will be used.

Both payment and subscription mode will show the saved payment method

[upper flume]

we received related mail from stripe, and then, check content from https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-saved_payment_method_options

If a card information has been registered to a customer in a subscription, it seems that the payment mode will always refer to the latest information for that customer as of now. Is this correct?

Should I understand that the redisplay does not occur only when subscribing to a different new subscription?

[unique ledge]

https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-saved_payment_method_options > This is for current Checkout Session whether the new payment method should be entered or not. It doesn't control whether the previous saved payment method should be prefilled

If a card information has been registered to a customer in a subscription, it seems that the payment mode will always refer to the latest information for that customer as of now. Is this correct?
Yes! Unless previous Checkout Session which created a checkout session specifies that the saved payment method should only be displayed for specific subscription: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-saved_payment_method_options-allow_redisplay_filters

[upper flume]

thank you for your response, how about

Should I understand that the redisplay does not occur only when subscribing to a different new subscription?

when customer re-subscribe new plan

[unique ledge]

Should I understand that the redisplay does not occur only when subscribing to a different new subscription?
In https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=stripe-hosted#save-payment-methods-to-prefill-them-in-checkout
Checkout automatically saves payment methods saved in subscription mode or using setup_future_usage with allow_redisplay: limited.

Could you share an undeleted customer with a Checkout Session that has payment method prefilled, so that I can check how the payment method is saved previously?

With reference to the above doc, the payment method saved from Checkout Session in subscription mode should have limited display in the future Checkout Session

[upper flume]

we created new customer cus_Q1wH83aGGL4rgX in test-mode.

[unique ledge]

How about the Checkout Session ID that the payment method ID is prefilled?

[upper flume]

the session id is cs_test_a13RuEEHGwZIouh37Rfd1JFaIhgiDjkOX9xCQ5TQk5EerqmzBPNcNFcVJH

it was pre-filled.

it is payment mode.

[unique ledge]

In https://dashboard.stripe.com/test/customers/cus_Q1wH83aGGL4rgX, pm_1PBsPVAfGkUsdeROBgFZgLKY (ending with 4242) was created from https://dashboard.stripe.com/test/logs/req_u7V0kdAaL5PuUW which was in payment mode.

This payment method has allow_redisplay as limited

[upper flume]

Like you said, the payment method was saved as limited, but the payment mode isn't affected, right? What's the problem?