I'm completely new to this, so please forgive the noob question.
It looks like the monetized content is sent in the initial request, but it just remains hidden until the browser sends payment. I suppose that could work in some cases, but how would you go about sending the monetized content only after verification? Is there a mechanism to send some kind of token to the server for server side checks?
Sneakerhead, champion tea-drinker and street art photographer. Former check-ins at dot-coms. Now helping advise early-stage technology startups. Can code. Won't code.
I'm completely new to this, so please forgive the noob question.
It looks like the monetized content is sent in the initial request, but it just remains hidden until the browser sends payment. I suppose that could work in some cases, but how would you go about sending the monetized content only after verification? Is there a mechanism to send some kind of token to the server for server side checks?
You're absolutely right. The Web Monetization site currently suggests this as a method, points out that you could fake monetization events and says that an example to verify Web Monetization from the server side will be coming soon. Once they have an example of server side verification I'll add that as an option to the components.
Ha, I checked that same page, and scanned the content but missed the bit about the server... even though it was staring me right in the face.
Thanks, this is a very exciting API, and if successful its effects will ripple on the web for a long time.
I agree, I'm pretty excited by what this might be able to unlock for creators on the web!
I look forward to getting the examples of server side verification though. It will make this a bit more trustworthy!
Definitely follow @sharafian as he explores more here including expanding server-side verification...
Followed! Will be great to see some docs on it soon.