Multiple Payment Methods in Self Service
R
Rebecca
Currently, there is only one default payment method per workspace, which is inherited by all projects.
In the future, it should be possible for a workspace owner to define multiple payments in self service, so that different projects within the workspace can have different payment methods assigned.
J
Julia Rengshausen
Could you give an update on how this feature is prioritized at the moment?
Jelle den Burger
Julia Rengshausen Unfortunately it is not very high on the burner. We are currently more focused on making platform engineering better and less focused on FinOps. However it is still one of the top (if not the toppest) topic for FinOps improvements.
Please let me know how the lack of this is currently impacting your work life to help prioritize this (also fine to send me an e-mail if this is too public)
J
Julia Rengshausen
Jelle den Burger Currently we've made it possible for users to change the label on their payment method by naming all of them "default" (see also https://feedback.meshcloud.io/feature-requests/p/allow-user-to-change-payment-method-tag-for-all-payment-methods-not-just-default).
But this is definitely only a workaround, because it still doesn't let users extend the expiry date. This leads to a lot of confusion, because users will update a cost center, but it will still be shown as expired. So I'm getting a lot of requests to extend or update payment methods, which I have to do manually, just copy-pasting the info they give me. This is something they should really be able to do on their own. Especially because I don't even have a way to fact-check the info they give me.
All the features the payment methods offer (budgets, expiry dates, substitute payment methods) cannot be accessed by users and in the worst case just confuse them.
Jelle den Burger
marked this post as
open
We are very aware of the requirement and would love to implement this but we will not touch this in the next 8 weeks on our roadmap.
Jelle den Burger
One more thing to keep in mind for this feature is how to handle the expiration date. Perhaps teams cannot pick this one or at most pick a maximum expiration date.
Jelle den Burger
Merged in a post:
Allow end users to manage payment methods in self service
S
Shamil Radzhabov
Using the Workspace wizard, end-users can automatically create a payment method. However, for any subsequent management, they must contact the central team. The following enhancements would improve the functionality:
- Enable setting an expiration date for the payment method during workspace creation, with the option to configure a default expiration period for new payment methods.
- Implement notifications to alert users about upcoming payment method expirations.
- Allow users to manage payment methods, including editing existing ones and creating new entries.
This last enhancement would reduce the workload of the central team, as end-users currently reach out to them for payment method modifications. Additionally, it feels inconsistent that users can create a payment method during workspace creation but cannot do so for an existing workspace, making the feature seem less optional than intended.
R
Rebecca
marked this post as
under review
R
Rebecca
We don't have this planned for the remainder of the year but are currently investigating if we can provide this in Q1 next year. We will get back to you!
Felix
As long as self-service für multiple payment methods isn't supported within meshStack, you might want to link to an external process that creates new payment methods via API.