wrongecho
I did some additional research on the MOTO requirements, and it looks like this is actually a pretty straightforward implementation. Stripe has official documentation for exactly this use case, and it's designed for MSPs like us who need to save payment methods on behalf of clients. With that said, I'm a generalist and would struggle to make heads or tails for much of those details and will obviously defer to your expertise.
The good news is it looks like you can leverage the existing save-card functionality you already built for the portal. From what I can see, it's mainly adding the moto: true flag to the existing Stripe API calls and creating an admin interface for entering the card details.
Here's my situation: I'm at a decision point where I need to commit to a billing platform for our recurring invoices. I've got about two weeks to make this call due to my oversight on this feature, entirely on me. ITFlow checks all the other boxes for us, but without the ability to save payment methods from the admin side, I can't use it for our main billing workflow. I'm trying to come up with something using stripe's native billing options in the meantime I guess. Though I'd much rather keep everything integrated within ITFlow if possible.
I totally understand if this is a bigger request than I anticipated, or if there are other priorities. If there's any way to fast-track this (even as a basic implementation that we can refine later) it would make a huge difference for us. I am more than happy to test this functionality.
What do you think? Is there a path to get something working in the next couple weeks, or should I start looking at alternatives?
Also, for clarity, my top concern/request is changing the auto-charge date to the invoice due date, followed by adding payments on behalf of clients. This is super duper major for me.