Open
Description
Describe the bug
Doing adjacent work we identified the need to revisit is_stripe_account_valid() method and where is used, as it was introduced before we started to use details_submitted and the concept of card capabilities being requested to indicate if an account is "valid" or not seems improvable from a first look
Ideally, we should audit where that method is used, rethink if that concept of validity makes sense with what we know now, and compare it with other existing account lifecycle checks
The output of the PR could be a small refactor on that area, could be just rename it if "account_valid" doesn't speak too well about what it's actually doing, or even change its logic