Search

Filter

  • Content Type
Samsung Wallet 100
Sorry, no results
found for "Samsung Wallet" on the website

Develop Samsung Blockchain

doc

Blockchain on Mobile

blockchain on mobile expansion of blockchain technology in the last couple of years, the number of blockchain services and products continues to sky rocket the fact that there is no centralized server needed makes it very attractive for many companies to jump into the blockchain business decentralized apps dapps and wallets are thriving to become part of our everyday life, yet, often face usability and scalability obstacles creating a wallet to manage cryptocurrencies, or sending and receiving a cryptocurrency is not an easy task for normal users user interaction is even harder when a user needs or wants to use a desktop wallet or a separate hardware wallet for key management interestingly, many of the decentralized apps look very similar to the mobile apps that we use today, except for the fact that in the background, instead of using a centralized and private server, dapps run on the blockchain network this leads us to conclude that in order to speed up the expansion of the blockchain ecosystem, it is critical to safely bring the blockchain technology onto mobile inevitable security vulnerabilities when bringing blockchain technology onto mobile when bringing blockchain technology onto mobile, there are inevitable security threats and vulnerabilities security measures to keep blockchain technology secure, yet transparent, etc all have been integrated throughout the blockchain technology thus, the main concern is not the blockchain technology itself, but rather the mobile environment that the blockchain technology is executed in because the wallet is the interface that signs and submits the transaction, it is often the main target for hackers since it is impossible to reverse a transaction that has been submitted, it is never enough to emphasize the importance of keeping and using the private key in a safe environment possible attacks to extort the private key include malicious software that physically looks exactly the same as the screen where the user needs to enter the 12 to 24 mnemonic words to recover a wallet or create and show a malicious screen that suddenly asks the user to enter such crypto secrets in order to proceed with signing a transaction phishing, even crypto secrets, can all lead to the user losing the private key, an access to all the cryptocurrencies, and cryptoassets the display can also be maliciously modified so that user confirms and signs a fake transaction for example, the address of the recipient displayed on the user’s screen could be maliciously modified so that user sends the cryptocurrency to the attacker, not to the intended recipient without any security measures to check the integrity of the transaction by the wallet, the user can sign and submit the transaction unconsciously these malicious attacks can result in the user losing a tremendous amount of cryptocurrencies or sending a crypto-asset to the attacker worst of all, the nature of blockchain makes it hard to track the attackers, and the user may never find out who caused the attack and stole the crypto assets top qualities of a “good” blockchain wallet to address these security threats and vulnerabilities mentioned, samsung blockchain keystore thoroughly evaluated and prioritized various security features, and came with the conclusion that the following qualities need to be supported in order to be a “good” blockchain wallet ① secure display in the blockchain network, the sensitive information in the transaction should never be tampered with sensitive information, especially used for user’s confirmation, must be shown on a safe and secure display ② secure touch what the user enters into the screen should be protected, and guaranteed to be not spoofed extremely sensitive information, such as the 12 to 24 mnemonic words that are equivalent to the user’s private key, or entering pin as a means of user authentication, all must be done in a secure environment ③ secure storage the cryptographic secrets to sign a transaction implies both user’s identity and user’s confirmation hence, they must be completely isolated from other normal apps and such environment that can be susceptible to malwares ④ secure computation the environment where the user is creating a new wallet, or signing a transaction, etc must all be executed in a secure environment these should not be mixed with apps running in ree rich execution environment , where android os runs and also the environment that is vulnerable to remote attacks when developing samsung blockchain keystore, security qualities mentioned above were taken into consideration and inherently applied into the service keeping these top qualities defined by samsung blockchain keystore team in mind, we will cover the overall architecture of samsung blockchain keystore and look into what makes samsung blockchain keystore safe and different from other wallets

https://developer.samsung.com/blockchain/keystore/understanding-keystore/blockchain-on-mobile.html

Develop Samsung Pay

doc

Test Cards on Samsung Pay

