Releases: maxmind/minfraud-api-python
Releases · maxmind/minfraud-api-python
1.3.2
- Recent releases of
requests
(2.12.2 and 2.12.3) require that the
username for basic authentication be a string or bytes. The documentation
for this module uses an integer for theuser_id
, which will break with
theserequests
versions. Theuser_id
is now converted to bytes
before being passed torequests
. - Fixed test breakage on 3.6.
1.3.1
1.3.0
1.2.0
1.1.0: New Event Types
- Added the following new values to the
/event/type
validation:
email_change
andpassword_reset
.
1.0.0: First Production Release
- Added the following new values to the
/payment/processor
validation:
concept_payments
,ecomm365
,orangepay
, andpacnet_services
. ipaddress
is now used for IP validation on Python 2 instead ofipaddr
.
0.5.0
- BREAKING CHANGE:
credits_remaining
has been removed from the web service
response model and has been replaced byqueries_remaining
. - Added
queries_remaining
andfunds_remaining
. Note that
funds_remaining
will not be returned by the web service until our new
credit system is in place. confidence
andlast_seen
were added to theDevice
response
model.
0.4.0
- Added support for the minFraud Factors.
- Added IP address risk to the minFraud Score model.
- Added the following new values to the
/payment/processor
validation:
ccnow
,dalpay
,epay
(replacesepayeu
),payplus
,
pinpayments
,quickpay
, andverepay
. - A
PERMISSION_REQUIRED
error will now throw aPermissionRequiredError
exception.
0.3.0
- Added support for new minFraud Insights outputs. These are:
/credit_card/brand
/credit_card/type
/device/id
/email/is_free
/email/is_high_risk
input
on theWarning
response model has been replaced with
input_pointer
. The latter is a JSON pointer to the input that
caused the warning.