Skip to main content
By following these steps, you’ll be prepared to provide the SHA-256 fingerprint of your app’s signing certificate and seamlessly integrate native-display checkout using our SDK.

​
Prerequisites

Keytool: A command-line tool for managing Keystores and certificates, usually included with the Java Development Kit (JDK). Ensure the JDK is installed on your machine.

​
Step 1: Generate a New Keystore

If you already have a Keystore for your application, you may skip this step.
  1. Open your terminal.
  2. Run the Keytool command:
keytool -genkey -v -keystore your_keystore_path -alias your_alias -keyalg RSA -keysize 2048 -validity 10000
  • your_keystore_path: The location where you want to save the keystore file (e.g., my-release-key.jks).
  • your_alias: The name you’ll use to refer to your key, typically your package name (e.g.,com.org.name).

​
Step 2: Complete the Keystore Prompts

After running the command, you’ll be prompted to enter the following information:
  1. Keystore Password: Choose a strong password to protect your keystore.
  2. Your Name: Enter your name (or your organization’s name).
  3. Organizational Unit: Optional; you can leave it blank.
  4. Organization Name: Enter your organization’s name.
  5. City or Locality: Enter the city where you are located.
  6. State or Province: Enter the state or province where you are located.
  7. Country Code: Enter the two-letter country code (e.g., US for the United States).
Confirm the details after entering them.

​
Step 3: Extract SHA-256 Fingerprint

Once your keystore is generated, you can extract the SHA-256 fingerprint by running this command: 
keytool -list -v -keystore your_keystore_path -alias your_alias
Replace your_keystore_path and your_alias with the values you used during keystore creation.

​
Step 4: Find the SHA-256 Fingerprint

In the command output, find the line starting with SHA256:. Your fingerprint will look like this:: 
SHA256: XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
Note: This is a public key and does not contain sensitive information about your game.

​
Step 5: Submit the Details

Provide both the package name and the SHA-256 fingerprint to the Appcharge team for integration.