test cards on samsung pay overview this guide explains test cards that can be registered on samsung pay's testing android application package stg apk these test cards can only be registered on the stg apk and also require a valid card registration on the wallet application’s production environment features after installing the stg apk, you can register the card information below to test online payments test card 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 2304 8218 credit 12/25 736 4622 9431 2304 8226 credit 12/25 454 mastercard card number card type expiry date cvv/cvc2 5186 1516 5001 2004 credit 12/25 123

https://developer.samsung.com/pay/web/test-card.html

Develop Samsung Blockchain

api

ScwDeepLink

package class tree deprecated index help com samsung android sdk coldwallet interface scwdeeplink public interface scwdeeplink links for the samsung blockchain keystore field summary fields modifier and type field and description static java lang string change_pin link to the page which change pin in the keystore static java lang string display_wallet link to the page which displays the mnemonic words in the keystore static java lang string galaxy_store link to the app updating page in the galaxy store static java lang string main link to the main page in the keystore static java lang string notice_content link to the page which shows a notice in the keystore static java lang string reset link to the page which resets hd wallet seed in the keystore field detail main static final java lang string main link to the main page in the keystore see also constant field values change_pin static final java lang string change_pin link to the page which change pin in the keystore see also constant field values reset static final java lang string reset link to the page which resets hd wallet seed in the keystore see also constant field values display_wallet static final java lang string display_wallet link to the page which displays the mnemonic words in the keystore see also constant field values notice_content static final java lang string notice_content link to the page which shows a notice in the keystore see also constant field values galaxy_store static final java lang string galaxy_store link to the app updating page in the galaxy store see also constant field values

https://developer.samsung.com/blockchain/keystore/api-reference/com/samsung/android/sdk/coldwallet/ScwDeepLink.html

FAQ security, blockchain, mobile

doc

FAQ

faq 1 what can users do with samsung blockchain keystore? with samsung blockchain keystore preloaded on select galaxy devices, users can now easily create a key storage in the secure file system for blockchain transactions users can run samsung blockchain keystore to check the 12 mnemonic words that correspond to the root seed that is used to derive both public and private keys when using a decentralized app dapp or cryptocurrency wallet that have integrated samsung blockchain keystore sdk, users will be able to confirm their transactions on a secure screen and sign the transaction with a private key 2 what happens if a user switches from a non-samsung blockchain keystore-supported device to a samsung blockchain keystore-supported device? if the dapp is integrated with a wallet that supports bip39-standard hd-wallet hierarchical deterministic wallet , such as metamask, dapps will need to make sure that users have saved the 12 to 24 mnemonic words from the wallet afterwards, users can restore the same wallet on samsung blockchain keystore by entering the 12 to 24 mnemonic words however, simply installing the same dapp or using smart switch from a non-samsung blockchain keystore supported device to a supported one will not move the user’s account directly 3 how does the authentication method work? personal identification number pin and biometrics authentication like fingerprint are all executed on samsung devices, and are not dependent on any type of network samsung blockchain keystore will authenticate users via pin or biometrics when a user’s confirmation is needed, such as signing a transaction 4 how is the key pair generated? samsung blockchain keystore generates the key pair on the device itself and safely stores them on the device samsung blockchain keystore does not rely on other network or third party to generate these keys 5 what are mnemonic words? mnemonic words are compatible to bip-39 standard and is the root to creating public and private keys users can check their mnemonic words, also known as recovery phrase, in samsung blockchain keystore settings the recovery phrase is the only way a user can recover the wallet when a device is lost or stolen 6 what is tui? trusted user interface allows users to make an input and show display safely, in a trusted execution environment tee supported by samsung knox a mobile security platform samsung blockchain keystore leverages this tui to help users to enter a pin and confirm transactions with greater security 7 what should i do if i get an error code, error_package_signature_verification_failed? it means your app does not have the authorization to access samsung blockchain keystore developers can use developer mode to bypass the app verification and enable apis however, for your release version, an api key, issued by samsung blockchain keystore team, will need to be included in your app to work properly 8 how can i send a signed transaction? sending a signed transaction is not in the scope of samsung blockchain keystore developers will need to setup their own nodes or use other public nodes 9 can i test samsung blockchain keystore by downloading it from galaxy store? no, samsung blockchain keystore is preloaded on selected devices only if your device is not supported, then you won’t be able to find it in the galaxy store either developers will need to test and integrate on the supported devices, or try out the remote test lab in samsung developers site to experience devices needed for samsung blockchain keystore sdk integration 10 what is the purpose of a seed hash? a seed hash aims to help developers distinguish if a user has setup samsung blockchain keystore and whether the root seed has been changed or not every time a root seed or a wallet is created, a random string, or a “seed hash” value will be created and returned to the developers this is not related to the contents of the seed, but developers can use the seed hash to check if a user’s root seed has been changed if the root seed has been changed due to user deleting and re-creating a wallet, then the developers will need to get user’s address again from samsung blockchain keystore and link it to your android app, since a different root seed implies a different address 11 is there a plan to support other cryptocurrencies as well as expand supported regions? yes, we plan to support more cryptocurrencies and expand supported regions in the near future

