#xaositect_paymentmethod-legacy
1 messages ¡ Page 1 of 1 (latest)
đ 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/1242516483922198590
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
xaositect_paymentmethod-legacy
@sonic moat no that's impossible. In theory though a card_123 and src_123 all work as PaymentMethods objects so it shouldn't be filtering those out. This looks like a bug in that beta so you'd report it to the support team as it's in beta: https://support.stripe.com/contact
cool. I wonder if I'm passing the wrong args into the customer session creation?
There's no specific parameter to pass so I don't see how
I think it's more likely that during the beta we focused only on newer objects and need to build it for the older versions
Okay, I'll submit a bug report. Thank you!