REST for Payments? Not really...

One of the things I have gotten feedback on is the lack of REST in
the http://xmlns.webpki.org/webpay/v1 scheme.

I haven't actually thought too much about this before but after looking a bit
further into the topic I believe skipping REST was a wise decision.

Signed Input Data:
===============
There is no obvious solution for signed input data using REST.

Illogical Messaging Structures:
=========================
input format
https://server/path?operation=checkfunds&amount=$3.75&currency=USD
output format
{
   "status": "ok",
   "sayswho": "your bank"
}
For the kind of systems I'm working with where messages are wrapped, dealing
with two formats would greatly complicate the design and make documentation,
debugging, and logging even more daunting than it already is.

Multi-hop:
=========
In real systems messages often have to traverse between different nodes which
makes REST-like messaging awkward while transferring messages like:
   {
     "operation":"checkfunds",
     "amount":"3.75",
     "currency":"USD"
   }
using HTTP POST is a no-brainer

Anders
Didn't take a REST :-)

Received on Monday, 28 September 2015 04:27:57 UTC