#dashen0897_docs
vestal kelpBOT
👋 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/1306439200437960837
📝 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.
- dashen0897_docs, 17 hours ago, 5 messages
- dashen0897_docs, 1 day ago, 27 messages
little ledge
No, there's no expiration date for a paymentIntent client secret.
wooden cape
Is it a one-time key?
little ledge
What do you mean by one-time?
wooden cape
If I intercept the client secret, can I use the same client secret to pay for multiple orders?
little ledge
No you can't
little ledge
Yes, the client_secret is associcated with only one PaymentIntent, you can't reuse the same client_secret for other payments.
little ledge
What's the order ID that you refer to? Is it something created by your own system?
wooden cape
yes，Our system's orderID
little ledge
Then it's really up to your system implementation, you may want to discuss this with your engineers.
wooden cape
There is no field similar to the unique manufacturer ID, right?
little ledge
No, but you can use metadata to associate custom data https://docs.stripe.com/api/metadata