Applies to: Point of Sale API - iOS | Point of Sale API - Android
Learn how to find the Android application certificate fingerprint to configure your Point of Sale API application in the Developer Console.
The certificate used to sign your Android application contains a SHA value known as a "fingerprint". You should use a debug fingerprint until you're ready to release your application to production. The SHA "fingerprint" shouldn't be confused with an Android device fingerprint sensor used to authenticate a user.
To use the Point of Sale API for Android, you must set the fingerprint of your mobile application in the Developer Console.
Find your debug fingerprint
Android SDK tools automatically generate a debug certificate and use the certificate to sign your Android package kit (APK) when you build your application locally for debugging and testing. The debug certificate includes your debug fingerprint (among other identifying information).
The certificate information is located in the debug.keystore file. You can find the keystore file with the other Android environment configuration files for your application. By default, configuration files live in the ~/.android directory of your development environment.
To find your debug fingerprint:
Use keytool to print information about your debug certificate.
keytool -list -v -keystore ~/.android/debug.keystore \
-alias androiddebugkey \
-storepass android \
-keypass android
Copy the SHA1 string from the output.
SHA1: LOOK_FOR_THIS_VALUE
The SHA1 string is your debug fingerprint.
Find your release fingerprint
Option 1: Copy it from the release certificate
To release an Android application (for example, to make it available on Google Play), you must generate a real certificate (.keystore) and use it to sign your APK. The release certification includes your release fingerprint (among other identifying information).
To find your release fingerprint:
Use keytool to print information about the .keystore file you created.
keytool -list -v -keystore PATH_TO_KEYSTORE -alias VALUE_OF_ALIAS
Copy the SHA1 string from the output:
SHA1: LOOK_FOR_THIS_VALUE
The SHA1 string is your release fingerprint.
Option 2: Copy it directly from a signed APK
If you don't have direct access to your .keystore file, you can copy the application fingerprint directly from the signed APK.
Use keytool to print information about the APK.
keytool -list -printcert -jarfile YOUR_APP.apk
Copy the SHA1 string from the output.
SHA1: LOOK_FOR_THIS_VALUE
The SHA1 string is your release fingerprint.