Payment issues

I have spoken to sagepay this morning and they were very helpful. Basically our Vendor Tx codes issued from the website are too simple and therefore this will continue to be a problem. If we can change the format of the vendor codes as per the info below this should stop the problem. When we were using opencard for example, the vendor code was the order number which was a 5 figure number and therefore did not cause any issues. Sagepay recommend the longer the number or more complicated the code, the less likely for the error.
THE VENDOR CODES CURRENTLY GENERATED ARE ONLY 2 DIGIT NUMBERS AND THIS SEEMS TO BE THE ISSUE. PLEASE ADVISE HOW THIS CAN BE CHANGED TO DIFFERENT FORMAT.

4001 : INVALID : The VendorTxCode has been used before. All VendorTxCodes sh...
Error number: 4001
Error message:
4001 : INVALID : The VendorTxCode has been used before. All VendorTxCodes sh...
Explanation:

The error message is generated when the vendor tx code you are using for the transaction has been used before. If the vendor tx code you are using for the transaction matches that of another you have processed you will receive the error - 4001.

The vendor tx code must be unique for every transaction that is processed through your account. When a transaction is generated you assign a reference for the transaction passed to Sage Pay as the field VendorTxCode=.

Aa
​0-9
{ }
,
-
_

Any characters that are added that are not on the allowed range will generate an error.

When creating a transaction the vendor tx code is allowed to contain up to 40 characters enabling you to always post a unique value to our systems. It can include the following characters -
Solution:

To prevent this error you will need to check the code you have in place to ensure a unique VendorTxCode is created for each new transaction.

Any attempt with a previously used vendor tx code will generate the error and prevent you form posting a transaction to our system.

A common practice for unique vendor tx codes is to use the company name followed by an incremental number that will always ensure vendor tx code is unique.

A few examples of this method are -
TestVendor-01
​TestVendor-02
​TestVendor-03

Alternatively you can include your own order references that will help ensure the codes do not match -
TestVendor-01-SP001
​TestVendor-01-SP002
TestVendor-01-SP003
​​This will prevent the error message from generating on your account.

Thankyou.

Hi guys,

We've got more SagePay problems again....

We have had an order through this afternoon as below, paid by Sagepay, but not down as confirmed paid on the website or by email from sagepay. ( I have now confirmed the order manually on the back end of the website, so the customer is not confused)
I have checked on our Sagepay account and it was paid at the time of order.
An order went through this morning via Paypal and this was confirmed!!
I have just done a test payment for £1 custom order VIA SAGEPAY and payment went through but came up with error message after payment. 'Error while processing encrypted data'
We have had this before, but cannot remember how it was resolved.
Can you suggest where things might be going wrong so that we can get this fixed?
Thanks,
R.

Hi
Still trying to resolve previous issue, but I have another more serious issue that has come to light today, in that the website after checkout and choosing any payment method (Sagepay and/or Paypal) is going to an error page ie invalid page. We have changed nothing on the back end of the website, so hoping this is hika shop issue and can be resolved easily. Having several problems since we upgraded to the latest edition amd getting very concerned as we are unable to take any orders at all.

[url=http://]http://backyardfarmer.co.uk/products/compost/checkout/task-step/step-4[/url]

- Can see you have released another update, so done this one two and problem now fixed.

Hi

Re the sagepay issue above, I have spoken to Sagepay and the password we have. has not been changed, and is the same. They have asked if any encryption information has been changed in the recent update and if it AES encryption.

Thankyou

Would also add that normally, hikashop sends an email as soon as an order is created and also one when order confirmed (confirmed by payment). Since this issue found today, we are not getting an email when order created either .....

Can see you have released another update, so done this one two and problem now fixed.

Hi

Have solved our other issue with a further upgrade, and was hoping this may also have fixed the original problem with Sagepay payments sending error msg 'Error while processing encrypted data' and not updating website or confirmation email.

Have done another test sale and though the same message appears and the admin back end of website still not updated, we are now getting an email from sagepay to say payment confirmed. If we can just rectify the encryption issue we are sorted. Any other ideas or fixes greatly received.

Thankyou

Hi

Altough we are able to take payments we still havn't resolved the encryption issue, which confuses our customers when they get the error page after payment and doesn't confirm payment back to the website.

following on however we have received notification from Sagepay of update as below re Secruity Certificate upate. Please can you advise whether or not this will have any affect on Hikashop ie does hikashop need to update their plug in

Security certificate update

Hi,

Further to our previous communication regarding our SSL Security Certificate update, we are notifying you of a change to the release date.

The LIVE update was scheduled for the 14th June 2016, however after listening to our customers it has become apparent that a short postponement is necessary to allow everyone time to complete the changes. The LIVE update will now take place on the 13th July 2016 and no further postponements will be considered.

We will be removing our current SHA-1 certificates and replacing them with SHA-256 based certificates (a version of SHA-2 certificates).

For more information on SHA please visit our support page.

How does this impact me

The way you currently process transactions uses Sage Pay hosted payment pages. As these pages are controlled by Sage Pay there is communication between our servers and yours.

Most modern software and hardware is SHA-2 compatible and it’s unlikely there will be any impact. As we do not have full visibility of the deployed ecommerce solution you will be best placed to assess the impact this may have.

To avoid any disruption to your integration you’ll need to ensure that their system is capable of working with the SHA-256 algorithm and support for SHA-1 will be disabled when we switch.

To see all compatible SHA-256 browsers and operating systems click here.

Hi
the orders are not automatically confirmed, I have to do it manually. Orders from paypal work ok and are confirmed but with sagepay the payment goes through ok, we get email confirmation from sagepay that the payments is successful, but it does not auto confirm on the back end fthe website and sends the error message "Error while processing encrypted data". Seems strange that it works for paypal not sagepay, so I would assume it is something to do with the sagepay plug in. Nothing has changed as far as sagepay are concerned and it worked fine until the last HIka update.

Apart from that and possibly more important, could you please check the other part of my query which is in red above re the security certificate update - can you please advise that Hikashop is compatable with everything they have mentioned.

Thankyou