#jot_portal-customername
small oakBOT
👋 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/1468290583683661982
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
lone olive
Hi there!
The Customer Portal needs a Customer to create the portal sessions so I suspect that it is something like we don't ask the name if we already have it
Do you have a specific portal session or customer I can look at?
karmic pollen
Hello, I just generated this portal session as an example: https://billing.stripe.com/p/session/test_YWNjdF8xU2YxRzdFdkJjNFZNczdDLF9UdWNYSmpjQXV5dDFkY1lLdXp4UmhtZklDMWg3aDBG0100OoSlkto2
I can technically use a payment method that is not in my name, so I was wondering if the name isn't asked because it's not required. But again, I don't get why the checkout session asks for it
lone olive
Can you give me an example Checkout Session? You can configure checkout sessions many different ways.
But, in general, it isn't always necessary to collect a cardholder's name to create a payment
karmic pollen
Sure, here's a checkout session that I just generated:
The customer doesn't exist yet for this session
lone olive
Yeah, nothing special in the creation request.
I have the general sense that we always require name to be collected on Stripe Hosted Checkout, which is likely an anti-fraud measure.
I'm not surpised that we don't always collect a name in the Customer Portal when you add a new payment method, because it isn't always necessary and you aren't making a purchase right then
I looked to see if you could require it on the billing portal configuration, but I don't think you can
karmic pollen
Yes, I don't see any setting for it 😕
I understand the fraud protection for the Checkout Session, but if a Customer changes the payment method from the customer portal, it will eventually lead to a payment from this new payment method. Is fraud protection less stringent on subscription renewals?
lone olive
No, I wouldn't say so, but it also isn't technically neccessary to collect a customer's name on a Subscription
But also, I'm not a fraud prevention or risk expert
I think that's a decent feature request for Billing Portal Configurations though so I am happy to pass that feedback on to our team
karmic pollen
Yes, thanks
In the meantime I'll simply consider the name as something not necessary when it comes to adding a payment method through the portal. Thank you for your support
small oakBOT