Is some another middleware really needed?

[petrkr]

this is really good idea how to introduce "pay to "email" address" . But is there really neede that bridge middleware if you already have working LNURL solutions ? Why just simply do not reply lnpayurl address in that "json" response?

I can understand use-case for plain lnd which does not implmenet lnurl/lnpay itself, but what is added benefit of another running piece of software server when there is already lnbits or btcpay for example?

I can go out with one static json file in webroot with lnpay poiting to lnbits (or btcpay) and it could work aswell. Yes for some more users this json could be generated from some DB or something. But that is already users-usecase, not for individual one-man wallets.

[andrerfneves]

You don't need a bridge server or middleware needed if you already have LNURL Pay in your server system. Lightning Address is a simple naming resolver for LNURL Pay. There are actually many paths to getting a Lightning Address to work, a simple JSON file on a server would technically/theoretically work I believe.