Disclosed are various embodiments for browser-based payment for content. A first request for content is sent to a network content server. A response protocol header is received indicating that a payment is sought for the content in response to the first request. Payment manager code integral to a browser or a browser plug-in is executed in response to receiving the response protocol header. A payment-signifying token is received from a payment provider in response to consummating the payment. A second request for the content is sent to the network content server, where the second request includes a request protocol header specifying the payment-signifying token. The content is received from the network content server in response to the second request.