Event-Driven Business Process Management and its Practical Application Taking the Exa


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Event-Driven Business Process Management and its Practical Application Taking the Exa
# 1  
Old 11-19-2008
Event-Driven Business Process Management and its Practical Application Taking the Exa

by Rainer von Ammon , Christoph Emmersberger, Florian Springer, Christian Wolff The recently coined term “Event-Driven Business Process Management” (EDBPM) is a combination of actually two different disciplines: Business Process Management (BPM) and Complex Event Processing (CEP). The common understanding behind BPM is that each company's unique way of doing business is captured in its business [...]

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
FraudDetect::preCharge(3pm)				User Contributed Perl Documentation			       FraudDetect::preCharge(3pm)

NAME
Business::FraudDetect::preCharge - backend for Business::FraudDetect (part of Business::OnlinePayment) SYNOPSIS
use Business::OnlinePayment my $tx = new Business::OnlinePayment ( 'someGateway', fraud_detect => 'preCharge', maximum_fraud_score => 500, preCharge_id => '1000000000000001', preCharge_security1 => 'abcdef0123', preCharge_security2 => '3210fedcba', ); $tx->content( first_name => 'Larry Walton', last_name => 'Sanders', login => 'testdrive', password => '', action => 'Normal Authorization', type => 'VISA', state => 'MA', zip => '02145', country => 'US', phone => '617 555 8900', email => 'lws@sanders.com', ip_address => '18.62.0.6', card_number => '4111111111111111', expiration => '0307', amount => '25.00', ); $tx->submit(); if ($tx->is_success()) { # successful charge my $score = $tx->fraud_score; my $id = $tx->fraud_transaction_id; #returns the preCharge transaction id } else { # unsucessful my $score = $tx->fraud_score; } DESCRIPTION
This module provides a driver for the preCharge Risk Management Solutions API Version 1.7 (16 Jan 2006). See Business::OnlinePayment and Business::FraudDetect for more information. CONSTRUCTION
Whe constructing the Business::OnlinePayment object, three risk management parameters must be included for the preCharge object to be properly constructed. o precharge_id This field is called "merchant_id" in the preCharge API manual o precharge_security1 This field is called "security_1" in the preCharge API manual o precharge_secuirty2 This field is called "security_2" in the preCharge API manual METHODS
This module provides no public methods. AUTHORS
Lawrence Statton <lawrence@cluon.com> Jason Hall <jayce@lug-nut.com> DISCLAIMER
THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. SEE ALSO
http://420.am/business-onlinepayment perl v5.12.4 2011-07-21 FraudDetect::preCharge(3pm)