Choose Your Integration
Lydian supports two ways to collect a payment. Both start the same way — your backend creates a Session — and differ only in where the customer completes payment.
Hosted Checkout (recommended)
Your backend creates a Session and redirects the customer to the Lydian-hosted checkout URL returned as qrData (for example https://pay.lydian.com/session/{sessionID}). Lydian handles asset and network selection, the wallet connection, and on-chain confirmation, then redirects the customer back to your successURL, cancelURL, or failureURL.
- Best for: getting live quickly with the least code.
- Where the code lives: your backend only — no frontend SDK required.
- Get started: Quickstart · Accept Your First Payment
Embedded Web Checkout
Keep the customer on your own site by embedding the checkout UI with the Web SDK. You add the <lydian-checkout> element to your page and initialize it with the session; the SDK renders the checkout inline.
- Best for: a fully branded, in-page checkout experience.
- Where the code lives: your backend (to create the Session) and your frontend (to embed the SDK).
- Get started: Web Checkout · Web SDK
Which should I choose?
| Hosted Checkout | Embedded Web Checkout | |
|---|---|---|
| Customer completes payment | On Lydian's hosted page | On your own site |
| Frontend work | None | Add the <lydian-checkout> element |
| Effort to integrate | Lowest | Moderate |
| Recommended for | Most integrations | In-page, branded checkout |
Both modes create the same Session and produce the same Transaction, so you can start with hosted checkout and move to embedded later without changing your backend.