>1) client sends request for content with some header with payment information attached. 2) server verifies payment transferred What you describe looks like au

>1) client sends request for content with some header with payment information attached. 2) server verifies payment transferred What you describe looks like authentication and authorization rather than payment processing. Which may be a good thing. Adding support for authentication to the RSS protocol (OAuth for RSS anyone?) and RSS clients can potentially make it more interesting for publishers and solve the problem with monetization.