#phani_ede
neon knot
versed quest
By PROD, I mean live mode here
jovial totem
Hi,
Are you facing a particular issue with this ? sorry not sure I'm understandning the ask here. Or this is just "is it normal"?
versed quest
Just "Is it normal?" in this case
Wanted to confirm this because we have seen issues before where CreateSetupIntent does not seem to behave in an equivalent manner between test mode and live mode
For example, CreateSetupIntent succeeded when we include payment_method in financial_connections' permissions in test mode during our initial testing.
However, on trying the same in live mode, we found that we did not actually have those permissions enabled for our Stripe account due to which we were seeing API call failures
For this reason, I'm trying to be extra careful about any discrepancies from the expected result
jovial totem
Can you share some concrete examples? with some PaymentIntentId and failed RequestId?
but AFAIk, there is no difference between test and live mode for this use case
versed quest
Good to know that this is expected in this case.
Will get a failed SetupIntent call and get back to you briefly
{
"error": {
"message": "You currently only have access to instant verifications. To access additional bank data from Financial Connections Accounts, submit your registration at https://dashboard.stripe.com/financial-connections/application.",
"request_log_url": "https://dashboard.stripe.com/logs/req_EUYLAsOZfDw18X?t=1674253691",
"type": "invalid_request_error"
}
}
This was the issue we were seeing earlier
However, similar calls were succeeding in test mode
Was this expected?
jovial totem
Checking.. give me couple of minutes please.
Probably, you should reach out to Support at https://support.stripe.com/contact
you need to submit your registration for live mode at https://dashboard.stripe.com/financial-connections/application
versed quest
After we saw the problem that day, we actually did register our Stripe account with financial connections required for this to pass.
It's just that this made me concerned about test mode being an accurate representation of live mode in cases like these
Hence, I wanted to confirm if the behavior with payment_method_options that I'd originally mentioned is expected so that we could avoid similar issues in live mode
Is this a gap in test mode according to you folks at Stripe?
jovial totem
Double checking...
Yes it looks like this is a difference between test and live mode, we just did a test and the workflow pass in test mode as you. I invite you to double check this with Stripe Support at
versed quest
Thanks for confirming. Will talk to Stripe support regarding this.
However, it does dent my confidence in the testing we are doing in test mode now. Not sure what other differences might show up in live mode leading to PROD issues in the future.
Is there any documentation where such differences are being kept track of? Having that would be extremely helpful.
jovial totem
Is there any documentation where such differences are being kept track of? Havin...
I'm not aware of something like this so far, nope.
versed quest
Makes sense. Thanks for the help!