nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqvpkystedk2lldqlkkyd084tj5e39rpxn7lad6qeq9uka7kfw9jrs2pzv63 (nprofile…zv63)
Fountain does this for our hosting customers - we accept payments from any app - either Keysend or Lightning Address - and aggregate payment stats and metadata in our dashboard - https://fountain.fm/podcasters
This is why I have been advocating for the rss::payment metadata spec because it's simple to implement and we can read the metadata from the x-rss-payment header and use this for our stats.