How Lydian Payments Work

Lydian turns a fiat price into a completed crypto payment. Your backend opens a payment context, the customer pays through Lydian checkout, and Lydian confirms the payment on-chain and reports the result. This page describes how the pieces fit together; for a step-by-step walkthrough see Accept Your First Payment.

The objects involved

Merchant
  │ creates
  ▼
Session  ──▶  Checkout (hosted or embedded)
                    │ customer selects an asset + network and pays
                    ▼
              Transaction  ──▶  processing / on-chain confirmation  ──▶  final state
  • A Merchant is who the payment is collected for.
  • A Session is the payment context — the amount, currency, and settings for one checkout.
  • Checkout is where the customer actually pays, either Lydian-hosted or embedded on your site.
  • A Transaction is the real payment: the asset, network, address, and on-chain result.

How a payment moves

  1. A Session is created first. Before the customer sees checkout, your backend creates a Session for the amount to collect. This returns a sessionID and a qrData checkout URL.
  2. The customer completes checkout. Checkout can be hosted (redirect to the qrData URL) or embedded (the Web SDK on your own page). Either way, the customer chooses an asset and network (for example USDT on Ethereum) and pays.
  3. A Transaction represents the payment. When the customer selects payment details, Lydian creates a Transaction associated with the session — this is the actual payment attempt Lydian processes and confirms on-chain.
  4. You observe the final state. Payment state can be read from the Session and Transaction APIs, or pushed to you via webhooks. See Payment Lifecycle & Statuses.

Where to go next