Outside observers read a slow payments release cycle as dysfunction. Usually it’s the opposite — it’s the one part of the org that has correctly priced in the cost of being wrong.
A shipped bug in a content feature costs you an apology tweet. A shipped bug in a settlement path costs you real money, moved to the wrong place, that you may not get back. Those two failure modes deserve completely different review processes, and treating them the same is how fast-moving product teams accidentally become slow-moving fintech companies.
Speed is still the goal. It just has to be earned with the kind of testing that makes the slow path unnecessary.