For both of your use-cases the 3rd example I gave will work Suho
On Sat, Nov 1, 2014 at 1:49 AM, Supun Muthutantrige <[email protected]> wrote: > Hi Suho, > > The scenario is, we should be able to trigger an alert when multiple > shipping's are being caused by applying a single credit card. In our case > this should occur when third distinct address pop's up in an event. So in > my previous example, if we consider the 4th transaction which is, > > *Colombo --> Kandy --> Colombo --> Kandy(4th)* > > This 4th transaction is not fraudulent since the credit card has been used > only for shipments for two distinct addresses (Kandy & Colombo). But when > the 5th transaction occurs from the same card, > > *Colombo --> Kandy --> Colombo --> Kandy --> Matara(5th)* > > The 5th transaction should be fraudulent, as it is the 3rd distinct > address (Matara, kandy & Colombo) that is being shipped by using the same > credit card. Thereafter, any transactions executed by the same credit card > should also be fraudulent, as three distinct destinations are already > available. > > So that is the requirement and I will use your examples and let you know. > > Thank you for the input suho. > > Thank you, > Regards. > > *Supun Rasitha Muthutantrige* > Software Engineer | Intern > WSO2 Inc: http://wso2.com > lean.enterprise.middleware > Mobile: 0758374608 > -- *S. Suhothayan* Technical Lead & Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * <http://wso2.com/>* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
