view release on metacpan or  search on metacpan

lib/Business/CCProcessor.pm  view on Meta::CPAN

=head1 DIAGNOSTICS

=for author to fill in:
    List every single error and warning message that the module can
    generate (even the ones that will "never happen"), with a full
    explanation of each problem, one or more likely causes, and any
    suggested remedies.

=over

=item C<< Error message here, perhaps with %s placeholders >>

[Description of error here]

=item C<< Another error message here >>

[Description of error here]

[Et cetera, et cetera]

=back


=head1 CONFIGURATION AND ENVIRONMENT

=for author to fill in:
    A full explanation of any configuration system(s) used by the
    module, including the names and locations of any configuration
    files, and the meaning of any environment variables or properties
    that can be set. These descriptions must also include details of any
    configuration language used.
  
Business::CCProcessor requires no configuration files or environment variables.


=head1 DEPENDENCIES

=for author to fill in:
    A list of all the other modules that this module relies upon,
    including any restrictions on versions, and an indication whether
    the module is part of the standard Perl distribution, part of the
    module's distribution, or must be installed separately. ]

None at the moment, though a future version will reguire
CGI::FormBuilder for some additional methods.


=head1 INCOMPATIBILITIES

=for author to fill in:
    A list of any modules that this module cannot be used in conjunction
    with. This may be due to name conflicts in the interface, or
    competition for system or program resources, or due to internal
    limitations of Perl (for example, many modules that use source code
    filters are mutually incompatible).

None reported.


=head1 BUGS AND LIMITATIONS

Apparently, some credit card processors require that their
clients register the domain and path of the scripts which
may refer a user and browser to them.  Paypal did not reject
connections coming from my own development sandbox.  But both
DiA and VeriSign seem to refuse to do business with the machine
under my desk, when I used keys for accounts who's forms are
hosted at real url's.  

If the Verisgn account is setup to screen posts to its forms by
referring url, it is possible to configure a new url by logging in to
the VeriSign account, and following the following links: 

	Account Information -> 
	   PayflowLink Info ->
	      Accepted URLs 	(look at bottom of configuration page)

No bugs have been reported, but I'm sure this is riddled
with them.

By no means should this module be mistaken for any sort of
informed distillation of the wisdom available in the API's
for the services these methods interface with.  This is more
an attempt to hide some of the ugly details from myself for
some code I found myself rewriting on a regular basis.

At this early stage of development, I am simply working to
write an interface which can be substituted into multiple
copies of similiar code I am hosting in various scripts,
which I'd like to refactor and simplify.  If it serves your
needs, great.  If not, perhaps over time, this can evolve into
a more generally useful tool to serve a broader audience.

At this point, this is a "works-for-me" kind of project and
your input, questions, bug reports, patches and tests to create
a more robust, stable and useful tool are certainly welcome.

I welcome bug reports and feature requests at both:
L<http://www.campaignfoundations.com/project/issues>
as well as through the cpan hosted channels at:
C<bug-business-ccprocessor@rt.cpan.org>, or through the web
interface at L<http://rt.cpan.org>.

=head1 SEE ALSO 

Business::OnlinePayment allows a script to accept credit card
data from an end user or other source and process a transaction
of funds between the account represented by the credit card
data and the account owned by the merchant which deploys
the script. Its a fine tool for a client who can afford the
security it requires to appropriately handle credit card data.


=head1 AUTHOR

Hugh Esco  C<< <hesco@campaignfoundations.com> >>


=head1 LICENCE AND COPYRIGHT