Payment Page

Click the button and a real checkout intent is created; the Lunixi payment form renders below. No keys required.

Try with insurance

Tick Sigortalı dene and the intent opens with a bus ticket line in its basket. The line carries the basket item insurance fields (insuranceCategory: "TICKET"); if the merchant has an active insurance product, the form offers ticket cancellation insurance at the payment step. Details: Insurance → Checkout Form.

Tick Sigortalı ve teklifli dene and the line also carries what the quote needs (insuranceData: the insured person and the ticket amount). The form requests the quote as soon as it opens and shows it with its price at the payment step; you still tick the insurance yourself. The demo passenger is fictitious.

Why this demo asks for no key

In the other demos you supply the key yourself. Here you cannot: the first two steps of the checkout flow are Ed25519-signed, and a signing key can never live in a browser.

[server]  POST /api/v1/auth/token        (signed)           → access_token
[server]  POST /api/v1/payments/intents  (signed + Bearer)  → checkoutFormContent
[browser] content is injected                               → form renders

The docs server opens the intent; only the content needed to draw the form reaches the browser. The access token and signing material never do.

In your own integration

Make the same two calls server-side and embed the returned checkoutFormContent. The SDK config's target field names the element it mounts into — if no container with that id exists, the form silently fails to appear.