Filter

Push Notification 53
Sorry, no results
found for "Push Notification" on the website

tutorials

blog

Send Push Notifications to Samsung Wallet Users Using the Send Notification API

samsung wallet provides an e-wallet service to its customers through wallet cards, as well as offering features designed to enhance user engagement and drive business growth for partners. sending push notifications to users is such a feature. partners can send push notifications to users' wallet cards directly, using pre-approved message templates. these notifications can be used to send promotional messages or alert users about important updates. this article demonstrates a complete implementation of the send notification api. in the example scenario, we send a notification to a user's wallet card from a partner's server using this api. system requirements the notification api has the following prerequisites: complete the onboarding procedure to obtain the required security certificates if you are new to samsung wallet. now create your wallet card. follow the step 1 - create wallet card template section of the documentation. create your notification template and request for approval. follow the notification workflow overview to complete this step. remember to check the template to detect prohibited content. no additional approval is required if it passes. get permission from samsung to use the send notification api. reach out to samsung developer support for further support. api fundamentals as an authorized partner, you can send notifications to the users linked to your card, using the send notification api from your server. endpoint: the endpoint below processes the notification requests. url https://tsapi-card.walletsvc.samsung.com/{cc2}/wltex/cards/{cardid}/notifications/{templateid}/send headers: header information is required to ensure secure communication between the samsung server and the partner server. authorization: bearer token for authentication. refer to json web token documentation for specifications. x-smcs-partner-id: unique partner identifier required for api access. x-request-id: a unique uuid string that identifies each request. body: a payload including a parameter named ndata possessing a jwt token that contains the relevant data to identify the card user. see the official documentation for detailed api specifications. api implementation process the send notification api allows you to send personalized push notifications to users. download the sample source code and follow the step-by-step process below for a better understanding of the implementation of the api. step 1: managing cryptographic keys cryptographic keys are needed for authorization purposes. in this step, use the certificate you obtained during the onboarding process to extract the necessary keys. these keys are needed for jwt token generation. extracting the public keys extract the public keys from the partner.crt and samsung.crt certificate files. def getpublickey(crt_path): try: with open(crt_path, "rb") as f: crt_data = f.read() certificate = x509.load_pem_x509_certificate(crt_data, default_backend()) public_key = certificate.public_key() public_key_pem = public_key.public_bytes( encoding=serialization.encoding.pem, format=serialization.publicformat.subjectpublickeyinfo ) return public_key_pem except exception as error: print(f"error reading public key from {crt_path}: {error}") return none extracting the private key extract the private key from the .pem file generated during the onboarding process. def getprivatekey(pem_path): try: with open(pem_path, "rb") as data: private_key = serialization.load_pem_private_key( data.read(), password=none, backend=default_backend() ) return private_key except exception as error: print(f"error reading private key from {pem_path}: {error}") return none step 2: constructing the authorization token an authorization token is needed to validate the api request. construct an authorization header with auth as the payload content type and include the certificate and partner ids. retrieve these ids from my account > encryption management in the wallet partner portal, then build the payload and construct the authorization token. the following code snippet implements the actions described. def generateauthtoken(partnerid, certificateid, utctimestamp, privatekey, cardid, cc2, templateid): auth_header = { "cty": "auth", "ver": 3, "certificateid": certificateid, "partnerid": partnerid, "utc": utctimestamp, "alg": "rs256" } auth_payload = { "api": { "method": "post", "path": f"/wltex/cards/{cardid}/notifications/{templateid}/send" }, } auth_token = jwt.encode( payload=auth_payload, key=privatekey, algorithm='rs256', headers=auth_header ) return auth_token step 3: constructing the notification data token the request payload requires the ndata parameter, which is a jwt token that contains information about the notification data and the cards’ identifiers. follow these steps to construct the ndata token. defining the notification object the notification object is a json structured data object containing a list of reference ids and the data. the reference ids identify the specific cards to send the push notification to. you can use a list of reference ids to send the push notification to multiple recipients at a time. the data contains the name-value pairs used in the notification template. in our sample notification template, we used two name-value pairs (name and insert_end_date). notifcationobject = { "refids": [ "4afb049c-efef-43ca-8f03-1df55243477c" ], "data": { "name": "premium", "insert_end_date": "12/12/2026" } } constructing the notification data jwt token next, construct the jwt token for notification data (ndata). you can get more information about the jwt format in the "card data token" section of this documentation. def generatecdatatoken(partnerid, samsungpublickey, partnerprivatekey, certificateid, utctimestamp, data): jwe_header = { "alg": "rsa1_5", "enc": "a128gcm" } jwe_token = jwe.encrypt( data, samsungpublickey, encryption=jwe_header["enc"], algorithm=jwe_header["alg"] ) print(f"jwe_token: \n{jwe_token}\n") jws_header = { "alg": "rs256", "cty": "notification", "ver": 3, "certificateid": certificateid, "partnerid": partnerid, "utc": utctimestamp, } jws_token = jws.sign( jwe_token, key=partnerprivatekey, algorithm='rs256', headers=jws_header ) print(f"jws_token: \n{jws_token}\n") return jws_token step 4: building and executing the post request construct the http post request to send the push notification using the following code structure. # --- prepare json body (python dictionary) --- payload = { "ndata": ndata } # --- build http request --- headers = { "authorization": "bearer " + authtoken, "x-smcs-partner-id": partnerid, "x-request-id": requestid, "content-type": "application/json" } # --- execute http request --- try: response = requests.post(endpoint, json=payload, headers=headers) response.raise_for_status() print("wallet card template notificatiom: " + json.dumps(response.json())) except requests.exceptions.requestexception as e: print("failed to notify the wallet card user:") print(f"error: {e}") if response: print("response body:", response.text) running the sample application once the four steps described above are implemented, open the sample project and do the following: update the partner_id, certificate_id, card_id, and template_id values in src/main.py with your actual values. place your partner.crt, samsung.crt and private_key.pem files in the /cert directory. install all dependent libraries listed in the requirements.txt file. run the main script in the terminal. after the script is executed successfully, a push notification is sent to the user's wallet. conclusion now that you have implemented the send notification api sample application successfully, you can implement this api with your server to send customized push notifications. additional resources for more information on this topic, consult the following resources: complete source code official samsung wallet api documentation

