The W3C Web Payments Working Group has published working drafts of Web Payments HTTP Specifications that include the Web Payments HTTP API 1.0 and Web Payments HTTP Messages 1.0. The two specifications are designed to work together to enable payment requests outside of a browser context.
Something awesome is happening in the world of music and the web. But first, some primer.
Rdio is one of the few music subscription services that do a tremendous amount of things right, including having its robust Rdio API. For $5 a month, you can get all of the music you want, have collaborative playlists, share content to Facebook and Twitter, and keep up with what your friends are listening to. For $10, you can do all that and store the music to your phone for offline or higher quality enjoyment.
The Take.io API from Brazil has a REST protocol with data formats in XML and JSON. According to Take.net, "The take.io RESTful API currently defines five services: SSO, Core, Billing, Messages and Reports." The company states further that, "Take.io is Take.net DNA translated into a set of APIs designed to allow companies to use SMS, MMS, voice, pricing, location, CRM, etc., all of which are integrated with their existing systems."