#melecouvreur_api

1 messages · Page 1 of 1 (latest)

tiny pumiceBOT
#

👋 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/1326572016311996508

📝 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.

lost havenBOT
stone lake
#

Hi there 👋 why we advise against that is explained in the doc linked to from that warning:

Stripe recommends against certificate pinning to avoid complications with your integration when we roll out new certificates for our systems. DigiCert, one of the major CAs, also recommends against certificate pinning.
https://docs.stripe.com/tls-certificates#certificate-pinning:~:text=Stripe recommends against certificate pinning to avoid complications with your integration when we roll out new certificates for our systems. DigiCert%2C one of the major CAs%2C also recommends against certificate pinning