This module comes with a documentation/manual (english), which has 5 pages. There you will find installation instructions, explanatory notes, general information about all features and the perspective of the module concerning ISPConfig 3.
Additionally you will find some code for your registrant module.

All further updates, bugfixes, new features and changes in ISPConfig 3 are included.
The price is only 30,00 EUR (one-time). Paymentmethod: PayPal

v1.0.2 released (9th Sep 2011):
- Add Loginlink in Clientarea
- Support for plan upgrading
- Support languages which are not in ISPC by default
- Bug: Problems with usernamehandling if it is a name like Johnny De Silva
- Bug: DNS not working___________________________________________________________________

Roadmap for v1.0.3:
- Support for using ISPC Addon Templates (?)
- Support for disc-, traffic-, .. usage in WHMCS (?)
- ...

Just to warn people, this module comes with a custom version of the remoting API (php files) for ISPConfig, which could pose issues with upgrades.

Germanius, can you confirm that features requests have been raised for each of the changes you've made to the remoting.inc.php and remote_user.tform.php files? If so, can you post the links on here so we can all vote?

As described in the documentation, the changes in the remotingfiles get overwritten, if you update ISPC. But you simply have to replace them again, then it is working again.

The changes I did in the remotingframework are already trasmitted to Till. He said, that he will include them in the stable SVN, so probably in the next ISPC version you dont have to change any remoting files.

Got it.
The only thing I have as a question is what to do with this. It's unclear what to change and where?

Add the code from function_RegisterDomain.txt to your registrar function RegisterDomain
at the end.
Add the code from function_TransferDomain.txt to your registrar function TransferDomain
at the end.
Add the code from function_RequestDelete.txt to your registrar function RequestDelete at
the end (if you have such a function).

That is optional. If you have the possibility to add custom code to your registrar module (if you already use one!!), then you can add the code to the existing function of your registrar module. But then you have to deactivate the domaintool function in the module, because these tasks are then done by the registrar module.

I think we should raise a Feature Request in the bug tracker to show Client Template ID & Server ID in the lists. If not, the only way to be sure you've got the right ID's would be to look in the database.

We are currently testing the new version 1.0.1, where those settings (serverid and defaultid's) are a little bit clearer, because of Servermanagement in WHMCS.
I will describe that in detail in the new manual, which will be released with the 1.0.1 in a few days.