https://developer.samsung.com/blockchain/keystore/keystore-sdk/faq.html

Develop Samsung Blockchain

doc

What Makes Keystore Unique

what makes samsung blockchain keystore unique? the main function of a general keystore is to generate keys and store them in a safe place in the blockchain industry, a wallet can use various open source libraries to generate the keys other option could be integrating with a hardware wallet unlike android keystore, which is used for general purpose, the name, “samsung blockchain keystore” implies that samsung blockchain keystore is a keystore that is dedicated to support blockchain transactions keeping this in mind, let’s look at some features that make samsung blockchain keystore unique from other keystores support blockchain-specific algorithms ecdsa with secp256k1 curve for bitcoin and ethereum algorithms used to generate keys and signatures are different by cryptocurrency for example, ecdsa elliptic curve digital signature algorithm with secp256k1 curve is needed for bitcoin and ethereum samsung blockchain keystore supports algorithms specifically used for such cryptocurrency transactions parse blockchain transactions samsung blockchain keystore parses blockchain transactions in a safe environment, and show the transaction details to the user a normal keystore usually does not parse any information to be signed, and focus on signing only secure display and secure touch trusted user interface trusted user interface tui is a general term that includes trusted display and trusted touch that are accessible by only the authorized trusted applications that run in the tee samsung blockchain keystore leverages tui in tee to display sensitive information and protect user’s input for instance, normal apps running in ree could maliciously show the recipient’s address or transfer amount that are different from what is actually included in the transaction but because samsung blockchain keystore leverages tee to use ta to parse the transaction details and show the actual details on tui, where the information can never be tampered with, user will be able to distinguish maliciously modified transactions the following are tui screens run by samsung blockchain keystore [pin] pin input screen is used to 1 register pin and 2 confirm pin when user authentication is needed when creating or importing a wallet, user needs to set up pin first user will be asked to enter the registered pin when making transactions and checking recovery phrase again user’s input of pin in all these cases are run in an isolated environment, by tui [recovery phrase] recovery phrase that represent the root seed and countless number of private keys, hence the secure display to show this recovery phrase cannot be emphasized enough [double checking recovery phrase] to complete creating a wallet, user must enter a few random words of the recovery phrase to confirm that user has written down the 12 words in a safe place user’s input is protected here [enter recovery phrase] when importing a wallet that was created from a different wallet, like a hardware wallet or samsung blockchain keystore on a different device, user has to enter the 12 to 24 words likewise, what user enters is protected via tui, including the keyboard [transaction confirmation] regarding transaction confirmation, after parsing the transaction by a trusted application in tee, samsung blockchain keystore will show selected sensitive transaction details on tui the sensitive information differs depending on the blockchain platform, but most of them focus on the amount to transfer, recipient address and fee secure computation trusted execution environment trusted applications and trusted user interface are all run in trusted execution environment, an isolated environment this means normal applications and malware that run in rich execution environment ree will have no access to any information in tee likewise, samsung blockchain keystore will be able to prevent users from confirming maliciously modified transaction user’s manual confirmation in order to sign a transaction via samsung blockchain keystore, the user must manually confirm by clicking confirmation button and enter pin or authenticate with a fingerprint a normal keystore usually completes its function by generating a key and making a digital signature but samsung blockchain keystore prioritizes the user confirmation via a tui feature in the belief that user’s explicit agreement is the most critical step in signing a transaction hence, it is impossible for malicious apps to acquire a user’s signature from the background or sign a transaction without the user knowing it parse blockchain transactions samsung blockchain keystore parses blockchain transactions in a safe environment, and show the transaction details to the user a normal keystore usually does not parse any information to be signed, and focus on signing only support algorithms for signatures keys are generated differently depending on the type of algorithm used for example, ecdsa elliptic curve digital signature algorithm is applied for bitcoin and ethereum some cryptocurrencies consume a different algorithm as a standard because samsung blockchain keystore is specific to blockchain, algorithms to generate keys and sign blockchain transactions are supported true random number generator trng we saw that a keystore generates keys but whether the randomness of the key is guaranteed so that the key cannot be predicted in any other way is another question generating this random key in a software environment is known to have security vulnerabilities samsung blockchain keystore leverages a true random number generator trng feature from the device to guarantee randomness from a hardware level safe key storage once the keys are generated, where and how safely the keys are stored is important hardware wallet was originally designed with the purpose to store the keys in a separate environment similarly, samsung blockchain keystore stores the encrypted root seed that generates numerous keys, in the secure file system, where normal apps will not have access to nor be able to decrypt the file

