Angie was so kind to answer this before in an email to me:
If you choose to use the passwordbyphone.com system to bill your own
content, the following will help you how to implement it to your sites.
(You are also able to use our content and sites at anytime.)
For every password your user calls for they get linked for 30 minutes (or
more) into YOUR content and you get paid for every password sold. In order
to set up the link into your content or member site we will need the
following data:
1) name/title of your site(s)
2) link into your content (protected member area);
example:
http://www.example.com/members/
Like with any other online billing systems (eg. your credit card billing
company), PasswordByPhone.com will have to communicate with your systems
member area. It works exactly the same as the linking to your existing
credit card processor. It is accomplished by a small script on your server
which acts as a gateway between the billing company and the technique you
use to secure your member area. This script would add entries to a htpasswd
file (for http basic authentication) or to your database for some kind of
session management. Therefore we need:
3) the url of a script on your server (see example below) to grant the user
30 minutes access / disconnect access through the PasswordByPhone.com
system.
Example:
http://www.example.com/interface/set...=abcdefg&passw
ord=123456
If you are already using other billing methods like credit card payment you
will mostly likely have all you need to integrate PasswordByPhone.com unto
your billing solutions and start to make start to make international money
immediately.
We will need this data for each of the sites you would want to use
PasswordbyPhone in. As soon we have received your info we will set it up and
we will send you an ID for each of your sites (a so-called 'package ID')
which you have to use within the banner codes. You will also get a brief
description on how easy it is to implement the banners and our system into
your sites.
Hope this answers your question.
Thanx,
Steve