#kandice-as0_api
rough snowBOT
👋 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/1430646875824062516
📝 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.
- kandice-as0_code, 1 day ago, 29 messages
true nexus
Hi there, looking into this now! Note that this channel is for API integration questions, but I can dig a bit to see what I can find
haughty rapids
Hi there, looking into this now! Note that this channel is for API integration q...
Hiya, im trying to integrate the stripe issuing API with my service 🙂
your API docs are very useful btw, I like them 🙂
Btw, is it possible to switch the issuing cardholder API from "individual" to "company" & have it reflect in the sidebar within the API Docs website
over here
I believe the individual vs company headers/ content is different
true nexus
I'm not seeing that name format that you're describing in the docs, if you look at the example here the cardholder name seems like a normal string (Jenny Rosen). Can you let me know if there's a different docs page you're referring to?
https://docs.stripe.com/issuing/cards/virtual/issue-cards?testing-method=with-code
haughty rapids
I'm not seeing that name format that you're describing in the docs, if you look ...
I think that is for the "individual" cardholder type, not the the "company" cardholder type
one second, I remember reading it somewhere
haughty rapids
I'm not seeing that name format that you're describing in the docs, if you look ...
Oh, my apologies, I pressed the "copy for LLM button"
& then I asked Claude AI a question & it mentioned in passing this:
weird, it hallucinated even when I gave it the docs in a supported format
I apologise
@true nexus oh weird, even your own AI says to use the format "Company name - use case"
(as shown in the sidebar on the right)
true nexus
Interesting. Are you looking at this docs page?
https://docs.stripe.com/api/issuing/cardholders/object#issuing_cardholder_object-name
haughty rapids
Interesting. Are you looking at this docs page?
https://docs.stripe.com/api/issu...
yep, that is the exact one
Iirc, that is the industry standard anyways "Company name - use case"
So I should be good right?
true nexus
Yes, the docs do not mention any restrictions with that field, so you can follow a convention that makes sense with your use case
haughty rapids
Yes, the docs do not mention any restrictions with that field, so you can follow...
Alright, thank you very much for your help 🙂
Have a good day!
/close