I'm setting up alternative sites,
Sagepay told me that I can use my same account but need to send vendorTx value accross to them as part of the payment process to identify alternative sites.
This will allow me to say vendorTX="site1" and vendorTx="site2" etc
when I then log into the sagepay reporting, that same value will be available to me for accountancy purposes.
Can anyone guide me where I need to place this extra bit of code, I'mm assuming its going to be in the OCC*.pl code
It would be even better to reference the "site=<actinic variable>"
Can I then reference that same code within the emails etc ?
I also note that there is a downloadable exe file from actinic that offers to upgrade the PSP files .
Should I apply this BEFORE doing any upgrade/ammendments ??
as a small PS, I seached sagepay for SELLERDECK but found absolutely no mention of that name, only ACTINIC.
Has anyone from SellerDeck contacted sagepay to suggest adding the sellerdeck name anywhere on their site.
kev
Sagepay told me that I can use my same account but need to send vendorTx value accross to them as part of the payment process to identify alternative sites.
This will allow me to say vendorTX="site1" and vendorTx="site2" etc
when I then log into the sagepay reporting, that same value will be available to me for accountancy purposes.
Can anyone guide me where I need to place this extra bit of code, I'mm assuming its going to be in the OCC*.pl code
It would be even better to reference the "site=<actinic variable>"
Can I then reference that same code within the emails etc ?
I also note that there is a downloadable exe file from actinic that offers to upgrade the PSP files .
Should I apply this BEFORE doing any upgrade/ammendments ??
as a small PS, I seached sagepay for SELLERDECK but found absolutely no mention of that name, only ACTINIC.
Has anyone from SellerDeck contacted sagepay to suggest adding the sellerdeck name anywhere on their site.
kev