https://developer.samsung.com/blockchain/keystore/understanding-keystore/what-makes-keystore-unique.html

FAQ security, blockchain, mobile

doc

FAQ

faq q01 what is the difference between samsung blockchain sdk and samsung blockchain keystore sdk? a samsung blockchain platform sdk is a superset of sdks it focuses to offer a friendly blockchain solution especially for mobile developers you can use keystore sdk if you already have dapp development experience when you need a hardware wallet but still, you may need a deeper knownledge to use it so that platform sdk may be a better option for beginners the main difference is the existence of network module samsung blockchain platform sdk is available to communicate with an external blockchain node providing a payment solution also samsung blockchain platform sdk has cucumber web-based dapp browser which is built using android webview so it is helpful to reduce costs to build your dapp for mobile environment q02 what would be a good choice among sdks? a samsung blockchain sdk the blockchain dapp developer needs a simple payment solution, dapp without handset limitation, integrated with various cold wallets, and a legacy player who already has an experience with e-commerce ex online shopping app especially it can be a better option for web based dapp partners who has a plan to integrate the service into mobile environment samsung blockchain keystore sdk for dapp partners who needs a key storage to directly handle it q03 which coin is supported? a it supports ethereum and tron you can see erc20, erc721 and trc10, trc20 item information when it follows the specification q04 does it have any device limitations / restrictions? a no samsung blockchain platforms sdk doesn’t have any device or region dependency but, please note that it needs a cold wallet so that it follows the cold wallet’s restriction for example, you can use your dapp integrated with sdk on any device released by samsung when you connect to external cold wallet but if you use the samsung keystore, it has to be same with the keystore’s restriction q05 what should i do using keystore via platform sdk? a you need an api key for getting a permission to access keystore please refer request for api key note that, in case of integrating ledger devices, you don't need this process q06 what should i do when i get the following build error "failed to transform artifact 'bcprov-jdk15on jar"? a add the following to your project's gradle properties android jetifier blacklist=bcprov

https://developer.samsung.com/blockchain/platform/platform-sdk/faq.html

Develop Samsung Pay

api

SamsungPay

