JamesOakley

This is an oldish thread, yes, but it also seems the best place to ask this (given the issues that people are citing when WHMCS moved from v4 -> v5): whmcsdesigns.com currently says this in the FAQ section: So here's the question: WHMCS v6 has been out for 4 weeks. From 5.3.x to 6.0.0, "client side templates have changed". So could @Sam Asante chime in at this point, and let us know what "shortly" means. When will v.6 versions of the templates be made available for download? Knowing would help with planning.

The first thing to say is that what I just said, and what I'm about to say, is not specific to the Stripe module. ServerPing's Stripe module simply allows Stripe to be used as the back-end payment processor for card payments in WHMCS. It does so fully within the spirit of Stripe - specifically with no data touching the server that hosts the WHMCS installation, and all card data going directly between the client and Stripe's servers. So I'm simply discussing how WHMCS handles card payments. Not quite. If they click on the link, they'll be taken to a copy of their invoice, with a "Pay Now" button. When they use that, they have the option to use a pre-stored card, or to enter new card details. The payment is then processed. What the "Disable CC Processing" option does is prevent card payments being taken automatically as the due date approaches. It ensures that, as you had previously with Xero, they'd have to pay manually (so, no auto-charge).

WHMCS Admin > Client Profile > Profile Tab > Disable CC Processing

I take it you are using the viewcart.tpl file from the web20cart folder in the Stripe module? My next debugging step would be to replace the necessary files in another orderform, and then try using that one instead. If that doesn't work, I'd unzipping a fresh copy of stripewhmcs215.zip, and following the instructions from the top again. But my bigger recommendation would be to open a support ticket at serverping and ask them to help. Assuming you've paid the small fee for support (which is worth doing to support the module, if for no other reason), you'll find Joe is extremely helpful.

It seems Stripe now accepts Bitcoin as a payment method. Are there any plans for this module to expand to include that feature?

I have upgraded to 5.3.11, yes (not 5.3.1.1). The module continued to work fine. To the best of my knowledge, there are no changes in this upgrade that would require a change in this module (I read the changelogs to check that before upgrading). However, if in the course of the upgrade, you overwrote (or lost entirely) any of the files that this module replaces / adds to a WHMCS installation, you would obviously have to put the module versions back again.

Joe's said it, but I'll say it another way seeing as the confusion seems to affect several people. In terms of recurring billing, this module (and Stripe themselves, when using this module) does not actually do any recurring billing of its own. A regular card payment module in WHMCS stores the user's card number, allowing WHMCS itself to do recurring billing if it's set up to do so. This Stripe module does just the same - except it secures the Stripe token itself, leaving all card storage in the hands of Stripe. To the end user, this Stripe module is no different from any other WHMCS set up that allows you to have a card on file. Whether that card is used to renew services automatically is entirely a matter for whether the WHMCS site owner asks WHMCS to do that.

I think it is a necessity because of the way Stripe works (perhaps Joe could comment on that in more detail). In essence, the card details have to be sent straight to Stripe by a POST direct to the Stripe servers. Back comes a token. You could not store the token in WHMCS, and just use it for a one-off charge, but then the card would still be stored at Stripe, and without a token there'd be no way to delete it. (Unless there was some way that you could (a) obtain the token, then (b) use the token to charge the card for this invoice, then either ©(i) store the token in the database, or ©(ii) use the token one final time to delete the card remotely. Jules, could you elaborate how you could automate card deletion with the hooks? If you've got it working, a slightly more detailed recipe would be helpful.

Well spotted, Brian. I had read that (not properly), and noticed that multiple reminders for the same client would be rolled together into one email. I had totally missed the fact that even if a client has only one domain, reminders for over 30 days would be sent on the 11th of the month. TBH, that is a surprising "feature", that (IMHO) should at least be optional. I had assumed that multiple reminders would be combined by WHMCS checking to see if that client has any other domain renewals due in the next 30 days, and if so waiting until it can send both. It's counter-intuitive that it will wait until a preset day of the month to send the reminder. Oh well - at least you found it in the docs, so we now know it's a feature rather than a bug!

Hmm So I've got my domain renewal emails set to go out after 60 days, then 30 days, then ... I had a couple of domains that were past 60 days but no emails had gone out. Then, suddenly, (when one had 52 days to go, and the other had 49), both clients got an email to let them know that their domains were due to expire in the next 60 days (such as domain X, with 49 days to go). Each client only had one domain, so WHMCS wasn't waiting to roll their multiple domains into one reminder. How come? Bug or feature? Surely, the cron run on {due-date minus 60 days} should have triggered the first reminder?

Matthew Joe's module does not determine when payment is made. If WHMCS attempts to charge their card, it use the Stripe module to do so. So it all depends how your WHMCS is set up. It's a WHMCS question, not a Stripe module question. If you've set up WHMCS to attempt card payment automatically N days before the due date, as each invoice reaches that point the daily WHMCS cron job will attempt card payment. But you can change those settings, and there is an option within WHMCS for any given client not to be charged automatically.

Sorry, yes, those are a red-herring. Those template files would be more to do with a client editing a card later, as opposed to going through checkout. But my question about which order form you're using is not a red-herring. Partly, it was an invitation to make sure you've copied across the order form completely. But more than that, if this thread is starting to get people going "me too", it's good to make sure that people are having the same issue. If all the people who are seeing this behaviour are using the same order form, and if none of the people who are saying "I'm fine" are using that particular order form, then the discussion becomes much more specific. Maybe the code for that order form needs altering slightly. Or maybe there's a trick to getting it to work that others have found.

If you're using a custom template, which creditcard.tpl and clientareacreditcard.tpl did you copy across - the "default" ones or the "portal" ones? And are you also using a custom order form, or are you using one of the built-in ones (ajaxcart, boxes, etc.) Have you taken out a year's support with Joe? If not that would be well worth doing (supports the module's development, too), and then you can work on it with him.

Yes - transactions in WHMCS show the fees for payments that arrived through this Stripe module.

As I understand it, Joe's always open to discussing having new features sponsored by those who want them.