Onboard 3DS web domains
D1 SDK 4.0.0 and earlier: domain onboarding is required only for the platform authenticator.
D1 SDK 4.1.0 and later: domain onboarding is also required for the biometric authenticator (app-domain binding).
Domain onboarding creates a secure association between a web domain and your issuer application.
This association prevents unauthorized issuer applications from using your 3DS configuration.
Share the web domain with the Thales delivery team during D1 onboarding.
Platform authenticator
Android
Host
assetlinks.jsonat:https://<your-domain>/.well-known/assetlinks.jsonDeclare your issuer application association:
package_name: your Android application ID (package name).sha256_cert_fingerprints: SHA-256 fingerprints of your signing certificate.
Generate the SHA-256 fingerprint using Java Keytool:
keytool -list -v -keystore my-release-key.keystoreYou can declare multiple fingerprints on the issuer application.
Example assetlinks.json:
Useful links:
iOS
Perform the following steps to onboard your domain:
Host
apple-app-site-associationat:https://<your-domain>/.well-known/apple-app-site-associationAdd the
webcredentialsservice:
The expected value is an
appIDin the<Application Identifier Prefix>.<Bundle Identifier>format.This file may contain information pertaining to other services as well.
Enable the Associated Domains entitlement in your issuer application:

Useful links:
Biometric authenticator
This mandatory feature applies to D1 SDK 4.1.0 and later.
To associate a website with your app, you have to host the associated domain file on your website at at https://<your-domain>/.well-known/idcloud-site-links.
Example idcloud-site-links
idcloud-site-linksThis file format is similar to assetlinks.json (Android) and apple-app-site-association (iOS) files defined by Google and Apple respectively.
Android:
package_namemust match yourapplicationIdinbuild.gradle.iOS: use the
appIDin<Application Identifier Prefix>.<Bundle Identifier>format.
Last updated
Was this helpful?