Proporcionar la configuración inicial

Use this checklist during project-based onboarding of Thales platform.

You exchange these parameters with the Thales delivery team during project kickoff.

Provide these parameters to Thales

Share the following parameters through the secure channel agreed for your project.

Provide a separate set for each environment (Sandbox environment and Production environment).

The merchant or PSP provides the following information:

Parameter	Description
Customer name	Name that will be configured in Thales platform. Refer to the customer's solution.
Server URL	The URL used for submitting the notifications from Thales backend to the customer's system.
TLS certificate	The TLS client self-signed certificate in PEM format, that will be added to Thales backend truststore.
JWE certificate	The self-signed certificate in PEM format, that Thales backend uses to encrypt the cardholder's sensitive data sent to the customer's system.
JWE certificate kid	The key identifier associated to the JWE certificate. This is set in the JWE header.
Scheme parameters	The supported schemes and associated parameters such as tokenRequestorId.

The merchant or PSP provides the following information only when Thales SDK is involved in the solution:

Parameter	Description
iOS Apple Team Identifier	It is a unique identifier assigned by Apple to a developer account or development team in the Apple Developer Program. It is used to associate apps, certificates, provisioning profiles, keychain access groups, and other app services with a specific development team. Example: ABCDE12345
iOS Bundle Identifier	It is a unique identifier for a specific application. It follows a reverse-domain-name format and uniquely identifies an app within the Apple ecosystem (App Store, provisioning profiles, push notifications, etc.). Example: com.company.myapp
Android Package Name	It is the unique identifier of an Android application. It follows a reverse-domain-name convention and uniquely distinguishes an app from all other apps on Android devices and in the Google Play Store. The package name is defined in the app's configuration and generally remains unchanged after the app is published. Example: com.company.myapp
Android App Signing Key	It is the cryptographic key used to digitally sign an Android application. It verifies the app's authenticity, ensures its integrity, and establishes trust between app updates and the original developer. The SHA-256 fingerprint of the app signing certificate used to digitally sign an Android application Example: 3A:7F:92:1C:8D:45:B1:2E:6F:9A:34:CD:EF:12:56:78:90:AB:CD:EF:12:34:56:78:9A:BC:DE:F0:12:34:56:78

Receive these parameters from Thales

Thales returns the configuration below for the same environment.

The following information is provided to the customer:

Parameter	Description
Server URL	Thales backend URL.
TLS certificate	The TLS client self-signed certificate in PEM format, that Thales backend uses to connect to the customer's system.
Customer API Key	The API key that the customer sets in the API calls to Thales backend.
Thales API Key	The API key that Thales backend uses when calling the customer's system.
JWE certificate	The self-signed certificate in PEM format, that the customer uses to encrypt the cardholder sensitive data towards Thales backend.
JWE certificate kid	The key identifier associated to the JWE certificate. It is set in the JWE header.
Merchant identifier	A technical identifier associated to each merchant.