Releases: maxmind/minfraud-api-ruby
Releases · maxmind/minfraud-api-ruby
2.7.1
2.7.0
- The minFraud Factors subscores have been deprecated. They will be removed
in March 2025. Please see our release notes
for more information. - Ruby 3.0+ is now required. If you're using Ruby 2.7, please use version
2.7.0.beta1 or 2.6.0 of this gem. - Added the processor
:epayco
toMinfraud::Components::Payment
.
2.7.0.beta1
- 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.6.0
- Updated the validation for the Report Transactions API to make the
ip_address
parameter optional. Now thetag
and at least one of the
following parameters must be supplied:ip_address
,maxmind_id
,
minfraud_id
,transaction_id
. - Updated the validation for the Report Transactions API to check that
ip_address
,maxmind_id
, andminfraud_id
contain valid values. - Added
billing_phone
andshipping_phone
attributes to the minFraud
Insights and Factors response models. These contain objects with
information about the respective phone numbers. Please see our developer
site for
more information. - Added the processor
:payconex
toMinfraud::Components::Payment
.
2.5.0
- Equivalent domain names are now normalized when
hash_address
is used.
For example,googlemail.com
will becomegmail.com
. - Periods are now removed from
gmail.com
email address local parts when
hash_address
is used. For example,[email protected]
will become
[email protected]
. - Fastmail alias subdomain email addresses are now normalized when
hash_address
is used. For example,[email protected]
will
become[email protected]
. - Additional
yahoo.com
email addresses now have aliases removed from
their local part whenhash_address
is used. For example,
[email protected]
will become[email protected]
for additional
yahoo.com
domains. - Duplicate
.com
s are now removed from email domain names when
hash_address
is used. For example,example.com.com
will become
example.com
. - Certain TLD typos are now normalized when
hash_address
is used. For
example,example.comcom
will becomeexample.com
. - Additional
gmail.com
domain names with leading digits are now
normalized whenhash_address
is used. For example,100gmail.com
will
becomegmail.com
. - Additional
gmail.com
typos are now normalized whenhash_address
is
used. For example,gmali.com
will becomegmail.com
. - When
hash_address
is used, all trailing periods are now removed from an
email address domain. Previously only a single period was removed. - When
hash_address
is used, the local part of an email address is now
normalized to NFC.