Difference between revisions of "Fraud Detection"

From MgmtWiki
Jump to: navigation, search
(Full Title or Meme)
(Full Title or Meme)
Line 1: Line 1:
 
==Full Title or Meme==
 
==Full Title or Meme==
 
An existing process in ecommerce where the [[Relying Party]] collects the claims about the user and the context of the request (which will likely include user behavior and value of the transaction) into a [[Trust Vector]] for processing by a [[Fraud Detection]] Service. The result will be used to make the [[Authorization]] decision, or it might initiate a continued collection of user claims for a retry.
 
An existing process in ecommerce where the [[Relying Party]] collects the claims about the user and the context of the request (which will likely include user behavior and value of the transaction) into a [[Trust Vector]] for processing by a [[Fraud Detection]] Service. The result will be used to make the [[Authorization]] decision, or it might initiate a continued collection of user claims for a retry.
 +
 +
==Context==
 +
*Today any company that handles money on the internet has some level of [[Fraud Detection]], most of the smaller companies relying on Services.
 +
*The original https://corpgov.law.harvard.edu/2016/02/07/fincen-know-your-customer-requirements/
 +
 
==References==
 
==References==

Revision as of 09:03, 26 August 2018

Full Title or Meme

An existing process in ecommerce where the Relying Party collects the claims about the user and the context of the request (which will likely include user behavior and value of the transaction) into a Trust Vector for processing by a Fraud Detection Service. The result will be used to make the Authorization decision, or it might initiate a continued collection of user claims for a retry.

Context

References