1. If the Samsung Pay app throws ERROR_NOT_ALLOWED (-6) / ERROR_UNABLE_TO_VERIFY_CALLER (-359), what needs to be checked on the partner app side?
For debug
Verify that the serviceId is correct; make sure it was generated for the test mode and not for release.
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.
Verify that the device’s Samsung Account is registered (allowed) under TEST ACCOUNTS in the service details.
For release
Verify that the serviceId is correct; make sure it was generated for release and not for the test mode.
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.
Ask your Samsung Pay Relationship Manager (RM) to confirm that the status of your service is Approved.
2. I received an onSuccess() callback for a `getAllCards()` response but the card list is empty even though there already one or more installed cards in SamsungPay.
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
3. I have received an onFail() callback for `getSamsungPayStatus()` with a `SPAY_NOT_SUPPORTED` status code.
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).
4. I am getting 500 error when registering a CSR while creating the 'Web Payment' service. What should I do?
If your CSR was signed using your own private key rather than signed by a Payment Gateway, please select payment gateway with 'NONE (Default)'.
The default PG name is 'NONE (Default)'
5. I am getting ERROR_PARTNER_APP_SIGNATURE_MISMATCH error
This error occurs due to the following reasons:
The package name configured in the Samsung Pay Portal is not the same as the application
The signature of the APK that has been uploaded to the Samsung Pay Portal and the testing APK is not sameSamsung Pay Portal > My projects > App management > Click on a specific App name
6. I am getting ERROR_NOT_REGISTERED_USER_FOR_DEBUGGING error
This error occurs if the Samsung account has not been added to Samsung Pay Portal while the service status is Debugging . Log into the Samsung Pay Portal first. Then go to My projects > Service Management > Click on your service name > Add test accounts in the service details page.
7. I am getting ERROR_INADEQUATE_DATA_FROM_DB error
This error occurs due to the following reasons:
Payment Gateway (PG) CSR is required for merchant who is integrating with PG. If this CSR is missing, merchant app will face this error. You should ask your PG to provide PG CSR and upload it into the Samsung Pay Portal . Log into the Samsung Pay Portal first. Then go to My projects > Service Management > Click on your service name to upload your CSR .
This error occurs when the APK uploaded to Samsung Pay Portal has invalid information
app.package name : 50(byte)
app.version : 20(length)
app.signature : 100(length)
8. I am getting ERROR_NOT_SUPPORTED_COUNTRY_CODE error
This error happens if selected countries in Samsung Pay Portal doesn't match with partner's device country or device ISO.
Please add the device country on service detail by following the steps below:
Go to Samsung Pay Portal > login using the Manager account > My projects > Service management > Click on a specific service > Click on Edit info > Add country under Service Location
9. I am getting ERROR_SERVICE_NOT_EXIST error
No service is found under the provided ID, service has been deleted or an invalid service ID. Please check the service Id or create a new service to use it for your further testing.
To check the service Id,
Log into the Samsung Pay Portal first. Then go to My projects > Service Management > Click on your service name
To create new service, go through the Partner On Boarding guide.
10. I am getting ERROR_NOT_APPROVED_SERVICE error
The error arises when the service is not in the "Debugging " state for test environments or "Approved " or "Verifying " for release environments.
Please contact your RM to change the status of your service.
11. I am getting SPAY_NOT_SUPPORTED error
The error code SPAY_NOT_SUPPORTED typically indicates that the device either lacks compatibility to run Samsung Pay or the Samsung Pay app is not installed.
Make sure the Wallet app you're using is a valid one or you could reach our support for help.
12. I am getting ERROR_SPAY_APP_NEED_TO_UPDATE error
This error signifies that the Samsung Wallet app requires an update. In such cases, the partner app should prompt the user to update Samsung Wallet app. If the user agrees, the app should invoke the SamsungPay().goToUpdatePage() API to guide the user to the update page for Samsung Wallet app.
13. I am getting ERROR_PARTNER_SDK_VERSION_NOT_ALLOWED error
This error indicates that the partner app is utilizing a Samsung Pay SDK that is not permitted. Using a valid Samsung Pay SDK version should solve this issue. We recommend using the latest version of the SDK. Please check the latest version from here .
14. I am getting ERROR_SDK_NOT_SUPPORTED_FOR_THIS_REGION error
This error indicates that the Samsung Pay SDK is not supported in particular region. For example, if the device is from the country that Samsung Pay SDK is not supported, then the partner app verification will be failed.
Please contact with your RM to know supported region for specific version of the Samsung Pay SDK.
15. I am getting ERROR_NOT_ALLOWED error
This error indicates that requested operation is not allowed. For example, partner app verification has failed in Samsung Pay server.
Please create support ticket in Developer Support channel by attaching the dumpstate log.
16. I am getting ERROR_INVALID_PAYLOAD error
This error indicates that payload is not correct. Samsung Pay does not provide detailed payload information. Please generate the provisioning payload in accordance with your card network specifications.
17. I am getting ERROR_CARD_NOT_SUPPORTED error
This error occurs if the Samsung Wallet service is not enabled by the card issuer.
Please contact your card issuer to enable the digital wallet service for your card.
18. I am getting ERROR_INVALID_PARAMETER error
The error caused by wrongly created payload. Issuer need to create payload correctly based on Card Network's specification.
19. I am getting ERROR_CARD_ALREADY_REGISTERED error
This error indicates that the requested operation is already done and this operation cannot be performed again.
At first, delete the card from Samsung Wallet app and then try push provisioning again.
20. I am getting UNKNOWN_ERROR_CODE error. What should I do?
You can create a ticket via Samsung Developer Portal >Support > Dev Support with the following information for technical support regarding this Samsung Pay SDK implementation error:here .
21. How to get Samsung Wallet Test app?
Please follow the steps below to get the Samsung Wallet Test app:
Login into pay.samsung.com/developer using your Samsung Account
Go to Support > Request Test App
Copy the Galaxy App URL
Then click on My Projects > Service Management
Select specific service
Register your test Samsung Account in Test account field