Samsung Checkout

This topic describes how you can develop a billing system for your Tizen .NET TV 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 within your .NET application, the user needs:

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

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.

DPI Service Environment

The DPI service provides information on buyable products in your application and the purchase history of your customers. It serves the appropriate product information for the user's country, provides user-specific purchase information, and manages applying the product after purchase. The DPI service also assures purchase integrity and provides security through preventing fraudulent access.

The DPI service environment is divided into 2 separate zones:

  • Operating Zone (PRD) for live production applications
    When you submit your application for publishing, set it to use the operating zone.

  • Staging zone (DEV) for development and testing
    The purpose of the staging zone is to facilitate the billing linkage development. This environment minimizes the exceptional country-specific cases that can happen when real payments are made in the operating zone.
    The staging zone also includes a dummy payment testing option, where the user does not need to register any payment method, but can still use all the DPI services as in real payment transactions.

    Dummy payment Actual Payment

    Table 1. Dummy and actual payment screens

The following figure illustrates the DPI service environments.

Figure 4. DPI service environments

Implementation information for each DPI service environment is described in the following table.

Service Environment Details
Operating zone Environment:


BillingRequestServerType servertype = BillingRequestServerType.Prd;
string securityKey = "*****"; // Your security key issued by DPI portal
                              // (Can be different from Sandbox's sSecurity key)
Staging zone Environment:


BillingRequestServerType servertype = BillingRequestServerType.Dev;
string securityKey = "*****"; // Your security key issued by DPI portal
Staging zone with dummy payment Environment:


BillingRequestServerType servertype = BillingRequestServerType.Dummy;
string securityKey = "*****"; // Your security key issued by DPI portal
Table 2. DPI service environment details

When you submit your application for publishing, make sure that it has been fully integrated with the billing system:

  • Ensure that the application detects the service environment and sets the server type accordingly.
  • Check that the product and price information in the operating zone (PRD) matches the tested information in the staging zone (DEV). No data is automatically shared between the zones.

Registering a Test User Payment Method

When the user registers their credit card as a payment method in Samsung Checkout, they can do it through their mobile phone or computer Web site by entering the authentication code.

When you are creating a test user for your application, pay attention to the URL you use to enter your authentication code and register a payment method. Each URL requests a different server to handle the payment:

Figure 5. Registering a credit card as a payment method