pull down to refresh

We're looking for a few Stackers to test our new Lightning integration and help us out with some feedback.
If anyone wants to connect their node (via LNbits) you can follow this guide: https://blog.zaprite.com/add-lightning-payments-to-your-invoices-using-lnbits/
Feedback appreciated:
  • Was the guide easy to follow?
  • Any UI/UX issues?
  • Did you receive the payment notification email?
The first 10 people to send us an invoice for USD$5 we'll pay it.
Steps to follow …
  1. Activate Lightning in your Zaprite account:
  2. Create a new Contact for 'Zaprite' (use: dropfiat@zaprite.com)
  3. Generate a new Invoice:
  • Use new Contact from #2 above
  • Add a new Line Item for USD$5.00
  • Enable Lightning as a payment option
  1. Click the 'Send' button to send the invoice to us
Cheers!
PS: If you don't have a Zaprite account yet, you can sign-up for free at: https://app.zaprite.com We only require an email address to sign-up—NO KYC!
As a payer to a zaprite invoice, is my experience similar to a standard fiat invoice (where the payer would make a fiat payment, which zaprite converts to BTC for the recipient)?
reply
No, unfortunately we can't take on that risk of doing Fiat->BTC conversions directly. Hopefully in the future there will be ways we can do it.
But… you can use Strike as the payer on a Lightning-enabled Zaprite invoice, and it will pull from your bank account via Strike.
reply
I haven't looked into much detail yet, but this is something similar to BTCPay, right? What are the differences? Similarities?
reply
It's similar to BTCPay in that it lets you run software on top of any Bitcoin wallet.
The main difference is that you don't need to run a node to use Zaprite.
BTCPay is awesome, but the vast majority of people are not going to run their own node. Zaprite aims to fill that gap where people can simply connect their own wallet and access a range of financial services, but delivered through a much better UI/UX.
reply
Regarding the guide, while setting up LN payments, I got slightly confused by the flow of the pdf. Node URL and API Key sections came out of the blue, it's only in the next section I understood I'd have to copy them into Zaprite. I'd put a little paragraph before those two sections you'll be needing them for the next section.
Or maybe I missed it as I went fast.
No UI/UX issues, but I had to toggle between turning tor on and off, on while accessing my node, off when on the Zaprite website as the latter wasn't responsive when behind tor.
I haven't received the payment notification email yet...
reply
Thanks for that. I'll take another look at the guide and see if the flow can be improved.
I use Brave's browser with built-in Tor and I can usually reach my node and the Zaprite web app using that.
I paid a bunch of invoices earlier today so hopefully your was included. If not, feel free to DM on Twitter and I'll find it and pay it!
reply
Actually, signing up now. Let me test it first, no need to answer the above, probably naive question.
reply
Hi @john!
Yes, the guide was easy to follow and I did not experience any UI/UX issues, note that I happen to be a veteran UNIX hacker so other peoples' mileage may vary.
No, I did not receive the payment notification email and no satoshi came, but that is OK as I may be too late and anyway you shall rather spend the time with real people in your close proximity.
Thank you anyway! I think this is a good service bridging the gap between old-world and non-KYC Bitcoin thinking for people who needed. All the best! And I actually love the UX and it works on a veteran Android 4.2.2 phone with old Opera browser, too.
Recommendation.
You are using a Purple icon for Lightning, it seems most people have standardized around Orange = Bitcoin, Yellow = BTC Lightning.
It took me a good 2 or 3 scans of available payment methods until I noticed that the purple icon was Lightning...
Further, I wouldn't just call it "Lightning", but either "Bitcoin Lightning" or "BTC Lightning.... in the future its quite likely there will be multiple LN networks (on Liquid for example). Further, its also quite likely different assets become hosted on LN....therefore starting with correct branding now saves you changes down the line trying to differentiate between all the possible options.