Yes, I know that you can actually set the transaction fee to anything you want, but I'm of course talking about a transaction which will actually be "processed" in a reasonable timeframe, "reasonable" being "what the average person would accept".
I've been working for a long time now on a service which exclusively supports Bitcoin for payments. I'm afraid that somebody who is supposed to pay me the Bitcoin amount of $5 USD will feel appalled at the very notion of paying another $5 in Bitcoin just to send my service that actual $5.
I've done numerous Bitcoin transactions, but it has varied wildly in the amount. I can't really figure out how Bitcoin Core is deciding on the amount. (I've never changed it in.)
I'm aware of these "side-chains", but I don't understand how I'm supposed to actually use them in practice. Introducing a bunch of requirements and extra complexity seems even worse than having people "bite the bullet" with large fees (compared to the amount sent).
You might say that I should be having them "deposit" Bitcoin and then hold it on my side, but due to the way that this service is constructed technically, as well as the expected usage pattern, such an "account" cannot be made; they have to get an "invoice" for each time they purchase something, with a unique Bitcoin receive address to which they send the amount. Again, the problem is that I fear that the transaction fees will put people off.
In general, how should I handle this?