Ok.  Just a few minutes ago, I paid through the second route.  I engaged in copy and paste of the invoice that you provided, and I got several errors before I was able to figure out a way for Phoenix (the wallet that I used for this transaction) to be able to recognize the invoice, which the app was saying: "this does not appear to be a lightning invoice".. so in my trouble shooting the matter, I saw that somewhere along the way, there were something like 4 extra spaces that ended up getting put into the invoice  that you had sent to me or the way that I had received it through my copy and paste - somewhere along the way, so when I took out those extra spaces (probably considered soft carriage returns), then my phoenix wallet was able to recognize the invoice so that I could pay it.

I will note a couple of things. 

1st.  I had mentioned PM in regards to making payments which I think is a better practice, especially in regards to OP sec, and perhaps even in regards to lesser of a need to be public about the potential back and forth difficulties that can play out through paying... that maybe we don't need to do within a thread like this.. because ultimately the question may only be whether the payment was received or not, rather than publicly discussing the process and/or maybe various barriers of how the payment was carried out.. or those kinds of minuscule matters.

2nd.  I am not sure what kind of a lightning wallet that you are using, and I am not sure if it is necessary to disclose, yet many times the lightning wallets will allow the production of a QR code, and that way we might get away from the copy and paste issues.  I know some wallets can also scan the invoice in its alphanumeric form and figure it out, but I am not sure if Phoenix can do that.. I tried to scan the invoice after I took out the spaces and even with the corrected invoice, Phoenix does not seem to be able to scan an alphanumeric format.

You can do what you like in regards to making an onchain payment to Chartbuddy, yet I cannot consider purposeful use of onchain payments for such low transactions amounts to be justifiable - especially if there are other options to still use bitcoin, but maybe on a second or a third layer as already discussed, including my stating my preference to not be fucking around with such small amounts on chain, especially if we might be able to figure out other options.. not trying to be against making direct bitcoin transactions, but instead attempting to be practical. 

As I think I already mentioned, in recent times, I also don't like the idea of sending payments under $100 onchain, and I would try to process for lower fees, and so the minimum fees have been fluctuating between 40 and 60 sats per vbyte - even though I do see some scattered blocks in the 20 sats per vbyte and the most recent block had fees as low as 17 sats per vbyte... but even attempting to process a transaction for around 20 sats per vbyt is going to cost around $1.74, and it may even take several days before it goes through - depending on what fees do in the immediate future, and then once it is received on the other end, then there may well be fees on that side too, but then we cannot know when the other side is going to end up attempting (or needing/wanting) to process the transaction down the road.

By the way, as a test, I just tried to process the same invoice a second time, just to see what happens, and when I went to paste the invoice into the Phoenix app, I got a notice: "You have already paid this invoice.  Paying it again could result in stolen funds."   So I am not sure if it could get paid more than once by a second person or through a second wallet..