Jason Judge

I do realise there are many legacy gateways that need to be supported and we don't have resources to completely rewrite them. But we also need to have an eye...

Cool - thanks. I'll try writing an OmniPay wrapper for my package and see how it goes, but it looks like it could slip in quite well. I think my...

Yes, it is certainly needed for PSR-7 to be _really_ useful as a portable interface. Having to create specific factory wrappers for each implementation now is a pain. I suspect...

Kind of. The PSR-7 implementations do not do simple stuff such as parsing the body. You need to do that yourself, which means inspecting the header and doing `json_decode()` and...

Laravel custom/bespoke apps - that's our main use-case.

PAYONE and Sage Pay Server, both use the notification interface. I've added some [documentation on how Sage Pay](https://github.com/thephpleague/omnipay-sagepay#notification-handler) uses it and also [how PAYONE uses it](https://github.com/academe/omnipay-payone#notification-callback). My hope is that...

I believe Payum handles the storage and sharing of transactions between the front end and the back-channel. This is something OmniPay does not do - it is more concerned with...

Not all gateways support dynamic notification URLs, so the transaction ID will be in the POST data. Same thing though - there is no context _until_ the handler inspects the...

On that note of derived fields, e.g. only `netPrice` and `tax` being supplied, then the gateway asking for `price` or `grossPrice`, then that would be a lot safer if a...

Too true. There is an example of it somewhere, but that's hard to find. IIRC the example just passes the items in as a nested array, and the core uses...