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.
Interesting! I checked out those examples, but one thing I don't see is payment amounts. The examples only show placing or removing the <meta> tag in certain ways, and showing monetization states based on events. How do payment amounts come into play?
EDIT: Ah, ok, I see the explainer shows an event.detail.amount property.
I take this to mean that a website could show a message like "pay such and such amount and receive such and such stuff", then the user can take that action, and eventually the website would see event.detail.amount.
How would something like selling individual products work? Would we need to dynamically switch out the meta tag (or go to an entirely separate page with its own meta tag) depending on which product the user will be paying for?
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 taking the below directly from @sharafian
— and it's likely best that he expand...
Web Monetization doesn't allow for the requesting of specific amounts. Discrete or 'retail' payments like that are better served by a traditional checkout flow or the Web Payments API.
Interesting. So how do you know if it is worth disabling ads for someone if your business relies on ads, for example? What if they donate only 1 cent. Maybe that won't outweigh the benefit of keeping the ads. There must be a way to track amounts. and therefore, a way to list those amounts somewhere on the website for users to set as their goal, which would equate to requesting specific amounts but in a different way.
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.
There are some interesting privacy related challenges here. Unless users/members explicitly opt-in of course. @sharafian
likely has thoughts and ideas here.
On the member side, @wobsoriano
has been working on a separate extension (they opt-in by explicitly installing something) for members showing them their spend. It's a work-in-progress for the hackathon and he is writing about it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Check out some samples within the Web Mometization documentation
Also perhaps wander across to the Grant for the Web Community Forum. There are loads of ideas being thrown about there by many others.
And lastly to highlight @ben main post above some starter ideas and demos listed under the Example Projects header.
Happy building!
Interesting! I checked out those examples, but one thing I don't see is payment amounts. The examples only show placing or removing the
<meta>tag in certain ways, and showing monetization states based on events. How do payment amounts come into play?EDIT: Ah, ok, I see the explainer shows an
event.detail.amountproperty.I take this to mean that a website could show a message like "pay such and such amount and receive such and such stuff", then the user can take that action, and eventually the website would see
event.detail.amount.How would something like selling individual products work? Would we need to dynamically switch out the meta tag (or go to an entirely separate page with its own meta tag) depending on which product the user will be paying for?
I'm taking the below directly from @sharafian — and it's likely best that he expand...
Interesting. So how do you know if it is worth disabling ads for someone if your business relies on ads, for example? What if they donate only 1 cent. Maybe that won't outweigh the benefit of keeping the ads. There must be a way to track amounts. and therefore, a way to list those amounts somewhere on the website for users to set as their goal, which would equate to requesting specific amounts but in a different way.
There are some interesting privacy related challenges here. Unless users/members explicitly opt-in of course. @sharafian likely has thoughts and ideas here.
On the member side, @wobsoriano has been working on a separate extension (they opt-in by explicitly installing something) for members showing them their spend. It's a work-in-progress for the hackathon and he is writing about it.