#mallain23_best-practices
viral belfryBOT
👋 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/1343606629525885020
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
idle dragonBOT
dry garden
Hi there 👋 I'm not sure I understand the limitation you ran into. Are you referring to our Guest Customers (which aren't created by you) or Customer objects (which you can create and reuse)?
small juniper
guest customer objects that we create
dry garden
Can you say more, because that isn't a concept in Stripe. Within Stripe, Guest Customers are created automatically and can't be reused.
https://docs.stripe.com/payments/checkout/guest-customers#:~:text=Checkout Sessions that don’t create Customers are associated with guest customers instead.
small juniper
how does that work?
dry garden
The guide I linked to explains the behavior of Guest Customers (which aren't actual objects that you can interact with in Stripe's ecosystem)
small juniper
ok thanks -- how does this work for auditing and viewing history
dry garden
Can you elaborate? How does what work with auditing and viewing history, and what do you mean by auditing and viewing history?
Chances are I won't be able to provide much insight there, since in this forum we specialize in helping developers work with our API, so we aren't too familiar with Guest Customers since they're a dashboard-only concept.