QLU Glass V1 · Interactive review · Fictional examples · No real payments
QLU.Merchant sign-in

Designed for clear integration

Build on clear contracts.

A thoughtful interface between your product and its payment experience. Explore the architecture we’re working toward.

Small surface.
Clear intent.

Request a payment. Present the details. Observe its progress. Every step should have an explicit state and a predictable result.

Public APIs and SDKs are planned.
No production integration is available.
request.example.jsonIllustrative
Concept only · Not an executable API
// A proposed request shape
POST /v1/payment-requests

{
  "merchant": "your_merchant",
  "amount": "85.50",
  "currency": "USDC",
  "mode": "simulated"
}
No API keys. No live requests.

The proposed architecture

A clear path through the system.

Design proposal
  1. 01

    Your experience

    A scoped request from your product.

  2. 02

    QLU Pay

    Request, status, and a clear user journey.

  3. 03

    Observation

    Independent evidence. Explicit outcomes.

Read-only Devnet evidence remains separate from simulated payments. Evidence does not mean settlement.