You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There has been some off and on discussion between our company and Sift in regards to the Device Fingerprinting API. As we heavily use the Sift PHP library, and have found the need to implement device fingerprinting into our answers to payment disputes, it would be convenient to be able to get access to the Device Fingerprinting API via this library.
Primarily, we would want to be able to query for the device's fingerprint with a session ID similar to the example shown in the JS example here, except with a method in the PHP library. This would enable us to catalog that fingerprint with the corresponding order so that if the payment for the order is disputed, we can send along that fingerprint as part of the Visa CE3.0 evidence package.
We have had conversation elsewhere about this becoming available (as well as comments here about it being possible), but we haven't adequately followed up on those conversations.
If this is a feature that could get added, we'd greatly appreciate it.
The text was updated successfully, but these errors were encountered:
There has been some off and on discussion between our company and Sift in regards to the Device Fingerprinting API. As we heavily use the Sift PHP library, and have found the need to implement device fingerprinting into our answers to payment disputes, it would be convenient to be able to get access to the Device Fingerprinting API via this library.
Primarily, we would want to be able to query for the device's fingerprint with a session ID similar to the example shown in the JS example here, except with a method in the PHP library. This would enable us to catalog that fingerprint with the corresponding order so that if the payment for the order is disputed, we can send along that fingerprint as part of the Visa CE3.0 evidence package.
We have had conversation elsewhere about this becoming available (as well as comments here about it being possible), but we haven't adequately followed up on those conversations.
If this is a feature that could get added, we'd greatly appreciate it.
The text was updated successfully, but these errors were encountered: