Samsung Checkout

This topic describes how you can develop a billing system for your application, to allow users to make purchases within your application.

Related Info


Samsung Checkout offers an optimized purchase experience for your users on Samsung TVs. The user can quickly and safely register a payment method and make frictionless payments repeatedly within the TV environment. In addition, Samsung Checkout provides a comprehensive global monetization platform, which allows you to integrate various business models and promotional campaigns into your services.

The TV-optimized purchase experience provides the user a quick and simple 3-step checkout, once a payment method is registered. The checkout requires only number-centric information to be entered, making it easy to use with a TV remote control. Users can register their payment method directly on the TV or through a mobile phone.

Figure 1. 3-step checkout: Confirm > Provide PIN > Done

To use Samsung Checkout, the user needs:

  • TV: Samsung Smart TV, 2016 or later model supporting Tizen (excluding Evolution Kit)
  • Payment method: Credit or debit card, PayPal, or Samsung Pay (in Korea, United States)
  • Security: Tizen SecureIME, 2nd-screen card registration (mobile or PC)
  • Account: Samsung Account (for sharing account and payment information with Galaxy phones)

Samsung Checkout provides :

  • One solution for payment execution :
    ✔ One solution supports all functions from payment operation.
    ✔ Operate automatically settlement and payout
  • Strong security Payment solution
    ✔ Acquire PCI-DSS certification and follow regulation each of countries (PSD2)
    ✔ Following PSD2 regulantion and GDPR
  • Deliver the coupon/promotional code in various ways of distribution with easiest UX
    ✔ Issue coupons for promotion
  • Provide DPI(Digital Product Inventory) System
    ✔ Create and manage service items
    ✔ Check the status of sales amounts and transaction scale
    ✔ Refund and cancel subscription

You can manage your product application and product sales through the DPI (Digital Product Inventory) and process the actual purchase through Samsung Checkout.

Samsung Checkout Purchase Process

When a user wants to purchase a product on your application, Samsung Checkout provides a common purchase GUI, which identifies the user and confirms first the purchase and then the purchase completion. After the user completes the purchase, Samsung Checkout returns the purchase result to your application.

Figure 2. Samsung Checkout process

Product, Purchase, and Payment Management

The following figure illustrates how you can use Samsung Checkout and the information in the DPI server to manage in-app purchases and payments in your application.

Figure 3. In-app purchase management

  1. Request the purchase list:

    1. Retrieve the customer purchase list using a Purchase List API request.
    2. Respond to the purchase list content:
      • If there are products in the purchase list which are not applied, verify the purchase and apply the products.
      • If there are products in the purchase list which have been refunded, retrieve the products.
    3. Send the application result to the server.
  2. Request the product list.
    Request the product information list using a Products List API request.

  3. The user purchases the product:

    1. When the user selects “Buy” in the application, provide a common purchase GUI through Samsung Checkout.
    2. The user can enter a voucher or coupon code to modify the purchase price.
    3. The user confirms the purchase by entering a PIN on the common purchase GUI, or biometric information on Samsung Pay.

      Samsung Checkout delivers the purchase result to your application.
  4. Request the purchase list.

    Update the customer purchase list.

  5. Verify the purchase.

    Verify the purchase using a Verify Purchase API request.

  6. Apply the product.

    Apply the product using an Apply Product API request, and send the application result to the server.

Payment flow with Dynamic Product

In case that partner already has CMS server which manage products and price, and it is required to change the product information frequently, partner and Samsung can discuss to use dynamic product when they integrate Samsung Checkout.

And once they agree on that products and prices will be managed by CMS of partner not by Samsung’s DPI, partner need to register a representative item on DPI so that Samsung Checkout system can display information on Samsung Smart TV App/Game store which is legally required.

Partner does not need to register each products on DPI that they sells in their app, however,
They should builds and operates its own CMS to manage products information including prices and provide rest API for verification of purchase requests.

The following figure shows data flow of initialize stage in payment process with dynamic product.

Figure 6. Dynamic product payment process flow

Additional requirement for DPI

As model require Partner CMS to manage product information, there is additional requirement that partner need to do for DPI settings.

  • Verification/No Verification

    ‘Verification’ is a recommended option otherwise partner has to handle the verification process by themselves and take all the responsibility for all the error cases related to verification process.

    If ‘Verification’ is selected, ‘Verify URI’ is also required. This URI should serve the function of checking product information such as product itself, price and currency in sequence of initialization during payment process.

    Figure 7. Verification setting

  • Price Setting

    Price range information of products that you actually sells in your app is required by country. It is not used for actual payment for providing the app information on Samsung Smart TV App/Game store which is legally required.

    Thus, it has to be updated when the price range of your products is changed.

    Figure 8. Price setting

