But the payer can always provide their pay-from address in a remittance advice which will enable attribution. And if I wanted to automate, I suppose I could ask them to email me their from address, and then use ITTT to search the blockchain for a payment from that address, to my address, after the email date until it finds it in a block that is at least two links old. Then have ITTT email them the article. That would be automated, but a bit of mucking around.
Getting back to the point, you need to be able to wait an amount of time, and check to ensure a transaction is confirmed without the customer having to wait. This system allows you to do just that, and you will be able to set any number of confirmations, depending on the value of the deliverable.
Again, you've added a lot of clarity. So where I suggested "two links old", that would be fine for minor transactions, but for something more significant, more confirmations adds security, up to about six where that is a lot of work to break.
The DNotes 2.0 blockchain will allow for someone to create event triggers, that would confirm a transaction. But this may be a better way to explain it, it would be like a transaction specific decentralized API, that anyone could call anywhere in the world to confirm.
That makes a lot of sense and I can see now how people would be eager to implement that in their websites.