​

Setting up Samsung Pay on the web

Before you configure your dashboard or write any code, you need to decide how Samsung Pay fits into your tech stack. Every integration comes down to three choices:

• The Checkout UI - Where does the payment button live, and whose code runs it? (e.g., lite Hosted Checkout vs. your own custom built UI).
• The Samsung Pay service - Who owns the Samsung Pay service and its Service ID? (lite or you).
• Token Decryption - Who holds the private key to unlock the encrypted payment credential? (lite or you).

These choices combine into the merchant use cases below. Find the one that matches your business.

​

Core technical constraints

• No domain verification. Samsung Pay on the web doesn’t use a domain verification file or a merchant session. You don’t host any file on your site. Samsung does require every checkout domain to be registered on the Samsung Pay service, which lite handles (see Direct API).
• lite owns the Samsung Pay service today. Every integration runs on lite’s Samsung Pay service. You never create a Samsung developer account, generate a CSR, or manage keys. Using your own Samsung Pay service is coming soon.
• Supported card brands. Visa and Mastercard. Co-badged mada cards run under their Visa or Mastercard brand.

​

Ready to build?

Select your integration method below to see the flows and requirements to go live.

• I use lite Hosted Checkout
• I embed the checkout on my website (coming soon)
• I build my own web checkout (Direct API)
• I need my own Samsung Pay service or an Android app (coming soon)

---

​

1. lite Hosted Checkout

Best for the fastest launch. Customers are redirected to lite’s checkout page, meaning lite handles the entire Samsung Pay browser flow, the Samsung Pay service, and token decryption. Availability: Samsung Pay on Hosted Checkout is controlled entirely by channel configuration. Once it is enabled for your channel in the lite Dashboard, no merchant-side Samsung setup is required. Merchant checklist

1. Enable Samsung Pay for your channel in the lite Dashboard.
2. Create a checkout session from your backend.
3. Redirect your customer to the lite checkout page.

​

Onboarding flow

​

Payment flow

---

​

2. lite Web SDK

---

​

3. Direct API (lite-managed Samsung Pay service)

Best when you want full control over the checkout UI using Samsung’s Web Checkout SDK, but you still want lite to own the Samsung Pay service and decrypt the payment credential. Your checklist

1. Enable Samsung Pay for your channel in the lite Dashboard.
2. Share every domain that hosts your checkout page (for example payments.mystore.com) with lite. lite registers them on its Samsung Pay service; Samsung rejects payments started from unregistered domains.
3. Read the Service ID from the checkout session (GET /checkout-sessions/{session_id} → payment_methods.samsung_pay.dependencies.service_id). Don’t hard-code it.
4. Render the Samsung Pay button and start Samsung Pay with Samsung’s Web Checkout SDK, using that Service ID.
5. Send the payment credential to your backend, register it with lite as a samsung_pay instrument, and create a payment with the instrument ID.
6. Send the payment result back to Samsung.

​

Onboarding flow

Uses the same channel activation as Hosted Checkout, plus registering your checkout domains on lite’s Samsung Pay service.

​

Payment flow

---

​

4. Direct API or an Android app (merchant Samsung Pay service)