Issue with SagePay Forms #130

1stChoiceSpares · 2019-03-27T16:20:27Z

Sorry I am unable to understand your documentation. I have setup a function with the following code:

$gateway = OmniPay::create('SagePay\Form')->initialize([
            'vendor' => 'OurVendorID',
            'testMode' => true,
            'encryptionKey' => 'OurEncryptionKey',
        ]);
        $response = $gateway->purchase([
            'amount' => '99.99',
            'currency' => 'GBP',
            'transactionId' => 'FC-TEST01',
            'description' => 'Pizzas for everyone at PHPNE',
            'returnUrl' => 'https://example.com/success',
            'failureUrl' => 'https://example.com/failure'
        ]);

        $result = $gateway->completePurchase()->send();

This just results in an error about crypt:
Missing or invalid "crypt" parameter

Instead I then use the following from your documentation:

$crypt = $_GET['crypt']; // or supplied by your framework
$result = $gateway->completeAuthorize(['crypt' => $crypt])->send();

Again this gives an error relating to Crypt:
Undefined index: crypt

So then I try switching in code found in the test functions:

$crypt = '@BE1508740B97BEC235E9E8474168E3D4DEAD71C1395CDAC1A24F4784A71135AE797F5451F48EB2EAF5669EB3F6953F466FC3A03E5815E607C4DD18C03D7BDD61D176DB4DF131DC0F02DFC5145FFBA841651641BDAA405E72F4EF8849C2B2FD1F08763E3E66EAF3C479429A92014C7B8316F3B446BA09D28A821EE81C243E3DDD6F4C1F41D6ADEAC74D42B221645ADCC69E2F22ECDCAA010F63CCD02EAF0CE20F98439DAC7C31E528A7574656191150C1CC6CCD9FBEFCBFC9B34029FAB8F62DBC1C1618628FF0529B4E66B8AB857A79CC2FD0F14299A3505D22F964322755E6190EDD5BD42066D88154F950585236B6A2951D28BDA474E3FB17638DAA2F6304EAEA3AB9513DD0604D447000208D55DA4FDF544BEE00B5744170C1FC1E6DC6AADA07BEF6EB1FA46C14B99C3371491816A5C2CF7E03EDF6D58142767F7550DFFFE634FA56532605768FFEC1B20BEC32177816DDAB804149E9A301E495F11568F58896E90B1AC5776C2F12CE578955292F640A1E81213AAAA7856CD622FC241C65AC08215B94F933FD47050E0CFB2BFA85D7570A9D401B2366001AA377C50825B6D3893BDEC46D87F9121EC39DBF948F69399B8E842635556C7BC08E2E0C85CFA3EA2F9E4582ABDB3EB9668C83EDC34A5862F3CBC1A10935A189493D42D5C3FE4AF2BFF29B8464934B221B5A56B407F4E638B6766E6C706996A0252F2DDB30AFC8C1DA65F89987F4A9AA317BB104ED42F749DE3A43C39C515B67B3EA619D4092843DA551EEFC22CF672F53F753DEB93F1E8487BFE89C0100AFB9799238B24E523B0D6D53F824DEC0F6897F97FA507648D13276841B3B2E98030CBCD8E04F5E2C06C57BCC6F6C346440E620718F8877FFE969';

$result = $gateway->completeAuthorize(['crypt' => $crypt])->send();

This then results in a blank page.

I fee the documentation is missing some vital parts to get this working. Could you provide me with a basic example function that will redirect to SagePay forms?

The text was updated successfully, but these errors were encountered:

judgej · 2019-03-27T18:21:13Z

On that last section, what does $result contain? Is it the result of the transaction? You may be getting an exception thrown if the $crypt value is not valid for your encryption key.

Okay, the process is:

That first section of code you posted will create a $result that is a redirect object. Use it to redirect to Sage Pay. The redirect will be a POST, and a very quick and dirty way of doing that will be to use $result->redirect(); This will output a self-POSTing form and send the user off to Sage Pay to enter their card details.
The next part of the code is to handle the result when the user returns from Sage Pay. It will be in a different endpoint on your site. Set up the $gateway object in the same way as before then execute the code to check the result. When the user returns from Sage Pay the URL you supplied as the return URL will have the crypt parameter. Just issue $result = $gateway->completeAuthorize()->send(); as a minimum and the gateway driver will attempt to find the crypt parameter for you. You can pass it in as a parameter just in case you have a framework that gets in the way, but normally it should work.

send() in step 1 does not actually send anything remotely, but it gives you can object with all the details of the redirect that you need to execute to send the user off.

send() in step 2 does not actually send anything either, but reads the payment result from the current URL and decodes it to give you the result of the payment.

The user flow is not explained fully, I agree, so it should be read in conjunction with the description of the flow in the Sage Pay documentation. Feel free to add to the documentation if you think it will help others, once you are familiar with what it is that is missing. I hope the above helps.

judgej · 2019-03-27T18:26:23Z

Another way to do the redirect could be a bit of PHP code like this, which will give the user a button to press to go to the Sage Pay site:

echo '<form method="'.$result->getRedirectMethod().'" action="'.$result->getRedirectUrl().'" accept-charset="UTF-8">';
foreach ($result->getRedirectData() as $name => $value) {
    echo '<input type="hidden" name="'.$name.'" value="'.htmlspecialchars($value).'" />';
}
echo '<p><button type="submit">Go To Sage Pay</button></p>';
echo '</form>';

The above form could POST to an iframe if you like. It's completely your choice, and Omnipay does not try to limit how you can set up your front end. The above would work with most Omnipay drivers for other gateways that redirect the user to their site to enter card details. Sage Pay form needs the user to enter details into a form hosted by Sage Pay. They do have a token-based JavaScript API too (Sage Pay Pi) but that is handled by a different driver.

