Releases: maxmind/minfraud-api-php
Releases · maxmind/minfraud-api-php
1.1.0
1.0.0: First Production Release
v1.0.0 First production release
0.6.2
- Added the following new values to the payment processor validation:
concept_payments
,ecomm365
,orangepay
, andpacnet_services
. - Upgraded
maxmind/web-service-common
to 0.3.0. This version uses
composer/ca-bundle
rather than our own CA bundle.
0.6.1
0.6.0: Removed creditsRemaining. New outputs.
- BREAKING CHANGE:
creditsRemaining
has been removed from the web service
models and has been replaced byqueriesRemaining
. - Added
queriesRemaining
andfundsRemaining
. Note thatfundsRemaining
will not be returned by the web service until our new credit system is in
place. confidence
andlastSeen
were added to theDevice
response model.
0.5.0
- Added support for the minFraud Factors.
- Added IP address risk to the minFraud Score model.
- Implement
JsonSerializable
. - Added the following new values to the payment processor validation:
ccnow
,dalpay
,epay
(replacesepayeu
),payplus
,pinpayments
,
quickpay
, andverepay
.
0.4.0
0.4.0 (2016-01-20)
- PHP 7 support was added. PHP 5.3 support was dropped.
- Previously an array within an array would incorrectly validate when using
the->with*
methods. This now correctly throws a validation exception. - Added support for new minFraud Insights outputs. These are:
/credit_card/brand
/credit_card/type
/device/id
/email/is_free
/emai/is_high_risk
input
on theWarning
response model has been replaced with
inputPointer
. The latter is a JSON pointer to the input that caused the
warning.
0.3.0
0.2.2: Fix POST bug
* Updated `maxmind/web-service-common` to version that fixes POST bug.
0.2.1: PHP 5.3 and 5.4 fixes
- Updated
maxmind/web-service-common
to version with fixes for PHP 5.3 and
5.4.