pull down to refresh

Zaptrain: Lightning invoicing where we only hold a receive-only keyzaptrain.com
3440 sats \ 12 comments \ @zaptrain 29 Sep bitcoin
zaps forwarded to @MaxFangX (20%) @phlip9 (20%)

Zaptrain is invoicing and hosted checkout over Lightning, built on Lexe (@MaxFangX, @phlip9). Invoices settle into the merchant's own self-custodial wallet. We only hold a receive-only credential — money can come in, none can leave.

1% per paid invoice, no subscription. Dashboard, REST API, webhooks and an MCP server.

Short demo: https://youtube.com/shorts/4JjxB_ttiJA

Just launched. What would stop you using it?

write
compose
related posts
94 sats \ 1 reply \ @Chikasunbeats 30 Sep

‎I run small suya stall experiment in Benin City, Nigeria. My biggest blocker is trust — customers think BTC na scam. If Zaptrain can make a simple QR that says "receive only, can't steal" in pidgin English, I can onboard 5 shops this month. Testing with chikasun@blink.sv

reply
101 sats \ 0 replies \ @MaxFangX fwd 1 Oct

Maybe you could ask them to try using Lexe wallet directly. It sounds like they're accepting in-person payments, so all they need is a mobile wallet?

reply
101 sats \ 1 reply \ @mkmloom 29 Sep

It looks interesting, we need to test it

reply
1 sat \ 0 replies \ @zaptrain OP 29 Sep

Please do. Would love your feedback. Thanks!

reply
1 sat \ 1 reply \ @06bc1a977d 30 Sep

Is this even ~lightning or just plugged into it? No opensource?

@remindme in 1 year

reply
1 sat \ 0 replies \ @zaptrain OP 30 Sep

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.

reply
1 sat \ 1 reply \ @ACYK 30 Sep

When NWC on Lexe? It would be great to recommend Lexe to people who didn't want to run a node on their own hardware and be able to hook it up to SN, auto top-ups on PPQ.ai, stream payments to podcasts using Castamatic, etc.

reply
10 sats \ 0 replies \ @ACYK 30 Sep

Should have checked my notifications first. Got a response over here: #1584720 . Awesome to hear NWC is actively in the works!

reply
1 sat \ 0 replies \ @YewTuBot 29 Sep
reply
1001 sats \ 2 replies \ @afa9dc72b3 29 Sep -1030 sats

Neat trust-minimization angle — a receive-only credential means Zaptrain literally can't rug a merchant's funds even if the dashboard or API key were compromised. Two things I'm curious about (disclosure: this reply is AI-assisted):

  1. Refunds. If the merchant wallet is self-custodial and Zaptrain never touches outbound funds, how does a refund actually happen — does the merchant have to manually pay back the customer's original invoice/address themselves, or does the API expose some refund-request flow that just notifies the merchant without moving money on Zaptrain's side?
  2. The MCP server. Exposing invoicing over MCP to an LLM agent is interesting given the receive-only design limits the blast radius, but what operations does it actually expose — just create-invoice/check-status, or also webhook/config management? If an agent can rewrite the merchant's webhook URL, that's a phishing/exfiltration vector even without touching sats directly.

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?