Fraud Fingerprinting

Fraud fingerprinting identifies the customer’s device when a conversation escalates to an agent. The SDK runs a Fingerprint identification on the device and sends the encrypted result to ASAPP, which uses it to assess fraud risk before routing the conversation. Fingerprinting is opt-in:

The SDK does not include the Fingerprint SDK. Apps that don’t enable fingerprinting don’t need any new dependency.
A scan runs only when your app enables it and ASAPP has enabled fraud detection for your company.
The SDK scans only when a conversation escalates to an agent, not when chat opens.
The SDK reuses a successful result for up to one hour. If a result from an earlier escalation is still valid when chat opens, the SDK also sends it to ASAPP at chat start. It doesn’t run a new scan then.

Before you begin

Fraud fingerprinting requires ASAPP Android SDK 11.5.0 or later. Contact your Implementation Manager at ASAPP to:

Enable fraud detection and fingerprinting for your company.
Allow your app’s package name, such as com.example.app. Identification requests from package names that aren’t allowed fail.

Enable fingerprinting

Add the Fingerprint Maven repository

Fingerprint publishes its Android SDK to its own Maven repository. Add it next to the ASAPP repository, wherever your project declares its repositories.

settings.gradle
build.gradle

Projects that declare repositories in dependencyResolutionManagement, the default for new Android Studio projects:

settings.gradle

dependencyResolutionManagement {
    repositories {
        maven {
            url "https://packages.asapp.com/chat/sdk/android"
        }
        maven {
            url "https://maven.fpregistry.io/releases"
            content {
                includeGroup "com.fingerprint.android"
            }
        }
    }
}

Projects that declare repositories in the top-level build.gradle:

build.gradle

allprojects {
    repositories {
        maven {
            url "https://packages.asapp.com/chat/sdk/android"
        }
        maven {
            url "https://maven.fpregistry.io/releases"
            content {
                includeGroup "com.fingerprint.android"
            }
        }
    }
}

Add the Fingerprint SDK dependency

Add the Fingerprint Android SDK to your app module’s dependencies, next to the ASAPP SDK:

app/build.gradle

dependencies {
    implementation 'com.asapp.chatsdk:chat-sdk:<version>'
    implementation 'com.fingerprint.android:sdk:4.2.0'
}

Use Fingerprint Android SDK 4.x. ASAPP can’t read results from other major versions.

Enable the scanner in your configuration

Set enableFingerprintScanner to true in the ASAPPConfig you pass to ASAPP.init:

import com.asapp.chatsdk.ASAPP
import com.asapp.chatsdk.ASAPPConfig

val asappConfig = ASAPPConfig(
    appId = "my-app-id",
    apiHostName = "my-hostname.test.asapp.com",
    clientSecret = "my-secret",
    enableFingerprintScanner = true
)
ASAPP.init(application = this, config = asappConfig)

Sync and rebuild your project. If the Fingerprint SDK dependency is missing, the SDK logs this error at initialization:

enableFingerprintScanner is set but the Fingerprint SDK is missing. Add com.fingerprint.android:sdk:4.2.0 to your app's dependencies.

You don’t need extra ProGuard or R8 rules. The ASAPP SDK and the Fingerprint SDK include their own consumer rules.

Declare data collection in Google Play

The Fingerprint SDK collects device identifiers. In your app’s Data safety form in the Google Play Console, declare that the app collects device or other IDs for fraud prevention. Refer to Fingerprint’s Android documentation for the full list of signals it collects. If your app enables fingerprinting, also update your app’s privacy policy to cover device identification for fraud prevention. Apps that don’t enable it don’t need these disclosures.

Network access

By default, the SDK sends identification requests to https://metrics.asapp.com and falls back to https://api.fpjs.io. If your app restricts network traffic, allow both hosts. ASAPP can change these endpoints for your company without an SDK update.

Troubleshooting

No fingerprint scan runs when a conversation escalates

Confirm that enableFingerprintScanner is true in the ASAPPConfig your app passes to the SDK.
Confirm that the Fingerprint SDK dependency is in your app, and look for the missing-dependency error in Logcat.
Ask your Implementation Manager to confirm that fraud detection and fingerprinting are enabled for your company.

Identification requests fail

Ask your Implementation Manager to confirm that your app’s package name is allowed.
Confirm that the app can reach the identification endpoints listed in Network access.

If a scan or its report fails, the conversation continues and routes normally without a fraud score. The SDK doesn’t show an error to the customer.

Digital Agent Desk

Insights Manager

Virtual Agent

Integrate Channels

AI Productivity

Fraud Fingerprinting

Before you begin

Enable fingerprinting

Declare data collection in Google Play

Network access

Troubleshooting

​Before you begin

​Enable fingerprinting

​Declare data collection in Google Play

​Network access

​Troubleshooting

Before you begin

Enable fingerprinting

Declare data collection in Google Play

Network access

Troubleshooting