This chapter covers user-initiated card addition. Select one link method, generate the link on a trusted system, and expose it through an approved Add to Samsung Wallet entry point.
The approved flow must collect or authenticate user input before resolving the card.
A predefined action in adata.
Request Action and an onboarding-approved Action Data configuration.
Do not select a method solely to shorten the URL. Consider where card data is created, whether a link may be forwarded, how the user is resolved and which inbound APIs the partner can operate securely.
Decision sequence
Start with Data Transmit Link if the complete card instance can be generated for the current user and placed in a short-lived cdata token.
Use Data Fetch Link if Samsung Wallet must resolve an opaque refId against the partner server.
Use Data Action Link only when the use case and action are agreed during onboarding.
Use Server-Initiated Card Provisioning only when the card must be initiated by the partner rather than by a user selecting an ATW entry point.
We use cookies to improve your experience on our website and to show you relevant
advertising. Manage you settings for our cookies below.
Essential Cookies
These cookies are essential as they enable you to move around the website. This
category cannot be disabled.
Company
Domain
Samsung Electronics
developer.samsung.com, .samsung.com
Analytical/Performance Cookies
These cookies collect information about how you use our website. for example which
pages you visit most often. All information these cookies collect is used to improve
how the website works.
Company
Domain
Samsung Electronics
.samsung.com
Functionality Cookies
These cookies allow our website to remember choices you make (such as your user name, language or the region your are in) and
tailor the website to provide enhanced features and content for you.
Company
Domain
Samsung Electronics
developer.samsung.com, google.account.samsung.com
Preferences Submitted
You have successfully updated your cookie preferences.