FAQ & Troubleshooting

For debug

  1. Verify that the serviceId is correct; make sure it was generated for the test mode and not for release.
  2. 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.
  3. Verify that the device’s Samsung Account is registered (allowed) under TEST ACCOUNTS in the service details.

For release

  1. Verify that the serviceId is correct; make sure it was generated for release and not for the test mode.
  2. 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.
  3. Ask your Samsung Pay Relationship Manager (RM) to confirm that the status of your service is Approved.

One of the most common exceptions during development is that “getAllCard()” returns an empty list even though the card has already been added to the Samsung Wallet. The main reason for this exception is the mismatch of an issuer name with the Samsung Pay portal. The issuer name on the Samsung Pay Portal and the actual issuer name of the card must be the same to overcome this problem.

If you cannot confirm the actual issuer name of the card, just add the card to Samsung Wallet app and see its details information.

Open Wallet App > Tap on the card > Three-dot menu > Customer service option > Under the title you will find the issuer name.

The following screenshot would be helpful for better understanding,

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).

If your CSR was signed using your own private key rather than signed by a Payment Gateway, please select payment gateway with 'NONE (Default)'.

  • NOTE:

The default PG name is 'NONE (Default)'
default PG name is