M. A. Hasan Molla

https://developer.samsung.com/wallet/blog/en-us/2026/03/31/send-push-notifications-to-samsung-wallet-users-using-the-send-notification-api

tutorials web

blog

Redeeming Push Notifications

push notifications have a terrible reputation but if done well can give your users a positive experience. you know that thing where you go to a web site then, before you can do anything, you have to acknowledge the push notification request. do you hate that? yeah, me too. jo franchetti even wrote an entire article about the crisis of websites bombarding people with permission requests and dialogs when they first arrive on the page. a crisis of permissions that’s just one of the many ways it’s easy to upset your users with push notifications, this article will try to detail some ways to do them better. a bad example of requesting for push notifications on first load failing before you even begin push notifications on the web are one of the most maligned apis on the web and this is one of the reasons why. it’s possible to give a bad impression before you even send a single notification. just like you wouldn’t ask to move in with someone on the first date, do not ask to send notifications on the very first user engagement. assume your users do not want push notifications. prove the worth of your web app with it’s high quality information and delightful user experience. make the users want push notification before you prompt them, the best way to do this is to have a checkbox to enable push notifications in context. this makes it clear not only what the push notification request is for but how they can turn them off when they do not want them. in this example app users can turn on notifications for particular information channels with the “notify me on updates” checkbox: if they check the checkbox then we will call pushmanager.subscribe() which will prompt the user to enable notifications. the users are more likely to enable push notifications because they chose to be prompted through their own intuition. on a related note app install banners: in some browsers, app install banners, pop up in a similar way to poorly done notification requests. it is not in response to a user action and are unrelated to your app’s content and not part of your apps user interface. it is possible to integrate this into your app interface, letting you hide this banner and letting you provide your own install button. do this in the beforeinstallprompt event: window.addeventlistener('beforeinstallprompt', handleinstallprompt); you can use this event to integrate an app install button into your app. if you get this event then you can show the button which allows the content to be installed. in the below image i put a subtle bubble at the bottom of the homepage for installing it. it’s easy to find and access but won’t intrude on the user’s app experience. the user pays the cost of notification, don’t be expensive. the user doesn’t pay a cost in money but they do in attention. each notification is a weight upon the user’s mind. a notification to a user when their attention is at their limit could be the motivation the user needs to block all notifications from the entire web browser. each notification should bring joy to the user. how do you bring joy? be timely if you could’ve given this information earlier or could show it later why bother interrupting the user right now. bad notification: ‘did you know you can send money with our app’ good notification: ‘alice has sent you $20’ be efficient opening an app or web page is comparatively slow, it can take a few seconds which is a long time to someone who is busy cooking dinner or watching netflix or at work. if you can put all the information in the notification without them opening the app then do that. if all the response you need is a simple option-a/option-b question such as yes/no then add those buttons. when the user presses the button update the notification to acknowledge the button press but don’t open the app. eve has requested $15 [send now] [decline] be clear there are many options to change the appearance of the notification use as many as possible to make it clear where the app is from, what it’s about and what action is expected from the user. use the badge and icon for your app icon. use the title to give a summary of what action the user needs to take, use the body and image to give relevant information and context. the next section describes how to customise your notificaition. do not waste the user’s time don’t push ads, don’t use them to beg users to return, don’t push boring notifications to remind the user your web app exists. i know it’s tempting and you have quotas to meet but it will only have an adverse effect on how the user views your app and notifications as a whole. the user probably does not love your app as much as you do and will be a lot less forgiving. fully customising push notifications here is an example notification where as much as possible has been configured: { body: "awkward zombie - disagree to agree", icon: "/icons/appicon.png", image: "https://example.com/previewimage.jpg", badge: "data:image/png;base64,ivborw0kggoaaa...", vibrate: [100, 50, 100], data: data, tag: data.url, actions: [ { action: "read now", title: "open" }, { action: "close", title: "close" }, ], }; self.registration.shownotification(title, options); if assets take too long to load they get ignored. the most important icon is the badge icon since it’s the one which gets put into the status. it’s also very small so is ideal to be url encoded and is kept in a constant in the service worker file, to ensure it is loaded reliably. for the icon we use the app icon so it’s extra clear where the notification is from. this is a locally loaded png to be sure it loads quickly. the image is loaded from the third party site the being loaded from the rss feed we don’t need to have it store local it’s okay for these to be from somewhere else. it adds good context but it isn’t essential so if it does not load in time then it’s not an absolute problem. these examples of action buttons i’ve done here are probably not totally necessary since notifications can be closed by some other means and we can just listen for notification clicks. better examples would be something like “open” and “remind me later”, defaulting to “open” if neither button is clicked. detailing the different parts of the notification combining notifications you can’t guarantee a user will check their device in between notifications. new notifications by default do not replace the the old ones so this can result in an overwhelming flood of notifications if they arrive in short succession. if you set the tag property then notifications which share the same tag can overwrite each other. in this example the tag is set to the rss feed’s url, so that notifications from the same rss feed overwrite each other. this is better since we don’t get flooded but now if a second notification comes through we lose the first one. it’s probably a good idea to check to see if you are replacing a notification and if you are concatenate them together. const existingnotifications = await self.registration.getnotifications({ tag: data.url, }); if (existingnotifications.length) { const oldnotification = existingnotifications[0]; options.body = oldnotification.body + '\n' + options.body; } there is a limited amount of text that can be fit into a notification body. an alternative solution would be to replace the notification with one that just says ‘you have n notificaitons’ then when the user taps on it open your web app’s notification interface. updating notifications this can also be a good way to update the user in notification only interfaces. once they have click on the notification to perform an action make, the request to the server to perform that action. once the request completes then show a new notification acknowledging it’s completion. self.addeventlistener("notificationclick", async function (e) { const notification = e.notification; const action = e.action; if (action === "close") { notification.close(); } if (action === "respond") { // close the old notification notification.close(); const response = await fetch('/api/respond.json') .then(r => r.json()); // let the user know if it succeeded or not if (response.ok) { self.registration.shownotification("success", options); } else { self.registration.shownotification(response.error, options); } } }); by having the user interact only through push notifications the user can complete their task and have a positive interaction with your app without needing to dedicate much mental energy to it giving a positive experience. together we can use push notifications to enrich people’s lives and make users have a positive association to push notifications.

Ada Rose Cannon

https://developer.samsung.com/internet/blog/en-us/2020/09/30/redeeming-push-notifications

Develop Samsung Wallet

doc

Online Test Tool

online test tool overview the "add to wallet" test tool is a mobile tool to test samsung wallet features by using a valid partner's private key add to wallet feature for testing adding a wallet card into your samsung wallet application, such as a boarding pass, ticket, coupon etc push notification feature for testing push notification scenarios for the samsung wallet application partners can access the test site using the address below server url prod https //partner walletsvc samsung com/addtowallettest step 1 sign in partners can sign in to samsung account via mobile click the sign in button to sign in to your samsung account step 2 add to samsung wallet" test partners can test their wallet cards by entering the information for each area, as shown below step 3 input partner's private key input the private key of a valid partner you want to test the private key can only be imported based on pkcs8 / algorithm rs256 step 4 select partner’s wallet card choose a partner card from the list to test it step 5 test for add to wallet complete entering the card data and click "add to samsung wallet" button each type of wallet card details is described in the wallet cards section step 6 test for push notification enter data referring to the wlt server specifications and click the request push notification button if it is called normally, the web view of the app appears as shown below, and the response called with the corresponding api is displayed in the web view

https://developer.samsung.com/wallet/codelabandtesttools/onlinetesttool.html

Develop Samsung Wallet

doc

Statistics

statistics performance monitoring the samsung wallet service is monitored to get an effective measure of the wallet performance overview wallet card total number of wallet cards registered in the portal wallet card type total number of wallet card types registered in the portal wallet card template total number of templates registered in the portal recent trends provides key indicators and trend charts for the selected period provides the ability to change the period and wallet card type being reviewed item description registered registration by wallet card category impressions count when the coupon or banner is displayed on each screen page click count of click on a specific link to the number of total users who view a coupon or banner click through rate percentage of clicks against impressions in the coupon or banner [ctr % = clicks/impressions] stats of wallet cards provides detailed statistical information for the selected wallet card provides the ability to change the period, template, and wallet card type checks detailed information and charts for each indicator item description registered registration by wallet card category number of registrations by wallet card category and registrations by template number of registrations by template , registered number of registrations for the specified wallet card category/template , registration by partner number of registrations by partner active device number of device registering cards in the wallet max number of unique device ids dmid the max number means the maximum value during the statistical period - the hourly graph shows the maximum time's value - the daily graph shows the maximum date's value top 10 of all templates statistics on top 10 templates based on number of registrations or clicks & ctr add to wallet - impressions number of impressions counts for 'add to wallet' button add to wallet - clicks number of clicks for 'add to wallet' button add to wallet –click through rate ratio of clicks against impressions for 'add to wallet' button [ctr % = clicks/impressions] wallet cards - impressions number of exposures of registered content wallet cards – clicks number of clicks on registered content wallet cards – click through rate click through rate of registered content age & gender age & gender statistics for impression/click/ctr data by wallet card / wallet category registered by end user push notification – impressions number of exposures of push notification content push notification – clicks number of clicks of push notification content

https://developer.samsung.com/wallet/overview/statistics.html

Distribute Galaxy Store

doc

User Attribution

user attribution user acquisition is the process required to attract, gain, and retain customers user attribution is a way to identify how a user finds your app's detail page in galaxy store that is, did the user and potential customer find your app from a link in a banner in galaxy store, as a result of a keyword search in galaxy store, or from a galaxy store badge link in a social media post? galaxy store statistics provides user acquisition reports that measure user attribution and breaks down the numbers by channel, source, keywords, and featuring galaxy store banner or icon notestatistics listed here are not available in all countries the following is the hierarchy and descriptions of the categories you may find in the user acquisition reports in the descriptions, organic users are users who are directed to your app's detail page from an item within galaxy store or galaxy themes such as a banner, icon, widget, or search result non-organic users are users who are directed to your app's detail page from an item outside of galaxy store or galaxy themes any user is any organic or non-organic user category description all channels any user who has accessed your app's detail page this is the total number of users who have visited you app’s detail page direct any user who does not fit into any category excluding all channels but whose source can be identified explore organic users who do not fit into any organic category these are users who are browsing galaxy store and viewing apps that are interesting to them featured banner organic users who click on a banner from one of the main pages in galaxy store featured icon organic users who click on an icon from one of the main pages in galaxy store galaxy store badge non-organic users who click a special short link that was generated from the samsung developer dashboard or in seller portal see galaxy store badge promotion for more information about galaxy store badges if a badge click comes from a category already tracked in gss for example, from a twitter post , the click is counted once and attributed to the galaxy store badge category only the badge must be linked to the product detail page of an android app or galaxy watch app gss does not track badges for theme product detail pages nor theme/galaxy watch seller brand pages galaxy store all organic users these users find your app from a link within galaxy store hun heads-up notification non-organic users who respond to a push notification generated by the galaxy store platform used exclusively by galaxy store see push notification for notifications generated by the samsung messaging platform native apps non-organic users whose source is another samsung product for example, bixby, gear manager [galaxy wearables], or s finder or from a samsung domain for example, com sec * or com samsung * others any user who does not fit into any category excluding all channels and whose source cannot be identified promotion organic users who visit a galaxy store promotion page and either download your app or go to your app's detail page galaxy store promotion pages are accessed by clicking the gift icon in the top right corner of any main section featured, exclusives, themes, or watch in galaxy store push notification non-organic users who respond to a push notification generated by the samsung messaging platform used by galaxy store and other samsung teams see hun for notifications generated by the galaxy store platform referral non-organic users who directly access your app's detail page and whose source cannot be identified samsung any user who finds your app's detail page from a samsung-generated source this includes organic, native apps, hun, push notification, social, galaxy store badge, and referral users search organic users who use the galaxy store search page to find your app's detail page social non-organic users who follow a link from a social networking platform such as twitter, instagram, line, or facebook if a click from a social networking platform comes from a galaxy store badge, the click is counted once and attributed to the galaxy store badge category only

https://developer.samsung.com/galaxy-store/galaxy-store-statistics/user-attribution.html

Develop Mobile Samsung Automation

doc

Service on Cloud

service on cloud samsung automation studio is provided as a subscription service through the cloud a beta program is currently in progress if you have a samsung account, you can use cloud runtime for up to 1 year according to the terms and conditions samsung automation consists of the following editor the editor distributed in k8s is developed as a web app flow based programming is possible through a web browser however, if you have not subscribed to the samsung automation service, you need to migrate flow to your own runtime to deploy and run flow sign up through your samsung account flows you create are securely stored in the cloud and it runs through the cloud runtime with one click for you to deploy also, you can improve your flow by checking the execution data of the created flow through the debug messages sent by the executed app samsung automation studio capsule the automation studio capsule, distributed in the bixby marketplace, allows you to call apps running in automation studio via bixby voice please check the following page for more details progressive web app you can use a pwa to send push notifications to your device in your flow after installing the pwa and accepting notifications, you can use notification node to send push notifications to registered devices please check the following page for more details backend provides restful api based on microservice architecture deployed in cloud native to support subscription users if you directly install and use samsung automation studio's public node, you cannot directly link backend as a result, you are limited in some managed features we recommend that you subscribe to automation studio's cloud service for full access to additional convenience features runtime built on node-red's runtime, automation studio's runtime runs in an isolated container per user through cloud foundry the small quata runtime we provide for free is managed so that you can experience flows-based programming and deploy and run multiple automations without problems get started - samsung automation studio beta

https://developer.samsung.com/automation/v2-service-on-cloud.html

Develop Samsung Wallet

doc

Notification for Partners

notification for partners deliver personalized push messages to samsung wallet users, linked to their wallet cards samsung wallet enables authorized partners to send targeted push notifications using pre-approved message templates this feature supports marketing, transactional, and engagement-driven use cases only partners with administrative approval can access and use the notifications feature the notifications tab is hidden for unauthorized accounts notification workflow overview step 1 create notification template partners can create push message templates through the partner portal or notification api templates define the structure and content of the notification type only merchant push is supported message category choose from marketing or other variables use dynamic placeholders with {{ }} syntax e g , hello {{name}}, your pass for {{event}} is ready if your wallet card supports multiple languages, a message template must be provided for each language variant after drafting the message run harmfulness check to detect prohibited content results pass or fail even if failed, templates can still be submitted but may be rejected in the next step step 2 request template approval once the template is complete click the request approval button in the portal an administrator will review the content if rejected the reason is provided via system email partners can revise and resubmit the template for approval if approved the approved date will appear in the portal the template becomes eligible for use in the notification api step 3 push notification with template once a template is approved, partners can push notifications to users linked to their wallet cards using a secure post api request required parameters template id – issued after template approval reference id – a unique identifier tied to the user’s wallet card created during the add to wallet process only pre-approved templates can be used in push requests step 4 monitor impressions and clicks after the push is delivered, partners can track impressions – number of users who viewed the notification clicks – number of interactions with the push these metrics can be accessed through the partner portal dashboard, enabling performance evaluation of each campaign send notification this api sends notifications to end users who have added the wallet card [request] type value description method post url /{cc2}/wltex/cards/{card id}/notifications/{template id}/send header authorizationstring 1024 required credential token the token can have prefix "bearer" as an authorization type e g , bearer <credentials> * refer to authorization token for more details x-smcs-partner-idstring 32 required partner id x-request-idstring 32 required request identifier randomly generated uuid string path parameters cc2string 2 required country code cc2 from send card state card idstring 32 required wallet card identifier granted from partners portal template idstring 32 required approved notification template identifier from partners portal payload ndatastring required notification object json * this field needs to be encrypted * refer to security for more details * the value of "cty" must be set to "notification" notification object refidsarray of string 100 required unique content identifier defined by the content provider data object required name-value pair for use in notification template [example] post /wltex/cards/12584806754/notifications/12353465344/send /*[headers]*/ authorization bearer eyjjdhkioijbvvriiiwidmvyijoxlcjwyxj0bmvyswqioiixmjg1o x-smcs-partner-id partner-id-0001 x-request-id req-202303140003 /*[payload]*/ { “ndata” “eyjjdhkioijbvvriiiwidmvyi…” } /*[notification object]*/ { "refids" [ "ref-20230304-0003", "ref-20230304-0004" ], "data" { "name" "logan", "place" "samsung wallet" } } [response] type value description http status 200 ok payload n/a [result] http status code description 200 ok success 400 bad request requests requests cannot or will not be processed the request due to something that is perceived to be a client error 401 unauthorized authorization token is invalid or expired 500 internal server error the server encountered an unexpected condition that prevented it from fulfilling the request adding notification templates in general, card notification creation is possible through the ‘wallet partners portal' however, a server api is provided for cases where it is necessary to create a large number of card notifications card notifications created through api can also be checked and managed in the same way on the ‘wallet partners portal' [request] type value description method post url /partner/v1/card/template/{card id}/notification header authorizationstring 1024 required credential token the token can have prefix "bearer" as an authorization type i e , bearer <credentials>* see json web token x-smcs-partner-idstring 32 required partner id x-request-idstring 32 required request identifier random generated uuid string path parameters card idstring 32 required the wallet card identifier granted through the partner portal * the identifier is needed when updating a specific card template body parameters ntemplateobject required actual payload data in basic json format to establish the communication between partners and samsung wallet this must be in the secure jwt json web token format * see the chapter security for more details payload object typestring 20 required notification type m merchant push, g geo push messagetypestring 20 required purpose of notification s service, m marketing messagedetails[]array of object required container of notification message messagedetails[] languagecodestring 20 required default notification language code,e g en, ko messagedetails[] messagestring 500 required notification message forcesaveynstring 10 optional sets whether to save when harmfulness is detected this must be set to either 'y' or 'n' * default 'n' [example notification template object ] { "type" "m", "messagetype" "s", "messagedetails" [ { "languagecode" "en", "message" "it’s notification message " }] } [example] post /partner/v1/card/template/3hdpejr6qi380/notification [headers] authorization eyjjdhkioijbvvriiiwidmvyijoxlcjwyxj0bmvyswqioiixmjg1o x-smcs-partner-id partner-id-0001 x-request-id req-202303140003 x-request-cc2 kr /** payload **/] { "ntemplate" "eyjjdhkioijkv1qilcjhbgcioijsinrpbwvzdgftcci6imnyzwf0z…" } [response] type value description http status 200 ok payload harmfulresult harmfulness check result responded as “pass” or “fail” harmfullabels reason for harmfulness detection responded only when harmfulresult is “fail” save indicates whether the forcesaveyn option has been set when set to “y”, it is responded as “force” [200 ok] { "resultcode" "0", "resultmessage" "success", "harmfulresult" "pass" } [200 ok] { "resultcode" "0", "resultmessage" "success", "harmfulresult" "fail", "harmfullabels" "hate,violence" } [200 ok] { "resultcode" "0", "resultmessage" "success", "save" "force", "harmfulresult" "fail", "harmfullabels" "violence" } [result] http status code description 200 200 ok 400 400 bad request requests cannot or will not be processed the request due to something that is perceived to be a client error 401 401 unauthorized authorization token is invalid or expired 500 500 internal server error 503 503 service unavailable get notification templates [request] type value description method get url /partner/v1/card/template/{card id}/notification headers authorizationstring 1024 required credential token the token can have prefix "bearer" as an authorization type i e , bearer <credentials>* see json web token x-smcs-partner-idstring 32 required partner id x-request-idstring 32 required request identifier random generated uuid string path parameters card idstring 32 required the wallet card identifier granted through the partner portal * the identifier is needed when updating a specific card template [example] get /partner/v1/card/template/3hdpejr6qi380/notification [headers] authorization eyjjdhkioijbvvriiiwidmvyijoxlcjwyxj0bmvyswqioiixmjg1o x-smcs-partner-id partner-id-0001 x-request-id req-202303140003 x-request-cc2 kr [response] type value description http status 200 ok [200 ok] { "resultcode" "0", "resultmessage" "success", "templates" [ { "id" "4091356465432138240", "type" "m", "messagetype" "s", "approval" "approved", "messagedetails" [ { "languagecode" "en", "message" "hi! {{name}}, this is merchant push " } ] }, { "id" "4092425423713135680", "type" "m", "messagetype" "s", "approval" "none", "messagedetails" [ { "languagecode" "en", "message" " hi! {{name}}, this is merchant push" } ] }, ] } [result] http status code description 200 200 ok 400 400 bad request requests cannot or will not be processed the request due to something that is perceived to be a client error 401 401 unauthorized authorization token is invalid or expired 500 500 internal server error 503 503 service unavailable get notification statistics [request] type value description method get url /partner/v1/card/template/{card id}/stats/notifications headers authorizationstring 1024 required credential token the token can have prefix "bearer" as an authorization type i e , bearer <credentials>* see json web token x-smcs-partner-idstring 32 required partner id x-request-idstring 32 required request identifier random generated uuid string path parameters card idstring 32 required the wallet card identifier granted through the partner portal * the identifier is needed when updating a specific card template query parameters notificationidstring 32 optional if specified, statistics are returned only for the specified notification if not specified, aggregated statistics for all notifications of the card are returned starttimetamp ms required start date unix timestamp in milliseconds endtimestamp ms required end date unix timestamp in milliseconds metricstring 32 required metric impression click [example] get /partner/v1/card/template/3hdpejr6qi380/stats/notifications?notificationid=123456789&start=1764514800000&end=1765465200000&metric=impression [headers] authorization eyjjdhkioijbvvriiiwidmvyijoxlcjwyxj0bmvyswqioiixmjg1o x-smcs-partner-id partner-id-0001 x-request-id req-202303140003 x-request-cc2 kr [response] type value description http status 200 ok [200 ok] { "resultcode" "0", "resultmessage" "success", "statistics" [ [ 1764820800000, 1 ], [ 1764896400000, 2 ], [ 1764900000000, 1 ], [ 1764903600000, 0 ], [ 1764907200000, 1 ], [ 1765134000000, 0 ] ] } [result] http status code description 200 200 ok 400 400 bad request requests cannot or will not be processed the request due to something that is perceived to be a client error 401 401 unauthorized authorization token is invalid or expired 500 500 internal server error 503 503 service unavailable

https://developer.samsung.com/wallet/businesssupportforspecialpurposes/notificationforpartners.html

Learn Code Lab

codelab

Utilize the Add to Samsung Wallet service for digital cards

utilize the add to samsung wallet service for digital cards notescenes in the demo video are simulated and does not represent any real-world conditions or outcomes objective learn how to use the add to samsung wallet service so that users can store digital contents, such as boarding passes, tickets, and coupons, to their samsung wallet app partnership request to create, manage, and monitor performance of wallet cards with the samsung wallet partners site, you must become an official samsung partner once done, you can fully utilize this code lab you can learn more by visiting samsung wallet partner onboarding process, here in samsung developers overview samsung wallet is an application that securely stores essential items such as boarding passes, tickets, and coupons, making them easily accessible from anywhere with this app, users can access various partner wallet cards in one place, simply by swiping up from the bottom of the screen the add to samsung wallet service provides interfaces for users to conveniently add digital content to samsung wallet here are examples of the supported wallet cards boarding pass journey information such as flights, trains, and buses can be provided as notifications, allowing easy retrieval when checking in by configuring server synchronization, updates to journey information such as gate changes, schedule changes, or cancellations can be received by the users ticket notifications about events and additional information, including benefits, can be provided based on real-time utilization of performances, sports games, movies, and admission tickets, status updates related to expiration and availability can be provided gift card gift card, also referred to as a prepaid card, provides real-time balance and transaction history loyalty loyalty cards function as membership credentials, managing membership information through these cards, loyalty points can be administered and redeemed id id cards can fulfill identification verification purposes, such as identity cards, employee cards, and licenses physical documents can be represented through wallet cards, and near field communication nfc -based authentication can be provided reservation reservation cards can contain diverse online booking details, including rental cars, restaurants, and accommodations ongoing reservation information can be managed as a journey pay as you go pay as you go cards allow users to register services that can be charged and utilized according to their preference for convenient use generic card generic cards enable users to create customized cards by selecting preferred card template layouts and designing elements notedepending on your country or region, some card types are not supported if you need assistance, please contact us at developer samsung com/dashboard/support the image below shows the process of managing wallet cards for more information, refer to manage wallet cards set up your environment you will need the following latest version of samsung wallet app from galaxy store samsung galaxy device that supports samsung wallet access to samsung wallet partners site internet browser, such as chrome openssl intellij idea or any java ide optional start the onboarding process partners can manage wallet cards and monitor performance with the samsung wallet partners site to join as partner generate a private key and certificate signing request csr using the openssl command you can follow the instructions in security factors notea private key enables encryption and is the most important component of certificates while csr, which is a necessary factor to obtain a signed certificate, includes the public key and additional information like organization and country proceed to register in the samsung wallet partners site using your samsung account follow the samsung wallet partner onboarding process upload the generated csr for data encryption in encryption setting management section after registration, you will receive a welcome email noteupon receiving the certificates via email, be sure to keep the information safe from exposure and only use them for the following purposes signed certificate used along with the private key to sign data samsung certificate used to encrypt card data and validate authentication tokens in server api headers create a wallet card follow the steps below to create a wallet card in samsung wallet partners site click the wallet cards menu and choose create wallet card fill out the general information form with the details of the wallet card in wallet card template, choose a card type and sub type select the design type and click done you can choose from various types of wallet card templates optimized for partners after inputting all necessary details, click save to set the wallet card status to draft launch the wallet card you can launch and request activation of the card by clicking the launch button upon agreeing to proceed, the launch button text changes to launched and the card status becomes verifying add the card to samsung wallet using the test tool open a web browser on your computer or galaxy mobile device, and go to the following link partner walletsvc samsung com/addtowallettest go to add to wallet tab and click choose key file to upload your private key in the select card dropdown menu, select the created card to display the card details and populate sample data navigate to the form tab and modify the card data as desired notethe structure for configuring wallet cards follows the defined specification you can refer to the full list of card-specific attributes specification scroll down to the bottom of the page and click the add to samsung wallet button click done when a preview of the card shows on your mobile screen with a message indicating that the card has been added to your wallet once the card is added to your samsung wallet app, you can check its details by clicking on it noteyou can also go to the playground tab and add cards to the samsung wallet app even without creating a card on the wallet partners site update the status of the added card if a server api info partner get card data and partner send card state is registered in the wallet card, real-time updates of the user's registered cards can be provided notefor more information, see server interaction modify and update the card's status by utilizing the push notification feature of the test tool navigate to the push notification tab ensure that the correct private key is uploaded and the same card as in the add to wallet tab is selected copy the ref id value from the add to wallet tab and paste it into ref id field in the push notification tab in the status field, enter one of the following card states expired, redeemed, held, suspended, or deleted the current state is set to active then, click the request push notification button check the card in the samsung wallet app to confirm the change tokenize card data and implement the add to samsung wallet button to your service optional notethis step is optional, but if you want to learn how to integrate the add to samsung wallet button into your services like an android app, web app, or email, you can follow these steps the samsung wallet partners site provides generated add to samsung wallet scripts for each wallet card you create you can simply copy and paste these scripts into your partner apps web and android or include them in emails/mms messages to implement the add to wallet button, follow these steps go to the [add to wallet script guide] section of the card you created click show to view the available scripts and then copy the appropriate script for your service develop a program that can generate tokenized card data cdata the cdata represents the actual content of the wallet card and comes in different formats depending on the card type you can check the cdata generation sample code for reference the cdata is derived from the card data, which is in json format for testing purposes, you can utilize the generated json from the test tool follow the implementing atw button guide to determine where to incorporate the generated cdata and gain further insights into this process you're done! congratulations! you have successfully achieved the goal of this code lab topic now, you can utilize the add to samsung wallet service by yourself! to learn more about samsung wallet, visit developer samsung com/wallet

https://developer.samsung.com/codelab/wallet/add-to-wallet-interface.html

featured

blog

Use "Add to Samsung Wallet" for Event Tickets

have you heard the news about samsung galaxy unpacked 2023, which was announced on the samsung developers portal and global channels? if you’ve received an email invitation to galaxy unpacked 2023, scheduled for july 26, add it to samsung wallet for a quick and convenient way to enter the event hall. the "add to samsung wallet" service enables samsung device users to clip and save a variety of digital content, such as tickets, coupons, boarding passes, membership cards, to samsung wallet for easy access. “add to samsung wallet” allows them to do this conveniently without having to leave the other online channels they are using, such as an application, website, email, or sms/mms message. smart ways to use "add to samsung wallet" 1. add your galaxy unpacked 2023 invitation on july 26, expect new, wonderful, and innovative android tablets, smart watches, and the most anticipated of all, 5th-generation foldable phones, to be revealed at galaxy unpacked 2023. you can also attend galaxy unpacked remotely by watching the real-time live stream on the samsung electronics website and youtube channel. try adding the invitation and entrance ticket for galaxy unpacked 2023 to samsung wallet for ease and convenience. open the email invitation on your galaxy mobile device and tap "add to samsung wallet" to add your ticket. 2. add other event tickets “add to samsung wallet” also supports different kinds of tickets, such as to movies, sports events, and concerts. the related apis allow you to implement the feature for your service, checking whether the user’s device supports samsung wallet and if so, enabling the "add to samsung wallet" button. for example, a tourist in france can add their tickets to exhibitions at the atelier des lumières art museum in paris and to the bassins de lumières in bordeaux to samsung wallet using the "add to samsung wallet" button (provided by splio). 3. add content from other services “add to samsung wallet” is not only for tickets! the "add to samsung wallet" feature also works with other content issued by our partners, such as boarding passes, coupons and membership cards: • add or register your boarding pass to samsung wallet to get push notifications for your boarding time and speed through the boarding process. • add coupons collected from various channels, including sms, mms and email, to samsung wallet. you can receive notifications and keep track of their validity. to learn more, see samsung wallet. special features for event tickets in samsung wallet • optional policy to prevent misuse of tickets • group ticket layout that presents multiple barcodes or qr codes in a single ticket • batch update the status for all tickets, for example, when an event is canceled or postponed; this feature requires the partner to share the relevant information. • provide up to 2 barcodes or qr codes for extra services at your event, such as coupons for snacks or parking, in addition to the barcode or qr code for the ticket itself • push notifications sent 1 hour before the event begins integrate "add to samsung wallet" for your event tickets for a detailed description of the registration process, development specifications, and testing tools for integrating “add to samsung wallet” to your service, go to the samsung wallet partner portal (english language links below). the partner portal contains tutorials that walk you through the integration process step-by-step. step 1. register as a partner at the samsung wallet partner portal https://developer.samsung.com/wallet/onboarding.html step 2. create and manage samsung wallet cards https://developer.samsung.com/wallet/manage.html step 3. integrate “add to samsung wallet” to your service https://developer.samsung.com/wallet/api/overview.html if you are in a country where the event ticket menu is not supported on galaxy devices, contact us through developer support and we will help you as quickly as possible.

Hye-In Min

https://developer.samsung.com/wallet/blog/en-us/2023/07/19/add-to-samsung-wallet-for-event-ticket

Develop Samsung Wallet

doc

Prerequisites

prerequisites prerequisites for using or developing samsung wallet are samsung galaxy device - a compatible samsung smartphone or wearable with samsung wallet pre-installed or available via galaxy store samsung account - users and developers must sign in with a valid samsung account to access wallet features and sync data securely supported os version - device must run a supported version of android and samsung one ui to ensure compatibility with wallet services partner registration - developers must register as a partner on the samsung wallet developer portal to gain access to tools and apis template and card certification - before launching wallet cards, partners must submit and get approval for their templates through the wallet partner portal csr certificate signing request - partners must upload a csr for secure communication and authentication when using server apis api authorization - access to wallet apis requires authorization tokens and approval for use cases like card issuance or push notifications testing mode & qa - new wallet cards are initially in testing mode developers must test thoroughly before requesting activation

https://developer.samsung.com/wallet/welcome/prerequisites.html

Didn’t find what you were looking for?

FAQ

Search frequently asked
questions
by keywords.

Join the Forum

Visit the Forum to ask
questions and exchange
ideas with other developers.

Get Support

Submit a 1:1 Support request
and receive a response
within 2 business days.

Preferences Submitted

You have successfully updated your cookie preferences.