NoteIf you are going to use the Save to Pay or App-to-App ID&V integration option only, no service creation is required.
To integrate with Samsung Pay, you need a service that consists of the following:
Service type, selected when creating the service
Service ID, generated by Samsung for your created service
When communicating with Samsung Pay, your app passes the service details so that Samsung Pay can verify your partnership status.
The service is bound to your app, and only one app can be bound with each service ID. However, depending on your certificate signing request (CSR) or testing requirements, you can deploy a single app with multiple services. For example, the usual process is to first create a service in the Staging environment for your app for testing purposes, and when the app is ready for production, to create a separate service (with the same configuration) in the Production environment and release it for live use.
Examples of service-app combinations
App deployment scenario
Unique service-app combinations
Global app using a different CSR in different regions
Service 1 = (com.issuer.walletapp, CSR1_US) Service 2 = (com.issuer.walletapp, CSR2_PLCC_ABCMart)
Global app using a different CSR for different card services
Service 1 = (com.issuer.walletapp, CSR1_Regular) Service 2 = (com.issuer.walletapp, CSR2_PLCC_ABCMart)
A service in the portal has a specific status:
Debugging: When you create a service, this status is used while you test your app.
Requested: After you request a status change (like release approval) for the service, this status shows that Samsung Pay is checking and processing your request.
Blocked: If Samsung Pay cannot approve the status change for any reason, the service gets blocked and you need to modify your app and request approval again. In the meanwhile, the service cannot be used.
Approved: After Samsung approves the service for live production, this status is shown.
Rejected: If a problem is found with a service already in production, this status is shown while you fix the problem and re-release the app. In the meanwhile, the service can still be used.
In the All Services section of your dashboard, click CREATE NEW.
Select Push Provisioning and click NEXT.
Configure your service:
Enter the Service Name for your new service.
Enter all your Issuer Names one by one and click ADD after each name. The names correspond to your financial institution's name registered with the card networks.
NoteThe issuer name on the Samsung Pay Portal and the actual issuer name of the card must match. If you cannot confirm the actual issuer name of the card, add your card to the Samsung Wallet app and confirm the name within the card's customer service details.
Select your Service Location countries.
Select Staging or Production for the Environment to indicate whether the service is for testing or live use.
Confirm your agreement with the portal's terms and conditions by ticking the check box.
Click NEXT.
Bind an app to the service. Select an existing app from the app list, or turn on the Create New App toggle and enter the app details below the app list to create and bind a new app.
We use cookies to improve your experience on our website and to show you relevant
advertising. Manage you settings for our cookies below.
Essential Cookies
These cookies are essential as they enable you to move around the website. This
category cannot be disabled.
Company
Domain
Samsung Electronics
developer.samsung.com, .samsung.com
Analytical/Performance Cookies
These cookies collect information about how you use our website. for example which
pages you visit most often. All information these cookies collect is used to improve
how the website works.
Company
Domain
Samsung Electronics
.samsung.com
Functionality Cookies
These cookies allow our website to remember choices you make (such as your user name, language or the region your are in) and
tailor the website to provide enhanced features and content for you.
Company
Domain
Samsung Electronics
developer.samsung.com, google.account.samsung.com
Preferences Submitted
You have successfully updated your cookie preferences.