X-Git-Url: http://git.freeside.biz/gitweb/?p=Business-OnlinePayment.git;a=blobdiff_plain;f=OnlinePayment.pm;h=41654511a4ec34d4c6cd6f1dcc1ba3b587600735;hp=f91ef1ef95d979570e9234906de5ca3d36fc373f;hb=d0a0086336b8c7b9f0ea3e4dea903f6a44bdefcc;hpb=4a0fcddf3100ea7e72007bee2cf3b758f7f4a32f diff --git a/OnlinePayment.pm b/OnlinePayment.pm index f91ef1e..4165451 100644 --- a/OnlinePayment.pm +++ b/OnlinePayment.pm @@ -1,50 +1,95 @@ package Business::OnlinePayment; use strict; -use vars qw($VERSION); +use vars qw($VERSION %_info_handler); use Carp; require 5.005; -$VERSION = '3.00_06'; +$VERSION = '3.03_01'; $VERSION = eval $VERSION; # modperlstyle: convert the string into a number # Remember subclasses we have "wrapped" submit() with _pre_submit() my %Presubmit_Added = (); -my %fields = ( - authorization => undef, - error_message => undef, - failure_status => undef, - fraud_detect => undef, - is_success => undef, - maximum_risk => undef, - path => undef, - port => undef, - require_avs => undef, - result_code => undef, - server => undef, - server_response => undef, - test_transaction => undef, - transaction_type => undef, +my @methods = qw( + authorization + order_number + error_message + failure_status + fraud_detect + is_success + maximum_risk + path + port + require_avs + result_code + server + server_response + test_transaction + transaction_type + fraud_score + fraud_transaction_id + response_code + response_header + response_page ); +#fallback +sub _info { + my $class = shift; + ( my $gw = $class ) =~ s/^Business::OnlinePayment:://; + { + 'info_compat' => '0.00', + 'gateway_name' => $gw, + 'module_notes' => "Module does not yet provide info.", + }; +} + +#allow classes to declare info in a flexible way, but return normalized info +%_info_handler = ( + 'supported_types' => sub { + my( $class, $v ) = @_; + my $types = ref($v) ? $v : defined($v) ? [ $v ] : []; + $types = { map { $_=>1 } @$types } if ref($types) eq 'ARRAY'; + $types; + }, + 'supported_actions' => sub { + my( $class, $v ) = @_; + return %$v if ref($v) eq 'HASH'; + $v = [ $v ] unless ref($v); + my $types = $class->info('supported_types') || {}; + ( map { $_ => $v } keys %$types ); + }, +); + +sub info { + my $class = shift; #class or object + my $info = $class->_info; + if ( @_ ) { + my $key = shift; + exists($_info_handler{$key}) + ? &{ $_info_handler{$key} }( $class, $info->{$key} ) + : $info->{$key}; + } else { + wantarray ? ( keys %$info ) : [ keys %$info ]; + } +} + sub new { my($class,$processor,%data) = @_; - Carp::croak("unspecified processor") unless $processor; + croak("unspecified processor") unless $processor; my $subclass = "${class}::$processor"; - if(!defined(&$subclass)) { - eval "use $subclass"; - Carp::croak("unknown processor $processor ($@)") if $@; - } + eval "use $subclass"; + croak("unknown processor $processor ($@)") if $@; my $self = bless {processor => $processor}, $subclass; - $self->build_subs(keys %fields); + $self->build_subs(@methods); if($self->can("set_defaults")) { - $self->set_defaults(); + $self->set_defaults(%data); } foreach(keys %data) { @@ -80,6 +125,8 @@ sub _risk_detect { $risk_transaction->content( %parent_content ); $risk_transaction->submit(); if ($risk_transaction->is_success()) { + $self->fraud_score( $risk_transaction->fraud_score ); + $self->fraud_transaction_id( $risk_transaction->fraud_transaction_id ); if ( $risk_transaction->fraud_score <= $self->maximum_fraud_score()) { return 1; } else { @@ -104,23 +151,21 @@ sub _pre_submit { # Search for an appropriate FD module foreach my $fraud_class ( @Fraud_Class_Path ) { my $subclass = $fraud_class . "::" . $fraud_detection; - if (!defined(&$subclass)) { - eval "use $subclass ()"; - if ($@) { - Carp::croak("error loading fraud_detection module ($@)") - unless ( $@ =~ m/^Can\'t locate/ ); - } else { - my $risk_tx = bless ( { processor => $fraud_detection } , $subclass ); - $risk_tx->build_subs(keys %fields); - if ($risk_tx->can('set_defaults')) { - $risk_tx->set_defaults(); - } - $risk_tx->_glean_parameters_from_parent($self); - return $self->_risk_detect($risk_tx); - } + eval "use $subclass ()"; + if ($@) { + croak("error loading fraud_detection module ($@)") + unless ( $@ =~ m/^Can\'t locate/ ); + } else { + my $risk_tx = bless( { processor => $fraud_detection }, $subclass ); + $risk_tx->build_subs(@methods); + if ($risk_tx->can('set_defaults')) { + $risk_tx->set_defaults(); + } + $risk_tx->_glean_parameters_from_parent($self); + return $self->_risk_detect($risk_tx); } } - Carp::croak("Unable to locate fraud_detection module $fraud_detection" + croak("Unable to locate fraud_detection module $fraud_detection" . " in \@INC under Fraud_Class_Path (\@Fraud_Class_Path" . " contains: @Fraud_Class_Path) (\@INC contains: @INC)"); } @@ -144,7 +189,7 @@ sub required_fields { push(@missing, $_) unless exists $content{$_}; } - Carp::croak("missing required field(s): " . join(", ", @missing) . "\n") + croak("missing required field(s): " . join(", ", @missing) . "\n") if(@missing); } @@ -172,7 +217,7 @@ sub remap_fields { sub submit { my($self) = @_; - Carp::croak("Processor subclass did not override submit function"); + croak("Processor subclass did not override submit function"); } sub dump_contents { @@ -197,6 +242,17 @@ sub build_subs { } } +#helper method + +sub silly_bool { + my( $self, $value ) = @_; + return 1 if $value =~ /^[yt]/i; + return 0 if $value =~ /^[fn]/i; + #return 1 if $value == 1; + #return 0 if $value == 0; + $value; #die?? +} + 1; __END__ @@ -230,9 +286,9 @@ Business::OnlinePayment - Perl extension for online payment processing Business::OnlinePayment is a generic module for processing payments through online credit card processors, electronic cash systems, etc. -=head1 METHODS AND FUNCTIONS +=head1 CONSTRUCTOR -=head2 new($processor, %processor_options); +=head2 new($processor, %processor_options) Create a new Business::OnlinePayment object, $processor is required, and defines the online processor to use. If necessary, processor @@ -243,7 +299,9 @@ supply reasonable defaults for this information, override the defaults only if absolutely necessary (especially path), as the processor module was probably written with a specific target script in mind. -=head2 content(%content); +=head1 TRANSACTION SETUP METHODS + +=head2 content(%content) The information necessary for the transaction, this tends to vary a little depending on the processor, so we have chosen to use a system @@ -254,149 +312,224 @@ correct fields in the backend. The currently defined fields are: =over 4 -=item * login +=item login Your login name to use for authentication to the online processor. -=item * password +=item password Your password to use for authentication to the online processor. =back -=head3 GENERAL TRANSACTION FIELDS +=head3 REQUIRED TRANSACTION FIELDS =over 4 -=item * type +=item type Transaction type, supported types are: CC (credit card), ECHECK (electronic check) and LEC (phone bill billing). Deprecated types -are: Visa, MasterCard, American Express, Discover, Check (not all -processors support all these transaction types). +are: Visa, MasterCard, American Express, Discover, Check. Not all +processors support all transaction types. -=item * action +=item action -What to do with the transaction (currently available are: Normal -Authorization, Authorization Only, Credit, Post Authorization) +What action being taken by this transaction. Currently available are: -=item * description +=over 8 -A description of the transaction (used by some processors to send -information to the client, normally not a required field). +=item Normal Authorization + +=item Authorization Only + +=item Post Authorization + +=item Reverse Authorization + +=item Void + +=item Credit -=item * amount +=item Recurring Authorization -The amount of the transaction, most processors don't want dollar signs -and the like, just a floating point number. +=item Modify Recurring Authorization -=item * invoice_number +=item Cancel Recurring Authorization + +=back + +=item amount + +The amount of the transaction. No dollar signs or currency identifiers, +just a whole or floating point number (i.e. 26, 26.1 or 26.13). + +=back + +=head3 OPTIONAL TRANSACTION FIELDS + +=over 4 + +=item description + +A description of the transaction (used by some processors to send +information to the client, normally not a required field). + +=item invoice_number An invoice number, for your use and not normally required, many processors require this field to be a numeric only field. +=item po_number + +Purchase order number (normally not required). + +=item tax + +Tax amount (portion of amount field, not added to it). + +=item freight + +Freight amount (portion of amount field, not added to it). + +=item duty + +Duty amount (portion of amount field, not added to it). + +=item tax_exempt + +Tax exempt flag (i.e. TRUE, FALSE, T, F, YES, NO, Y, N, 1, 0). + +=item currency + +Currency, specified as an ISO 4217 three-letter code, such as USD, CAD, EUR, +AUD, DKK, GBP, JPY, NZD, etc. + =back =head3 CUSTOMER INFO FIELDS =over 4 -=item * customer_id +=item customer_id A customer identifier, again not normally required. -=item * name +=item name The customer's name, your processor may not require this. -=item * first_name +=item first_name -=item * last_name +=item last_name The customer's first and last name as separate fields. -=item * company +=item company The customer's company name, not normally required. -=item * address +=item address The customer's address (your processor may not require this unless you are requiring AVS Verification). -=item * city +=item city The customer's city (your processor may not require this unless you are requiring AVS Verification). -=item * state +=item state The customer's state (your processor may not require this unless you are requiring AVS Verification). -=item * zip +=item zip The customer's zip code (your processor may not require this unless you are requiring AVS Verification). -=item * country +=item country Customer's country. -=item * ship_first_name +=item ship_first_name -=item * ship_last_name +=item ship_last_name -=item * ship_company +=item ship_company -=item * ship_address +=item ship_address -=item * ship_city +=item ship_city -=item * ship_state +=item ship_state -=item * ship_zip +=item ship_zip -=item * ship_country +=item ship_country These shipping address fields may be accepted by your processor. Refer to the description for the corresponding non-ship field for general information on each field. -=item * phone +=item phone Customer's phone number. -=item * fax +=item fax Customer's fax number. -=item * email +=item email Customer's email address. +=item customer_ip + +IP Address from which the transaction originated. + =back =head3 CREDIT CARD FIELDS =over 4 -=item * card_number +=item card_number + +Credit card number. + +=item expiration -Credit card number (obviously not required for non-credit card -transactions). +Credit card expiration. -=item * cvv2 +=item cvv2 CVV2 number (also called CVC2 or CID) is a three- or four-digit security code used to reduce credit card fraud. -=item * expiration +=item card_token -Credit card expiration (obviously not required for non-credit card -transactions). +If supported by your gateway, you can pass a card_token instead of a +card_number and expiration. -=item * recurring billing +=cut + +#=item card_response +# +#Some card_token schemes implement a challenge/response handshake. In those +#cases, this field is used for the response. In most cases the handshake +#it taken care of by the gateway module. + +=item track1 + +Track 1 on the magnetic stripe (Card present only) + +=item track2 + +Track 2 on the magnetic stripe (Card present only) + +=item recurring_billing Recurring billing flag @@ -406,64 +539,112 @@ Recurring billing flag =over 4 -=item * account_number +=item account_number + +Bank account number + +=item routing_code + +Bank's routing code -Bank account number for electronic checks or electronic funds -transfer. +=item account_type -=item * routing_code +Account type. Can be (case-insensitive): B, +B, B or B. -Bank's routing code for electronic checks or electronic funds -transfer. +=item account_name -=item * account_type +Account holder's name. -Account type for electronic checks or electronic funds transfer. +=item bank_name -=item * account_name +Bank name. -Account holder's name for electronic checks or electronic funds -transfer. +=item bank_city -=item * bank_name +Bank city. -Bank's name for electronic checks or electronic funds transfer. +=item bank_state -=item * check_type +Bank state. -Check type for electronic checks or electronic funds transfer. +=item check_type -=item * customer_org +Check type. + +=item customer_org Customer organization type. -=item * customer_ssn +=item customer_ssn -Customer's social security number. Typically only required for -electronic checks or electronic funds transfer. +Customer's social security number. -=item * license_num +=item license_num -Customer's driver's license number. Typically only required for -electronic checks or electronic funds transfer. +Customer's driver's license number. -=item * license_dob +=item license_dob -Customer's date of birth. Typically only required for electronic -checks or electronic funds transfer. +Customer's date of birth. =back -=head2 submit(); +=head3 RECURRING BILLING FIELDS + +=over 4 + +=item interval + +Interval expresses the amount of time between billings: digits, whitespace +and units (currently "days" or "months" in either singular or plural form). + +=item start + +The date of the first transaction (used for processors which allow delayed +start) expressed as YYYY-MM-DD. + +=item periods + +The number of cycles of interval length for which billing should occur +(inclusive of 'trial periods' if the processor supports recurring billing +at more than one rate) + +=back + +=head2 test_transaction() + +Most processors provide a test mode, where submitted transactions will +not actually be charged or added to your batch, calling this function +with a true argument will turn that mode on if the processor supports +it, or generate a fatal error if the processor does not support a test +mode (which is probably better than accidentally making real charges). + +=head2 require_avs() + +Providing a true argument to this module will turn on address +verification (if the processor supports it). + +=head1 TRANSACTION SUBMISSION METHOD + +=head2 submit() Submit the transaction to the processor for completion -=head2 is_success(); +=head1 TRANSACTION RESULT METHODS + +=head2 is_success() Returns true if the transaction was submitted successfully, false if it failed (or undef if it has not been submitted yet). -=head2 failure_status(); +=head2 error_message() + +If the transaction has been submitted but was not accepted, this +function will return the provided error message (if any) that the +processor returned. + +=head2 failure_status() If the transaction failed, it can optionally return a specific failure status (normalized, not gateway-specific). Currently defined statuses @@ -476,65 +657,161 @@ newest processor modules, and that, even if supported, a failure status is an entirely optional field that is only set for specific kinds of failures. -=head2 result_code(); +=head2 authorization() + +If the transaction has been submitted and accepted, this function will +provide you with the authorization code that the processor returned. +Store this if you would like to run inquiries or refunds on the transaction +later. + +=head2 order_number() + +The unique order number for the transaction generated by the gateway. Store +this if you would like to run inquiries or refunds on the transaction later. + +=head2 card_token() + +If supported by your gateway, a card_token can be used in a subsequent +transaction to refer to a card number. + +=head2 fraud_score() + +Retrieve or change the fraud score from any Business::FraudDetect plugin + +=head2 fraud_transaction_id() + +Retrieve or change the transaction id from any Business::FraudDetect plugin + +=head2 response_code() + +=head2 response_headers() + +=head2 response_page() + +These three fields are set by some processors (especially those which use +HTTPS) when the transaction fails at the communication level rather than +as a transaction. + +response_code is the HTTP response code and message, i.e. +'500 Internal Server Error'. + +response_headers is a hash reference of the response headers + +response_page is the raw content. + +=head2 result_code() Returns the precise result code that the processor returned, these are normally one letter codes that don't mean much unless you understand the protocol they speak, you probably don't need this, but it's there just in case. -=head2 test_transaction(); +=head2 avs_code() -Most processors provide a test mode, where submitted transactions will -not actually be charged or added to your batch, calling this function -with a true argument will turn that mode on if the processor supports -it, or generate a fatal error if the processor does not support a test -mode (which is probably better than accidentally making real charges). +=head2 cvv2_response() -=head2 require_avs(); +=head1 MISCELLANEOUS INTERNAL METHODS -Providing a true argument to this module will turn on address -verification (if the processor supports it). - -=head2 transaction_type(); +=head2 transaction_type() Retrieve the transaction type (the 'type' argument to contents()). Generally only used internally, but provided in case it is useful. -=head2 error_message(); - -If the transaction has been submitted but was not accepted, this -function will return the provided error message (if any) that the -processor returned. - -=head2 authorization(); - -If the transaction has been submitted and accepted, this function will -provide you with the authorization code that the processor returned. - -=head2 server(); +=head2 server() Retrieve or change the processor submission server address (CHANGE AT YOUR OWN RISK). -=head2 port(); +=head2 port() Retrieve or change the processor submission port (CHANGE AT YOUR OWN RISK). -=head2 path(); +=head2 path() Retrieve or change the processor submission path (CHANGE AT YOUR OWN RISK). +=head1 HELPER METHODS FOR GATEWAY MODULE AUTHORS + +=head2 build_subs( @sub_names ) + +Build setter/getter subroutines for new return values. + +=head2 get_fields( @fields ) + +Get the named fields if they are defined. + +=head2 remap_fields( %map ) + +Remap field content (and stuff it back into content). + +=head2 required_fields( @fields ) + +Croaks if any of the required fields are not present. + +=head2 dump_contents + +=head2 silly_bool( $value ) + +Returns 0 if the value starts with y, Y, t or T. +Returns 1 if the value starts with n, N, f or F. +Otherwise returns the value itself. + +Use this for handling boolean content like tax_exempt. + =head1 AUTHORS +(v2 series) + Jason Kohles, email@jasonkohles.com -(v3 rewrite) Ivan Kohler +(v3 rewrite) + +Ivan Kohler Phil Lobbes Ephil at perkpartners dot comE +=head1 COPYRIGHT + +Copyright (c) 1999-2004 Jason Kohles +Copyright (c) 2004 Ivan Kohler +Copyright (c) 2007-2012 Freeside Internet Services, Inc. + +All rights reserved. + +This program is free software; you can redistribute it and/or modify it under +the same terms as Perl itself. + +=head1 HOMEPAGE + +Homepage: http://420.am/business-onlinepayment/ + +Development: http://420.am/business-onlinepayment/ng.html + +=head1 MAILING LIST + +Please direct current development questions, patches, etc. to the mailing list: +http://420.am/cgi-bin/mailman/listinfo/bop-devel/ + +=head1 REPOSITORY + +The code is available from our public CVS repository: + + export CVSROOT=":pserver:anonymous@cvs.freeside.biz:/home/cvs/cvsroot" + cvs login + # The password for the user `anonymous' is `anonymous'. + cvs checkout Business-OnlinePayment + +Or on the web: + + http://freeside.biz/cgi-bin/viewvc.cgi/Business-OnlinePayment/ + +Many (but by no means all!) processor plugins are also available in the same +repository, see: + + http://freeside.biz/cgi-bin/viewvc.cgi/ + =head1 DISCLAIMER THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED