Jason Judge

`acceptNotification()` implemented for all three APIs. Needs some tests written before a release.

Note that: * `acceptNotification()` MUST be used for the `Shop_Frontend` API and there are no `complete*()` methods. * `acceptNotification()` MUST be used for the `Shop_Client` API, but there are `complete*()`...

We could split the name that is entered into first and surname, but I imagine that would start to get tricky with double-barrel names, and when titles are added ("MR...

No, we used the JS library from Stripe instead. That works well enough.

Just rereading, and the structure of a theme is still eluding me.I am guessing some parts of a theme need to sit in the application and some parts in the...

Just a cursory glance through the docs, it looks like it works very much like Stripe. The payment form is on your site, and the card details are fields with...

Server-to-server calls to this API use HTTP basic authentication. That's not something I'm come across in a payment gateway before, but the HTTP package OmniPay uses would need to support...

It would make sense to include the "Request Merchant Session Key" stage too. That is a REST call server-to-server to get a temporary (400 second lifetime) access token. The "Use...

This API implements token-based security though HTTP header fields in all calls, plus HTTP Basic auth on _most_ calls. I'm not sure how many other gateways mess around with custom...

I have realised while testing this API that the `sagepay.js` script is not necessary to use it. The whole API can be used just like _SagePay Direct_ without grabbing any...