Difference when Dynamic Product

  • When buyItem()

    Unlike ordinary purchase, when Dynamic Product, Partner need to set values as below in order to complete payment process.

    "OrderItemID" - Representative productID that registered to DPI Portal as dynamic product type

    "OrderTitle" - Customized name for each purchase displayed as in Figure 9.

    "OrderTotal" - Customized price for each purchase displayed as in Figure 9.

    "DynmcProductID" - Unique product ID managed by Partner CMS

    Figure 9. Dynamic product purchase page

  • When Verify Product

    Partner need to strictly verify the below values in order to identify if it's appropriate product information.

    "appId" - if it's appropriate application for this payment process

    "productId" - if this is same as representative ProductID from DPI Portal

    "productPrice" - if price of product that partner intended to sell to user

    "dynmcProductID" - if this is is appropriate ID that are under control of partner CMS

    Checkout Service County List

No Area Country
1 North America Canada
2 North America United States
3 Europe Aland Islands
4 Europe Albania
5 Europe Austria
6 Europe Belgium
7 Europe Bosnia and Herzegovina
8 Europe Bulgaria
9 Europe Croatia
10 Europe Cyprus
11 Europe Czech Republic
12 Europe Denmark
13 Europe Estonia
14 Europe Faroe Islands
15 Europe Finland
16 Europe France
17 Europe Germany
18 Europe Greece
19 Europe Greenland
20 Europe Guernsey
21 Europe Hungary
22 Europe Iceland
23 Europe Ireland
24 Europe Isle of Man
25 Europe Italy
26 Europe Jersey
27 Europe Latvia
28 Europe Lithuania
29 Europe Luxembourg
30 Europe Montenegro
31 Europe Netherlands
32 Europe North Macedonia
33 Europe Norway
34 Europe Poland
35 Europe Portugal
36 Europe Romania
37 Europe Serbia
38 Europe Slovakia
39 Europe Slovenia
40 Europe Spain
41 Europe Sweden
42 Europe Switzerland
43 Europe United Kingdom
44 Europe Liechtenstein
45 Europe Belarus
46 Europe Kazakhstan
47 Europe Kyrgyzstan
48 Europe Moldova
49 Europe Mongolia
50 Europe Russian Federation
51 Europe Tajikistan
52 Europe Turkmenistan
53 Europe Ukraine
54 Europe Uzbekistan
55 Europe Armenia
56 Europe Azerbaijan
57 Europe Georgia
58 Asia Australia
59 Asia Hong Kong
60 Asia India
61 Asia Indonesia
62 Asia Korea, Republic of
63 Asia Malaysia
64 Asia New Zealand
65 Asia Philippines
66 Asia Singapore
67 Asia Taiwan, Province of China
68 Asia Thailand
69 Asia Vietnam
70 Asia Cambodia
71 Asia Myanmar
72 Asia Laos
73 Asia Macao
74 Asia Bangladesh
75 Asia Nepal
76 Asia Sri Lanka
77 Latin America and the Caribbean Argentina
78 Latin America and the Caribbean Bolivia
79 Latin America and the Caribbean Brazil
80 Latin America and the Caribbean Chile
81 Latin America and the Caribbean Colombia
82 Latin America and the Caribbean Costa Rica
83 Latin America and the Caribbean Dominican Republic
84 Latin America and the Caribbean Ecuador
85 Latin America and the Caribbean Guatemala
86 Latin America and the Caribbean Mexico
87 Latin America and the Caribbean Panama
88 Latin America and the Caribbean Peru
89 Latin America and the Caribbean Venezuela
90 Latin America and the Caribbean Paraguay
91 Latin America and the Caribbean Uruguay
92 Latin America and the Caribbean El Salvador
93 Latin America and the Caribbean Honduras
94 Latin America and the Caribbean Nicaragua
95 Latin America and the Caribbean Bahamas
96 Latin America and the Caribbean Jamaica
97 Latin America and the Caribbean Trinidad & Tobago
98 Middle East Algeria
99 Middle East Bahrain
100 Middle East Egypt
101 Middle East Ghana
102 Middle East Iraq
103 Middle East Israel
104 Middle East Jordan
105 Middle East Kenya
106 Middle East Kuwait
107 Middle East Lebanon
108 Middle East Libya
109 Middle East Mauritius
110 Middle East Morocco
111 Middle East Nigeria
112 Middle East Oman
113 Middle East Pakistan
114 Middle East Qatar
115 Middle East Saudi Arabia
116 Middle East South Africa
117 Middle East Tunisia
118 Middle East Turkey
119 Middle East United Arab Emirates
120 Middle East Yemen