Minfraud

Latest version: v2.10.0

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

Scan your dependencies

Page 2 of 7

2.6.0

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

* Upgraded ``geoip2`` to 4.5.0. This adds mobile country code (MCC) and mobile
network code (MNC) to minFraud Insights and Factors responses. These are
available at ``response.ip_address.traits.mobile_country_code`` and
``response.ip_address.traits.mobile_network_code``. We expect this data to be
available by late January, 2022.
* Added the following new values to the ``/payment/processor`` validation:

* ``boacompra``
* ``boku``
* ``coregateway``
* ``fiserv``
* ``neopay``
* ``neosurf``
* ``openbucks``
* ``paysera``
* ``payvision``
* ``trustly``
* ``windcave``

* The ``/credit_card/last_4_digits`` input has been deprecated in favor of
``/credit_card/last_digits`` and will be removed in a future release.
``last_digits``/``last_4_digits`` also now supports two digit values in
addition to the previous four digit values.
* Eight digit ``/credit_card/issuer_id_number`` inputs are now supported in
addition to the previously accepted six digit ``issuer_id_number``. In most
cases, you should send the last four digits for ``last_digits``. If you send
an ``issuer_id_number`` that contains an eight digit IIN, and if the credit
card brand is not one of the following, you should send the last two digits
for ``last_digits``:

* ``Discover``
* ``JCB``
* ``Mastercard``
* ``UnionPay``
* ``Visa``

2.5.0

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

* Previously, the ``py.typed`` file was not being added to the source
distribution. It is now explicitly specified in the manifest.

2.4.0

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

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

* ``cardknox``
* ``creditguard``
* ``credorax``
* ``datacap``
* ``dlocal``
* ``onpay``
* ``safecharge``

* Added ``rule_label`` to minFraud output ``/disposition``.
* Added ``was_3d_secure_successful`` to ``/credit_card`` validation

2.3.1

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

* In 2.2.0 and 2.3.0, a ``KeyError`` would be thrown if the response from the
web service did not have the ``ip_address`` key but did contain the text
"ip_address" in the JSON body. Reported and fixed by Justas-iDenfy. GitHub
78.

2.3.0

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

* You may now set a proxy to use when making web service requests by passing
the ``proxy`` parameter to the ``AsyncClient`` or ``Client`` constructor.
* Added ``apple_pay`` and ``aps_payments`` to the ``/payment/processor``
validation.
* You may now enable client-side email hashing by setting the keyword argument
``hash_email`` to ``True`` in the web-service client request methods (i.e.,
``score``, ``insights``, ``factors``). When set, this normalizes the email
address and sends an MD5 hash of it to the web service rather than the
plain-text address. Note that the email domain will still be sent in plain
text.
* Added support for the IP address risk reasons in the minFraud Insights and
Factors responses. This is available at ``.ip_address.risk_reasons``. It is
an array of ``IPRiskReason`` objects.

2.2.0

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

* Added ``tsys`` to the ``/payment/processor`` validation.
* The device IP address is no longer a required input.

Page 2 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.