Sorry—n00b question but I just want to confirm my understanding. Web Monetization is run with the document.monetization API (docs), so it’s only supposed to run on the client-side where document is available.
If we have monetized (ie. “paywalled”) content and implement it on a SSR site, the server-generated pages will only have the free content; no way to authenticate user from the server. Is this correct?
I work on web monetization at Coil. Passionate about improving the web, open standards, and helping developers build amazing things. Formerly at Mozilla where I worked on MDN and Developer Relations.
Yes, generally the easiest way to add web monetization is client-side with the meta tag. We are working on offering back-end integration and options.
There is also an option to use the OAuth Web Monetization Script. However, you will need to register your client app and be approved for OAuth access. docs.coil.com/
Sorry—n00b question but I just want to confirm my understanding. Web Monetization is run with the
document.monetizationAPI (docs), so it’s only supposed to run on the client-side wheredocumentis available.If we have monetized (ie. “paywalled”) content and implement it on a SSR site, the server-generated pages will only have the free content; no way to authenticate user from the server. Is this correct?
Yes, generally the easiest way to add web monetization is client-side with the meta tag. We are working on offering back-end integration and options.
There is also an option to use the OAuth Web Monetization Script. However, you will need to register your client app and be approved for OAuth access. docs.coil.com/
Thank you for your answer, Ali!