<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://igamingforums.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results for 'tag:Fraud tag:Risk' matching tags 'Fraud' and 'Risk'</title><link>http://igamingforums.com/search/pro.htm?q=tag%3aFraud+tag%3aRisk</link><description>Search results for 'tag:Fraud tag:Risk' matching tags 'Fraud' and 'Risk'</description><dc:language>en-US</dc:language><generator>CSMOD (Build: 3273.32735)</generator><item><title>Re: Money Laundering</title><link>http://igamingforums.com/iGaming/MoneyLaundering/bbc/post.htm#308</link><pubDate>Mon, 23 Jun 2008 21:54:29 GMT</pubDate><guid isPermaLink="true">e9fc6c38-44c2-448e-ad72-ab9133b77580:308</guid><dc:creator>expat.iain</dc:creator><description> quote user peter Is it primarily up to the iGaming company Payment service provider or the Software Vendor to look out for fraud Who takes the responsibility quote Look at in this way 1 Gaming Company GC takes 100 bets on different account IDs with the same credit card CC the GC will have safeguards in place with the Risk amp Fraud team RF team to counteract this type of fraud This sort of action will be flagged instantly as WTF 2 100 GCs take one bet each from a client account The PSP notices that they have 100 transactions coming in from 100 different GCs each transaction being made with the same CC That s going to flag up on the RF team systems In these basic examples it s not a case of any one single entity performing their necessary due diligence procedures but more that we all have to be on our guard against this type of activity and each RF team will play its part in reducing the possibilities and instances of the occurrence of fraud We all have the responsibility not only to watch out for potential cases of fraud but all cases of unusual user activity HTH Iain </description></item></channel></rss>