PaySwarm recently announced a new PaySwarm Alpha for developers (read our two part series about PaySwarm here). The article states, “This is a public sandbox — a developer test ground — that implements some of the newest PaySwarm REST API features.” It continues, “The biggest change was replacing the authentication mechanism that we were using for PaySwarm. We had implemented the system last year using the OAuth protocol only to find out that it made things more complicated than they need to be for the use cases that we were trying to cover. Some developers have asked why OAuth didn’t work for PaySwarm when it works for large sites like Facebook and Twitter.”

The announcement goes on, “The core of the issue has to do with the scope of PaySwarm. Typically, developers that implement OAuth only need to perform secure API authorization. PaySwarm needs to perform secure API authorization as well as digital signatures on messages and data. The fundamental lesson that we learned last year was that if you need to support digital signatures, then you basically have a secure API authorization mechanism, and thus adding OAuth unnecessarily complicates the overall system.”

Read more here.

Image: Courtesy PaySwarm