#akash_api
small oysterBOT
đ 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/1384059555398549595
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
gleaming pasture
It's not about the parameter, it's about fraud. See on your Dashboard: https://dashboard.stripe.com/payments/pi_3RaRudHF0VMkBzj01olSwgKp
past goblet
so why it is happening, or how we can solve it, because this one is autorecurring payment
gleaming pasture
Fraud means we detect that the customer may have been not-a-good-factor based on various signals collected in different source. Blocking them would protect you as a merchant from dispute later. If you have talked directly with the customer and they confirmed they still own the Sepa DD payment method, you can reach out to Stripe Support to see if they can lift the block
Otherwise, maybe it's faster to just ask your customer to provide a different payment method
past goblet
this pm is given my stripe by stripe migration tool, when we replace all source src_ with the pm_ and with their mandate
gleaming pasture
I see, in that case please write to Support and initialize an email case. We will follow-up there