Skip to content
loading...

re: Announcing the Grant For The Web Hackathon on DEV VIEW POST

TOP OF THREAD FULL DISCUSSION
re: You're correct that server-side verification requires a custom payment pointer right now; it can be quite complex and requires peering into the Int...
 

Thanks for replying! Basically I was thinking of some form of middle-man for the monetization system where a user (who makes the content) can manage it without knowledge of coding.

For example, if they wanted to do profit sharing off a particular page, just knowing the page URL and who they wanted to split it between would be enough. Similarly, if they wanted to donate a particular % to charity or something, they can automagically do that with some changes in an admin system.

While there are JS examples on the Web Monetization site that do a revenue sharing example, to me this is something that makes more sense as a server-side system and I figured "incepting" the actual money through its own custom payment pointer to do the processing on makes the most sense for a real implementation.

Gotcha, that's a cool idea! Implementing a revenue share like that is easier than writing a payment pointer which verifies payments, because it doesn't require you to hook into the Interledger network yourself.

If you want to do revenue sharing server-side you can run a server that redirects to different payment pointers, just like this example on webmonetization.org. The website that wants to use your revsharing service would embed a URL from the revshare service instead of their own payment pointer. Then the user can adjust the revenue sharing parameters on your service without having to update their page every time.

code of conduct - report abuse