tibbian-settings | Stripe Developers | Page 1

spark gate Jun 15, 2022, 1:13 PM

#

hi! we mainly answer about the API here so support knows more than I do, but some pages/settings are shared between modes yes, depends on the exact settings, so that's certainly possible

#

I thought these were separate last time I looked, but it does seem to be shared now that I look

#

I'll investigate as well since this surprises me too but for now I'd suggest you just work with support on this.

thorny eagle Jun 15, 2022, 1:22 PM

#

Thanks, I wrapped up with support and gave them the feedback that if settings are going to be shared between Test Mode and production then something needs to be done to make that clear in the Stripe web UI, the current state shown in the screenshot seems to strongly suggest that Test Mode is supported on that page.

I normally only bring questions here when the answer from support is surprising as it is in this case. With these settings being shared between Test Mode and production I am left with not great options when it comes to changing these settings.

For example, failed subscription renewal payments currently cause the invoice to be marked uncollectible and the subscription to be cancelled. But I have a project to leave the subscription and invoice as-is instead. The webhooks generated for a failed renewal payment will now look quite different and I have written new code to handle them appropriately. I'm obviously not going to throw my code over the wall to production and hope for the best, so I'm stuck writing more code to simulate the Stripe webhooks in my test environment in order to run integration tests.

#

I guess the above is more of a rant than a question, but if you could at least double check in the backend that there is no Test Mode support for these settings I would appreciate it.

spark gate Jun 15, 2022, 1:23 PM

#

totally agree and understand, like I said some settings pages are shared because they don't store the settings on the backend in a mode-sharded way, I wish everything did for reasons you mention but not everything is prioritised

#

having a look but it might just be the case that you're "supposed to" create a separate Stripe account for testing if they're not stored in a sharded way

thorny eagle Jun 15, 2022, 1:24 PM

#

if wishes were fishes lol, I know exactly what you mean, work gets prioritized and that's life

#

Do you have a way of looking at the way a particular setting is stored in the backend to see if it supports sharding by mode? I'd feel a lot better if I knew that this wasn't just a bug in the Stripe web UI, I'm more than willing to use an API approach if that gives me the ability to configure these settings in Test Mode only

spark gate Jun 15, 2022, 1:28 PM

#

sorry to be clear, there's no API for those settings so that's not an option

#

it's just that it depends how we build the actual implementation of the settings, they might be global across your account, or might have different sets for live and test (seems it's the former), just trying to figure out if that was always the case. And sure, I agree the UI is confusing if that's the case

#

ok I had a look and I asked some colleagues and those settings have always been shared. I agree the UI should make that clear, I'll raise it as feedback internally. To your specific needs, the best option is likely to create a new account for testing with(which is lightweight to be clear and you don't have to activate it, it's just clicking the dropdown in the top left of the dashboard, create an account from there, and grab its API keys and tinker with it). I know it's not ideal

#tibbian-settings