#kenny_unexpected
crimson cobaltBOT
👋 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/1362345249158074519
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- kenny_code, 1 day ago, 71 messages
- kenny_code, 1 day ago, 74 messages
gritty cedar
What's the pm_xxx ID?
hot timber
pm_1REnCuCWRQ9TqHkCtXsORYQJ
here's the checkout session id as well: cs_test_a1drgnenrgL4lOlTc255NW6qH3UvINgquFLA031YfuJbiEiAKwHr3rm096
I have 3 payment methods, 2 have their redisplay value set to "limited" and the third one (the one I sent to you) should be set to "always"
gritty cedar
I think it's because there's billing fields missing:
The payment method includes billing_details required by the Checkout Session’s billing_address_collection value:
- auto requires values for email, name, and address[country]. US, CA, and GB billing addresses also require address[postal_code].
- required requires values for email, name, and all address fields.
hot timber
Why would that prevent it from showing though. These show up fine in the stripe dashboard and when I hit the payment methods endpoint directly
gritty cedar
Because Checkout has strict requirements as the doc outlines
hot timber
im not expecting it to prefill fields though
gritty cedar
I understand that, and I'm not sure that this is the problem. But can you please at least try and update the PM with the fields outlined above?
Custom Checkout is still new to us too so not entirely familiar with this
hot timber
how can I do that? can it be done through the dashboard?
gritty cedar
But based on existing Checkout requirements, I suspect this might be the issue
gritty cedar
how can I do that? can it be done through the dashboard?
Yep!
gritty cedar
There's no email field:
auto requires values for email, name, and address[country]. US, CA, and GB billing addresses also require address[postal_code].
hot timber
ah i guess ill need to update that via the api
adding the email seemed to do the trick:
sPM [{"id":"pm_1REoGECWRQ9TqHkCTlk5Ic90","type":"card","card":{"brand":"visa","expMonth":4,"expYear":2028,"last4":"4242"},"billingDetails":{"address":{"city":null,"country":"MY","line1":null,"line2":null,"postal_code":null,"state":null},"email":"kenny@kdco.llc","name":null,"phone":null,"tax_id":null}}]
Perfect!
hot timber
This is a bit troublesome for my use-case. Each stripe customer belongs to an "organization" not a particular user so how do you suggest I collect the email for this? For example, a user creates an account and they either need to create an organization or join one. Maybe the owner of the organization's email is defaulted to the "billing email" which they can change later? What are your thoughts?
sturdy stirrup
Hi. I'm taking over from my colleague. Please, give me a moment to catch up.
hot timber
ok
sturdy stirrup
I would say the Customer object represents a buyer. You don't need to create a Customer for each of the individual users of your app, but rather for an organization that buys your products/services. And the email can be either of the person responsible for buying, or some shared company email address, this depends on your users' preference