The client side SDK and fingerprinting is a core component of a Castle integration that enhances Castle's ability to detect fraudulent and malicious abuse of in-application activity.
The main objective for the client-side integration is to generate a "request token", which is an opaque string that represents the current state of the device being used. This token should be included in the calls to Castle APIs
The client-side integration is required in order to use the Risk and Filter APIs
Note: The "request token" string is only valid for one minute, so it's important that a new one is generated when the user takes the action, rather than e.g. at page load.
Castle offers client-side SDKs for both web and native mobile apps. Pick the client-side Castle integration that you want to learn more about:
Updated 3 days ago