overview package class tree index help package com samsung android sdk samsungpay v2 class samsungpay java lang object samsungpaybase com samsung android sdk samsungpay v2 samsungpay public final class samsungpay extends samsungpaybase this class provides apis to get the samsung pay status on the device also, this class provides apis to activate samsung pay on the device partner apps must check the samsung pay status on the device before performing any card management or payment operation since api level 1 1 constructor summary constructors constructor description samsungpay android content context context, partnerinfo partnerinfo constructor to get the samsungpay instance the caller should set the valid serviceid in partnerinfo method summary all methodsinstance methodsconcrete methods modifier and type method description void activatesamsungpay api to bring the samsung pay app to a state in which cards can be added samsung pay might be either in stub only state or samsung account is not signed in state partner app checks the samsung pay status with getsamsungpaystatus statuslistener api if the status is #spay_not_ready and #extra_error_reason is #error_spay_setup_not_completed, partner app can call this api to launch samsung pay and user can sign in to the app void getsamsungpaystatus statuslistener listener api to get the samsung pay status on the device partner issuers, merchants, and so on applications must call this api to check the current state of samsung pay before doing any operation void getwalletinfo list<string> keys, statuslistener listener api to get the requested wallet information from samsung pay partner app can use this information to uniquely identify the user and samsung pay app on a particular device void gotoupdatepage api to go to samsung pay update page partner app checks the samsung pay status with getsamsungpaystatus statuslistener api if the status is #spay_not_ready and #extra_error_reason is #error_spay_app_need_to_update, partner app can call this api to go to update samsung pay app if samsung pay app version is same or bigger than 2 1 00, it goes to "about samsungpay" menu if samsung pay app version is lower than 2 1 00 or kr device, it launches samsung pay app main screen methods inherited from class java lang object equals, getclass, hashcode, notify, notifyall, tostring, wait, wait, wait constructor details samsungpay public samsungpay android content context context, partnerinfo partnerinfo constructor to get the samsungpay instance the caller should set the valid serviceid in partnerinfo partnerinfo is passed to samsung pay for partner verification context ct = activity; // or context ct = service; // set the serviceid which is assigned by the samsung pay developer during on boarding string serviceid = "sampleserviceid"; bundle bundle = new bundle ; bundle putstring samsungpay partner_service_type, samsungpay servicetype inapp_payment tostring ; partnerinfo pinfo = new partnerinfo serviceid, bundle ; samsungpay samsungpay = new samsungpay ct, pinfo ; parameters context - activity context or service context partnerinfo - partner information throws nullpointerexception - thrown if parameters are null since api level 1 1 method details getsamsungpaystatus public void getsamsungpaystatus statuslistener listener api to get the samsung pay status on the device partner issuers, merchants, and so on applications must call this api to check the current state of samsung pay before doing any operation // set the serviceid which is assigned by the samsung pay developer during on boarding string serviceid = "sampleserviceid"; bundle bundle = new bundle ; bundle putstring samsungpay partner_service_type, samsungpay servicetype inapp_payment tostring ; partnerinfo pinfo = new partnerinfo serviceid, bundle ; samsungpay samsungpay = new samsungpay context, pinfo ; samsungpay getsamsungpaystatus new statuslistener { @override public void onsuccess int status, bundle data { // success case if status == spay_ready { log d tag, "samsung pay is ready on the device" ; // perform your operation } else if status == spay_not_ready { // samsung pay is supported but not fully ready // if extra_error_reason is error_spay_app_need_to_update, // call gotoupdatepage // if extra_error_reason is error_spay_setup_not_completed, // call activatesamsungpay } else if status == spay_not_allowed_temporally { log d tag, "samsung pay is not allowed temporally" ; // if extra_error_reason is error_spay_connected_with_external_display, // guide user to disconnect it } else { // samsung pay is not supported on this device log d tag, "device does not support samsung pay" ; } } @override public void onfail int errorcode, bundle errordata { log e tag, "onfail callback is called, errorcode " + errorcode ; // to get more reason of the failure, // check some extra error codes in the errordata bundle such as samsungpay extra_error_reason if provided } } ; parameters listener - callback through which the result is provided on success, samsung pay status code is provided via statuslistener onsuccess int status, bundle data if samsung pay is ready to be used, samsungpay#spay_ready will be returned otherwise, samsungpay#spay_not_ready or samsungpay#spay_not_supported or samsungpay#spay_not_allowed_temporally can be returned with samsungpay#extra_error_reason from bundle also, partner can get extra information from bundle data bundle keys if provided bundle values #extra_country_code device country code iso 3166-1 alpha-2 #extra_member_id string memberid for korean issuers only on any failure, the failure code is provided via statuslistener onfail int errorcode, bundle errordata note please refer spaysdk common_status_table in detail throws nullpointerexception - thrown if the callback passed is null since api level 1 1 gotoupdatepage public void gotoupdatepage api to go to samsung pay update page partner app checks the samsung pay status with getsamsungpaystatus statuslistener api if the status is #spay_not_ready and #extra_error_reason is #error_spay_app_need_to_update, partner app can call this api to go to update samsung pay app if samsung pay app version is same or bigger than 2 1 00, it goes to "about samsungpay" menu if samsung pay app version is lower than 2 1 00 or kr device, it launches samsung pay app main screen // set the serviceid which is assigned by the samsung pay developer during on boarding string serviceid = "sampleserviceid"; bundle bundle = new bundle ; bundle putstring samsungpay partner_service_type, samsungpay servicetype inapp_payment tostring ; partnerinfo pinfo = new partnerinfo serviceid, bundle ; samsungpay samsungpay = new samsungpay context, pinfo ; samsungpay gotoupdatepage ; since api level 1 2 activatesamsungpay public void activatesamsungpay api to bring the samsung pay app to a state in which cards can be added samsung pay might be either in stub only state or samsung account is not signed in state partner app checks the samsung pay status with getsamsungpaystatus statuslistener api if the status is #spay_not_ready and #extra_error_reason is #error_spay_setup_not_completed, partner app can call this api to launch samsung pay and user can sign in to the app // set the serviceid which is assigned by the samsung pay developer during on boarding string serviceid = "sampleserviceid"; bundle bundle = new bundle ; bundle putstring samsungpay partner_service_type, samsungpay servicetype inapp_payment tostring ; partnerinfo pinfo = new partnerinfo serviceid, bundle ; samsungpay samsungpay = new samsungpay context, pinfo ; samsungpay activatesamsungpay ; since api level 1 1 getwalletinfo public void getwalletinfo list<string> keys, statuslistener listener api to get the requested wallet information from samsung pay partner app can use this information to uniquely identify the user and samsung pay app on a particular device // set the serviceid which is assigned by the samsung pay developer during on boarding string serviceid = "sampleserviceid"; bundle bundle = new bundle ; bundle putstring samsungpay extra_issuer_name, "issuer name" ; bundle putstring samsungpay partner_service_type, samsungpay servicetype app2app tostring ; partnerinfo pinfo = new partnerinfo serviceid, bundle ; samsungpay samsungpay = new samsungpay context, pinfo ; // bundle keys added to get wallet information from samsung pay // this information can be delivered to the partner server for eligibility check arraylist&#60string&#62 keys = new arraylist<> ; keys add samsungpay wallet_user_id ; keys add samsungpay device_id ; samsungpay getwalletinfo keys, new statuslistener { @override public void onsuccess int status, bundle walletdata { // log d tag, "dowalletinfo onsuccess callback is called" ; // for visa, deviceid can be set to "clientdeviceid" as defined by visa string deviceid = walletdata get samsungpay device_id ; // for visa, walletuserid can be set to "clientwalletaccountid" as defined by visa string walletuserid = walletdata get samsungpay wallet_user_id ; } @override public void onfail int errorcode, bundle errordata { log e tag, "onfail callback is called, errorcode " + errorcode ; // to get more reason of the failure, // check some extra error codes in the errordata bundle such as samsungpay extra_error_reason if provided } } parameters keys - key list to get wallet information if the list is empty, all possible key values are returned the possible keys are #wallet_dm_id #device_id #wallet_user_id listener - callback through which the result is provided on success, statuslistener onsuccess int status, bundle data is invoked with wallet information the success code can be one of the following codes with bundle data status bundle keys bundle values usage vts mdes #error_none samsungpay#wallet_dm_id string device management id n/a paymentappinstanceid = device_id + padding "00" + wallet_dm_id *if you need 'paymentappinstanceid', you can generate it as above samsungpay#device_id string device id clientdeviceid samsungpay#wallet_user_id string wallet user id clientwalletaccountid on any failure, the error code is provided via statuslistener onfail int errorcode, bundle errordata note please refer spaysdk common_status_table in detail throws nullpointerexception - thrown if parameters are null since api level 1 2 samsung electronics samsung pay sdk 2 22 00 - nov 19 2024

