FAQ & Troubleshooting

For debug

  1. Verify that debug_mode is set as Y in your Android Manifest.
  2. Verify that your spay_debug_api_key is valid in Android Manifest. Go to the Samsung Pay Developers portal, sign in, and open your service details to check/retrieve the correct debug API key.
  3. Verify that your spay_debug_api_key has not expired.
  4. Verify that the serviceId is correct; make sure it was generated for the test mode and not for release.
  5. Verify that the serviceType is correct; make sure it is same as the value assigned by the Samsung Pay Developers portal when you create the service.
  6. Verify that the device’s Samsung Account is registered (allowed) under TEST ACCOUNTS in the service details.

For release

  1. Verify that debug_mode is set as N in your Android Manifest.
  2. Verify that spay_debug_api_key is not defined in your Android Manifest (it must be an empty string or "").
  3. Verify that the serviceId is correct; make sure it was generated for release and not for the test mode.
  4. Verify that the serviceType is correct; make sure it is same as the value assigned by the Samsung Pay Developers portal when you create the service.
  5. Ask your Samsung Pay Relationship Manager (RM) to confirm that the status of your service is Approved.

The most common reason for returning an empty card list is a mismatch between the issuer name registered on the Samsung Pay Developers portal and the actual issuer name for the card.
If you cannot confirm the actual issuer name of the card, just enroll the card with SamsungPay and see its detail information. Below is a sample screen shot of the test card, with the issuer name highlighted in yellow
Check Issuer Name

If your app’s target API level is set to 30 or higher, refer to Setting up your SDK development environmen part and follow guide for Android R OS(targetSdkVersion 30).