Releases: maxmind/minfraud-api-dotnet
Releases · maxmind/minfraud-api-dotnet
5.3.1
5.3.0
- .NET 10.0 has been added as a target.
- The language version has been updated to C# 14.0.
- Added
Securepayto thePaymentProcessorenum. - Added
CreditApplication,FundTransfer, andSimSwapto theEventTypeenum. - Added the input
/event/party. This is the party submitting the
transaction. You may provide this using thePartyproperty on
MaxMind.MinFraud.Request.Event. - Added the input
/payment/method. This is the payment method associated
with the transaction. You may provide this using theMethodproperty on
MaxMind.MinFraud.Request.Payment. - Added support for new
/email/domainoutputs. These are available in
minFraud Insights and Factors responses:/email/domain/classification- The classification of the email domain.
Available via theClassificationproperty on
MaxMind.MinFraud.Response.EmailDomain. Possible values include
Business,Education,Government, andIspEmail./email/domain/risk- A risk score for the email domain, ranging from
0.01 to 99. Available via theRiskproperty on
MaxMind.MinFraud.Response.EmailDomain./email/domain/volume- The activity indicator for the email domain
across the minFraud network, expressed as sightings per million. Available
via theVolumeproperty onMaxMind.MinFraud.Response.EmailDomain./email/domain/visit/has_redirect- Whether the domain automatically
forwards visitors elsewhere. Available via theHasRedirectproperty on
MaxMind.MinFraud.Response.EmailDomainVisit./email/domain/visit/last_visited_on- The date when the domain was last
visited by MaxMind's automated inspection system. Available via the
LastVisitedOnproperty onMaxMind.MinFraud.Response.EmailDomainVisit./email/domain/visit/status- The status of the domain from automated
inspection. Available via theStatusproperty on
MaxMind.MinFraud.Response.EmailDomainVisit. Possible values include
Live,DnsError,NetworkError,HttpError,Parked, and
PreDevelopment.
5.2.0
5.1.0
- .NET 6.0 and .NET 7.0 have been removed as targets as they have both
reach their end of support from Microsoft. If you are using these versions,
the .NET Standard 2.1 target should continue working for you. - .NET 9.0 has been added as a target.
- The minFraud Factors subscores have been deprecated. They will be removed
in March 2025. Please see our release notes
for more information. - Added
Epaycoto thePaymentProcessorenum.
5.1.0-beta.1
- 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.
5.0.0
- Updated
TransactionReportto make theipAddressparameter optional. Now
thetagand at least one of the following parameters must be supplied:
ipAddress,maxmindId,minfraudID,transactionID. - Added
BillingPhoneandShippingPhoneproperties 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
Payconexto thePaymentProcessorenum. - Removed several obsolete constructors as well as the
Last4Digits
property onMaxMind.MinFraud.Request.CreditCard.
4.3.0
- Added
PxpFinancialandTrustpayto thePaymentProcessorenum. - Equivalent domain names are now normalized when
hashAddressis used.
For example,googlemail.comwill becomegmail.com. - Periods are now removed from
gmail.comemail address local parts when
hashAddressis used. For example,f.o.o@gmail.comwill become
foo@gmail.com. - Fastmail alias subdomain email addresses are now normalized when
hashAddressis used. For example,alias@user.fastmail.comwill
becomeuser@fastmail.com. - Additional
yahoo.comemail addresses now have aliases removed from
their local part whenhashAddressis used. For example,
foo-bar@yahoo.comwill becomefoo@yahoo.comfor additional
yahoo.comdomains. - Duplicate
.coms are now removed from email domain names when
hashAddressis used. For example,example.com.comwill become
example.com. - Certain TLD typos are now normalized when
hashAddressis used. For
example,example.comcomwill becomeexample.com. - Additional
gmail.comdomain names with leading digits are now
normalized whenhashAddressis used. For example,100gmail.comwill
becomegmail.com. - Additional
gmail.comtypos are now normalized whenhashAddressis
used. For example,gmali.comwill becomegmail.com. - When
hashAddressis used, all trailing periods are now removed from an
email address domain. Previously only a single period was removed. - When
hashAddressis used, the local part of an email address is now
normalized to NFC.
4.2.0
- .NET 5.0 has been removed as a target as it has reach its end of life.
However, if you are using .NET 5.0, the .NET Standard 2.1 target should
continue working for you. - .NET 7.0 and .NET 8.0 have been added as a target.
- Added
GooglePay,Placetopay, andShopifyPaymentsto the
PaymentProcessorenum. - Added
IWebServiceClientto facilitate mocking ofWebServiceClient.
Pull request by Ian Göbl. GitHub #152. - Updated
MaxMind.GeoIP2dependency to version that includes theIsAnycast
property onMaxMind.GeoIP2.Model.Traits. This istrueif the IP address
belongs to an anycast network.
This is available in minFraud Insights and Factors.
4.1.0
- Added the
Countryproperty toMaxMind.MinFraud.Response.CreditCard.
This is the country where the issuer of the card is located. This may be
passed instead ofIssuerIdNumberif you do not wish to pass partial
account numbers or if your payment processor does not provide them.
4.0.0
- This library no longer targets .NET 4.6.1.
- .NET 6.0 was added as a target.
- Removed deprecated code, include:
- The class
MaxMind.MinFraud.Response.GeoIP2Countrywas removed. This was
a subclass ofMaxMind.GeoIP2.Model.Countrythat added anIsHighRisk
property. This property was marked obsolete in 2019. Now
MaxMind.GeoIP2.Model.Countryis used directly. - In
MaxMind.MinFraud.Response.Subscores, the propertiesEmailTenure
andIPTenurewere removed. These were deprecated in the web service
and always return a fixed value.
- The class