https://developer.samsung.com/pay/api-reference/com/samsung/android/sdk/samsungpay/v2/SamsungPay.html

Develop Samsung Pay

doc

Outbound to Partner

outbound to partner general contract base url base url for outbound apis to be provided by the partner during the onboarding process security mutual ssl is required common headers header name type validation description request-id uuid required unique identifier for the request partner-id uuid required unique identifier that is provided to partner during onboarding response-id uuid required request-id echoed back in the response headers event notification notify partner for events request post /notifications body event regid description registration id type uuid validation required example event type description event type type enum refer to event types and errors for details validation required example event error description more information about the failure type enum refer to event types and errors for details validation optional example event desc description additional description of the event type string validation optional example user description container for user information type object validation conditional will be present for payment cards example user id description samsung account id type string validation required example emailmatches description is true if the email provided in the registration request matches with samsung account email type boolean validation conditional it is present only if an email was provided in the registration request example phonematches description is true if the phone number provided in the registration request matches with device phone number type boolean validation conditional it is present only if a phone number was provided in the registration request example device description container for device information type object validation conditional will be present for payment cards example device id description device id type string validation required example device imeilast4 description last 4 of device imei type string size 4 validation optional example device seriallast4 description last 4 of device serial number type string size 4 validation optional example device locale country description device country code type countrycode validation optional example wallet description container for wallet information type object validation conditional will be present for payment cards example wallet id description wallet id type string validation required example event types and errors type error description wa_ready wallet app is ready for provisioning wa_provisioned indicates card was successfully provisioned into the wallet wa_provision_failure indicates provisioning failed for some unknown reason wa_provision_failure card_already_present indicates card is already present response status http/1 1 200 ok header name value content-type application/json body card data encrypteddata description encrypted pan data that will be returned to the device to provision the card type string size 65536 validation conditional required if card data was not provided in the registration request example example post /notifications { "event" { "regid" "395ce2e29485442cbd9bacdc77105126", "type" "wa_ready" }, "emailmatches" true, "phonematches" true, "user" { "id" "rcsm3gwjt9mxgfwy5sg123" }, "wallet" { "id" "gpccugejs9giih8zch1111" }, "device" { "id" "mtuxmte5mdawmjawmdm1n999", "imeilast4" "6166", "locale" { "country" "us" }, "seriallast4" "4934" } } http/1 1 200 ok { "card" { "data" { "encrypteddata" "*****" } } }