1stChoiceSpares · 2019-03-27T18:33:22Z

Thanks for your response, I believe I might be having an issue with the creation of the 'crypt'.

I have tried to add:

$response->redirect();

But this gives me the error:
'This response does not support redirection.'

How do you go about generating the crypt value? I did find the following code:
$crypt = openssl_encrypt($response, 'aes-128-cbc', $key, OPENSSL_RAW_DATA, $key);

$key being my encryption key but I the error is along the lines of the $response must be a string.

Sorry about this, payment methods confuse me to no end!

1stChoiceSpares · 2019-03-27T18:41:03Z

I have the out put of my result here, any thoughts on where I am going wrong? Thanks:

judgej · 2019-03-27T18:47:48Z

Have you got the purpose of steps 1 and 2 that I posted earlier? What I'm seeing here looks like they are mushed together. Only step 1 creates a redirect object. You need to focus on that first - setting up the data, then redirecting the user to Sage Pay. The completeAuthorize() is something you do when the user returns to your success URL.

Are you getting the initial redirect?

judgej · 2019-03-27T18:48:41Z

Here, play with this, it runs the code in the documentation:

https://omnipay.acadweb.co.uk/sagepay3x/test3.php

1stChoiceSpares · 2019-03-27T18:50:14Z

Ah! I see what you mean. I think I was misunderstanding there. I will have a play and get back to you, cheers, had a moment of clarity now.

judgej · 2019-03-27T18:57:32Z

Needs a diagram really. This may help just to set the picture: https://www.sagepay.co.uk/support/12/36/sage-pay-form In that diagram, $gateway->purchase() sets up an object to handle flow "2", and $getway->completeAuthorize() handles what comes back in flow ~~"3"~~, sorry "4". It's the simplest of all the Sage Pay payment methods, as it is just two steps - send the user off with an encrypted payment request, and get the user back carrying their encrypted payment result. This package does all the encryption and decryption for you, based on a encryption key that Sage Pay supplies for you (log into your control panel as the admin - only the admin can do it - to generate a key).

1stChoiceSpares · 2019-03-27T19:02:28Z

Thanks very much :) I'll have another crack at it tonight and see what I can get working.

…e` a little clearer.

Issue #130 documentation changes

1stChoiceSpares · 2019-03-28T12:57:25Z

Thanks I think I have the process clear in my head now. I am coming up with this error though:

LOG.error: Call to undefined method Omnipay\SagePay\Message\Form\PurchaseRequest::redirect()

I must not have included something correctly although I do have:
use Omnipay\Omnipay;

At the top of my controller. Any idea what I have missed out?

judgej · 2019-03-28T13:49:47Z

redirect() is in the purchase response, not the request.

Remember $response = $request->send() where $request = $gateway->purchase().

1stChoiceSpares · 2019-03-28T17:17:59Z

Thanks! I have it redirecting to sagepay as expected. Now just got to get my success function working.

Thanks very much for all your help :)

judgej · 2019-03-30T10:41:14Z

No problem. Please close this issue when you are ready, and feel free to contribute to the documentation, even if it is just one line - everything helps.

judgej · 2019-06-18T09:42:57Z

Closing as answered.

judgej added a commit to academe/omnipay-sagepay that referenced this issue Mar 27, 2019

Issue thephpleague#130 Expand documentation to make `completeAuthoriz…

24210c2

…e` a little clearer.

judgej added the question label Mar 27, 2019

This was referenced Mar 27, 2019

Validate transactionId on Sage Pay Form result #131

Closed

Issue #130 documentation changes #132

Merged

judgej added a commit that referenced this issue Mar 27, 2019

Merge pull request #132 from academe/master

bba571a

Issue #130 documentation changes

judgej closed this as completed Jun 18, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Issue with SagePay Forms #130

Issue with SagePay Forms #130

1stChoiceSpares commented Mar 27, 2019

judgej commented Mar 27, 2019 •

edited

Loading

judgej commented Mar 27, 2019 •

edited

Loading

1stChoiceSpares commented Mar 27, 2019

1stChoiceSpares commented Mar 27, 2019 •

edited by judgej

Loading

judgej commented Mar 27, 2019

judgej commented Mar 27, 2019

1stChoiceSpares commented Mar 27, 2019

judgej commented Mar 27, 2019 •

edited

Loading

1stChoiceSpares commented Mar 27, 2019

1stChoiceSpares commented Mar 28, 2019

judgej commented Mar 28, 2019

1stChoiceSpares commented Mar 28, 2019

judgej commented Mar 30, 2019

judgej commented Jun 18, 2019

Issue with SagePay Forms #130

Issue with SagePay Forms #130

Comments

1stChoiceSpares commented Mar 27, 2019

judgej commented Mar 27, 2019 • edited Loading

judgej commented Mar 27, 2019 • edited Loading

1stChoiceSpares commented Mar 27, 2019

1stChoiceSpares commented Mar 27, 2019 • edited by judgej Loading

judgej commented Mar 27, 2019

judgej commented Mar 27, 2019

1stChoiceSpares commented Mar 27, 2019

judgej commented Mar 27, 2019 • edited Loading

1stChoiceSpares commented Mar 27, 2019

1stChoiceSpares commented Mar 28, 2019

judgej commented Mar 28, 2019

1stChoiceSpares commented Mar 28, 2019

judgej commented Mar 30, 2019

judgej commented Jun 18, 2019

judgej commented Mar 27, 2019 •

edited

Loading

judgej commented Mar 27, 2019 •

edited

Loading

1stChoiceSpares commented Mar 27, 2019 •

edited by judgej

Loading

judgej commented Mar 27, 2019 •

edited

Loading