Difference between revisions of "Business::FraudDetect"

From Freeside
Jump to: navigation, search
(adding quick fraud detection specs)
 
(reverting spam)
 
(39 intermediate revisions by 10 users not shown)
Line 5: Line 5:
 
== proposed Business::OnlinePayment fraud detection API ==  
 
== proposed Business::OnlinePayment fraud detection API ==  
  
my $transaction = Business::OnlinePayment(
+
  my $transaction = Business::OnlinePayment(
  $gateway,
+
    $gateway,
  'fraud_detection' => 'preCharge',
+
    'fraud_detection' => 'preCharge',
  'preCharge_id' =>'',
+
    'preCharge_id' =>'',
  'preCharge_security_1' => '',
+
    'preCharge_security_1' => '',
  'preCharge_security_2 => ''
+
    'preCharge_security_2 => ''
);
+
  );
  
 
== OO ==
 
== OO ==
Line 21: Line 21:
 
== Packaging ==
 
== Packaging ==
  
The new modules should go in the Business-OnlinePayment distribution, so that an installation of Business::OnlinePayment gives you Business::FraudDetect and Business::FraudDetect::preCharge as well.
+
The new modules should go in the Business-OnlinePayment distribution (checked into CVS for now, uploaded to CPAN upon project completion), so that an installation of Business::OnlinePayment gives you Business::FraudDetect::preCharge as well.

Latest revision as of 17:20, 25 July 2009

preCharge API

https://helpdesk.precharge.net/index.php?_m=downloads&_a=downloadfile&downloaditemid=1

proposed Business::OnlinePayment fraud detection API

 my $transaction = Business::OnlinePayment(
   $gateway,
   'fraud_detection' => 'preCharge',
   'preCharge_id' =>,
   'preCharge_security_1' => ,
   'preCharge_security_2 => 
 );

OO

Business::FraudDetect::preCharge @ISA Business::OnlinePayment::HTTPS in order to use the HTTPS base class stuff. It can be written just like a Business::OnlinePayment gateway module, with a new action "Fraud Detect". That way gateways which support internal fraud detection can just add the new action.

When passed a fraud_detection argument, Business::OnlinePayment would look for a matching Business::FraudDetect::$module and then a Business::OnlinePayment::$module, and then run a "Fraud Detect" transaction against it, then run the real transaction if the fraud detection came back okay.

Packaging

The new modules should go in the Business-OnlinePayment distribution (checked into CVS for now, uploaded to CPAN upon project completion), so that an installation of Business::OnlinePayment gives you Business::FraudDetect::preCharge as well.