https://developer.samsung.com/pay/save2pay/api-outbound-to-partner.html

Develop Samsung Blockchain

doc

Overview

samsung blockchain keystore sdk essential contents samsung blockchain keystore sdk v1 6 0 | dec 12, 2023 431 47 kb api reference v1 6 0 160kb release note programming guide sample application 340 78kb overview samsung blockchain keystore puts consumers in control of their data by providing a platform to consolidate and easily manage private information and digital keys with vaultlike security samsung blockchain keystore is isolated within the samsung knox trustzone and protected by defense-grade trusted execution environment tee software to ensure complete security, the private key and information located in the samsung blockchain keystore are never saved to a samsung or external cloud, nor is it seen by the devices’ android os this allows samsung blockchain keystore to provide security unlike ever before, protecting information from data breaches, malware, or other threats the samsung blockchain keystore stores and processes private data to allow create, store, manage, and backup of a private key, including the ability to import already generated private keys from third-party applications this can be protected through a preset mandatory pin, with the option of further protection through fingerprint authentication authorization of digital signatures for use with your android app and services that require a private key for stronger security during encrypted transactions or purchases the facilitation of a trusted user interface trusted ui ensures the information exchanged between trusted applications and consumers that can’t be accessed or modified by any malware or unauthorized application enabling cryptocurrency transactions please refer to keystore sdk restrictions section for more details integration process api key will be issued after the internal team’s review it may take several weeks to complete the review process if there are many submissions an additional dapp partnership is required for listing on the samsung blockchain wallet please refer to the getting started section in the programming guide for more details in each step benefits samsung blockchain keystore sdk allows your android dapp to communicate directly with samsung blockchain keystore, a preloaded feature on selected galaxy devices by integrating samsung blockchain keystore sdk into your android app, you can leverage the following get blockchain address to link to the samsung blockchain keystore developers can link user’s blockchain address like a user’s account with the address returned from samsung blockchain keystore, developers can check and show users how much cryptocurrency balance is in the account as well as view the transaction history samsung blockchain keystore supports bip-39 compatible hd hierarchical deterministic wallet – a standard tree structure, represented by derivation paths developers can use samsung blockchain keystore api to enter an hd path samsung blockchain keystore will derive the address from the public key that corresponds to the hd path so developers can simply receive and utilize the address in return sign a cryptocurrency transaction developers can use samsung blockchain keystore api to request the samsung blockchain keystore to sign a cryptocurrency transaction samsung blockchain keystore will show the requested transaction to the user on a secure screen called, trusted user interface tui , executed in the trusted execution environment tee once the user checks the transaction information and confirms the transaction with a pin or a biometric authentication like fingerprint, samsung blockchain keystore will sign the transaction with a private key derived from the root seed stored in the secure file system check samsung blockchain keystore status developers can use an api provided by the samsung blockchain keystore to check if a user is ready to use samsung blockchain keystore if the user has not created a wallet yet, developers can direct the user to create a new wallet to leverage samsung blockchain keystore features when a user chooses “create a wallet”, it implies that a root seed is created and stored safely in the secure file system the user can also “import a wallet” by entering mnemonic words created from a different wallet, thereby restoring the root seed samsung blockchain will check the existence of a root seed and return the status value

