Use case

The Samsung Pay developer documentation targets the following developer stakeholders:

  • Individual merchants who want to offer the Samsung Pay payment option for their customers in their app or on their website

  • Payment gateways (PG) who offer a payment solution to their own merchants and manage it on the merchants' behalf

    A PG can provide either a ready-made solution or a simple framework for their merchants:

    • A ready-made solution means that the PG integrates Samsung Pay to their own systems and provides relevant integration instructions to their merchants for handling customer payments.
    • A simple framework means that the merchant follows the integration instructions on this site to handle customer payments and links their integration to their PG during onboarding.

The Samsung Pay use case is card transactions, which allows merchants and PGs to create a card transaction after the customer has decided to pay for their purchase with a card in Samsung Wallet:

  1. During checkout, the merchant displays a checkout page with a Samsung Pay button.
  2. The customer clicks the button and authorizes the payment with the Samsung Wallet app.
  3. Samsung Pay sends payment credentials to the merchant who requests payment approval from their PG.
  4. The PG connects to the payment network which identifies the customer's card based on the token and gets approval for the payment from the card issuer.
  5. The PG notifies the merchant of the payment approval.

Card transaction flow