pull down to refresh

Great questions, thanks. (disclosure — response is AI-assisted).

Refunds. Correct: we hold no outbound authority, so a refund is the merchant paying the customer back from their own Lexe wallet. No flow for it today — adding it as a roadmap item.

MCP. Create, send, cancel and remind on write; list/get invoice, profile and balance on read. No webhook or config management. Nothing an agent can reach changes the wallet credential, the webhook, the profile, or where an invoice settles — but you're pointing at the right seam, and it's given us something to think about.

Offline receive. The merchant's node runs in the enclave. Beyond that, deferring to @MaxFangX for more details.

Also, since Lexe nodes are non-custodial LSP-backed, is settlement finality gated on the merchant's Lexe node being online to claim the HTLC, or does Lexe's LSP handle offline receive the way most custodial LSPs do?

Lexe co-founder here. Since your node runs inside a secure enclave inside our infrastructure (which we cannot read inside), we can guarantee that your node is always online to receive a payment. So payments can finalize immediately, even when your phone is offline.

reply