No. No, that has not changed. So again, I'm going to make distinctions beyond the card management processing environment that I just made reference to. So on top of that capability, which is, call it, baked processing, so rather transaction over a network, getting authorizations and the authorization back, et cetera, right, basic transaction processing stuff, think of that as what we did last year.
Then on top of that, our product features are organized in a set of, what we'd call internally, stacks. So we have a contemporary BaaS stack, we have a legacy stack and we have other technologies associated with some of our businesses. And so the activity that we've been undertaking of which the processor conversion was important to is eliminating older legacy stacks, which the stacks have product features within them. And that activity, that investment is unchanged. We continue to do that and we'll continue to do that. In fact, some of our most significant investments this year are focused on that effort.
So the question when we think about our product road map longer term and we think about small business offerings or credit offerings, et cetera, credit might be the better example. When we are poised to launch consumer credit across our platform down the road, not in a current period, but down the road, the question will be, should we then implement a core banking system that already has those account features built on a third-party basis? Or do we enhance our then consolidated stack?
So the consolidation and simplification that you're asking about is underway and unimpacted by this decision. How we launch future products and features, that is impacted by this decision. However, we have plenty of runway ahead of us to make that decision in a timely, coordinated way. So the simplification work, I want to be very clear, is not impacted at all by this choice.