"Device tamper detected" or "already enrolled"

Last updated: June 24, 2026

Quick answer

Usually caused by two Tap to Pay apps on one device or rapid re-enrollment.

  1. Uninstall other Tap to Pay apps and your app, clear Visa Tap to Ready cache/storage, reinstall one app, enroll, and test
  2. Keep Visa Tap to Ready updated
  3. Wait a few minutes between cycles

See Installing the Android SDK and Running Payments on Android.

Symptoms

  • Device tamper detected
  • already enrolled
  • Android enrollment conflict

Solution

This usually indicates two Tap to Pay apps on one device, or rapid unenroll/re-enroll cycles. To resolve:

  1. Uninstall all other Tap to Pay apps and the Koard-integrated app.

  2. Clear cache and storage for the Visa Tap to Ready app.

  3. Reinstall a single Tap to Pay app and enroll again.

  4. Wait a few minutes between enrollment cycles.

  5. Keep the Visa Tap to Ready app updated to the latest version.

Android Tap to Pay requires the Visa kernel app, which hosts the NFC kernel and runs in the background. This is a hard requirement for MPOC-certified app-to-app solutions.

Related articles

See also