Must have better credit card management for tokenized gateways - specifically Quantum Vault

[MBayDesign]

An addon module written for Quantum Vault (Quantum Vault Client Management by Site Ox) previously did some of the lifting that should really be native to token-based credit card management within WHMCS. Unfortunately, the developer of that module will not be updating the module to work with the newer incarnation of WHMCS – and I'm not referring to 8, but back to 7.8.2 (or thereabouts) when multiple payment method functionality was added – so anyone using Quantum Vault (or presumably any other tokenized gateway) is stuck with half-developed functionality. Since I do not see any reference or updates to those functions in the ver. 8 release notes, I assume the same inadequacies will exist when that is released.

1. In order to add a new credit card, an invoice MUST exist which means that when credit card expiry notices go out – or if the client needs to update their card for other reasons in advance of a new invoice – they are out of luck and they have to wait for a new invoice.
2. A client can update an existing credit card, but the information displayed (both on the front and backend) will not update - therefore, the old card's last 4 and the old expiration continues to display.
3. And if you enter a NEW card with a new invoice as you're supposed to, the expiry on a new card displays with an incorrect date pulled out of thin air apparently 10 years in the future - i.e. 12/2030.

While #1 can be reluctantly accepted as a function of this method, #2 and #3 should be considered BUGS. To deal with the incorrect information displayed in scenario 2 and 3, apparently it is an acceptable solution to simply put a message on the page that the information you see might be wrong… Really?  

Since showing an incorrect expiry is worse than no expiry at all, I've had to edit the template to not display it and I have to urge clients in emails that mention credit cards to wait for a new invoice to add a new card. At least then the last 4 will display correctly.

It is also unclear to me if the credit card expiry notification works correctly. If the system doesn't know what the real expiry is, then how can a notice of expiration be sent? Does it query the API? If it does know, then why can't that information (and the correct last 4) be placed into the local DB for display?

There are so many good things about Quantum Vault - and tokenized methods in general. The addon module creator mentioned at the top made Quantum Vault a fully functional method. Why can’t WHMCS?

I’m sorry, but these issues are not acceptable just because you say the behavior is "as expected."