What non CC payment options do you use?
 

Anything easy to implement to allow access to existing members areas?

Do the alternative billing company's scripts collide in .htaccess with cc billing & member management scripts? If so what is the usual workaround?

Your opinion or advice?

Passwordbyphone is good allegedly.

So I have read, PBP got me to start this thread. Looking for input from people who have implemented it or an alternative & any tips.

In febuary I will be using these people:

http://www.globaladultbilling.com/

Cool, I noticed your attentiveness to alternative billing in your "serious post".

Thanks I'll check them out now.

Yep, I will also be using passwordbyphone as well...
I understand exactly what you mean when you you say you are concerned as to compatibility issues, and all the scrips 'playing nicely' with each other....
Thats a major concern to me as well :)

Doing my research, Im lead to believe they all should be compatible... But Im actually heading my bets slightly by doing a few 'different versions' of the same videos, using diff methods... For example, I particularly like the 'tubecash' variant they offer:

http://www.globaladultbilling.com/tubecash/

So I will have my vids using this method on a diff URL but with the same branding... ie main site is 'MyFetishName'POV.com but the same vids using the tubecash method will be on the url of 'MyFetishName'tube.com

So I cant see major problems... But then Im not really offering 'membership' as such... Just short accsess periods when the video can be viewed online... Not the '30 Day recurring' model...

Yeah it must vary when using a pay per shoot payment model, mostly as you say I am wondering if the scripts need mirrored content or HOPEFULLY they can use the same members area.

Anyone simply added password by phone or global adult billing to an existing site? How did that go?

I spoke with EmmJay (PasswordByPhone) in person at WMA amsterdam, and he assured me that with his system, it was possible to just have them add in the system for you with no problems, to a 'standard' members area thing...

Havnt got that info for GAB though...

Bump for anyone already using either system?

a friend uses visa and mastercard giftcards for direct payments, most are available in pharmacies, grocery stores, malls, etc in US, Canada, etc

Anyone making money with password by phone or global adult billing?

I never trusted scripts from different billers to update htaccess - AFAIK there's no portable way to lock a file in unix, which means that if they attempted to update at exactly the same time there's a good chance the file will be corrupted. I ended up having the biller scripts write to separate password files then another script to join them together. The generated htaccess file can still be corrupt if two billers update simultaneously, but a cron job entry will regenerate that file (properly) soon afterwards.

Thanks...

Passwordbyphone seems pretty good as far as customer support and so forth.

I've tested Linux file locking under EXTREME conditions - tens of thousands of processes
all trying to access the same file at once. An NFS system (cluster) can fail this test
spectacularly if it's not configured fto choose reliable locking rather than performance,
but a normal Linux system is extremely solid. Remember, Unix/Linux was from the start
back in the 1970s designed as a multi-user system, designed to make it impossible for
two users to step on each other even if they tried. This is the same reason it's
inherently secure - I could give you a SSH account on my server, allowing you to
use it, and theoretically you STILL couldn't mess up the system. Thus the better
security than Windows, where any access to the system whatsoever is complete
access to fuck it up in any way you want because Windows was designed as a
single user, non-networked system.

On the other hand, most processors' scripts all suffer from the same bug - when you
run out of disk space they'll wipe the file out completely. It's for this reason that I
find separate password files can be handy - when one processor's file gets hosed
the others may still be OK. Also in case of a hack - hopefully only one processor's
file gets hacked.

You may want to double check your script which combines the password files -
it probably doesn't help one bit if you have a locking problem because you still
have to lock that combined file unless you're going to have delayed joins, where
someone doesn't get immediate access. Many sites, such as those using Strongbox,
can use multiple password files and database tables without any untested script to
combine them - Strongbox supports multiple password files, databases, and authentication
servers out of the box.