Sagepay problem - VendorTXCode

  • Posts: 10
  • Thank you received: 0
10 years 6 months ago #156604

-- url of the page with the problem -- : mywebsite.com/mypage
-- HikaShop version -- : www.hunterstoves.co.uk/
-- Joomla version -- : 2.5.14
-- PHP version -- : x.x.x
-- Browser(s) name and version -- : XXXXX x.x.x
-- Error-message(debug-mod must be tuned on) -- : Error_message

Our sage pay plugin has been working fine until now. We now have an error message on Sagepay. Sagepay say its a transaction code issue on our site and we should speak to you.

INVALID : The VendorTxCode has been used before. All VendorTxCodes sh...
Support

Every transaction registration that is sent over to the Sage Pay systems must have its own unique VendorTxCode. If the VendorTxCode matches that of a previous transaction registration for a successful transaction against your account you will receive this error message.

Solution:
You must check your code to ensure that you are posting a unique VendorTxCode for each new transaction. If you are posting over a VendorTxCode that has been used for a previous transaction registration for a successful transaction against your account you will be presented with this error message.

Ok - how can this be done in Hikashop? Could anyone help?

Last edit: 10 years 6 months ago by mediaset. Reason: additional info

Please Log in or Create an account to join the conversation.

  • Posts: 82868
  • Thank you received: 13376
  • MODERATOR
10 years 6 months ago #156610

The VendorTxCode contains the order ID.
This indicates that you're using the same order IDs as before and SagePay doesn't allow that. You probably must have done some tets with your account and then reset the order ids and thus it's colliding with the previous orders ids you had.
PayPal has actually a similar check on the order id. Here is the documentation relative to PayPal for that issue:
www.hikashop.com/support/documentation/i...l-error.html#already
It explains how to increase the order_id to 10000 so that you don't get the problem anymore.

Please Log in or Create an account to join the conversation.

Time to create page: 0.057 seconds
Powered by Kunena Forum