Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 10 of 10

Thread: Has anyone got Sagepay (Protx) working in ML 8.0.1.2?

  1. 09-23-2011, 08:50 AM #1
    enazx7gv is offline Junior Member
    Join Date
    Sep 2011
    Posts
    5

    Default Has anyone got Sagepay (Protx) working in ML 8.0.1.2?

    Has anyone got Sagepay (Protx) working in ML 8.0.1.2
  2. 09-24-2011, 04:16 AM #2
    webopius is offline Senior Member
    Join Date
    Nov 2008
    Location
    London, UK
    Posts
    440

    Default

    Yes, but it's been a while since I did a Sagepay install on v8.

    What's the problem?
    Webopius.com: ASPDotNetStorefront web development and ecommerce project management
    Webopius is now a Sage Pay Approved Partner
  3. 09-26-2011, 01:27 AM #3
    esedirect is offline Senior Member
    Join Date
    Feb 2010
    Location
    Norfolk, UK
    Posts
    343

    Default

    Have it working for 8.0.1.2 currently. Some months ago Sagepay changed the URLs, so this might be your issue.
    http://www.esedirect.co.uk
    --------------------------------------------------------------------------
    Using MS 9.2.0.0 with the following customisations:

    Lightbox/Fancybox enlarged images;
    Auto-suggest searchbox;
    Extra product information shown only to our IP Address (such as supplier info, costs, etc.);
    Failed transactions emailed via trigger;
    Custom app to show basket contents when customer online;
    Orders pushed through to accounting systems.

    All the above without source!
  4. 09-26-2011, 06:26 AM #4
    enazx7gv is offline Junior Member
    Join Date
    Sep 2011
    Posts
    5

    Default

    The URLs have been changed to the new Sage Pay ones but I get the error "BillingSurname field is required" when doing a live or test transaction (not bothered about simulation), any ideas?
  5. 09-26-2011, 09:21 AM #5
    webopius is offline Senior Member
    Join Date
    Nov 2008
    Location
    London, UK
    Posts
    440

    Default

    Hi,

    SagePay's protocol version 2.23 onwards now makes the BillingSurname, BillingFirstnames and BillingAddress1 fields compulsory.

    However, as part of calling the SagePay gateway, ASPDNSF v7 (and I think v8) should specify the protocol to use as 2.22. In this case, the 'Billing....' fields are not compulsory and v7 certainly only used to send across the BillingAddress field only.

    So either:

    Your V8 version is calling SagePay requesting the 2.23 protocol to be used (you'll need your source code to check this).
    OR
    SagePay has changed and is insisting on the 2.23 protocol - unlikely, because of course this would affect all v8 SagePay users.
    OR
    Something in your SagePay control panel config is insisting on the 2.23 protocol

    Adam
    Webopius.com: ASPDotNetStorefront web development and ecommerce project management
    Webopius is now a Sage Pay Approved Partner
  6. 09-28-2011, 07:04 AM #6
    enazx7gv is offline Junior Member
    Join Date
    Sep 2011
    Posts
    5

    Default

    Thanks, looking at the FailedTransaction table it looks like it could be sending 2.22 values but with VPSProtocol=2.23, can anyone help?
    Last edited by enazx7gv; 12-02-2011 at 06:58 AM.
  7. 09-28-2011, 07:30 AM #7
    webopius is offline Senior Member
    Join Date
    Nov 2008
    Location
    London, UK
    Posts
    440

    Default

    Hi

    It sounds like your best course of action is to:

    Contact SagePay support and ask them which protocol your account is set to use. You can also ask them at the same time to check which protocol your store is sending requests as.

    If you need the latest 2.23 gateway and your site is using 2.22, Vortx can help
    Webopius.com: ASPDotNetStorefront web development and ecommerce project management
    Webopius is now a Sage Pay Approved Partner
  8. 10-05-2011, 08:38 AM #8
    enazx7gv is offline Junior Member
    Join Date
    Sep 2011
    Posts
    5

    Default

    Quote Originally Posted by esedirect View Post
    Have it working for 8.0.1.2 currently. Some months ago Sagepay changed the URLs, so this might be your issue.
    Please could you list the URLs you are using? It might also useful to others that are having problems as well.
  9. 10-05-2011, 08:49 AM #9
    esedirect is offline Senior Member
    Join Date
    Feb 2010
    Location
    Norfolk, UK
    Posts
    343

    Default

    Here are the appconfigs:

    Code:
    Name			ConfigValue
ProtXURL.Live.Abort	https://live.sagepay.com/gateway/service/abort.vsp
ProtXURL.Live.Callback	https://live.sagepay.com/gateway/service/direct3dcallback.vsp
ProtXURL.Live.Purchase	https://live.sagepay.com/gateway/service/vspdirect-register.vsp
ProtXURL.Live.Refund	https://live.sagepay.com/gateway/service/refund.vsp
ProtXURL.Live.Release	https://live.sagepay.com/gateway/service/release.vsp
    http://www.esedirect.co.uk
    --------------------------------------------------------------------------
    Using MS 9.2.0.0 with the following customisations:

    Lightbox/Fancybox enlarged images;
    Auto-suggest searchbox;
    Extra product information shown only to our IP Address (such as supplier info, costs, etc.);
    Failed transactions emailed via trigger;
    Custom app to show basket contents when customer online;
    Orders pushed through to accounting systems.

    All the above without source!
  10. 12-02-2011, 07:02 AM #10
    enazx7gv is offline Junior Member
    Join Date
    Sep 2011
    Posts
    5

    Default

    This is an update which may be useful to other people, the site was upgraded to 8.0.1.4 and appears to be working with Sagepay.