Adding CCbill to a site that already has Ibill?
 

How difficult is it to add CCbill as a second processor to an existing site(already have Ibill)? Is there any extra soft ware needed?

thx,
Ray

signup with them and let them install on your site.
Im using ccbill and am gonna signnup with ibill now.
hows the setup with ibill?

Pretty straight forward concidering they do it all.

So, it can be done without some sort of cascading proggy?

you can setup as many as you want without cascading so you shouldnt be concerned.
Now, about cascading between ibill and ccbill that would be very nice....any info on this without having to use mpa lol

do you end up using the same .htpasswd file for both processors? i was curious about this as well, as ccBill keeps their .htpasswd in a directory that is nested within the "ccbill" directory, can another billing company's script add/manage members within the same .htpasswd file?

i'm unclear as to whether you would end up w/ two active .htpasswd files, is that even possible..?

Good points..bump

if you are using ccbill as your primary, they give you a place to redirect your declines. This is where you should redirect them to an ibill join page.

I'm not familliar with ibill's set up, so I dont know if it works the same in reverse or not

Good questions in this thread, anyone have an answer thats done it before?

Good post, going to bump because I want to know the answers.

easy!:Graucho

:helpme

I have Ibill and another Euro biller. For the EURO one, I just changed in the cgi script the location of the password file ( same file for both ). New passwords are written to that file as well as deleted one.

Maybe Ibill could do it for you, but just be ready for many emails.

Ray,

It is actually very easy. There are many ways we can make this work without the use of any extra software. We can have you up and running in no time.

chupacabra,

In most cases we write to the existing password file as this is the easiest method. You can have two password files but it really depends on your servers configuration.

If you have any further questions please contact clientsupport at ccbill dot com

-Paul

thx Directfiesta, that is very similar to what i'm wanting to do... can i hit you on ICQ perhaps w/ a couple queries?


ccBillPaul, thats kinda what i thought but i was worried that the ccBill "rebuild password file" function could become a deadly weapon, wiping out all pw pairs that had been placed by the secondary processor..

I was using verotel before ccbill and had ccbill install it in the same place where verotel pass file is.

on another site i let ccbill setup up their usual way which is nested within the "ccbill" directory....
Whichever you choose its usally pretty easy to do both ways, just have to specify to tech dept

CCbill and Epoch (Paycom ) work together well forget Ibill they are more trouble than they are worth and they will just give your money to Visa. Stick with the best guys CCbill and Paycom and you will make more $$$$

No Paycom in UK.


Thanks for everyones help..some great replies. I will be contacting CCbill soon.

peace!

I wish I could use Paycom.

Password Management on the iBill system will allow you to use multiple processors in conjunction with the same password file. If the password file is in a CCBILL folder, we can simply point our Password Management script to communicate with the absolute path to the current .htpasswd file. The installation isn't too complicated and can be installed in very short time frame. The requirements for Password Management are UNIX server with .htaccess support. We also offer a solution that can be used with Windows 2000 and SQL Server 2000.

We allow the client the ability to customize their own html version of the decline page in the event the transaction fails. This gives you the ability to customize several options for declined transactions.

One final bit of advice, you may need to think about not just sending your secondary processor decline traffic. The issue is that you will potentially be sending them very high risk traffic which could result in high chargeback rates on that processor. You may want to consider putting multiple processors on your join page and referring delines back to that page or using a cascade billing solution.

If you have any questions, please feel free to contact iBill for support.

me 2

:(

On a Linux server it's pretty easy to share the same .htpasswd:

> cd /yourpath/cgi-bin/ccbill/some_cryptic_letters_and_figures/password

> rm -f .htpasswd (assuming it's not in use yet!)

> ln -s /path/to/your/real/.htpasswd .htpasswd

No guarantee. Modifications at your own risk! :Graucho

We've had this setup for one of our clients using MySQL for storing usernames. Both IBill and CCBill writing to the same DB. Just needed to update IBill for inserting rows and add a duplicate username test in case it tried to register a username that was in use by CCBill already.