For something like a web request, all the frameworks catch the exception at the request level. Prod should not be going down.

Maybe you mean requests are failing on uncaught exceptions, in which case I'd say it's working well.

For the customer there is hardly any difference that the server keeps running if a critical workflow, especially with a payment in flight, crashes and burns.

There're a huge different between a broken feature and the whole server crashing every time that feature is attempted.

Anyway, you prefer critical workflow like payment to show a success but actually be an unhandled error?

For the customer the difference hardly matters, they cannot fulfill what they intended to do, because someone somewhere forgot to catch an exception, going all the way out of the MVC controller, providing a very bad UI/UX, and from security point of view, a possible DOS attack vector.

I prefer an happy customer, and not having to deal with support calls.