-
@ PayPerQ
2025-05-24 14:47:33
Paying out change is nice. Does the client need to trust that the server will refund change? I assume so.
What if the payer doesn't have cashu tokens to begin with? For example, the user pays via lightning... can I give them cashu change even if they don't own any themselves? The change can be credits for my platform that they may use in their next request...
But if that is the case, their wallet needs to know how to recycle the change into future payments...
It's getting complicated fast.
If ecash was widespread tech this all seems feasible, but because it isn't such a solution would only appeal to a very narrow audience for now. Isn't that correct?
So basically, this schema could only work for payers which have the infrastructure to process the cashutokens to begin with. They need to have some cashu handliny library on their client side, right?
Lastly, the latency issue still exists. If Cashu payments have all of the same checks that lightning payments do than the time delay is gonna suck. But maybe they don't?
Thanks for reading my stream of thought.