<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01044nam a22001337a 4500</leader>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Financial Action Task Force (FATF)</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Money Laundering Using New Payment Methods</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">France: </subfield>
    <subfield code="b">FATF,</subfield>
    <subfield code="c">2010. </subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">117p</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">In October 2006, the FATF published its first report on New Payment Methods (NPMs). The report was an initial look at the potential money laundering (ML) and terrorist financing (TF) implications of payment innovations that gave customers the opportunity to carry out payments directly through technical devices such as personal computers, mobile phones or data storage cards. The report concluded that it should be updated within a few years, or once there was greater clarity over the risks associated with these new payment tools. This report updates the 2006 report on NPMs and provides an overview of the most recent developments.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Money Laundering, Transcations</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">http://iffoadatabase.trustafrica.org/iff/money_laundering_using_new_payment_methods.pdf</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">CF</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">207</subfield>
    <subfield code="d">207</subfield>
  </datafield>
</record>
