{"title":"Manage your Android Mobile solution","category":"default","creationDate":1770713460,"content":"<p>There are certain tasks that need to be done when going live with an Android Mobile solution, such as registering your Mobile SDK-enabled app with Adyen. Then, when your solution is live and distributed to your users, you need to ensure that all required software updates are carried out. Otherwise there is a risk of temporarily not being able to continue transacting.<\/p>\n<h2 id=\"google-play\">Upload your app to Google Play<\/h2>\n<p><div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;success&quot;>\n        Applies to:\n    <\/tag>\n<\/div>\n Android Tap to Pay and Card reader.<br \/>\n<div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;error&quot;>\n        Does not apply to:\n    <\/tag>\n<\/div>\n Android Payments app.<\/p>\n<p>When going live with an Android Mobile SDK-enabled app, consider uploading your app to Google Play. Uploading to Google Play is optional, but it is a convenient way to distribute the app to your stores.<\/p>\n<p>For information and instructions, see the Android Studio documentation about <a href=\"https:\/\/developer.android.com\/studio\/publish\/app-signing\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">app signing<\/a>.<\/p>\n<p>Google will ask you to provide:<\/p>\n<ul>\n<li><strong>Information for <a href=\"#safety\">Google Play's Data safety section<\/a><\/strong>.<\/li>\n<li><strong><a href=\"#declaration\">Use of foreground service declaration<\/a><\/strong>.<\/li>\n<\/ul>\n<h3 id=\"safety\">Google Play's Data safety information<\/h3>\n<p>For the <a href=\"https:\/\/support.google.com\/googleplay\/android-developer\/answer\/10787469?hl=en#zippy=,optional-format-for-sdks,data-collection,data-sharing,data-types\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Google Play's Data safety section<\/a>, use the following details on what data the SDK accesses:<\/p>\n<ul>\n<li><strong>Name of SDK:<\/strong> Adyen IPPMOB Tap to Pay and NYC1 SDK<\/li>\n<li><strong>Security Practices:<\/strong>\n<ul>\n<li>Provide the link to the Adyen privacy policy: <a href=\"https:\/\/www.adyen.com\/privacy-policy\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">https:\/\/www.adyen.com\/privacy-policy<\/a><\/li>\n<li>All data is encrypted in transit.<\/li>\n<li>No data is shared with third parties.<\/li>\n<\/ul><\/li>\n<li>\n<p><strong>Data Types accessed or collected:<\/strong> see the following table.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: center;\">Data Types accessed or collected<\/th>\n<th style=\"text-align: center;\">Category<\/th>\n<th style=\"text-align: center;\">Purpose<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<th style=\"text-align: left;\">Sharing<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: center;\">Precise Location<\/td>\n<td style=\"text-align: center;\">Location<\/td>\n<td style=\"text-align: center;\">App functionality<\/td>\n<td style=\"text-align: left;\">On devices with Android OS 11 or earlier, the SDK accesses the precise location for Bluetooth discovery and connection.<\/td>\n<td style=\"text-align: left;\">This data is not shared or transferred to third parties.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: center;\">App info<\/td>\n<td style=\"text-align: center;\">App info and performance<\/td>\n<td style=\"text-align: center;\">App functionality<\/td>\n<td style=\"text-align: left;\">The SDK collects the following info: App version, Device OS version, Connected peripherals.<\/td>\n<td style=\"text-align: left;\">This data is not shared or transferred to third parties.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\n<\/ul>\n<h3 id=\"declaration\">Use of foreground service declaration<\/h3>\n<p>From Mobile SDK version 2.14.0 or later, you need to <a href=\"https:\/\/support.google.com\/googleplay\/android-developer\/answer\/13392821?hl=en&amp;sjid=3362498663504981577-EU\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">declare any foreground service types <\/a>that you use in a new declaration in Play Console under <strong>Monitor and improve<\/strong> &gt; <strong>App content<\/strong>. Use the following text:<\/p>\n<p><em>The Adyen In-Person Payments SDK uses a foreground service with the <code>dataSync<\/code> type to synchronize payment transactions with Adyen's backend while the user's application is in the foreground. Transaction synchronization is financially critical \u2014 incomplete syncs can result in accepted transactions that are never settled, causing direct losses for the merchant. WorkManager is avoided to prevent dependency and configuration conflicts with the host application, and <code>shortService<\/code> is unsuitable because the number of pending offline transactions and poor network conditions can require well over three minutes to complete a full sync.<\/em><\/p>\n<h2 id=\"register-app\">Register your app with Adyen<\/h2>\n<p><div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;success&quot;>\n        Applies to:\n    <\/tag>\n<\/div>\n Android Tap to Pay and Card reader.<br \/>\n<div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;error&quot;>\n        Does not apply to:\n    <\/tag>\n<\/div>\n Android Payments app.<\/p>\n<p>When going live with an Android Mobile SDK-enabled app that you built, you must register the app in your live Customer Area. To register, you upload the SHA-256 fingerprint of the app's signing certificate and the package name of the app. This is a security measure that enables Adyen to use the fingerprint of the app's signing certificate to detect if the integrity of the app has been compromised.<\/p>\n<p>We block all live transactions if:<\/p>\n<ul>\n<li>The app has not been registered yet.<\/li>\n<li>We detect that a registered app has been tampered with.<\/li>\n<\/ul>\n<p>It is possible to register multiple certificates that sign versions of the same app. For example, a developer-signed app version that developers use to test the live environment, and a Google Play-signed version.<\/p>\n<p>To register your Android app with Adyen:<\/p>\n<ol>\n<li>\n<p>If you uploaded your app to Google Play, get the SHA-256 fingerprint of the app's signing certificate as follows:<\/p>\n<ol>\n<li>In the <span translate=\"no\"><strong>Google Play Console<\/strong><\/span>, go to <span translate=\"no\"><strong>Setup<\/strong><\/span> &gt; <span translate=\"no\"><strong>App signing<\/strong><\/span> &gt; <span translate=\"no\"><strong>App signing key certificate<\/strong><\/span>.<\/li>\n<li>Copy the <span translate=\"no\"><strong>SHA-256 certificate fingerprint<\/strong><\/span>.<\/li>\n<\/ol>\n<\/li>\n<li>\n<p>If you did not upload your app to Google Play, use an OpenSSL command to get the SHA-256 fingerprint of your app's signing certificate:<\/p>\n<div data-component-wrapper=\"code-sample\">\n<code-sample :title=\"'.pem files'\" :id=\"''\" :code-data='[{\"language\":\"bash\",\"tabTitle\":\"\",\"content\":\"openssl x509 -in SIGNING_CERTIFICATE_OF_YOUR_APP.pem -noout -sha256 -fingerprint\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<p><\/p>\n<div data-component-wrapper=\"code-sample\">\n<code-sample :title=\"'.crt or .cer files'\" :id=\"''\" :code-data='[{\"language\":\"bash\",\"tabTitle\":\"\",\"content\":\"openssl x509 -inform der -in SIGNING_CERTIFICATE_OF_YOUR_APP -noout -sha256 -fingerprint\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<\/li>\n<li>\n<p>In your <a href=\"https:\/\/ca-live.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">live Customer Area<\/a>, go to <strong>In-person payments<\/strong> &gt; <strong>Tap to Pay &amp; card reader<\/strong>.<\/p>\n<\/li>\n<li>\n<p>In the <strong>Registered Android apps<\/strong> box, select <strong>Register app<\/strong>.<\/p>\n<\/li>\n<li>\n<p>In the dialog:<\/p>\n<ol>\n<li>Enter the <strong>Package name<\/strong> of your app.<\/li>\n<li>Paste the <strong>SHA-256 fingerprint<\/strong> of your app's signing certificate.<\/li>\n<li>Select <strong>Save<\/strong>.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<p>Your app is now added to the list of registered Mobile SDK-enabled Android apps.<\/p>\n<p>You can unregister your app by deleting the SHA-256 fingerprint of the app's signing certificate from the Customer Area. It can take up to ten minutes for this to take the effect. Be careful: transactions with the unregistered app will be blocked.<\/p>\n<div class=\"notices yellow\">\n<p>When you delete the SHA-256 fingerprint from the Customer Area, you can no longer transact with the app that is linked to the deleted fingerprint.<\/p>\n<\/div>\n<h2>Keep the Mobile SDK up to date<\/h2>\n<p><div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;success&quot;>\n        Applies to:\n    <\/tag>\n<\/div>\n Android Tap to Pay and Card reader.<br \/>\n<div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;error&quot;>\n        Does not apply to:\n    <\/tag>\n<\/div>\n Android Payments app.<\/p>\n<p>To make sure that you can continue making payments using your Mobile solution, you need to regularly update the Mobile SDK.<\/p>\n<p>As part of our security policy, each version of the Mobile SDK expires six months after the version was released. When a version of the Mobile SDK for Android has expired, you can no longer make  Tap to Pay transactions and  card reader PIN transactions with that version.  Only card reader transactions without PIN are possible. <\/p>\n<p>Make sure to <a href=\"#stay-informed\">stay informed about Mobile SDK version changes<\/a> and <a href=\"\/pt\/point-of-sale\/mobile-android\/build\/tap-to-pay\/\">add the new version to your project<\/a> .<\/p>\n<p>You can find the expiry date of a specific Mobile SDK for Android version in the <a href=\"\/pt\/point-of-sale\/firmware-release-notes\/\">release notes<\/a> of that version.<\/p>\n<h3>SDK support policy<\/h3>\n<p>The Mobile SDK follows semantic versioning MAJOR.MINOR.PATCH:<\/p>\n<ul>\n<li>MAJOR: a major version increment indicates incompatible changes.<\/li>\n<li>MINOR: a minor version increment indicates added functionality that is backwards compatible.<\/li>\n<li>PATCH: a patch version increment indicates backwards-compatible bug fixes.<\/li>\n<\/ul>\n<p>We do not support bug fixes to earlier MINOR or PATCH SDK versions. If you find bugs in an older MINOR or PATCH version, we recommend to update to the latest available SDK.<\/p>\n<p>You can find the expiry date of a specific Mobile SDK for Android in the following ways:<\/p>\n<ul>\n<li>In your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>, go to <strong>In-person payments<\/strong> &gt; <strong>Tap to Pay &amp; card reader<\/strong> and select the <strong>SDK &amp; OS versions<\/strong> tab.<\/li>\n<li>In your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>, go to <strong>In-person payments<\/strong> &gt; <strong>Payment devices<\/strong>, and select the <strong>Mobile devices<\/strong> tab.<\/li>\n<li>Check the <a href=\"\/pt\/point-of-sale\/firmware-release-notes\">release notes<\/a> of that version.<\/li>\n<\/ul>\n<div class=\"notices green\">\n<p>Only Mobile SDK for Android versions 1.0.0 or later are visible in the Customer Area. <\/p>\n<\/div>\n<h2>Keep the Android Payments app up to date<\/h2>\n<p><div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;success&quot;>\n        Applies to:\n    <\/tag>\n<\/div>\n Android Payments app.<br \/>\n<div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;error&quot;>\n        Does not apply to:\n    <\/tag>\n<\/div>\n Android Tap to Pay and Card reader.<\/p>\n<p>To make sure that you can continue making payments using your Mobile solution, you need to regularly update the Android Payments app.<\/p>\n<p>As part of our security policy, each version of the Android Payments app expires six months after the version was released. When a version of the Android Payments app has expired, you can no longer make  transactions with Tap to Pay on Android.   Only card reader transactions without PIN are possible. <\/p>\n<p>Make sure to <a href=\"#stay-informed\">stay informed about Android Payments app version changes<\/a> and we recommend enabling the automatic updates in your mobile device.<\/p>\n<p>You can find the expiry date of a specific Mobile SDK for Android version in the <a href=\"\/pt\/point-of-sale\/firmware-release-notes\/\">release notes<\/a> of that version.<\/p>\n<h3>SDK support policy<\/h3>\n<p>The Android Payments app follows semantic versioning MAJOR.MINOR.PATCH:<\/p>\n<ul>\n<li>MAJOR: a major version increment indicates incompatible changes.<\/li>\n<li>MINOR: a minor version increment indicates added functionality that is backwards compatible.<\/li>\n<li>PATCH: a patch version increment indicates backwards-compatible bug fixes.<\/li>\n<\/ul>\n<p>We do not support bug fixes to earlier MINOR or PATCH Android Payments app versions. If you find bugs in an older MINOR or PATCH version, we recommend to update to the latest available Android Payments app.<\/p>\n<h2 id=\"keep-os-updated\">Keep the device OS up to date<\/h2>\n<p><div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;success&quot;>\n        Applies to:\n    <\/tag>\n<\/div>\n All Android Mobile solutions.<\/p>\n<p>To make sure that you can continue making payments using your Mobile solution, you need to regularly update the Android version on your mobile device.<\/p>\n<p>If your mobile device is not running the minimum required Android version, all Mobile SDK transactions will be blocked. Make sure to check the  <a href=\"\/pt\/point-of-sale\/mobile-android\/requirements\/#software\">software requirements<\/a>  and subscribe to <a href=\"#stay-informed\">system messages<\/a> about required OS updates.<\/p>\n<p>You can enforce a minimum OS version by following the <a href=\"https:\/\/developer.android.com\/studio\/publish\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Android versioning guide<\/a>.<\/p>\n<p>You can find the OS version of your mobile devices in the following ways:<\/p>\n<ul>\n<li>In your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>, go to <strong>In-person payments<\/strong> &gt; <strong>Tap to Pay &amp; card reader<\/strong> and select the <strong>SDK &amp; OS versions<\/strong> tab.<\/li>\n<li>In your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>, go to <strong>In-person payments<\/strong> &gt; <strong>Payment devices<\/strong>, and select the <strong>Mobile devices<\/strong> tab.<\/li>\n<\/ul>\n<h2>Keep the card reader up to date<\/h2>\n<p><div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;success&quot;>\n        Applies to:\n    <\/tag>\n<\/div>\n Android Card reader.<br \/>\n<div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;error&quot;>\n        Does not apply to:\n    <\/tag>\n<\/div>\n Android Tap to Pay, Android Payments app.<\/p>\n<p>The firmware of the card reader must be updated from time to time, to keep the reader secure.<\/p>\n<div class=\"notices yellow\">\n<p>You must check for new firmware updates regularly, and update your card readers to the latest version.<\/p>\n<\/div>\n<p>The Mobile SDK provides <a href=\"\/pt\/point-of-sale\/mobile-android\/understand\/#updating-card-reader\">built-in screens<\/a>  to alert the user to firmware updates and to start the update. If you do not use the built-in UI, you must implement this functionality into your own custom UI.<\/p>\n<h2>Keep the dock up to date<\/h2>\n<p><div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;success&quot;>\n        Applies to:\n    <\/tag>\n<\/div>\n Android Card reader in combination with a dock.<br \/>\n<div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;error&quot;>\n        Does not apply to:\n    <\/tag>\n<\/div>\n Android Tap to Pay, Android Payments app.<\/p>\n<p>The firmware of the dock must be updated from time to time, to keep the dock secure.<\/p>\n<div class=\"notices yellow\">\n<p>You must check for new firmware updates regularly, and update your docks to the latest version.<\/p>\n<\/div>\n<p>The Mobile SDK provides <a href=\"\/pt\/point-of-sale\/mobile-android\/understand\/#updating-usb-dock\">built-in screens<\/a>  to alert the user to firmware updates and to start the update. If you do not use the built-in UI, you must implement this functionality into your own custom UI.<\/p>\n<h2 id=\"stay-informed\">Stay informed about version changes<\/h2>\n<p><div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;success&quot;>\n        Applies to:\n    <\/tag>\n<\/div>\n All Android Mobile solutions.<\/p>\n<p>To stay informed about version changes of the Mobile SDK for Android, the card reader, the Payments app,  or the minimum required device OS, you need to subscribe to system messages.<\/p>\n<ol>\n<li>In your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>, in the top navigation bar, select the <strong>Notification center icon<\/strong> <i class=\"adl-icon-alert\"><\/i>.<\/li>\n<li>Select <strong>Settings<\/strong>.<\/li>\n<li>Under <strong>Developers and Integrations<\/strong>, on the rows for <strong>Mobile SDK releases<\/strong> and <strong>Mandatory updates<\/strong> select how you want to be informed: by <strong>Email<\/strong> and\/or in the <strong>Notification center<\/strong>.<\/li>\n<\/ol>\n<p>Also keep an eye on the <a href=\"\/pt\/point-of-sale\/firmware-release-notes\/\">release notes<\/a> for the expiry date of a specific SDK version or Payments app version .<\/p>\n<h2>Change the language<\/h2>\n<p><div data-component-wrapper=\"tag\">\n    <tag :variant=&quot;success&quot;>\n        Applies to:\n    <\/tag>\n<\/div>\n  All Android Mobile solutions.<\/p>\n<div class=\"sc-notice info\"><div>\n<p><img src=\"\/user\/themes\/adyen\/images\/illustrations\/warning.svg\"> The Android Mobile SDK supports English, Dutch, Finnish, and French. More languages will be added in future releases.<\/p>\n<\/div><\/div>\n<p>English is the language that the SDK uses by default for the transaction flow and the UI for card reader operations. To switch to a different language, you have the following options:<\/p>\n<ul>\n<li>\n<p>In the system settings of the mobile device, select the other language as the highest priority language. This changes the system language of the device.<\/p>\n<\/li>\n<li>\n<p>If only your POS application should be shown in the other language, in the system settings go to the app language settings, select your POS app, and select the other language.<\/p>\n<\/li>\n<\/ul>\n<p>If you select a language that the SDK does not support, the SDK will use English.<\/p>\n<h3>Change the receipt language<\/h3>\n<p>The default language of the shopper receipt and the merchant receipt is English. To switch to a different supported language for either or both receipts, contact our <a href=\"https:\/\/ca-test.adyen.com\/ca\/ca\/contactUs\/support.shtml?form=other\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Support Team<\/a>.<\/p>\n<h2>See also<\/h2>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/point-of-sale\/mobile-android\/checklists#go-live-checklist\"\n                        target=\"_self\"\n                        >\n                    Go-live checklist\n                <\/a><\/li><li><a href=\"\/point-of-sale\/firmware-release-notes\"\n                        target=\"_self\"\n                        >\n                    Release notes\n                <\/a><\/li><li><a href=\"\/point-of-sale\/mobile-android\/understand#ui-for-card-reader-operations\"\n                        target=\"_self\"\n                        >\n                    UI for card reader operations\n                <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/point-of-sale\/mobile-android\/manage","articleFields":{"description":"Learn how to enable and maintain your solution and keep the software up-to-date.","parameters":{"generic_sdk_name":"Mobile SDK","specific_sdk_name":"Mobile SDK for Android","mobile_app_name":"Android Payments app","platform":"Android"},"type":"page","feedback_component":true,"filters_component":false,"page_id":"f336d250-3c1f-4fb2-8efa-a293a4688a38","decision_tree":"[]","last_edit_on":"17-03-2026 10:06"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/point-of-sale\/mobile-android\/manage","title":"Manage your Android Mobile solution","content":"There are certain tasks that need to be done when going live with an Android Mobile solution, such as registering your Mobile SDK-enabled app with Adyen. Then, when your solution is live and distributed to your users, you need to ensure that all required software updates are carried out. Otherwise there is a risk of temporarily not being able to continue transacting.\nUpload your app to Google Play\n\n    \n        Applies to:\n    \n\n Android Tap to Pay and Card reader.\n\n    \n        Does not apply to:\n    \n\n Android Payments app.\nWhen going live with an Android Mobile SDK-enabled app, consider uploading your app to Google Play. Uploading to Google Play is optional, but it is a convenient way to distribute the app to your stores.\nFor information and instructions, see the Android Studio documentation about app signing.\nGoogle will ask you to provide:\n\nInformation for Google Play's Data safety section.\nUse of foreground service declaration.\n\nGoogle Play's Data safety information\nFor the Google Play's Data safety section, use the following details on what data the SDK accesses:\n\nName of SDK: Adyen IPPMOB Tap to Pay and NYC1 SDK\nSecurity Practices:\n\nProvide the link to the Adyen privacy policy: https:\/\/www.adyen.com\/privacy-policy\nAll data is encrypted in transit.\nNo data is shared with third parties.\n\n\nData Types accessed or collected: see the following table.\n\n\n\nData Types accessed or collected\nCategory\nPurpose\nDescription\nSharing\n\n\n\n\nPrecise Location\nLocation\nApp functionality\nOn devices with Android OS 11 or earlier, the SDK accesses the precise location for Bluetooth discovery and connection.\nThis data is not shared or transferred to third parties.\n\n\nApp info\nApp info and performance\nApp functionality\nThe SDK collects the following info: App version, Device OS version, Connected peripherals.\nThis data is not shared or transferred to third parties.\n\n\n\n\n\nUse of foreground service declaration\nFrom Mobile SDK version 2.14.0 or later, you need to declare any foreground service types that you use in a new declaration in Play Console under Monitor and improve &gt; App content. Use the following text:\nThe Adyen In-Person Payments SDK uses a foreground service with the dataSync type to synchronize payment transactions with Adyen's backend while the user's application is in the foreground. Transaction synchronization is financially critical \u2014 incomplete syncs can result in accepted transactions that are never settled, causing direct losses for the merchant. WorkManager is avoided to prevent dependency and configuration conflicts with the host application, and shortService is unsuitable because the number of pending offline transactions and poor network conditions can require well over three minutes to complete a full sync.\nRegister your app with Adyen\n\n    \n        Applies to:\n    \n\n Android Tap to Pay and Card reader.\n\n    \n        Does not apply to:\n    \n\n Android Payments app.\nWhen going live with an Android Mobile SDK-enabled app that you built, you must register the app in your live Customer Area. To register, you upload the SHA-256 fingerprint of the app's signing certificate and the package name of the app. This is a security measure that enables Adyen to use the fingerprint of the app's signing certificate to detect if the integrity of the app has been compromised.\nWe block all live transactions if:\n\nThe app has not been registered yet.\nWe detect that a registered app has been tampered with.\n\nIt is possible to register multiple certificates that sign versions of the same app. For example, a developer-signed app version that developers use to test the live environment, and a Google Play-signed version.\nTo register your Android app with Adyen:\n\n\nIf you uploaded your app to Google Play, get the SHA-256 fingerprint of the app's signing certificate as follows:\n\nIn the Google Play Console, go to Setup &gt; App signing &gt; App signing key certificate.\nCopy the SHA-256 certificate fingerprint.\n\n\n\nIf you did not upload your app to Google Play, use an OpenSSL command to get the SHA-256 fingerprint of your app's signing certificate:\n\n\n\n\n\n\n\n\n\nIn your live Customer Area, go to In-person payments &gt; Tap to Pay &amp; card reader.\n\n\nIn the Registered Android apps box, select Register app.\n\n\nIn the dialog:\n\nEnter the Package name of your app.\nPaste the SHA-256 fingerprint of your app's signing certificate.\nSelect Save.\n\n\n\nYour app is now added to the list of registered Mobile SDK-enabled Android apps.\nYou can unregister your app by deleting the SHA-256 fingerprint of the app's signing certificate from the Customer Area. It can take up to ten minutes for this to take the effect. Be careful: transactions with the unregistered app will be blocked.\n\nWhen you delete the SHA-256 fingerprint from the Customer Area, you can no longer transact with the app that is linked to the deleted fingerprint.\n\nKeep the Mobile SDK up to date\n\n    \n        Applies to:\n    \n\n Android Tap to Pay and Card reader.\n\n    \n        Does not apply to:\n    \n\n Android Payments app.\nTo make sure that you can continue making payments using your Mobile solution, you need to regularly update the Mobile SDK.\nAs part of our security policy, each version of the Mobile SDK expires six months after the version was released. When a version of the Mobile SDK for Android has expired, you can no longer make  Tap to Pay transactions and  card reader PIN transactions with that version.  Only card reader transactions without PIN are possible. \nMake sure to stay informed about Mobile SDK version changes and add the new version to your project .\nYou can find the expiry date of a specific Mobile SDK for Android version in the release notes of that version.\nSDK support policy\nThe Mobile SDK follows semantic versioning MAJOR.MINOR.PATCH:\n\nMAJOR: a major version increment indicates incompatible changes.\nMINOR: a minor version increment indicates added functionality that is backwards compatible.\nPATCH: a patch version increment indicates backwards-compatible bug fixes.\n\nWe do not support bug fixes to earlier MINOR or PATCH SDK versions. If you find bugs in an older MINOR or PATCH version, we recommend to update to the latest available SDK.\nYou can find the expiry date of a specific Mobile SDK for Android in the following ways:\n\nIn your Customer Area, go to In-person payments &gt; Tap to Pay &amp; card reader and select the SDK &amp; OS versions tab.\nIn your Customer Area, go to In-person payments &gt; Payment devices, and select the Mobile devices tab.\nCheck the release notes of that version.\n\n\nOnly Mobile SDK for Android versions 1.0.0 or later are visible in the Customer Area. \n\nKeep the Android Payments app up to date\n\n    \n        Applies to:\n    \n\n Android Payments app.\n\n    \n        Does not apply to:\n    \n\n Android Tap to Pay and Card reader.\nTo make sure that you can continue making payments using your Mobile solution, you need to regularly update the Android Payments app.\nAs part of our security policy, each version of the Android Payments app expires six months after the version was released. When a version of the Android Payments app has expired, you can no longer make  transactions with Tap to Pay on Android.   Only card reader transactions without PIN are possible. \nMake sure to stay informed about Android Payments app version changes and we recommend enabling the automatic updates in your mobile device.\nYou can find the expiry date of a specific Mobile SDK for Android version in the release notes of that version.\nSDK support policy\nThe Android Payments app follows semantic versioning MAJOR.MINOR.PATCH:\n\nMAJOR: a major version increment indicates incompatible changes.\nMINOR: a minor version increment indicates added functionality that is backwards compatible.\nPATCH: a patch version increment indicates backwards-compatible bug fixes.\n\nWe do not support bug fixes to earlier MINOR or PATCH Android Payments app versions. If you find bugs in an older MINOR or PATCH version, we recommend to update to the latest available Android Payments app.\nKeep the device OS up to date\n\n    \n        Applies to:\n    \n\n All Android Mobile solutions.\nTo make sure that you can continue making payments using your Mobile solution, you need to regularly update the Android version on your mobile device.\nIf your mobile device is not running the minimum required Android version, all Mobile SDK transactions will be blocked. Make sure to check the  software requirements  and subscribe to system messages about required OS updates.\nYou can enforce a minimum OS version by following the Android versioning guide.\nYou can find the OS version of your mobile devices in the following ways:\n\nIn your Customer Area, go to In-person payments &gt; Tap to Pay &amp; card reader and select the SDK &amp; OS versions tab.\nIn your Customer Area, go to In-person payments &gt; Payment devices, and select the Mobile devices tab.\n\nKeep the card reader up to date\n\n    \n        Applies to:\n    \n\n Android Card reader.\n\n    \n        Does not apply to:\n    \n\n Android Tap to Pay, Android Payments app.\nThe firmware of the card reader must be updated from time to time, to keep the reader secure.\n\nYou must check for new firmware updates regularly, and update your card readers to the latest version.\n\nThe Mobile SDK provides built-in screens  to alert the user to firmware updates and to start the update. If you do not use the built-in UI, you must implement this functionality into your own custom UI.\nKeep the dock up to date\n\n    \n        Applies to:\n    \n\n Android Card reader in combination with a dock.\n\n    \n        Does not apply to:\n    \n\n Android Tap to Pay, Android Payments app.\nThe firmware of the dock must be updated from time to time, to keep the dock secure.\n\nYou must check for new firmware updates regularly, and update your docks to the latest version.\n\nThe Mobile SDK provides built-in screens  to alert the user to firmware updates and to start the update. If you do not use the built-in UI, you must implement this functionality into your own custom UI.\nStay informed about version changes\n\n    \n        Applies to:\n    \n\n All Android Mobile solutions.\nTo stay informed about version changes of the Mobile SDK for Android, the card reader, the Payments app,  or the minimum required device OS, you need to subscribe to system messages.\n\nIn your Customer Area, in the top navigation bar, select the Notification center icon .\nSelect Settings.\nUnder Developers and Integrations, on the rows for Mobile SDK releases and Mandatory updates select how you want to be informed: by Email and\/or in the Notification center.\n\nAlso keep an eye on the release notes for the expiry date of a specific SDK version or Payments app version .\nChange the language\n\n    \n        Applies to:\n    \n\n  All Android Mobile solutions.\n\n The Android Mobile SDK supports English, Dutch, Finnish, and French. More languages will be added in future releases.\n\nEnglish is the language that the SDK uses by default for the transaction flow and the UI for card reader operations. To switch to a different language, you have the following options:\n\n\nIn the system settings of the mobile device, select the other language as the highest priority language. This changes the system language of the device.\n\n\nIf only your POS application should be shown in the other language, in the system settings go to the app language settings, select your POS app, and select the other language.\n\n\nIf you select a language that the SDK does not support, the SDK will use English.\nChange the receipt language\nThe default language of the shopper receipt and the merchant receipt is English. To switch to a different supported language for either or both receipts, contact our Support Team.\nSee also\n\n\n                    Go-live checklist\n                \n                    Release notes\n                \n                    UI for card reader operations\n                \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Terminais","lvl2":"Android Mobile solutions","lvl3":"Manage your Android Mobile solution"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/point-of-sale","lvl2":"https:\/\/docs.adyen.com\/pt\/point-of-sale\/mobile-android","lvl3":"\/pt\/point-of-sale\/mobile-android\/manage"},"levels":4,"category":"In-person payments","category_color":"green","tags":["Manage","Android","Mobile","solution"]}}