Filter
-
Content Type
-
Category
Mobile/Wearable
Visual Display
Digital Appliance
Platform
Recommendations
Filter
tutorials mobile
blogare you a company looking to enhance your users' experience by allowing them to add digital content such as tickets, coupons, or boarding passes to samsung wallet? or perhaps you're an online merchant interested in integrating samsung pay as a secure payment option for your customers? look no further! the samsung wallet partner portal is the perfect solution for your needs. the samsung wallet partner portal is a dedicated platform designed for companies who wish to collaborate with samsung wallet. by becoming a partner, you'll gain access to a wide range of services and resources that will enable you to seamlessly integrate your digital content or payment systems with samsung wallet. how to become a partner to become a partner and start collaborating with samsung wallet, simply visit the samsung wallet partner portal and follow the onboarding process. once registered, you'll gain access to the portal's features and resources, allowing you to start integrating your digital content. to help you better understand the partner portal onboarding process and usage, we've prepared a tutorial video for you: notethe tutorial video also has a helpful guide for online merchants interested in integrating secure samsung pay functionalities into their mobile app or website. don't miss out on new business opportunities by joining the samsung wallet partner portal now! if you have any further questions, submit a support request or join the forum. for more information, please refer to the following resources: samsung wallet for partner samsung pay for partner
tutorials digital payments
blogthis article demonstrates how to integrate samsung pay in-app payments into your android application, covering everything from account setup to release. follow these steps to ensure a smooth integration process so you can start accepting payments with samsung pay quickly. figure 1: steps of implementing samsung pay set up and configure samsung pay register as a partner to begin accepting payments through samsung pay, first you need to register as a samsung pay partner and complete your samsung pay developer profile. visit the samsung account website go to the samsung account web site and do one of the following: if this is your first time on the site, click “create account” at the top right corner to create an account. for a smooth approval, use a business email (not personal) for registering your account. if you already have a samsung account, simply log in. complete your developer profile follow these steps to enable your samsung pay developer account: go to the samsung pay developer portal and log in with a business account. become a pay partner by creating a business account. provide appropriate data which exactly matches your business and legal documents. read the terms and conditions carefully and accept them. submit your partnership request. the approval process generally takes a few days. if you encounter any issues, please contact developer support for assistance. configure your service and app while working with the samsung pay, you will encounter the terms “service” and “app.” let’s unpack them below. understanding services and apps service: an interface to the samsung pay system that provides the payment facilities. the service talks with the samsung pay system and collaborates with the partner system and payment gateway for processing payments. app: an app works like a bridge between the service and the partner application. the app ensures the communication and security between the partner application and the service. create an in-app payment service to create an in-app payment service, from the samsung pay partner portal, follow the steps below: select service management, under my projects in the top-right corner menu, in the service management screen, click create new service. select the in-app online payment service type, then click save and next. enter the service information, attach a valid csr file for secure payment, and then click save and next. fill in the required details to define your in-app service. if you have created one previously, you can also use it instead. then click save and next to advance to the next step. define a tentative debug date by clicking generate new date. click add samsung account to add the samsung accounts that will be used for testing purposes. click done. figure 2: creating an in-app payment service this completes the creation of your service and links it with your application. wait for it to be approved. the team will contact you promptly once your request has been processed. in case of any delays, feel free to reach out to 1:1 support for assistance. samsung pay feature development now that your partner account set up is complete, it's time to integrate samsung pay functionality into your android application. next we will integrate the samsung pay sdk and implement core payment features to enable seamless in-app transactions in your app. download and add the sdk go to the downloads page in samsung pay and scroll down to the android section to download the samsung pay sdk. sdk components the samsung pay sdk has the following components: java library (samsungpay_x.xx.xx.jar): contains the classes and interfaces to integrate with the samsung pay. sample apps: demonstrates the implementation of samsung pay apis to simplify the process of building your own. add the sdk to your project create a folder called ‘libs’ if one does not already exist, and move the sdk .jar file into this folder. /app ├── libs/ │ └── samsungpay_x.xx.xx.jar ├── src/main/ │ ├── kotlin/ │ ├── res/ │ └── androidmanifest.xml configure gradle and dependencies update settings.gradle.kts add the ‘libs’ folder with the other repositories, if it is not there already. dependencyresolutionmanagement { repositories { google() mavencentral() flatdir { dirs 'libs' } } } add the sdk dependency in app/build.gradle.kts add the samsung pay sdk as a dependency for your application. dependencies { implementation(files("libs/samsungpay_x.xx.xx.jar")) } sync the gradle to apply the changes. configure android app manifest add the following configurations in your androidmanifest.xml. this ensures the compatibility and proper functioning of your application. add the element <queries> <package android:name="com.samsung.android.spay" /> </queries> add metadata <meta-data android:name="spay_sdk_api_level" android:value="2.xx" /> <!-- latest version is recommended] --> implement functionality now that the samsung pay sdk integration is complete, let us use this sdk to implement the complete functionality of the samsung pay sdk in your android application. here we will go through the complete flow of initiating a payment using the samsung pay sdk. check samsung pay availability initiating a payment starts by checking if samsung wallet is available for payment or not. initialize the samsung pay service with your partner credentials, then verify if samsung pay is supported. if available, display the samsung pay button in your app. val serviceid = "partner_service_id" val bundle = bundle() bundle.putstring(samsungpay.partner_service_type, samsungpay.servicetype.inapp_payment.tostring()) val partnerinfo = partnerinfo(serviceid, bundle) val samsungpay = samsungpay(context, partnerinfo) samsungpay.getsamsungpaystatus(object : statuslistener { override fun onsuccess(status: int, bundle: bundle) { when (status) { samsungpay.spay_not_supported -> samsungpaybutton.setvisibility(view.invisible) samsungpay.spay_not_ready -> { samsungpaybutton.setvisibility(view.invisible) val errorreason = bundle.getint(samsungpay.extra_error_reason) if (errorreason == samsungpay.error_setup_not_completed) samsungpay.activatesamsungpay() else if (errorreason == samsungpay.error_spay_app_need_to_update) samsungpay.gotoupdatepage() } samsungpay.spay_ready -> samsungpaybutton.setvisibility(view.visible) } } override fun onfail(errorcode: int, bundle: bundle) { samsungpaybutton.setvisibility(view.invisible) log.d(tag, "checksamsungpaystatus onfail() : $errorcode") } }) set up payment details and request the payment after the availability check is completed, you need to set up the payment details such as merchant information, transaction information, order number, and so on, before requesting the payment. the following code snippets show how to accomplish this. make customsheet create a simple custom payment sheet with amounts and items for the transaction. this sheet will be displayed during the payment process. you can customize the sheet according to your requirements. private fun makeupcustomsheet(): customsheet { val amountboxcontrol = amountboxcontrol(amount_control_id, mbinding.currency.selecteditem.tostring()) amountboxcontrol.additem( product_item_id, mcontext.getstring(r.string.amount_control_name_item), mdiscountedproductamount, "" ) amountboxcontrol.additem( product_tax_id, mcontext.getstring(r.string.amount_control_name_tax), mtaxamount + maddedbillingamount, "" ) amountboxcontrol.additem( product_shipping_id, mcontext.getstring(r.string.amount_control_name_shipping), mshippingamount + maddedshippingamount, "" ) amountboxcontrol.setamounttotal(totalamount, amountformat) val sheetupdatedlistener = sheetupdatedlistener { controlid: string, sheet: customsheet -> log.d(tag, "onresult control id : $controlid") updatecontrolid(controlid, sheet) } val customsheet = customsheet() customsheet.addcontrol(amountboxcontrol) return customsheet } make customsheetpaymentinfo create payment information with merchant details, order number, and card brand preferences. private fun maketransactiondetailswithsheet(): customsheetpaymentinfo { // get brandlist (supported card brands) val brandlist = getbrandlist() val customsheetpaymentinfo: customsheetpaymentinfo val customsheetpaymentinfobuilder = customsheetpaymentinfo.builder() customsheetpaymentinfobuilder.setaddressinpaymentsheet(mrequestaddressoptions.requestaddresstype) customsheetpaymentinfo = customsheetpaymentinfobuilder .setmerchantid("your_merchant_id") .setmerchantname("your_merchant_name") .setordernumber("your_order_number") .setaddressinpaymentsheet(customsheetpaymentinfo.addressinpaymentsheet.do_not_show) .setallowedcardbrands(brandlist) .setcardholdernameenabled(mbinding.cardbrandcontrol.displaycardholdername.ischecked) .setcustomsheet(makeupcustomsheet()) .build() return customsheetpaymentinfo } request the payment initiate the samsung pay payment process with transaction details and handle payment callbacks. mpaymentmanager.startinapppaywithcustomsheet( maketransactiondetailswithsheet(), object : customsheettransactioninfolistener{ override fun oncardinfoupdated( selectedcardinfo: cardinfo?, sheet: customsheet? ) { // update your controls if needed based on business logic for card information update. // updatesheet() call is mandatory pass the updated customsheet as parameter. try { paymentmanager.updatesheet(customsheet) } catch (e: java.lang.illegalstateexception) { e.printstacktrace() } catch (e: java.lang.nullpointerexception) { e.printstacktrace() } } override fun onsuccess( customsheetpaymentinfo: customsheetpaymentinfo?, paymentcredential: string?, extrapaymentdata: bundle? ) { // triggered upon successful payment, providing customsheetpaymentinfo and paymentcredential. // for example, you can send the payment credential to your server for further processing with pg. or you could send it directly to the pg as per business need. sendpaymentdatatoserver(paymentcredential) } override fun onfailure(errcode: int, errordata: bundle?) { // fired when the transaction fails, offering error codes and details. log.d(tag, "onfailure() : $errcode") showerrordialog(errcode, errordata) } }) testing and release test and validate to ensure a seamless and reliable integration of samsung pay, thorough testing is essential. this process validates transaction performance and guarantees a positive user experience for making a robust business impact. testing goes beyond error detection; it aims to comprehensively assess the quality and functionality of your samsung pay integration. release after successful testing, the next step is to secure release version approval from samsung through the samsung pay developers portal. once approved, your application can be launched, allowing you to monitor user satisfaction and optimize performance. conclusion by integrating samsung pay in-app payments, you’ve enabled secure, convenient transactions for samsung pay users. this implementation expands your payment options while providing a seamless checkout experience. additional resources for additional information on this topic, refer to the resources below. samsung pay faqs samsung pay in-app payment documentation
Yasin Hosain
tutorials
blogintroduction smartphones have become an essential part of our everyday lives. users are continually searching for more convenient ways to perform their tasks on their smartphones, driving them toward services with greater usability. as smartphones advance, our lives become simpler. galaxy users have completely embraced the convenience of paying with samsung pay, and no longer carry physical payment cards. this led to the evolution of samsung pay into samsung wallet, incorporating biometric-authentication-based security solutions and adding various features to replace conventional wallets. since june 2022, samsung wallet has been expanding its service area based on the existing samsung pay launching countries. this article aims to introduce samsung wallet and guide you through the integration process of the "add to samsung wallet" feature, which allows you to digitize various content and offer them as wallet cards. notice this article introduces non-payment service cards. if you want to learn more about the payment service of samsung wallet, visit the samsung pay page. you can get information on online payment services such as in-app payments, web checkout, and w3c payments. add to samsung wallet service let's delve deeper into the "add to samsung wallet" feature. digitized content registered in samsung wallet comes in the form of cards called wallet cards. registering a wallet card is effortless: simply click the "add to samsung wallet" button, and the card is stored securely on users’ galaxy smartphones. "add to samsung wallet" button and wallet card notice the benefits of using wallet cards can be found in the commercial video forgetting can be awesome. wallet cards the "add to samsung wallet" service is an open platform that supports offering various types of content such as wallet cards. we are streamlining service integration with content providers across different regions and adding useful features. boarding pass event ticket loyalty gift card coupon id card generic card pay as you go (in progress) reservation (in progress) digital key (in progress) notice generic card supports unstructured forms of cards. be a samsung wallet partner partner onboarding to begin offering content through samsung wallet, you must first register as a partner on the samsung wallet partner portal. the integration process is detailed on the samsung developer portal. to join the samsung wallet partner portal, create a samsung account that is used as the service administrator. wallet card management once enrolled, you can create service cards on the wallet cards menu. each card is assigned a card id representing the service, and you can set the card type and linking information. you can manage cards according to their status – test or live. configuring wallet card notice after completing all required forms for the wallet card, click the launch button to request card activation. before providing the service to actual users, remember to turn off the 'test mode.' how to safely secure user data key generation and certificate request the registration process includes certificate exchange to securely transmit service data. refer to the diagram and developer guide, security key & certificate creation guide, to complete the certificate registration and partner enrollment smoothly. certificates exchange process ensuring data security to prevent forgery and leakage of user card data, secure tokenization processing is required. json web token (jwt), which includes encryption and signature, has a validity time basis for verification, thus providing enhanced security. in particular, when generating this token, the key and certificate previously obtained through the certificate exchange process are used. process of generating and verifying security tokens notice depending on how partners provide content services to users, you can choose how to deliver data to the samsung wallet service. two ways to transfer wallet card data add to samsung wallet interface provides two methods for partners to deliver users digital content as wallet cards. data transmit link the general way to transfer wallet card data is to organize tokenized data in the link attached to the button, and the card data is transmitted to the samsung wallet service when the user clicks the button. as long as samsung wallet support is confirmed, you can generate a link containing the user's card data and configure the "add to samsung wallet" button to run the link when pressed, either on an application or web page. data transmit process data fetch link another method to transfer wallet card data is to include only the refid, which represents the user's content, in the "add to samsung wallet" link and transmit it to the samsung wallet service. when a user clicks the "add to samsung wallet" button, samsung servers refer to the get card data api information set on the wallet card and retrieve user content using the received refid to complete registration. data fetch process this method is suitable for providing user's data through email or mms messages where static links cannot be avoided. there is an option to secure these static links. data fetch process for static links setting up data synchronization on the partner portal, you can set up the wallet card information and configure the server interaction api that the content provider needs to prepare. this api is an interface for managing card registrations, deletions, information, and state changes to sync with those registered on samsung wallet. register wallet cards when a user card is added to samsung wallet, samsung wallet servers use the send card state api to communicate card registration and deletion status to the content provider, allowing them to manage content that needs to be synchronized with samsung wallet. when a wallet card is registered, added event is sent to the partner's server update wallet cards changes to the synchronization target content can be notified to the samsung wallet service through the update notification api. here, the value that distinguishes each piece of content is the refid that the partner must provide when registering the users’ wallet card. through the get card data api, samsung wallet servers can check the latest content information any time. if updates occur on the partner's side, updated event notifications should be sent to the samsung server in case users withdraw content from the partner's side in case users delete cards from samsung wallet notice both servers should verify requests using the authorization header of the api request. this authorization token is in jwt format, familiar from card data security. effortless wallet card registration with just one click this feature is primarily composed of a link-connected button and can be provided through the content provider's application, web page, email, or mms message. various service channels javascript library for web developers we provide a javascript library and a user guide, implement the button, to help integrate your web pages. creating buttons and links in your app for configuring buttons in applications, utilize the button image resources. providing services via mms, email, or qr codes to provide services through fixed links, check out the details of the data fetch link. these static links can also be used by scanning qr codes. experience the service and practice you can experience service integration development using the codelab and use the testing tool to preregister the wallet cards created on the partner portal, which could be helpful. conclusion we've looked at how to provide digital content through the "add to samsung wallet" feature. we continuously update the guides on the developer portal, so please refer to them when preparing for integration. summary the "add to samsung wallet" service welcomes participation from content service partners and developers. for inquiries or technical support, please contact us through the form provided on the developer portal. i hope this post has been helpful, and now i'll conclude my writing here. thank you. this post was written based on the sdc23 korea session.
Choi, Jonghwa
Develop Samsung Pay
doc4 1 how to configure the stg environment 4 1 1 how to add test account set up a test account using the steps below this is required to access and interact with the test environment test environment setup go to my projects > service management partners can create or update an existing service to create a service, click create new service, and select your chosen service type fill the respective service information fields once filled, click save and done to proceed to the next section to update a service, click an existing service to redirect to the service details page in debug effective date, click generate new date to generate the debug expiration date of the test accounts for existing services, generate new date button is a feature to extend the debug effective date in service details page, partners can extend test date by clicking the button on the prompt alert before generating the date, a prompt alert is displayed to add email addresses of the test accounts the test accounts must be samsung accounts associated with a registered samsung pay app on a supported device you may add up to 30 test accounts note use commas to input multiple accounts example test1@samsung com,test2@samsung com,test3@samsung com after adding the test accounts, click generate to generate the debug expiration date of the test accounts alternatively, partners can add test accounts by clicking add samsung account button, and input the test account email addresses once the test environment information is filled out, click done to save the service configuration the service is displayed in the service management dashboard with a debugging status partners can use their service with sdk and test accounts until the generated debug effective date 4 1 2 how to get samsung wallet test app copy link for test app in samsung pay partner portal support > request test app > galaxy app url download test app in your test device open url in your test device select ‘participate’ in galaxy store select ‘install now’ to install test app 4 1 3 list of test cards test card numbers including fpan, cvv, cvc, expiration date from the payment networks listed below can be on supported devices to test within the samsung pay staging environment visa card number card type expiry date cvv 4622 9431 2312 3870 credit 12/26 550 4622 9431 2312 3880 credit 12/26 695 4622 9431 2312 3890 credit 12/26 774 4622 9431 2312 3900 credit 12/26 308 4622 9431 2312 3910 credit 12/26 039 mastercard card number card type expiry date cvv/cvc2 5186 1516 5001 2004 credit 12/26 123 discover card number card type expiry date cvv 6011 0092 7412 9795 credit 08/27 687 6011 0080 3081 6410 credit 04/30 269 6011 0006 9386 3380 credit 06/27 779 4 1 4 test check list push provisioning use the following checklist to ensure you’ve completed all the required steps in your samsung pay integration for push provisioning install the samsung wallet test app check the 2 b section for details setup the wallet app follow the steps below to complete the setup sign in with samsung account use your samsung account and credentials to sign in set up a pin/biometric use a pin or biometric to protect your wallet app check samsung pay status check the samsung pay status on the device to determine if the samsung wallet is working properly refer to this checking samsung pay status guide for more details add card with proper parameters use proper payload as per the token provider guidelines follow the add card flow follow and accept the steps of samsung wallet app to complete the process verify with getallcards check if the card is successfully added on the samsung wallet app in-app payment use the following checklist to verify that all necessary steps for samsung pay in-app payment integration have been completed install the samsung wallet test app refer to section 2 b for detailed instructions setup the wallet app complete the setup by following the steps below sign in with samsung account log in using your samsung account credentials set up a pin/biometric secure your wallet app with a pin or biometric authentication if you do not have any cards currently stored in your samsung wallet app, please proceed to add a card from the provided test card 2 c follow the necessary steps to input the card details make a payment initiate a payment through the merchant app/web complete the payment process by authenticating with your pin or biometric method as required
Develop Samsung Pay
doc2 2 steps for successful partner onboarding the onboarding involves becoming a registered partner, gaining access to development tools sdks and apis , and configuring payment-related services for in-app, web, or push provisioning functionalities below are the recommended and supported steps for successful onboarding become a member samsung developers account go to samsung developers sign up for a samsung account if you don’t have one accept the terms and conditions required to join the samsung developers program if you have a samsung account, click log in otherwise, click sign up use a company email for account creation—preferably one that’s stable over time e g , dev@company com accept the terms and privacy policy complete the signup form and verify your email via an activation link submit your business or organization information company name contact details type of service bank, merchant, fintech, etc this step allows samsung to validate and approve you as a potential partner after signing in, begin the membership registration process choose "i am the first samsung pay member of my company" — if you're the first registrant "my company is already registered" — if joining an existing partner enter partner id fill in company details name, type of business, location, size add user details contact person, phone number, job title submit and wait for samsung to review your profile once approved, you’ll receive full access to restricted tools and documents note your account must be approved before you can manage services or invite team members upon review of the information provided, your samsung pay relationship manager rm may request additional details once your membership registration is approved, you'll be granted access to currently restricted areas of the samsung pay portal and you can invite members of your team to collaborate on your samsung pay projects until then, take advantage of valuable resources like the samsung pay sdk and sdk programming guide from the following link android sdk [in-app payment and push provisioning] https //developer samsung com/pay/native/sdk-overview html web checkout sdk https //developer samsung com/pay/web/overview html w3c mobile payment https //developer samsung com/internet/android/web-payments-integration-guide html when you receive the email notifying you of membership approval, you're ready to get started in your browser, return to the samsung pay portal and sign in set up your partner project once approved, begin setting up your integration project navigate to the "my projects" section in the partner portal create a new project to associate with your app or service integration app your mobile app issuer or merchant app service integration instance linking the app, certificate, and sdk configuration e g , card enrollment or web payments choose your project type based on your intended service inapp online payment push provisioning web online payment w3c mobile web you can create different service for the same package for multiple purpose testing note only one application can be added under one service id for example app deployment scenario unique service-app combinations global issuer app using a different csr encryption key for services in different regions to interact with local servers service 1 = com issuer walletapp, csr1_us service 2 = com issuer walletapp, csr2_plcc_abcmart same issuer app for all customers but different csrs for managing different card services b2b vs plcc service 1 = com issuer walletapp, csr1_regular service 2 = com issuer walletapp, csr2_plcc_abcmart multiple merchant apps using the same pg service 1 = com merchant electronicsapp, csr_pg1 service 2 = com merchant groceryapp, csr_pg1 global merchant app using a different pg for each country service 1 = com merchant electronicsapp, csr_pg1 service 2 = com merchant electronicsapp, csr_pg2 multiple web sites using the same pg service 1 = electronicssite merchant com, csr_pg1 service 2 = grocerysite merchant com, crs_pg1 global merchant web site using a different pg for each country service 1 = electronicsapp merchant com, csr_pg1 service 2 = electronicsapp merchant com, csr_pg2 create new service samsung pay supports several types of services on the create new service tile, click go and create select one of the following service types in-app online payment service push provisioning web online payment w3c mobile web note samsung pay provides a variety of partner integration services via the samsung pay developers site, each addressing a set of features apropos to your specific app or mobile web site requirement select service type based on samsung pay functionality you want to make available
Develop Samsung Pay
webdo morewith your money. join samsung pay partners and integratesecure samsung pay functionalitiesinto your mobile app or website. get started together with new partner you can now create and publish content such as coupons, boarding pass or tickets to the users of samsung pay. this is enabled by a two-step process where you onboarding on our partner portal. where can pay be used in-app payments the samsung pay sdk with its api library offers a quick and easy way to enable secure, one-touch payments in your app using your existing payment infrastructure. once you integrate the sdk within your app's payment. web checkout samsung pay web checkout is an online payment method accessed from a web browser, pc-based or mobile, with authentication performed by samsung pay on the user's samsung device. initiated from a merchant web page, web checkout leverages samsung pay's in- app solution. w3c payment merchant websites can now use samsung pay by adhering to the w3c payment request standard. this reduces merchant checkout friction and card abandonment; enables a more advanced and secure mobile pay method. discover available gateways/platformssupporting samsung pay worldpay view more adyen view more fiserv view more cybersource view more gateway view more lyra view more how to designsamsung pay we encourage you to learn and follow the rules and guidelines suggested to ensure message consistency and drive brand awareness. learn more news and blogs learn more how can we help you? faq search frequently asked questionsby keywords. join the forum visit the forum to ask questions andexchange ideas with other developers. get support submit a 1:1 support request and receive a response within 2 business days.
Develop Samsung Internet
docweb payments integration guide overview to help standardize and streamline how payments are done on the web, the worldwide web consortium w3c has introduced a payment request api to provide an interface between a merchant web page and a mobile payment app, like samsung pay, to facilitate payment transactions samsung internet browser leverages the w3c payment request api to support samsung pay as a payment method for web purchases chrome also supports a samsung pay web payment method why integrate samsung pay into your website? samsung pay is accepted at more retail locations than any other mobile payment service available because of its unique ability to transact with newer nfc-supported payment terminals and legacy payment terminals it continues to enjoy the best user reviews among mobile payment apps now available for mobile website integration, samsung pay is secure, easy to set up, simple to use, and pre-installed on all new samsung galaxy-class smartphones when integrated with your website, samsung pay presents your users with a common checkout process that leverages samsung pay’s secure purchase authentication technology, eliminating manual entry or re-entry of card details and shipping destinations checkout is streamlined, conversions are maximized, and the exposure of sensitive data is kept to the absolute minimum simplifying the transaction process the benefits of the new process, certainly from an end-user perspective, is that the previous tedium ― request, authorization, payment, and result ― can now be handled in a single step for the web developer, it entails a single javascript api call for samsung pay users, there’s no change at all in the way a payment card is selected and authenticated after selecting the desired merchandise from the merchant’s web site, the user initiates checkout, selects samsung pay as the preferred payment method, authenticates with a fingerprint or pin, and voila ― payment complete that’s the user experience at its most basic when properly implemented, the api also supports editing the billing/shipping address in samsung pay and selecting a different enrolled card before approving the transaction with a fingerprint scan or entering a pin in terms of convenience, it’s a remote shopper’s dream ― no complicated, input-intensive forms to fill out, no fumbling for a plastic card to enter the account number, card expiration, and security code, and no worrying that someone other than the legitimate cardholder is attempting to make the payment meanwhile, samsung pay’s tokenized payload securely protects the transaction from intercept and replay attacks about this guide intended for web developers with a working knowledge of javascript and json, this guide takes you through the complete process of onboarding as a samsung pay merchant partner, creating/registering the w3c service for your domain, adding the w3c payment request object to your website, then testing and releasing your merchant website offering samsung pay as a payment method let's get started determining your gateway integration mode the api methods for integrating samsung pay with your website depend on the type of payment token your payment gateway pg handles — either gateway tokens or network tokens samsung pay supports requests for both types for instance, if stripe is your pg, you will want to request a gateway token from samsung pay on the other hand, if you’re using first data, you’ll want to request an encrypted network token bundle, for which you handle the token decryption yourself or work with the pg first data in this case to handle decrypting the token bundle the process begins when your merchant website makes a payment request and passes all required information to the browser, which then determines compatibility between the accepted payment methods for your website and the methods apps installed on the target device let’s take a brief look at how each integration mode — gateway token and network token — works with samsung pay gateway token mode although samsung pay doesn’t process the payment, your merchant website will still need to invoke the appropriate payment gateway apis to charge and process the token returned by your pg hence, when samsung pay returns a gateway token from stripe, for example, the recommended flow looks like this user selects samsung pay as the payment method at checkout in the merchant's website and the samsung pay app requests partner verification from the samsung pay online payment server encrypted payment information and the partner id are passed to the samsung-pg interface server samsung-pg interface server sends a transaction authorization request to the pg on behalf of the merchant; pg authenticates the partner id before generating a transaction reference id samsung-pg interface server returns the payment token to the pg i e , the gateway token it received from the samsung pay app in step 2 pg continues payment processing with the acquirer and payment network the result approved/declined is returned to the merchant website on the device for display to the user in this mode, samsung pay makes a call to your pg on your behalf and returns a chargeable gateway token network token mode under network token mode, the samsung pay api returns an encrypted network token bundle, which you can then either decrypt yourself or leverage the apis of your pg first data, for example to handle decryption and charge the token user selects samsung pay as the payment method at checkout in the merchant's website and the samsung pay app requests partner verification from the samsung pay online payment server encrypted payment information is passed from the samsung pay app to the pg through the merchant app via the pg sdk applying the merchant's private key, pg decrypts the payment information structure and processes the payment through the acquirer and payment network upon receiving authorization or rejection, pg notifies the merchant website through its pg sdk to simplify integration of network tokens, you can pass the encrypted payload directly to your pg and let it handle decryption in general, decrypting the payload yourself is more complex and involves private key management see your particular pg’s documentation for details once you determine which mode your pg supports, you're ready to register with the portal first, however, there are a number of prerequisites you'll need to satisfy prerequisites registering with the samsung pay developers portal and adapting the appropriate payment request apis for your website in accordance with the guidance contained herein will help to ensure a successful implementation to that end, the following requirements apply release contents minimum samsung pay app version 2 8 xx minimum samsung internet browser version 5 4 minimum chrome browser version 61 supported device models samsung galaxy-class smartphones running minimum version of the wallet app and browser supported payment gateways pgs view the most current list in the portal's payment gateway drop-down menu in service create/edit mode see step 5 under registering your domain for the w3c service registering with the portal through the samsung pay developers portal you can access valuable resources to help you manage the samsung pay features you incorporate into you partner app, including the ability to create multiple samsung pay service groups so you can use different services without the need to create multiple accounts invite co-workers to the portal to help you manage samsung pay features for your website register your website with samsung pay configure your samsung pay w3c service s to create a member account on the samsung pay developers portal open a browser like chrome, go to https //pay samsung com/developers, click sign up and confirm/acknowledge that you accept the samsung pay terms and conditions and understand the privacy policy, then do one of the following a if you already have a valid samsung account, click sign up and enter your samsung account id and password b if you do not have a samsung account, click create a samsung account to create one open the account activation email you receive and click the account activation link if you’re the first samsung pay member of your company to register, select the first option, click next, and complete a company and user profile if, on the other hand, you were given a samsung pay partner id by a co-worker, select the second option — my company is already registered — and enter your company’s partner id in the field provided, then click next after you receive notification by email that your membership is approved, typically within 2 business days, return to https //pay samsung com/developers, click sign in and enter your samsung account id and password for site access as a new member registering your domain for the w3c service your domain is the url associated with your website, whether in test or production the service type specifically associates w3c with your domain once you create the service, you will be prompted to configure the domain you want associated with it to create a new service go to my projects > service management and click create a new service select for test to define the service for initial integration with samsung pay, then click next select w3c mobile web payments as the service type and click next enter a service name and select “united states” as the service country select a payment gateway from the list of supported pgs if your payment gateway uses the network token mode, upload the certificate signing request csr you obtained from your pg supported formats are csr or pem contact your pg for details otherwise, key management is already established for pgs supporting samsung pay’s gateway token mode; hence, click connect with to create a new service connection with the pg and click ok enter the payment domain name s for your website in the service domain field and click add for example, if your domain is mywebstore com but the checkout page is hosted on the subdomain payments mywebstore com, you’ll need to enter payments mywebstore com as the service domain in the portal for each additional domain name, click add notewhen entering the domain name on the portal, do not include an https // prefix confirm your agreement with the terms and conditions, then click next adding w3c payment requests objects to your website in order to accept payments from samsung pay, your website must adhere to the w3c payment request api specification you can get started with the basics by completing the steps that follow and making the appropriate substitutions for your website step 1 feature detect prior making a w3c payment request, it’s wise to run a feature detect to ensure the browser in use supports the w3c payment request api if not, you should fall back to your traditional/normal checkout page example if window paymentrequest { // use payment request api } else { // fallback to traditional checkout window location href = ‘/checkout/traditional’; } step 2 create the paymentrequest constructor the first step is to create a paymentrequest object by calling the paymentrequest constructor, which has the following parameters methoddata – contains a list of payment methods that the website supports e g , visa, amex, samsung pay details – contains information about the shopping cart purchases e g , total, tax, fees, etc options – details pertaining to shipping address, user contact information, etc example var request = new paymentrequest methoddata, // required payment method data details, // required information about transaction options // optional parameter for things like shipping, etc ; step 3 add samsung pay to the methoddata parameter the methoddata parameter contains a list of payment methods supported by the merchant to support samsung pay, you’ll need to add it as a supported payment method notebasic-card is an optional supportedmethod for credit and debit cards saved in the browser, the card details of which are returned directly to the website from the browser before configuring this method, make sure your website and pg can handle generic payment information received from the browser and process with required pci compliance, if applicable see the [w3c basic card payment specification][7] for additional details be aware, however, that if you intend to support a branded samsung pay button, only samsung pay can be enabled as a payment method within the paymentrequest object; basic-card or any other payment method cannot be included if you already offer a generic payment request method, you can continue to do so — and include samsung pay as a payment method within that paymentrequest object from a user experience standpoint, the two distinct pathways look like this standard w3c implementation a standard w3c implementation adds samsung pay to your standard paymentrequest object as one of many supportedmethods available for user selection tapping checkout or its equivalent launches the standard browser payment sheet for user selection of the payment method and/or to add a debit/credit card to the list of options selecting samsung pay as the payment method and tapping pay launches the samsung pay payment sheet branded samsung pay implementation a branded implementation displays a "buy with samsung pay" button in place of your standard checkout button tapping the button will skip directly to the samsung pay payment sheet for authentication unless you specify paymentoptions if paymentoptions is not null, the browser payment sheet is launched see paymentoptions in step 7 for additional guidance first launching your website's checkout page is recommended for branded implementations this is because the samsung pay payment sheet only provides the user's billing address, which means your website will need to capture the user's preferred shipping address, where applicable for physical delivery of purchased goods if no shipping address and/or other options are needed, set the paymentoptions parameter to null as mentioned above, if you populate paymentoptions, the browser payment sheet is automatically launched keeping the foregoing implementations in mind, let's look at how to construct the methoddata argument for the network token mode and gateway token mode, respectively the fields in methoddata comprise supportedmethods – required; specifies https //spay samsung com/ i e , the samsung pay app and other methods suppored by your website data – values specific to the method; for samsung pay, these include version specifies the data structure being used by the merchant; should always be set to 1 until further notice required productid the service id obtained from the samsung pay partner portal required for partner verification; see step #8 under registering your domain for the w3c service merchantgatewayparameter this is the userid value registered with your pg required for gateway token mode in addition, userid should be set in the request parameter for mada token if a merchan request mada token, this field is mandatory as this filed should be included in the payload for mada token, there is a 15-character length limit paymentprotocol defaults to “protocol_3ds,” the only protocol currently supported by samsung pay optional allowedcardnetworks specifies the card brands/networks accepted by the merchant and supported by the pg required merchantname the name of the merchant to be displayed on the payment sheet; must be identical to the merchant name registered on the samsung pay partner portal required ordernumber unique value for merchant use as an external reference id optional isrecurring specifies transaction on subscription basis optional; default = false billingaddressrequired determines if a billing address must be filled-in by the user optional; default = false shown next are examples of the methoddata parameter for each of the supported token modes please note that samsung pay's w3c support for card brands is currently limited to mastercard, visa and american express discover is scheduled for support soon example – network token mode var methoddata = [ { supportedmethods ['https //spay samsung com'], data { 'version' '1', // always 1 until further notice 'productid' '2bc3e6da781e4e458b18bc', // service id from partner portal 'allowedcardnetworks' ['mastercard','visa'], 'merchantname' 'shop samsung demo ', // merchantname must be identical to merchant name on portal 'ordernumber' '1233123', } }] example – gateway token mode var methoddata = [ { supportedmethods ['https //spay samsung com'], data { 'version' '1', // always 1 until further notice 'productid' '7qr7h9ws1872bc3e6da781', // service id from partner portal 'merchantgatewayparameter' {"userid" "acct_ 17irf7f6ypzj7wor"}, 'allowedcardnetworks' ['mastercard','visa'], 'merchantname' 'shop samsung demo ', //merchantname must be identical with merchant name on portal 'ordernumber' '1233123', } }] step 4 fill out the transaction details parameter the details parameter contains information about the transaction there are two major components a total, which reflects the total amount and currency to be charged, and an optional set of displayitems that indicate how the final amount was calculated this parameter is not intended to be a line-item list, but is rather a summary of the order’s major components subtotal, discounts, tax, shipping costs, etc example var details = { displayitems [ { label "total of all items", amount { currency "usd", value "65 00" }, // us$65 00 }, { label "friends & family discount", amount { currency "usd", value "-10 00" }, // -us$10 00 pending true // the price is not yet determined } ], total { label "total", amount { currency "usd", value "55 00" }, // us$55 00 } } step 5 check eligibility to display samsung pay button if you do not support basic-card and you try to call show in step 6 when samsung pay or any other supportedmethod is not present on the device, the returned promise will reject with the following error domexception the payment method is not supported you can, however, check beforehand to see if the user has an available/supported method set up this is done with the canmakepayment method, which tells you whether the user has a payment method that can fulfill the current payment request example – canmakepayment const paymentrequest = new paymentrequest supportedpaymentmethods, transactiondetails, options ; // if canmakepayment isn’t available, default to assume the method is supported const canmakepaymentpromise = promise resolve true ; // feature detect canmakepayment if request canmakepayment { canmakepaymentpromise = paymentrequest canmakepayment ; } canmakepaymentpromise then result => { if !result { // the user does not have a supported payment method // todo redirect to traditional checkout flow return; } // todo the user has a payment - call show } catch err => { // todo either fall back to traditional checkout or call show } ; notebranded samsung pay buttons can be found on the [samsung pay developers][8] portal under the resources tab direct cdn links will be available soon step 6 call the show method to display the payment sheet the payment sheet can be activated by calling its show method this method invokes the browser’s native ui so the user can examine the details of the purchase, add or change the information, and submit it for payment a promise, indicated by its then method and callback function, resolves what will be returned when the user accepts or rejects the payment request example – show request show then function paymentresponse { // process paymentresponse here paymentresponse complete "success" ; } catch function err { console error "uh oh, something bad happened", err message ; } ; step 7 handle the paymentresponse once the user approves the payment request by verifying the payment option and shipping option if provided , the show method’s promise resolves, resulting in a paymentresponse object comprised of the following fields methodname string indicating the chose payment method e g , visa details dictionary containing information for methodname shippingaddress shipping address of the user, if requested shippingoption id of the selected shipping option, if requested payeremail email address of the payer, if requested payerphone telephone number of the payer, if requested payername name of the payer, if requested here, it’s important to remember that the response from the payment request api must be submitted by the merchant in accordance with the pg’s integration model and apis in all cases, the samsung pay response is encapsulated within the paymentresponse details parameter, which comprises the following fields paymentcredential – contains the payment credential information necessary for processing the transaction with the pg in network token mode, this field includes 3ds data in gateway token mode, it includes token information network token mode type use “s” version 1 0 0; standard for payment authentication aka mastercard securecode, verified by visa, and american express safekey data encrypted payload value gateway token mode reference token id reference status authorized or rejected/declined billingaddress – contains the billing address and related attributes for the cardholder, possibly including country [iso3166] alpha-2 code; canonical form is upper case for example, “us” addressline[n] most specific part of the address; can include a street name, a house number, apartment number, a rural delivery route, descriptive instructions, or a post office box number region top level administrative subdivision of the country; can be a state, a province, an oblast, or a prefecture city city/town portion of the address dependentlocality dependent locality or sub-locality within a city; fused for neighborhoods, boroughs, districts, or uk dependent localities postalcode postal code or zip code, also known as pin code in india sortingcode bank sorting code; for example, in the british and irish banking industries, the sort code is a six-digit number, is usually formatted as three pairs of numbers, for example 12-34-56, identifying both the bank and the branch where the account is held languagecode [bcp47] language tag for the address, in canonical form; used to determine the field separators and the order of fields when formatting the address for display organization organization, firm, company, or institution at this address recipient name of the recipient or contact person this member may, under certain circumstances, contain multiline information; for example, it might contain “care of” information phone telephone number of the recipient or contact person paymentinfo – contains the payment information, including card_last4digits last four digits of the card’s dpan cardbrand currently, either mastercard or visa ordernumber merchant’s unique external reference id supplied in the original request’s methoddata parameter if the user pays with a credit card using the basic-card method, then the details response returned directly to your website from the browser will contain cardholdername, cardnumber, expirymonth, expiryyear, cardsecuritycode, billingaddress example request show then paymentresponse => { var paymentdata = { // payment method string, e g “amex” method paymentresponse methodname, // payment details contains payment information details paymentresponse details /* request details depends on pg token mode network - e g , first data; or gateway - e g , stripe ---------------------------------------------------------|------------------------------------------------------| * gateway token mode |* network token mode | * “details” { |* “details { | * “paymentcredential” { |* “method” “3ds”, | * “reference” “tok_1asceoyf6ypzj7f8se6grp0i”, |* “paymentcredential” { | * “status” “authorized” |* “type” “s”, | * }, |* “version” “100”, | * |* “data” “long_encrypted_payload_value”, | * |* }, | *--------------------------------------------------------|------------------------------------------------------| * “paymentinfo” { * “card_last4digits” “1489”, * “cardbrand” “mastercard”, * “ordernumber” “1233123”, * “billingaddress” { * “country” “usa”, * “addressline” [“chhccy”, “hdyxych”], * “region” “ca”, * “city” “mountain view”, * “dependentlocality” “”, * “postalcode” “94043”, * “sortingcode” “”, * “languagecode” “en”, * “organization” “”, * “recipient” “”, * “phone” “” * } * } * } * */ }; return fetch ‘/validatepayment’, { method ‘post’, headers { ‘content-type’ ‘application/json’ }, body json stringify paymentdata } then res => { if res status === 200 { return res json ; } else { throw ‘payment error’; } } then res => { paymentresponse complete “success” ; }, err => { paymentresponse complete “fail” ; } ; } catch err => { console error “error, something went wrong”, err message ; } ; once payment information is received from samsung pay, the website should submit the payment information to the merchant’s pg for transaction processing the ui will show a spinner while the request takes place when a response is received, the website should call complete to close the ui the website is then free to show an order complete or order confirmation page for user feedback as previously mentioned, you can simplify integration of network tokens by passing the encrypted payload directly to your pg and letting it handle decryption in all cases, how you handle a submitted network token depends on the payment gateway refer to your particular pg’s documentation for details paymentoptions is an optional parameter in thepaymentrequest constructor depending on your particular requirements, you may want additional information, such as the user’s shipping address for physical goods purchased and contact details for guest users paymentoptions currently comprises the following requestpayername true if payer name is required; otherwise, false requestpayeremail true if payer email address is required; otherwise, false requestpayerphone true if payer telephone number is required; otherwise, false requestshipping true if shipping address is required; otherwise, false shippingtype available label options “shipping/pickup/delivery” for indicating to user; solely for display purposes example var options = { requestpayeremail false, requestpayername true, requestpayerphone false, requestshipping true, shippingtype "delivery" } noteif any of the elements listed above are set to true, the browser payment sheet is launched; otherwise, the samsung pay payment sheet is displayed putting it all together let’s assemble the various code blocks into a prototype to demonstrate the w3c payment request api in action function onbuyclicked { const samsung_pay = 'https //spay samsung com'; if !window paymentrequest { // paymentrequest api is not available - forwarding to legacy form based experience location href = '/checkout'; } // setup var supportedinstruments = [{ supportedmethods [ samsung_pay ], // 'https //spay samsung com' data { "version" "1", "productid" "2bc3e6da781e4e458b18bc", //service id from partner portal "allowedcardnetworks" ['mastercard','visa'], "ordernumber" "1233123", "merchantname" "shop samsung demo ", //merchant name in partner portal "merchantgatewayparameter" {"userid" "acct_17irf7f6ypzj7wor"}, "isrecurring" false, "billingaddressrequired" false, "paymentprotocol" "protocol_3ds" } }]; var details = { displayitems [{ label 'original donation amount', amount { currency 'usd', value '65 00' } }, { label 'friends and family discount', amount { currency 'usd', value '-10 00' } }], total { label 'total due', amount { currency 'usd', value '55 00' } }; var options = { requestshipping true, requestpayeremail true, requestpayerphone true, requestpayername true }; // initialization var request = new paymentrequest supportedinstruments, details, options ; // when user selects a shipping address request addeventlistener 'shippingaddresschange', e => { e updatewith details, addr => { var shippingoption = { id '', label '', amount { currency ‘usd’, value ‘0 00’ }, selected true}; // shipping to us is supported if addr country === 'us' { shippingoption id = 'us'; shippingoption label = 'standard shipping in us'; shippingoption amount value = '0 00'; details total amount value = '55 00'; // shipping to jp is supported } else if addr country === 'jp' { shippingoption id = 'jp'; shippingoption label = 'international shipping'; shippingoption amount value = '10 00'; details total amount value = '65 00'; // shipping to elsewhere is unsupported } else { // empty array indicates rejection of the address details shippingoptions = []; return promise resolve details ; { // hardcoded for simplicity if details displayitems length === 2 { details displayitems[2] = shippingoption; } else { details displayitems push shippingoption ; } details shippingoptions = [shippingoption]; return promise resolve details ; } details, request shippingaddress ; } ; // when user selects a shipping option request addeventlistener 'shippingoptionchange', e => { e updatewith details => { // there should be only one option do nothing return promise resolve details ; } details ; } ; // show ui then continue with user payment info request show then result => { // post the result to the server return fetch '/pay', { method 'post', credentials ‘include’, headers { 'content-type' 'application/json' }, body json stringify result tojson } then res => { // only if successful if res status === 200 { return res json ; } else { throw 'failure'; } } then response => { // you should have received a json object if response success == true { return result complete 'success' ; } else { return result complete 'fail' ; } } then => { console log 'thank you!', result shippingaddress tojson , result methodname, result details tojson ; } catch => { return result complete 'fail' ; } ; } catch function err { console error 'uh oh, something bad happened ' + err message ; } ; } document queryselector '#start' addeventlistener 'click', onbuyclicked ; refer to the official w3c integration specs for additional details and definition testing once you have the code saved and loaded, you’re ready to test be sure to test your website or test domain on a device running samsung internet browser and with the samsung pay wallet app already set up and ready to go in accordance with the prerequisites cited above if you use a separate subdomain for your test environment, be sure to add it as an eligible service domain for the service you configured under registering your domain for the w3c service remember that any/all subdomains for production must also be added to the service, up to a maximum of 10 service domains again, please note that samsung pay’s webpay api currently supports mastercard and visa only support for american express and discover is under development and will be available soon be sure to test using the samsung internet and chrome mobile browser apps to test select samsung pay as the payment method by clicking on the branded samsung pay button branded implementations or the samsung pay radio button standard w3c implementations this should launch the samsung pay payment sheet authenticate payment validate your results end to end isolate issues in the log, debug, and test again contact your samsung pay rm to coordinate assistance with troubleshooting recommended test cases check if the samsung pay is available in the payment option on the website verify samsung pay logo on browser sheet verify order summary on the payment sheet verify “edit” and “pay” buttons on payment sheet verify purchased item in the summary verify the billing address on the payment sheet change the billing address try to change the card in payment sheet when only one card is enrolled in samsung pay try to change the card when multiple cards is enrolled in samsung pay verify the payment amount verify the payment options verify the payment completion screen verify merchant name on the payment sheet verify merchant domain name on the payments sheet verify “cancel” and “pay” buttons on browser sheet try to make payment with large amount larger than max allowed amount and verify the behavior make a payment using samsung pay with a card already added for the merchant’s website basic-card verify transaction notification after w3c purchase verify transaction notification after refund set payment options for shipping address and verify that browser payment sheet launches and captures shipping address input/changes by user verify that the shipping cost is updated based on a shipping address change and is reflected in the updated total amount release once your tests are successful and you are satisfied with the results, take the following steps to ready your integrated with samsung pay website for release go to the samsung pay developers portaland create a new release service sharing identical attributes with the service you successfully tested a click on service management, then click create new service b select for release pictured , then click next c select w3c mobile web payments as the service type, then click next d enter a "release" service name and select "united states" as the service country e select united states as the service country f select your payment gateway from the drop-down menu, then click connect with for gateway token mode or provide a valid csr for network token mode g enter your service domain and click add for each additional domain name, click add remember, when entering domain names on the portal, do not include a "https"//" prefix h confirm your agreement with the terms and conditions, then click next retrieve the service id from the service details page and enter copy-paste it into your website's methoddata object in place of the current testing service id when your service is approved by your samsung pay rm — as indicated in the status column of your service management dashboard — you're ready to release your integrated website to the public send queries concerning service package approval to webpayment@samsungpay com
Develop Samsung Pay
doc2 1 samsung pay integration life cycle partner onboarding is the formal process through which third-party organizations—such as banks, card issuers, merchants, payment gateways, or fintechs—are authorized and enabled to integrate their services with the samsung pay ecosystem let’s first understand the samsung pay integration lifecycle, structured into the five key phases based on the process you’ve outlined this will help developers, project managers, and stakeholders understand the full journey of integrating samsung pay into their application integrating samsung pay involves the following steps that guide partners—from registration to release—ensuring a secure, compliant, and user-friendly payment experience register as a member objective gain access to samsung pay sdks, documentation, and services create a samsung developer account on the samsung pay developer portal complete the partner registration process as a merchant, issuer, or developer agree to legal terms and samsung’s partnership requirements test and validate objective ensure your integration is secure, functional, and user-ready key areas to test push provisioning performance transaction processing and response handling ui/ux compliance with samsung branding and interaction guidelines samsung provides sandbox environments and qa support during this phase release objective launch your samsung pay-integrated service publicly submit the final version of your integration for approval through the developer portal receive samsung certification or go-live approval go live and begin monitoring real-world usage, analytics, and feedback post-launch, you can track adoption gather user feedback update sdks as needed summary of samsung pay integration life cycle phase objective outcome register gain developer access to samsung pay become an approved partner test validate functionality and compliance issue-free, certifiable integration release submit for approval and go live production-ready payment solution
Develop Samsung Pay
docfaqs and troubleshooting 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 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, 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 environment part and follow guide for android r os targetsdkversion 30 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 ' note the default pg name is 'none default ' 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 same check the app’s package name from samsung pay portal > my projects > app management > click on a specific app name 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 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 please double check with below limitations app package name 50 byte app version 20 length app signature 100 length 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 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 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 i am getting spay_not_approved_service 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 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 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 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 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 i am getting error_invalid_payload 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 i am getting error_card_not_supported 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 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 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 i am getting unknown_error_code error 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 description or comment to explain what kinds of issue you are having as possible as detail for example what is the issue? which apis used for your test scenario? what is expected response from the api and what is actual response? dumpstate log to take dumpstate log please follow the steps from here 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
Develop Samsung Pay
doc4 3 proceed to release your app when you finish the testing and are ready to release your app, request for ‘approved’ status for your service id from samsung pay developer portal for push provisioning, you need to upload your release version of the apk go through the register a partner app guide to know how to upload your app in samsung pay developer portal
We use cookies to improve your experience on our website and to show you relevant advertising. Manage you settings for our cookies below.
These cookies are essential as they enable you to move around the website. This category cannot be disabled.
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.
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.
These cookies gather information about your browser habits. They remember that you've visited our website and share this information with other organizations such as advertisers.
You have successfully updated your cookie preferences.