#hallmatt_api
ruby geodeBOT
👋 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/1285236329093009468
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
candid valveBOT
tropic moat
Hi there 👋 I'm assuming you're referring to our Pricing Table when you say "pricing grid", but let me know if that's a bad assumption.
Passing existing Customers in a Pricing Table integration is discussed here:
https://docs.stripe.com/payments/checkout/pricing-table#customer-session
sudden locust
yep!
but when i pass in a customer to that customersession...the existing customer's payment methods don't show up within Checkout
tropic moat
Regarding their previously used payment methods showing in the Checkout Session that is created by the Pricing Table, there are some additional requirements there. Let me double check what those are.
sudden locust
thank you!
i'm seemingly able to pass the customer fine...pretty simple...but the customer's email AND previously used payment methods don't seem to show. which makes me think im doing something wrong 🙂
- don't seem to show in Checkout
tropic moat
It's a bit buried, but we discuss the requirements here:
https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=stripe-hosted#handling-existing-customers
Typically the limiting factor is that there aren't complete billing details saved with the payment method, usually a billing address isn't collected and that limits the payment methods from being able to be shown.
Are you using the Pricing Table for all of your payments?
sudden locust
we are going to switch to Pricing Table for all...yes
tropic moat
Gotcha, it may be too late to reuse the existing Payment Methods you have, but I believe if you configure the Pricing Table so that it collects full billing addresses that you'll be able to reuse the payment methods created from the Pricing Table.
I'd suggest testing that:
sudden locust
interesting...so the existing payment methods might not have billing information?
tropic moat
That's my suspicion, do you have the ID of a Payment Method that you aren't seeing dispalyed that we could take a closer look at?
sudden locust
yeah hang on one second. thank so much!
using this customer: cus_7iKYkxkhfbqNJA
pm_1Pyh1h4rOnkhckTrHk65vBwz
but even the email doesn't show up
but i have a "billing email" on that customer
here's a billing portal session i'm passing to the Pricing Grid: bps_1PzfXr4rOnkhckTrbzqLhYyC
wait. i think i solves that issue
tropic moat
It's all or nothing for payment method filling, if any detail is missing then nothing is populated automatically.
I'm taking a closer look at that PM now.
Ah, so that one looks like it has all the details, so for a payment mode Checkout Session it'd be populated if it was used for the Customer's most recent payment
** but**
allow_redisplay is set to limited there which I believe also prevents it from being displayed in checkout:
https://docs.stripe.com/api/payment_methods/object#payment_method_object-allow_redisplay
sudden locust
this PM was created in checkout: pm_1PzfcN4rOnkhckTrlqhhPxrb
but doesnt autofill when i come back and use the pricing grid again
so is there a customer portal / checkout / pricing grid setting to allow redisplay?
the checkoutsession seems to not let me set that when using the pricing_grid component...as only one component is allowed
ruby geodeBOT
buoyant crag
👋 stepping in here and catching up
sudden locust
thank you!
buoyant crag
Yeah so you can't specify saved_payment_method_options (https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-saved_payment_method_options) when using Pricing Table
So the redisplay is going to default to limited
This is basically a limitation of Pricing Table at the moment
So what you could do is manually update that redisplay option for the PaymentMethod using https://docs.stripe.com/api/payment_methods/update#update_payment_method-allow_redisplay after the Checkout Session is completed.
sudden locust
gotcha ok
i think i tried pricing tables out 2 years ago when it was first in beta...but it was missing some of these little features that make it worthwhile. the big one was that missing was the ability for an existing customer to look at a pricing table and select a new plan. it seems like this is still not available. how do people show a pricing table to existing customers and allow them to update their subscription? it seems like the customer portal won't show any details on the plans...just the name and price, correct?
buoyant crag
What do you mean by "details on the plans"?
sudden locust
the pricing table shows "this includes:..."
if i try to update an existing plan in Customer Portal...it doesn't show what it includes
buoyant crag
Where are you setting This includes:?
Is that set as the description on the Product?
sudden locust
i guess thats on the pricing table i believe
so thats why it wouldnt show up
essentially...i want to use pricing table for new and existing customers. but it seems to not work with existing customers to update an existing subscription...just new subscriptions only. which really doesn't help. cause it seems like i'll still need a separate custom-built pricing table for existing customers to know what they heck they're upgrading TO
so the question is...how are people using the pricing table for existing customers? or they're not? or using some other link?
buoyant crag
Yeah Pricing Table is only meant for new Subscriptions.
It isn't designed for updates
You use Customer Portal for updates.
Otherwise, if you want this all-in-one, you build your own custom UI here
And handle this yourself
sudden locust
thats extremely frustrating
im not sure what good a pricing table is if it's only for new customers...and theres no way for existing customers to understand what they're getting when upgrading
buoyant crag
It is a simple premade UI, it isn't meant for complex checkout/designs here.
It sounds like you want to handle a bunch of complexity all-in-one, which means you need to build out your own custom flow in that case.
sudden locust
showing a pricing gird to an existing customer is as basic as it gets my friend
buoyant crag
No that is not true
First, there is tons of complexity involved with all of this different variation.
Second, we already offer that -- that is what Customer Portal does.
So one option, if you want to leverage these prebuilt UIs, is to figure out what your customer is trying to do up front. Then you can either redirect them to Customer Portal for an update or you can show them Pricing Table for a new Subscription.
And while yes, I agree that it would be really nice if we also built this into Pricing Table, it isn't just "simple".
Everything is a trade off of what is built and what is invested in.
So the current state is that that wasn't prioritized over other Billing features.
sudden locust
you can use customer portal to update a subscription, but the customer has no idea what they're upgrading to
so...you need to build a custom pricing table anyway to show them what they're upgrading to...which defeats the purpose of using stripe's
buoyant crag
you can use customer portal to update a subscription, but the customer has no id...
That's not true?
We absolutely show the Price/Product for what they are updating to
sudden locust
only a name of a product (which often is like "premium" or "basic" and a price)
a product...or subscription...for most companies...could empass dozens of features in an upgrade
which is exactly why pricing tables were created. cause stripe understands that. but it's quite puzzling why stripe would say "hey! we understand you need pricing tables...but JUST for new customers". logic just doesnt follow that existing customers would't need the SAME pricing grid in order to figure out which plan to upgrade to
buoyant crag
The Customer Portal does show whatever you set in description for the Product when the customer clicks the "Update plan" button
Which is the same thing Pricing Table shows
sudden locust
ok! that might work! thats good! ill give that a try
better than nothin'!
i saw something about "deep links" into the customer portal, i believe. would that help me at all? maybe i could list out products within the app and deep link to a specific product update in the customer portal?
buoyant crag
Yes I believe that should work. You should be able to deep link into the specific update I think
Let me check
Yes I believe this should work. You would deep link to the subscription_update flow (https://docs.stripe.com/api/customer_portal/sessions/create#create_portal_session-flow_data-type) and then you use a Portal Configuration where you specify within features_subscription_updates.products the Product/Price that you are sending them to update (https://docs.stripe.com/api/customer_portal/configurations/object#portal_configuration_object-features-subscription_update-products)
I'd recommend testing it out to make sure it works as expected as I haven't tested that exact flow before
sudden locust
ill give it a try!
thanks for your help. hopefully one day ill win the lottery and stripe will come out with a way to use pricing tables for existing customers 🙂
buoyant crag
lol fingers crossed
sudden locust
🙂
just solving some of these little painpoints would help make pricing tables more amazing. i'm a developer...i can work around it somehow (custom pricing table, integration, etc). but might as well try to use stripe's built in stuff if we can
buoyant crag
Yep we want to provide as many things out-of-the-box as we can!