2. Onboarding

Provide onboarding data

Before you start integrating the NFC Wallet SDK, exchange a set of application identifiers, keys, and endpoints with the Thales delivery team.

Send required data to the Thales delivery team

Provide the following information for your digital wallet application.

Parameter	Format	Description
PreProd FCM service account	JSON file	Enables sending push notifications to your digital wallet application in the PreProd environment.
Production FCM service account	JSON file	Enables sending push notifications to your digital wallet application in the Production environment.
PreProd HMS Push Kit configuration	See below	Optional Enables sending push notifications to your digital wallet application running on Huawei devices in the PreProd environment.
Production HMS Push Kit configuration	See below	Optional Enables sending push notifications to your digital wallet application running on Huawei devices in the Production environment.
Application binding key	Hexadecimal string	Thales uses this key to bind wallet enrollment requests to your digital wallet application.

Get your application data

Get FCM service account

For details on an FCM service account, see the Firebase Console.

Then contact the Thales delivery team to complete the push notification setup.

FCM can deliver push notifications to the same digital wallet application from multiple senders.

Get HMS Push Kit configuration

For details on HMS Push Kit, see HMS Push Kit and HMS Authentication.

Then contact the Thales delivery team to complete the push notification setup.

The solution supports two authentication methods:

• OAuth 2.0 authentication
• API key authentication

Get application binding key

The application binding key is computed from the application signing certificate.

Thales uses this key to bind wallet enrollment requests to your digital wallet application.

Only registered digital wallet applications can enroll wallets. See Enroll wallet.

For details on how to compute the application binding key, see Compute the application binding key.

You can specify multiple values for different signing configurations used in your application's build and deployment process.

Signing key rotation / Multiple signers

NFC Wallet supports signing key rotation and mulipe signers

To avoid any issue:

• Provide oldest signing key
• Ensure that the oldest signing key is provided as the first signer.

In signing key rotation oldest signing key provided in the proof-of-rotation struct is used as the first signer.

Receive this from the Thales delivery team

Configure the following values in your digital wallet application and, if applicable, your backend.

Parameter	Description	Format
PreProd source IP addresses	IP addresses to allowlist in FCM so the Thales backend can send push notifications to the PreProd environment.	Comma-separated list of IPv4 or IPv6 addresses
Production source IP addresses	IP addresses to allowlist in FCM so the Thales backend can send push notifications to the Production environment.	Comma-separated list of IPv4 or IPv6 addresses
PreProd URLs	Endpoints to connect to the Thales backend in the PreProd environment.	String
Production URLs	Endpoints to connect to the Thales backend in the Production environment.	String
PreProd card information encryption key	Key to secure transmission of card information (PAN, CSC, and expiration date) in the PreProd environment.	Hexadecimal string or PEM certificate
Production card information encryption key	Key to secure transmission of card information (PAN, CSC, and expiration date) in the Production environment.	Hexadecimal string or PEM certificate