#shaun_mandate-error
strong bronzeBOT
👋 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/1461778819370455132
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
atomic panther
👋 Hey Shaun, any chance you have a request ID handy demonstrating the error you are encountering?
echo plume
I don't have a request ID, but we're seeing this in our logs (outside of Stripe) Error: Missing required param: mandate_data.
atomic panther
This is what comes to mind first, https://docs.stripe.com/india-recurring-payments?integration=paymentIntents-setupIntents#testing
Just wondering if we have an concrete examples of what you're doing and what you're trying to test.
echo plume
It seems like a pretty clear situation where we're doing something wrong, and I think I know the possible solutions - I just can't find any way to replicate the error within our test environment
Yeah, that page seems like the most relevant to what we're trying - I tried all of those test cards and none of them cause the same error to occur
What I think is happening - on Production, when we run the stripe.setupIntents.confirm (through NodeJS) it requires mandate_data, but I haven't been able to find a test card that simulates the same requirement.
atomic panther
Do you have the account ID handy, I can try looking for an example case.
echo plume
Unfortunately I don't, our production Stripe account has limited access so I will have to ask someone to find it for me - I'll check and see if I can get it for you
strong bronzeBOT
echo plume
Ok, I found someone who could look for the errors on the Stripe dashboard and it looks like the error we're seeing is being caught by the API, so the request to confirm the SetupIntent was never actually sent to Stripe.
vital rover
@echo plume do you still need further help on this?
echo plume
If you have any ideas, that would be great - we're trying to figure out how to catch these errors in our E2E tests
It kind of looks like the thing we are missing is a way to create a SetupIntent that requires mandate_data in order to be confirmed
vital rover
hmmm yeah it's going to be tough without an exact request id to try and understand what is even failing. Can you look into your logs in the Dashboard in Workbench to try and find an example?
echo plume
Yeah, trying to get the request ID where the SetupIntent was created (since we don't have anything to look at on the failed verification)
vital rover
shaun_mandate-error
Can you share your account id acct_123 otherwise (in DM is fine if you don't want to share publicly)
echo plume
This should be one of the request ID's for the setup intent creation - req_gDO6aCf9CAGFvK
vital rover
okay the real failure which you should see in the logs is req_YhXwD5kczQUYXW
you're trying to confirm with Link which does require a Mandate. So in Test mode to trigger that error you'd want to use a Link PaymentMethod pm_12345 that doesn't have a Mandate yet
echo plume
Ohhh, cool - that's really helpful! Thanks!
I didn't even consider that Link might be involved in this issue 🙂
vital rover
🙂
cards don't require mandates (other than for Indian customers) so that's likely why you weren't able to reproduce easily
echo plume
Definitely! Thanks again!