Apache-Centipaid
view release on metacpan or search on metacpan
Centipaid.pm view on Meta::CPAN
#in httpd.com
<directory /document_root/path_path>
AuthName centipaid
AuthType custom
PerlAuthenHandler Apache::Centipaid
require valid-user
PerlSetVar acct account_name
PerlSetVar pass receipt_password
PerlSetVar amount 0.01
PerlSetVar duration 1d
PerlSetVar access /pay_path
PerlSetVar domain your.domain.name
PerlSetVar lang en
PerlSetVar enforce_ip 0
PerlSetVar https https://pay.centipaid.com
PerlSetVar authserver centipaid_receipt_server
PerlSetvar authport 2021
Centipaid.pm view on Meta::CPAN
At this stage, Apache::Centipaid realizes that a rececipt is being submited
as payment. It takes the receipt number and autheticates with centipaid's
receipt server to insure that the receipt is a valid one, and that the
proper funds have been paid.
If the rececipt is valid, then the information is stored locally. The
information stored included the ip of the client (for optional enforcment
of payment tied to ip), amount paid, date of transaction, expiry date,
and the zone the payment covers. And since centipaid micropayment system
is designed to allow users to pay without having to provide username,
password or any other payment information other than the recipt
number, it makes the process easy to manage and neither the payer or
payee have to worry about financial information falling into the wrong
hands.
B<How do we track payments?>
When a user makes a payment, the Apache::Centipaid module inserts a cookie
that contains the receipt number, and it sets the expiry of the cookie
based on the payment B<duration> specified in the configuration file.
Everytime a user visits protected areas in a site, the cookie is
inspected, and if it exists it is matched with the receipt database. if
Centipaid.pm view on Meta::CPAN
=over
=item B<Account and Access Information>
=item B<acct> account_name
The account number is issued by ceentipaid.com
for a given domain name. This number is unique
and it determines who gets paid.
=item B<pass> receipt_password
The password is used only in socket authetication.
It does not grant the owner any special access
except to be able to query the receipt server for
a given receipt number.
=item B<amount> 0.5
The amount is a real number (float, non-integer)
that specifies how much the user must pay to be
granted access to the site. For example amount
0.5 will ask the user to pay 50 cents to access the
Centipaid.pm view on Meta::CPAN
configuration file.
=item B<dbuser> user
This should be the username of the user that has
access to read/write to the database defined in
dbname.
=item B<dbpass> pass
This should be the password of the user that has
access to read/write to the database defined in
dbname.
=back
=head1 Database Schema
B<MySQL> The receipts are stored in a locally accessible database.
The MySQL database structure is as follows
Q)I installed Apache::Centipaid and everything installed properly without
any error messages. However when I try to access a section that is
protected I get an apache error. What is going on?
1)First insure that all the proper perl modules are installed. You can simply
check that by running make test in the Apache::Centipaid directory.
---> if this condition is met, thenm proceed to next test
2)Check that the local database "centipaid_rcpt" is installed and can be accessed
using the username/password specified in the configuration
---> if this condition is met, thenm proceed to next test
3)Check the error logs of your virtual host with Apache::Centipaid
If you see an error log that references to CGI/Cookie.pm (see example)
then you need to reinstall CGI.pm - We have included a tested version
of CGI.pm in the contrib directory, however it is recommended to get the
latest version from http://www.perl.com/CPAN/modules/by-module/CGI/
>Attempt to free unreferenced scalar.
RCS/Centipaid.pm,v view on Meta::CPAN
#in httpd.com
<directory /document_root/path_path>
AuthName centipaid
AuthType custom
PerlAuthenHandler Apache::Centipaid
require valid-user
PerlSetVar acct account_name
PerlSetVar pass receipt_password
PerlSetVar amount 0.01
PerlSetVar duration 1d
PerlSetVar access /pay_path
PerlSetVar domain your.domain.name
PerlSetVar lang en
PerlSetVar enforce_ip 0
PerlSetVar https https://pay.centipaid.com
PerlSetVar authserver centipaid_receipt_server
PerlSetvar authport 2021
RCS/Centipaid.pm,v view on Meta::CPAN
At this stage, Apache::Centipaid realizes that a rececipt is being submited
as payment. It takes the receipt number and autheticates with centipaid's
receipt server to insure that the receipt is a valid one, and that the
proper funds have been paid.
If the rececipt is valid, then the information is stored locally. The
information stored included the ip of the client (for optional enforcment
of payment tied to ip), amount paid, date of transaction, expiry date,
and the zone the payment covers. And since centipaid micropayment system
is designed to allow users to pay without having to provide username,
password or any other payment information other than the recipt
number, it makes the process easy to manage and neither the payer or
payee have to worry about financial information falling into the wrong
hands.
B<How do we track payments?>
When a user makes a payment, the Apache::Centipaid module inserts a cookie
that contains the receipt number, and it sets the expiry of the cookie
based on the payment B<duration> specified in the configuration file.
Everytime a user visits protected areas in a site, the cookie is
inspected, and if it exists it is matched with the receipt database. if
RCS/Centipaid.pm,v view on Meta::CPAN
=over
=item B<Account and Access Information>
=item B<acct> account_name
The account number is issued by ceentipaid.com
for a given domain name. This number is unique
and it determines who gets paid.
=item B<pass> receipt_password
The password is used only in socket authetication.
It does not grant the owner any special access
except to be able to query the receipt server for
a given receipt number.
=item B<amount> 0.5
The amount is a real number (float, non-integer)
that specifies how much the user must pay to be
granted access to the site. For example amount
0.5 will ask the user to pay 50 cents to access the
RCS/Centipaid.pm,v view on Meta::CPAN
configuration file.
=item B<dbuser> user
This should be the username of the user that has
access to read/write to the database defined in
dbname.
=item B<dbpass> pass
This should be the password of the user that has
access to read/write to the database defined in
dbname.
=back
=head1 Database Schema
B<MySQL> The receipts are stored in a locally accessible database.
The MySQL database structure is as follows
RCS/Centipaid.pm,v view on Meta::CPAN
d364 23
a386 2
as payment. It accepts the receipt number and autheticates it with
centipaid.com to make sure that the site owener got paid what he asked for.
d388 2
a389 7
If the rececipt is valid, then we store the receipt information along with
the ip of the client (for optional enforcment of payment tied to ip), amount
paid, when it was paid, and when does the payment expire. Centipaid payment
system is designed to allow users to pay for service without having to provide
username, password or any payment information such as credit card number. As
a user you only provide a receipt number which is not tied to any of the users'
information.
d471 7
@
1.1
log
@Initial revision
@
RCS/Centipaid.pm,v view on Meta::CPAN
a326 1
one of the payment methods accepted by centipaid.com (i.e. internet stamps).
d359 2
d363 5
a367 3
* acct account_name
The account number is issued by ceentipaid.com for a given domain
name. This number is unique and it determines who gets paid.
d369 1
a369 4
* pass receipt_password
The password is used only in socket authetication. It does not grant
the owner any special access except to be able to query the receipt
server for a given receipt number.
d371 11
a381 5
* amount 0.5
The amount is a real number (float, non-integer) that specifies how
much the user must pay to be granted access to the site. For example
amount 0.5 will ask the user to pay 50 cents to access the
d384 16
wishing to charge their customers nominal fees for accessing their online
resources. For example, a site could charge customers $1 to use their search
facility for seven days, and $0.05 to access a public forum for one day, without
having to redesign their website, or integrate complex subscription applications.
Apache::Centipaid allows content and service providers to seamlessly accept
micro payments from online visitors without changing their website design.
The micro payment system relies on specially designed internet stamps which
are used by their visitors to make payments online quickly and securely. Paying
with an Internet stamp is secure and easy, there are no usernames, or
password to enter. No financial or personal information is used or transmitted
while making a payment. When paying with an internet stamp, a user only provides
the stamp itself. There is no need to provide a credit card number or any other
form of identification
Internet stamps
---------------
Internet stamps are specially crafted electronic images containing encrypted
information required for clearing payments through Centipaid. The stamps are
assembled using our patent-pending process to create steganographically encrypted
stamps used in making secure and anonymous micro payments online.
Each internet stamp is unique from an electronic point of view, having an
individual serial number. Each one is treated as a virtual pre-paid card and
is uploaded to Centipaid whenever payment is requested. This parallels the
swiping of a credit cards through a card reader at a physical store location.
By uploading the stamp, there is no need to remember, enter, or jot down
usernames, passwords, or credit card numbers.
Latest Version
==============
Please check for the latest version of this software for important fixes and
added features at http://www.centipaid.com/download/apache_centipaid.html
Support
=======
Centipaid maintains current support issues in the Knowledgebase at
http://www.centipaid.com/faq/ and the support forums at
( run in 1.267 second using v1.01-cache-2.11-cpan-49f99fa48dc )