Congrats on LexeConnect. Zaptrain now uses it: tap Connect Lexe, approve in the app, and you can send Lightning invoices. No keys to copy. We only request the receive scope.

Zaptrain video: https://youtu.be/2dFZPlAIWGo

Try it: https://zaptrain.com

Hey @k00b - new here at SN and enjoying it a lot. We launched Zaptrain yesterday, built on Lexe, and the engagement on SN has been great.

Went to attach a wallet and there's no Lexe option. A lightning address covers receive but not send - Lexe has scoped, revocable client credentials that do both: https://docs.lexe.tech/authentication/#lexe-client-credentials

Might be a good one to add.

cc @MaxFangX

Yep, same. We built it on top of Lexe — @MaxFangX and @phlip9 have been awesome to work with.

Lexe is a self custodial lightning wallet, and Zaptrain plugs into it. As a user looking to issue invoices to accept sats, you create a self custodial wallet at Lexe, then generate Receive Only credentials and give those to Zaptrain and you are all set to issue business invoices. Payer pays with any lightning wallet and money lands in your Lexe self custodial wallet.

Please do. Would love your feedback. Thanks!

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.