Jason Judge

Still nothing from Sage Pay but promises. Documentation is dated back to 2015 for direct, 2017 for Pi, and yet there are warnings that we *will* need to change the...

@BigManatee Yes it is confusing, because Sage Pay always fail to speak with a unified voice. This means you have to pick up snatches of detail from here and there,...

Yes, I believe that is correct. Sage Pay are great on the phone - responsive, informative, helpful. I just don't know *why* we have to keep calling them. Nothing I...

This simple app provides an example of the drivers in action: https://github.com/thephpleague/omnipay-example It gives you screens to enter config data, and to enter payment data, and they will run through...

Laravel 6 support was added a few weeks ago. I'm not sure anything really changed in it: https://github.com/barryvdh/laravel-omnipay/blob/master/composer.json#L13

Webhook handling is a complicated one, since there are so many different responses expected from different gateways. Some just expect a `200`, some need a JSON message, and some need...

Hmm, no release tag for Laravel 6 yet - give @barryvdh a nudge or try `dev-master` to get going.

What do you have installed as a HTTP client? If nothing yet, try installing Guzzle. If you give us the "requires" section of your `composer.json`, that might tell us what...

I don't see the guzzle client in your `composer.json`. Are you specifically trying to use the curl client, or trying to get it working any which way? Guzzle 7 client...

Like this? https://github.com/thephpleague/omnipay-braintree Or is something missing from that?