Lunor Pay
Accept and reconcile digital asset payments from one checkout.
A checkout for businesses that need to accept digital assets and still reconcile the payment against the order.
- product
- Lunor Pay
- surface
- Pay
- category
- Payments
- backend
- Not attached
- status
- Coming Soon
This page describes the intended product. Nothing here accepts a payment, sells a ticket, opens a workspace, sends a campaign, or answers a support conversation.
The problem
Accepting crypto is easy to announce and awkward to operate.
A wallet address on an invoice is not a payment system. The business still has to notice the transfer, match it to the right order, handle a partial payment, and explain the state to the customer who already thinks they paid.
The tools that do this well are usually built for a different checkout, a different ledger, and a different support team. The payment record ends up in one place and the order in another.
The approach
One checkout. One payment record. One place to see what settled.
Lunor Pay is the intended gateway for that job. A business creates a payment, the customer completes it in a checkout built for digital assets, and the result is a record tied to the order: requested, pending, confirmed, or failed.
Nothing on this site accepts a payment. There is no merchant account, no settlement, and no live checkout behind this page. The product is specified so an operator can see the surface before it exists.
Capabilities
What the module does.
Checkout
A payment request with amount, asset, and a clear state the customer can read.
Order matching
The payment is attached to the order, not left as an unmatched transfer.
Payment states
Requested, pending, confirmed, underpaid, and failed — each one explicit.
Merchant view
What was requested, what arrived, and what still needs a person.
Asset support
Designed around digital assets a business chooses to accept, not a fixed catalog on this page.
Reconciliation
A record an operator can export against their own books.
Failure handling
Expired and partial payments stay visible instead of disappearing into a wallet history.
Not live
No checkout, no custody, and no settlement run from this site.
How it works
The workflow, step by step.
- 01Create the payment
Amount, asset, and the order it belongs to.
- 02Send the checkout
The customer sees what to pay and the state of that request.
- 03Watch it settle
Pending until the transfer is confirmed, then matched to the order.
- 04Handle the exceptions
Underpaid, expired, and failed payments stay on the record for a person to resolve.
- 05Reconcile
Export the payment record against the orders it closed.
Specification
At a glance.
- Surface
- Checkout and merchant record
- Unit
- One payment request per order
- States
- Requested, pending, confirmed, underpaid, failed
- Settlement
- Specified, not operated from this site
- Custody
- None on this site
- Status
- Coming soon — no published date
Security
A payment page that cannot take a payment should say so on the page.
- This site has no checkout, no merchant keys, and no settlement path
- No wallet connection and no broadcast from the public page
- Production custody and settlement, if built, sit in a separate payments operation
- No claim is made here about licensing, chargebacks, or fiat conversion
- Partial and failed payments are specified as visible states, not silent losses
Full posture, including what we deliberately do not claim, is on the security page.
Use cases
Where it gets used.
A product checkout
Take a digital asset payment for a specific order and keep the receipt with that order.
Invoicing
Send a payment request with an amount and an expiry, then see whether it settled.
Reconciliation
Give finance a payment record that matches orders, instead of a wallet export.
FAQ
Questions asked before adopting this module.
Can I accept a payment here?
No. Lunor Pay is coming soon. This page describes the intended checkout. It does not create a payment, hold funds, or settle anything.
Which assets?
The product is specified so a business chooses what it accepts. This page does not publish a live asset list, because there is no live checkout.
Do you custody the funds?
Not from this site. If Lunor Pay is built, settlement and custody sit in a separate payments operation, with its own controls. Nothing on lunorprotocol.com holds customer funds.
When does it ship?
No date is published. It moves up when a real business needs the checkout and is willing to be the first operator.
Other modules
Same Console, same project record.
Next step
Tell us if you need this one.
Modules move up the sequence when a real project needs them. If this is the one blocking you, that is useful information.