Releases: maxmind/minfraud-api-java
Releases · maxmind/minfraud-api-java
1.18.0
- The following payment processors were added to the
Payment.Processorenum:CARDKNOXCREDITGUARDCREDORAXDATACAPDLOCALONPAYSAFECHARGE
- Documented the new
testdisposition action. - Added support for the
/disposition/rule_labeloutput in Score, Insights and
Factors. This is available atresponse.getDisposition().getRuleLabel(), and
is the label of the custom rule that was triggered by the transaction. - Added support for the
/credit_card/was_3d_secure_successfulinput in Score,
Insights and Factors. This input should indicate whether or not the outcome of
3D-Secure verification (e.g. Safekey, SecureCode, Verified by Visa) was
successful.trueif customer verification was successful, orfalseif the
customer failed verification. If 3-D Secure verification was not used, was
unavailable, or resulted in another outcome other than success or failure, do
not include this field. Use thewas3dSecureSuccessful(Boolean)method on
com.maxmind.minfraud.request.CreditCard.Builderto set it.
1.17.0
- The following payment processors were added to the
Payment.Processorenum:APPLE_PAYAPS_PAYMENTS
- Added additional normalizing of the email address if
hashAddressis
enabled. - Added support for the IP address risk reasons in the minFraud Insights and
Factors responses. This is available atresponse.getIpAddress().getRiskReasons().
It is a list ofIpRiskReasonobjects.
1.16.0
1.15.0
- The following payment processors were added to the
Payment.Processorenum:CASHFREEFIRST_ATLANTIC_COMMERCEKOMOJUPAYTMRAZORPAYSYSTEMPAY
- Added support for three new Factors outputs:
/subscores/device(the risk
associated with the device),/subscores/email_local_part(the risk
associated with the part of the email address before the @ symbol) and
/subscores/shipping_address(the risk associated with the shipping
address).
1.14.0
1.13.0
1.12.0
- Added support for the new email output
/email/domain/first_seenThis can
be accessed viaresponse.getEmail().getDomain().getFirstSeen(). - Added
Device.getLastSeenDateTime(),Device.getLocalDateTime(),
Email.getFirstSeenDate(), andGeoIp2Location.getLocalDateTime()methods
that returnjava.timeobjects rather than strings. - The request event time is now stored internally as a
ZonedDateTime. An
Event.Builder.time(ZonedDateTime)method was also added to the event
builder. - The following payment processors were added to the
Payment.Processorenum:CARDPAYEPX
1.11.0
1.10.0
- IMPORTANT: Java 8 is now required. If you need Java 7 support, please
continue using 1.9.0. - Added constructor to
com.maxmind.minfraud.request.Email.Builderthat
allows validation to be disabled. - The client-side validation for numeric custom inputs has been updated to
match the server-side validation. The valid range is -9,999,999,999,999
to 9,999,999,999,999. Previously, larger numbers were allowed. - Responses with chunked encoding are now handled correctly.
- The following payment processors were added to the
Payment.Processorenum:AFFIRMAFTERPAYCETELEMDATACASHDOTPAYECOMMPAYG2A_PAYGOCARDLESSINTERACKLARNAMERCANETPAYEEZYPAYLIKEPAYMENT_EXPRESSPAYSAFECARDSMARTDEBITSYNAPSEFIVEREPAY
- Deprecated
VERAPAYin thePayment.Processorenum. This was a misspelling
ofVEREPAY. - Deprecated
getEmailTenure()andgetIpTenure()methods of
com.maxmind.minfraud.response.Subscores. - Deprecated the
isHighRisk()method ofcom.maxmind.minfraud.response.GeoIP2Country.
1.9.0
- Renamed MaxMind user ID to account ID in the code and added support for the
newACCOUNT_ID_REQUIREDerror code. - The following payment processors were added to the
Payment.Processorenum:CCAVENUECT_PAYMENTSDALENYSONEYPOSCONNECT
- Added new type to the
Event.Typeenum:PAYOUT_CHANGE - Added support for new Device output:
/device/local_time
- Added support for new CreditCard output:
/credit_card/is_virtual