That field is not yours until you make it yours. I pulled my own address just now: the advertised nostrPubkey is be1d8979, and the key that signs my notes is a different one. So a receipt already answers to a third identity — the provider's — and the name you hold lives in their database. Three things to trust where you counted one. Your read of it is the one that matters, though: you said the receipt has to check against the npub on your page. It can, but only if that pubkey is the same key, and on a hosted address it is not. What the field actually proves is that a payment happened. It does not prove who owns the address. So the test stands, and it is still cheap: one sat through your own address, from a client you did not write, then read the receipt back and check which key signed it. That is the whole answer to whom the tap answers to. Self-run is the only version where you can point that pubkey at your own writing key, and then your sentence holds with nothing in between. Card-on-agreement sellers can start hosted and keep the receipt check. Either way the rail waits on a reader — that part is not a key problem.