#alec_error
shut gulchBOT
đ 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/1240073664397840434
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
stuck folio
Hi there!
The error above means you're passing payment_method_types when creating the PaymentIntent and passing 'demo_pay' as a value.
I think this means you may have used some code we have in a demo
I recommend omitting payment_method_types altogether and using dynamic payment methods: https://docs.stripe.com/payments/payment-methods/dynamic-payment-methods
soft jungle
Yes! This is a test we have implemented in CI, which should be writing to test stripe. I wonder if somehow we are using live keys.
I can confirm were using test keys but this error persists.
Im getting this error when createing a payment intent
with the golang client
stuck folio
Can you share a request ID?
soft jungle
req_ON6B4lAs6mqKKp
stuck folio
Thanks! Looking
soft jungle
interesting
we've been able to get it to work by disabling automatic payment method
Maybe some subtle regression in functionality?
stuck folio
I'm digging into the error message yes, but it seems related to dynamic payment methods/automatic payment methods
Okay, yes, it looks like something changed on our end that is resulting in that error message when using dynamic payment methods, but only for some users
I'll keep you posted on any updates in the next 10-15 minutes, but you may need to reach out to our support team if resolution takes longer
coral sparrowBOT
hasty talon
I came here looking for this topic. We've seen the same error today from some of our regression tests.
shut gulchBOT
@hasty talon looks like you're in the wrong place, this thread is for someone else's question.
- If you have your own thread please chat there.
- If you have a question or a followup to a closed thread use one of the buttons in https://discord.com/channels/841573134531821608/842637025524842496 to get help (we don't reopen closed threads).
Note that posting inappropriate messages in other people's threads is against the rules. No worries if this was just an honest mistake, but anyone who violates the rules multiple times will be removed from this server.
lament timber
For reference, a fix is being rolled out, I recommend that you check again some time (probably a few hours later). Otherwise you can also reach out to support to be notified when the fix is deployed
soft jungle
great thanks!