Minfraud

Latest version: v2.11.0

Safety actively analyzes 687732 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 7

2.12.0b1

+++++++++++++++++++

* ``setuptools`` was incorrectly listed as a runtime dependency. This has
been removed.
* Added support for the new risk reasons outputs in minFraud Factors. The risk
reasons output codes and reasons are currently in beta and are subject to
change. We recommend that you use these beta outputs with caution and avoid
relying on them for critical applications.

2.11.0

+++++++++++++++++++

* Updated the validation for the Report Transactions API to make the
``ip_address`` parameter optional. Now the ``tag`` and at least one of the
following parameters must be supplied: ``ip_address``, ``maxmind_id``,
``minfraud_id``, ``transaction_id``.
* Added ``billing_phone`` and ``shipping_phone`` properties to the minFraud
Insights and Factors response models. These contain objects with information
about the respective phone numbers. Please see `our developer
site <https://dev.maxmind.com/minfraud/api-documentation/responses/>`_ for
more information.
* Added ``payconex`` to the ``/payment/processor`` validation.

2.10.0

+++++++++++++++++++

* Added the following new values to the ``/payment/processor`` validation:

* ``pxp_financial``
* ``trustpay``

* Equivalent domain names are now normalized when ``hash_email`` is used.
For example, ``googlemail.com`` will become ``gmail.com``.
* Periods are now removed from ``gmail.com`` email address local parts when
``hash_email`` is used. For example, ``f.o.ogmail.com`` will become
``foogmail.com``.
* Fastmail alias subdomain email addresses are now normalized when
``hash_email`` is used. For example, ``aliasuser.fastmail.com`` will
become ``userfastmail.com``.
* Additional ``yahoo.com`` email addresses now have aliases removed from
their local part when ``hash_email`` is used. For example,
``foo-baryahoo.com`` will become ``fooyahoo.com`` for additional
``yahoo.com`` domains.
* Duplicate ``.com`` s are now removed from email domain names when
``hash_email`` is used. For example, ``example.com.com`` will become
``example.com``.
* Certain TLD typos are now normalized when ``hash_email`` is used. For
example, ``example.comcom`` will become ``example.com``.
* Additional ``gmail.com`` domain names with leading digits are now
normalized when ``hash_email`` is used. For example, ``100gmail.com`` will
become ``gmail.com``.
* Additional ``gmail.com`` typos are now normalized when ``hash_email`` is
used. For example, ``gmali.com`` will become ``gmail.com``.
* When ``hash_email`` is used, the local part of an email address is now
normalized to NFC.

2.9.0

++++++++++++++++++

* IMPORTANT: Python 3.8 or greater is required. If you are using an older
version, please use an earlier release.
* Updated ``geoip2`` to version that includes the ``is_anycast`` attribute on
``geoip2.record.Traits``. This property is ``True`` if the IP address
belongs to an `anycast network <https://en.wikipedia.org/wiki/Anycast>`_.
This is available in minFraud Insights and Factors.

2.8.0

++++++++++++++++++

* IMPORTANT: Python 3.7 or greater is required. If you are using an older
version, please use an earlier release.
* Added the following new values to the ``/payment/processor`` validation:

* ``google_pay``
* ``placetopay``
* ``shopify_payments``

2.7.2

++++++++++++++++++

* Updated code to correctly handle ``None`` ``Content-Type`` from minFraud
web service. This should never happen, but if it does, the correct
exception will now be thrown.

Page 1 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.