My pull request was merged 4 months ago, however today I ran a composer update - and it blew out all of my edits and brought my site down temporarily.

I had to manually paste over the update code with my previous code.

This repo reflects the correct code but composer update does not....

I don't know if this library is still being maintained or not but in case anyone else runs into this maybe I can save you from busting your head open against a wall like I did.

The packaged version of guzzle that this lib depends upon has included its own cacert.pem file which it stores in vendors/guzzle/guzzle/src/Guzzle/Http/resources/cacert.pem

This ca is old and not valid for the new first data / payeezy certificates and will throw a CURL 60 SSL error whenever you try to use this library.

I cannot see any way in the configuration to override this behavior from my code without manually overriding code in this library.

I am going to fork this library to fix this for myself. If the fix I come up with would work for the production code I'll supply a PR but I'm up against a time constraint on this so I'm not going to spend a lot of time on this.

My credentials are working using v2.3 of this project but not v 2.4

I'm noticing that if I echo out my hmac string just before the request is sent, it is empty. This seems to be a difference between 2.3 and 2.4. Version 2.3 does not have hmac, and it uses API version 11 instead of 14.The documentation does not mention initializing the hmac at all, or there being a key.

Is there something I'm missing? Perhaps I'm misreading the documentation.

Client error response↵[status code] 401↵[reason phrase] Unauthorized↵[url] https://api.demo.globalgatewaye4.firstdata.com/transaction/v14

I am receiving the above error.

Any help will be highly appreciated.

Based on the following snippets, it seems to me like it isn't:

class CompletePurchaseRequest extends PurchaseRequest
{
    public function sendData($data)
    {
        return $this->response = new CompletePurchaseResponse($this, $data);
    }

class PurchaseResponse extends AbstractResponse implements RedirectResponseInterface
{
    public function isSuccessful()
    {
        // FIXME: This makes no sense.
        return false;
    }

As far as I can see, the FirstData_Connect gateway never issues a post request. It just creates a response object using the request data.

Am I missing something? Otherwise it would be good to remove it from the readme.

Add gateway support for First Data's RapidConnect^1,2.

Using FirstData_Webservice, getting a null response on the transaction send.

        $card = Omnipay::creditCard($cardInput);

        $response = Omnipay::purchase([
            'amount'        => '100.00',
            'transactionId' => '100.00',
            'accountId'     => '100.00',
            'card'          => $cardInput
        ])->send();

        dd($response->getMessage());

I am using this package for a Laravel project 7.x, When upgrading to Laravel 8, it requires guzzlehttp/guzzle 7.x while php-http/guzzle6-adapter requires guzzlehttp/guzzle 6.x. Do we have any plans to support guzzlehttp/guzzle 7.x for this package?

php-http/guzzle6-adapter#72
php-http/discovery#189

There appears to be no way to submit a transarmor tokenization transaction in the library. I can create a token by submitting a $0 pre-auth and receive it back just fine but I see no way of using that token to complete a transaction. Am I missing something? There is basically nothing on StackOverflow about this.

There appear to be some issues with sandbox credentials for the Connect 2.0 gateway. The instructions on the First Data web site on how to obtain these no longer work. Contacting First Data support doesn't achieve anything. If anyone has a set of sandbox credentials for this gateway that they can loan me, I would appreciate the use of them.

I see the master branch has commits supporting V3, is there any additional work required to upgrade this driver to V3 of Omnipay?

Hello,

We use the OmniPay/FirstData_Payeezy plugin to process payments. This works great.

We are now interested in enabling 3D secure, and have received the relevant credentials from CardinalCommerce. When we enable 3D secure in Payeezy, it does not route all payments through 3D secure.

Is there anything else we need to do in the code to activate 3D secure for Payeezy?

Thanks

Is this repo still supported?

I'm trying to implement it and added it to my Laravel installation with Omnipay. When I attempt to make payment through the system it just hangs up. I went into my Payeezy sandbox account and it shows a way different URL than what is showing in the Message/PurchaseRequest.php file for test mode and even live mode.

Is there any chance someone can update the repo with the latest functionality of Payeezy?