SagePay Protocol 2.23 Actinic V7

[Spitos]

Is it possible to use the 2.23 protocol with Actinic V7? I can only find thorough documentation for protocol 2.22 but it won't let us do what we need it to.

We are currently on protocol 2.20 and we want to enable PayPal payments through the SagePay system. We almost got there and thought everything was set up correctly. We amended our custom templates to include the PayPal option and enabled it through the mysagepay admin area so that the user can select to pay via paypal.

We hit a stumbling block whilst placing a test order:
Once the customer reaches their Paypal account they have their standard Paypal address shown as the delivery address and can also change it.
This is a problem as it doesn’t pass this information back to our shopping cart. We need to remove the ability for them to change the delivery address in Paypal and also for their address details to be brought through from our cart instead.

So we have spent some time talking to SagePay and PayPal on this issue and here is the response from PayPal:
“if the merchant is stating that the shopper is given the option to edit the address once on the PayPal pages, it sounds as though they are using an older version of the Sage Pay Protocol (2.22).

So in order to ensure the shopper is not given the option of choosing their address options on the PayPal screens, the merchant will need to upgrade to Sage Pay Protocol 2.23.”

SagePay also confirm that we need to use the latest protocol, so it looks like i'll have to re do our custom templates from scratch.


Post #37 here:
http://community.actinic.com/showthr...t=46852&page=3

Claims that the changes can be made by getting a copy of the V10 Act_OCCPROTXTemplate.html and comparing the changes but I'd rather not guess and spend the day working at it if it doesn't work at the end. SagePay also tell us that PayPal is not active on the TEST account so we can only see if what I've done is successful if we post to the LIVE account, but this could break all the other payment options if it hasn't worked!

This page details the changes needed to make protocol 2.23 work with V10:
http://www.teclan.com/blog/?p=276

Has anyone modified the V10 version to work with V7 so that they can use the latest protocol?
Does anyone have a copy of that file?
Can anyone offer and help or advice from their own experiences with PayPal integration in V7?


Any help appreciated!

[Spitos]

Does anybody have any experience with this?

I think I have most of it sussed out but 2.23 requires a separate first name and surname which is not very easy to do in V7 considering we have actinic link to transfer the customer data into sage.

There is this code in the latest protocol (which I got from the V10 trial):

#
# add the invoice address and customer name
#
my ($sFirstName, $sLastName);
$sLastName = $::InvoiceContact{NAME}; # default to a blank first name and complete last name
if ($sLastName =~ /^(.+)\s+(\S+)/) # if the name field looks to contain at least two name parts
{
$sFirstName = $1; # break the name up
$sLastName = $2;
}


To me this implies that it will split the names if they are passed on a single field but this is more wishful thinking than anything.

Is there anyone who can please help on anything at all in here?

[Duncan Rounding]

Have you tried the v10 files as is in v7?

[Spitos]

Yes pretty much apart from adding the secret key details etc.

P.S. Thanks for your post about WinMerge, I can't believe I hadn't found this before it is so useful!

I'm waiting for Sage Pay to upload the templates to the test site, i'll post any updates when I have them for anyone else interested.