First of all, CCBill has two different methods of user management and billing. The first is that CCBill manages your accounts and logins for you. They install some code on your system for you and somehow automagically you are supposed to be able to take logins. Of course, with a system like this, you have no idea who has access to your site and if you decide to leave them for another cc processor, you're screwed.
The second method is for those people who handle their own account provisioning and site security, and just want CCBill to do credit card processing only. You can have your users prefill out a form, check it for problems (like login ID already taken), assign a temporary password, then send it off to CCBill for processing. Once CCBill gets a successful billing on their credit card (or checking acount, phone number, etc), it will pass data to a script you've specified, via POST method. Your receiving script then finishes provisioning the authenticated account.
Two radically differnt methods for implementing CCBill. My question for you is, which method are you using? Method #1 is much easier to implement. Method #2 gives you more control over your login accounts, is more portable, and also keeps CCBill out of your code. Given the spyware/adware infestations CCBill has let through in the past, Method #2 is a much safer implementation. Method #2, however, requires extensive code writing to implement properly.