https://developer.samsung.com/blockchain/keystore/overview.html

Develop Samsung Blockchain

doc

Release Note

release note dec 29, 2023 introduction release version 1 2 03 release date dec 29, 2023 release contents download contents in here description of content are below sdk libraries provides samsung blockchain platform sdk libraries in aar format documents api references for more information about samsung blockchain platform apis, see api reference programming guide programming guide includes getting started, using the sblockchain class, explanation on how to implement features and glossary samples sample application sample application aerowallet includes most functions supported by samsung blockchain platform sdk codelab contents create shopping application with samsung blockchain platform sdk and pay using ethereum network project files and instruction guide is also supported [developing a simple blockchain payment application] change history samsung blockchain platform sdk v1 2 03 new update added support for android 14 compatible with latest version of samsung blockchain keystore sdk samsung blockchain platform sdk v1 2 02 support for two new test networks added support for test networks goerli and sepolia samsung blockchain platform sdk v1 2 01 bug fix fix "it's not samsung device" ssdkunsupportedexception with android 12 devices samsung blockchain platform sdk v1 2 00 support for eip-1559 transactions support added for ethereum eip-1559 transactions on both samsung blockchain keystore and external wallet ledger nano x and s to facilitate sending eip-1559 transactions, new gas price estimation apis have also been introduced for estimating basefee and priorityfee s support for evm-compatible networks support added for transacions on the following evm-compatible blockchain networks klaytn binance smart chain polygon avalanche c-chain fantom samsung blockchain keystore required version for support element version application version 1 3 06 5 or higher sdk version 1 5 1 or higher samsung blockchain platform sdk v1 1 01 support for eip-155 transactions support added for ethereum eip-155 compliant transaction on both samsung blockchain keystore and external wallet ledger nano x and s samsung blockchain keystore required version for support element version application version 1 3 05 2 or higher sdk version 1 5 1 or higher samsung blockchain platform sdk v1 1 00 support tron native tronservice is added for account management, transaction management trx, trc10, trc20 and smart contract call is supported new payment ui for tron is added both sign methods for normal transaction and personal message are supported support tron signing with keystore support tron signing with external cold wallet external cold wallet integration is supported currently it supports nano x, nano s by ledger update cucumber update web3 js version to 1 2 2 tronweb provider is added fix bugs 2020 06 01 sample application - aero wallet "send to smart contract error" bug fixed samsung blockchain platform sdk v1 0 00 samsung blockchain platform sdk first release samsung blockchain platform sdk sdk version 1 0 00 | oct 29, 2019 | 674 42kb

https://developer.samsung.com/blockchain/platform/release-note/release-note.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.