I know this idea was declined 4 years ago, but I'd like to try it again.
1. If you use WHMCS to bill for a variety of services beyond just hosting you clients might demand the ability to use different cards and payment options/ product or service. For example, they might want to charge hosting services to one card. But one off items would get charged on another.
2. A credit card on file might be maxed out one month and a client would prefer to add another card, without necessarily ditching the details of the card they want to use.
3. It's also just plain convenient to be able to store a few cards on file and chose when and how to use them.
The way it stands now, each time you want to use a new card, you have to lose the details of the card on file. It just creates a bit more work for the client.
I like this idea
Really need this feature!
WHMCS already created this for me via their custom development team.
How alinford I would like to use this too
How do you foresee this working when a user has multiple credit cards and multiple products? Would you want the client to be able to select a different credit card to use for each of their products? And if we do that, how would we handle a situation where a customer has asked for one product to be billed to one card, and another to another, but then the items get invoiced on the same invoice, or merged for example?
Dev team...
One card should always be the default card, if a product/service does not have a nominated card the default will be used. If multiple products/services are to be billed on a given day they should be invoiced 'per card'.
If a user removes a card they should be prompted to re-assign products/services to the default card or another card within the account.
This whole 'multiple cards' should support multiple gateways, so for example a customer could have a Credit Card and Direct Debit (GoCardless) payment method associated with their account.
To understand my issues, and from what I have heard, other peoples issues... We have clients call in consistently to pay their balance, and sometimes run up to 5 cards to get the bill paid. Having all on file and sequentially going through them when their primary card has failed (on recurring billing day) Would be a great option. Not to complicate things, but adding "last tried date" and result code in the invoice display would be another great option.
I would like to know how to get this feature too.
I have clients with multiple businesses and want to use different cards for each one. I just want to be able to assign default cards for each business or recurring invoice.
If this will also fix the issue for deleting stored credit cards, when a client try to pay manually and this fails, I need this too.
Because it is not helpful if the card data is not being stored, when the manually initiated credit card payment fails.
In my case, the card is good. However the bank/card issuer declined it, card holder needs to call the bank and they unlock the transaction (because merchant was not in the same country as card holder). Client send me an email to try the card again, as it is good now as the bank unlocked the transaction.
Now, I can not run card again because card is not stored anymore. WHMCS is hammering client with invoice reminder emails, telling client that no credit card is on file, which makes client angry.
In the end it is a poor customer experience. And when you get poor customer experience, you may switch merchants. At least it is more likely to lose the client with his business and I can not afford that.
Speaking from my own experience, no longer working with a hosting company because their billing system is such a hassle, that it is a pain in the butt. They are ignorant, they don't fix or change it to make it more convenient. Well, they are losing my business.
Initially would be nice just to be able to house multiple cards and mark one as the default to be charged, then the users can select which card they want to use at checkout when paying for a service or invoice which they can select to become the default. After that is established can look into more advanced functionality such as Staff mentioned above things like being able to use certain cards for certain services and the like which could work well just if they fall on the same invoice that could be tricky and either does two transactions for the one invoice or just doesn't let them do that? Hmm. But mainly I think the first point just being able to store more than one and set one to default is a big help as many clients use differing cards and the ability to select between them at checkout or paying an invoice can be very helpful on the user-end, think amazon checkout and changing your card to use just for that one purchase type of thing.
I am most interested in servicing customers who occasionally wish to use a different credit card for payment. It would be convenient if they had the option to save more than one credit card and select the saved payment method they wish to use for each/any invoice.
If/when a customer wishes to remit payment for an item or items on a single invoice using multiple credit cards we can split the invoice to accommodate them. This is most likely something the customer who needs to do this will ask for any way.
Currently a customer can inadvertently or deliberately delete previously saved credit card data by erroneously entering new/updated credit card details and/or having the same rejected by the gateway.This would not happen if WHMCS supported multiple credit card storage per account.
I have the same types of needs for this feature. Ability to have a default card and others stored in case a client wants to charge one time charges to a separate credit card. Ideally when you created an invoice you could associate it to that card and then manually process it. I think it poses an issue with the way WHMCS calls on the payment gateway as the payment source verses having a payment type which is then associated to a gateway. Then you could select say Paypal, Cash/Check, MC 2344, VISA 2345 as the associated default payment type at the profile level and then manually assign others to individual services or invoices as you do now.
The ability to save multiple payments account is very common if done right just like Amazon and Authorize.net CIM. Moreover whmcs competitor already has this feature by default https://goo.gl/zHKtsX - I don't know why they don't add this essential feature!
Agreed on first pass being easier:
version 0)
- Allow a single checkout/payment with a card other than the on-file card. (without saving card / 'guest checkout' for a limited contact.. or a customer who doesn't want to disrupt their recurring payments for a 1 time purchase)
version 1)
- store N cards per customer, with contact_id for which contact created it
- 1 card can be marked default (all automated charges happen here. If card fails it fails, they can manually or request default change. no need for complex logic)
- "admin" contacts can use any card, limited contacts can only use cards they supplied - would be great for larger organizations
version 2)
- Associate recurring services to any of the stored cards (basically: override default, for that recurring service)
Another +1 for this feature. I have a client that has multiple locations and wants to pay for different products with different credit cards.
I think thats an awesome idea,
WHMCS UI was originally created to show 1 credit card account on file for each client, however this has greatly changed over the years. With the help of payment providers such as Stripe and Auth.net now the client can store several cards AND bank accounts on file.
Current UI does not show the multiple cards on file and worst of all it doesn't even show ANYWHERE (admin or client area) that the client's bank account has been stored on file (through Auth.net eCheck module), therefore this UI and functionality should be updated asap. Here is what I propose:
CLIENT AREA
Replace current "manage credit card" page https://goo.gl/Dfi5uH with a clear and simple way for client to see all payment methods store and add them accordingly. See simple example as to how Stripe does it https://goo.gl/PKtH77
This is also how retailers like Amazon makes it simple for its users to pay (there is a reason why they are big). Instead of "manage credit card" the new page should be called "Payment Methods"
ADMIN AREA
Similarly to the front end we should be able to see the payment methods available for the client, obviously on a secured format (only the last 4 digits). This is what I propose:
Instead of the "credit card information" link create a new box/section called "Payment Methods" or as shown here https://goo.gl/XkKaV5 inside of it you can show it the same way as Stripe does https://goo.gl/PKtH77
Please make this change a priority! - The ability to make it easy for clients and admins to manage payment methods should be TOP priority. Thanks
WHMCS, please provide option to have client store multiple credit cards to be used for various products and/or services in their account. For example, a customer might want to bill their business hosting services on their business credit card while bill a different card for their personal hosting services. Another example is for large purchases, business customers might want to use a different credit card while the recurring monthly costs are billed on another credit card.
if this is implemented, it should allow an arbitrary number of payment methods (not just cc) for each client. each method should have its own set of values as needed (name, address, card for cc, email for paypal, etc, routing info for ach). each one should have a user set nickname. even allowing multiple check paytypes with different contact info would be great as well.
and hopefully at the same time, the newest token systems that provide the strongest pci compliance (suitable for saq-a) should be implemented as well.
Great to see this is planned! Just a bit of feedback from gateway developers - the key here is allowing more than one gateway to store a token under a client's account - so that if a client has multiple payment method tokens on file, the correct one will be used based on the payment method on an invoice.
And, obviously the current page where you add/update a credit card would need a bit of redesign to more accurately show the multiple payment methods/tokens on file - with the option to add/update/edit/delete them.
Hi all,
Thanks for your comments and votes thus far.
I'm pleased to advise that we are targeting Multiple Payment Methods for 2019! Please keep the feedback coming.
I was advised to add my comments here as it addresses an additional issue that is related to this (thankfully) upcoming function. Currently, the Manage Credit Card screen is at the mercy of the last method used to pay an invoice. Even though there is only a single actual credit card method (in this case, using Quantum Vault which is the only visible method to the client), if a mail in payment (check payment set via admin) is used to pay the most recent invoice and if the payment method on a client's account is set to default set per order, the MCC screen will show the WHMCS-generated MCC screen allowing them to enter credit card details directly into the database. This not only adds full cc details to the database, but it also gives the impression to the client that they have updated their credit card when they have not.
The full details and steps of this issue are in this feature request: https://requests.whmcs.com/topic/when-using-quantum-vault-prevent-erroneous-display-of-the-whmcs-generated-manage-credit-card-screen
Having multiple gateways is a good idea too. For me, it was more important to have multiple cards under one gateway (stripe). If the solution looked like one card/gateway it wouldn't be useful to me and probably too complex for my clients.
Agreed with @Sean. Especially because Stripe is now a core WHMCS module - I think it seems reasonable to add the option to allow clients to store more than one card on file - through Stripe. I'm sure this would then lead to functionality/structure that other gateways could use to store payment methods the same way.
I guess this could be accomplished in an additional table, for example tblpaymentmethods - where all tokens would be stored (instead of in tblclients>gatewayid).
Then, this table would have columns like:
ID client_id payment_method gateway_id
1 205 Stripe cus_182938393839383
2 206 QuantumVault skiw0202339393
And so on? This way, this could be leveraged throughout the admin/client area to choose which Payment method + card to be assigned to a service / invoice, because you should no longer be able to set just a payment method by itself.
The ability to force a default for the "Manage Credit Card" client area page would be helpful. Maybe a checkbox in the payment gateway settings to force the default for the manage credit card page? That way, if you have multiple gateways, but only one credit card gateway you wish for clients to be able to manage, you can force the default. If none are checked as default, the existing method of WHMCS determining the default would still be in place.
The following features would be very helpful:
I use the Quantum Vault gateway, and have an add-on module I sell that provides these features and more. Many WHMCS users who use Quantum Vault have purchased my module to add the additional functionality for their clients. I would be more than happy to provide the source code of the module to WHMCS if you would consider implementing the features.
Yes - PLEASE add the features noted by SiteOx above.
The addon he developed for the Quantum Vault is critical to a higher functioning gateway. Without it, the Quantum Vault is clunky and inconvenient for the client.
The ability to automatically charge the next card of the file when the first one fails would also be an anifty feature to have in here. There may be some privacy concern here as the client may have only intended to have x service billed to a card. However, when entering in a new card perhaps there is a prompt, saying upon card failure, try an alternative card which the client could tick.
Hi all,
Version 7.8 has now reached public beta, which includes this feature: https://preview.whmcs.com
The documentation for these new options has been published at https://docs.whmcs.com/Pay_Methods
Please join us during the pre-release testing period and provide your feedback in our dedicated beta community board: https://whmcs.community/forum/471-v78-beta-discussion/
Comments have been locked on this page!