Jump to content

recoil

Member
  • Posts

    17
  • Joined

  • Last visited

About recoil

recoil's Achievements

Junior Member

Junior Member (1/3)

0

Reputation

  1. Hello all, I was wondering if there has been some change regarding WHMCS's relationship with resellerclub? The url I used to use, domains.whmcs.com, no longer directs to the resellerclub login. Also, on the WHMCS domains page even though Enom and Resellerclub are listed, both images direct to the WHMCS Enom information page.
  2. I'd be happy to do that, but I don't see any correlation between the two. A new signup is given a stripe customer ID which I don't see anywhere in whmcs and vice versa.
  3. I have the same problem with 21.0.1180.89 m
  4. I don't mean to double post, but it looks like my post should've went in this thread: Anyone have issues with customers saving credit cards using this module? I was able to implement it without issue - I thought. My customers can't pay or update their credit cards. But signing up a new account works fine. Does the module not support existing customers? It looks like there is no way to correlate the stripe customer id with the whmcs id. My customers are getting the following when trying to update their credit card: Remote Transaction Failure. Please Contact Support I see in the gateway log: UserID => 11 ERRORMSG => No such customer: 11 PATH => :storeremote::update::c2:
  5. Is there new discount code for this module by any chance?
  6. Ahh. thanks! It was in fact the vault key, which had special characters in it. This should definitely be noted in the whmcs kb article for the migration.
  7. Any luck with this? I tried the migration and every single one of mine failed.
  8. The author of this plugin wrote me today to inform me that he is in the middle of switching servers, that is why webhostingcolumn (and therefore whmcsgold.com) are down. That's all I know, thought I'd share.
  9. Is the most recent version of this the one post from March, 0.9b2?
  10. Right. That's what I thought. Sorry for not being clear. The domain "blitz" caused my enom account to deplete unexpectedly therefore causing problems for a few renewals.
  11. Thanks for the post. Perhaps I wasn't clear, I am referring to domain renewals where the client has paid (order accepted) and the API is unable to successfully execute due to insufficient funds at the registrar. So the order, from the client billing perspective, has been fulfilled, however the backend call didn't renew the domain.
  12. I've been giving Matt and crew a run for their money lately with a few helpdesk tickets, so I thought I'd ask this one in the forum: Let's say I was out of town for a week and don't top off my registrar account (with say enom) during a domain registration blitz. A few client domains attempt to renew as they've paid and I get a message indicating there isn't enough funds to cover renewals. So now I would have a few "Manual Domain Renewal" items in my to-do list. What is the correct procedure from here? Do I go in an manually renew the domains at the registrar or do I top off the account and whmcs will rerun the renewal request via the registrar API?
  13. Is there anyway to set a subject for these like the admin cron? Or is it in the encoded file? I get enough cron messages with the servers we manage. Ideally it would say "{registrar} Sync Report".
  14. Maybe I'm misunderstanding: So with WHMCS I have to change my server config any time I change my password (which is frequently)? If that's the case then we definitely need the Remote Access Key option.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated