Announcement

Collapse
No announcement yet.

SagePay problem, VSP Protocol

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    SagePay problem, VSP Protocol

    Unable to take payments via SagePay this morning (Actinic V8), customers get the following error:

    This transaction attempt has failed. We are unable to redirect you back to the web store from which you were purchasing. The details of the failure are given below.
    Status: INVALID

    Status Detail: 3098 : The VPSProtocol value is not supported by the system in use.

    SagePay have said:

    We have been made aware this morning of a issue with vendors posting to us using the 2.20 protocols causing this error, this is being investigated at the moment but in the mean time if you move your VSP protocol version to 2.21 and this will stop the error straight away.

    Is this something I can change within Actinic???
    Hope someone can help, losing orders in the meantime.
    Regards Steve

    www.UltimateFightwear.co.uk
    www.thedancersshop.co.uk
    www.ice-dancer.co.uk


    There must be a get rich quick scheme that works!

    #2
    yeah, that was well advertised by them wasn't it - NOT.

    I got the same thing this morning, protx just stopped working on all my sites.

    They said:

    It seems you are using the old protocol versions for SagePay.

    SagePay upgraded its protocol over 9 months ago and has sent multiple emails to advise of the required amendments.

    It looks like you have been affected by this.

    I suggest you update your protocol versions to 2.23.
    "multiple emails"? I don't remember seeing it at all. Probably included it in their newsletters and just assumed people have got time to actually read them... Certainly didn't receive any entitled "Action Required: You need to update your protx protocols or your payment pages will fail on 14th April" - that would have caught my attention...

    They then forwarded me to some huge online integration guide and told me to go away and read that! I asked if they had a quick guide on updating the protocols, but no. Apparently, they couldn't be bothered. Just point the customer at some online manual that's probably full of useless information for this particular eventuallity and let them figure it out themselves...

    Answers to follow up emails have been equally unhelpful ("talk to your developer" - I AM the developer!)

    Luckily last time they screwed up and went offline for a day or so I signed up to securetrading and set protx as a secondary payment option.

    So not so urgent for me - I just switched off the protx/sagepay option and reuploaded my sites - job done.

    But still need to get it fixed at some point (just in case securetrading go down!) so if anyone know what we're supposed to do to 'upgrade the protocols' I'd also like to know.

    Thanks.

    ps.
    We have been made aware this morning of a issue with vendors posting to us using the 2.20 protocols causing this error
    Glad I'm not the only one who failed to notice their "multiple emails"
    John

    Comment


      #3
      We didn't even get offered a manual

      Just the 'speak to your developer', yes I am the developer!!
      Regards Steve

      www.UltimateFightwear.co.uk
      www.thedancersshop.co.uk
      www.ice-dancer.co.uk


      There must be a get rich quick scheme that works!

      Comment


        #4
        Latest update from sagepay:
        "You will need to contact Actinic as there will be a setting somewhere that you can update"
        We didn't even get offered a manual
        Well here's the link we were given, if you have the time and urgency perhaps you can check to see if it contains the answer? I took a quick look but I just don't have the time to trawl through that...

        For information on the new protocol please view the following link:

        http://www.sagepay.com/developers.asp
        John

        Comment


          #5
          Just taken a look, surprise surprise, nothing specific to Actinic an no search facility.

          Anyone know how we change the protocol being used?
          Regards Steve

          www.UltimateFightwear.co.uk
          www.thedancersshop.co.uk
          www.ice-dancer.co.uk


          There must be a get rich quick scheme that works!

          Comment


            #6
            yeah, thought as much...

            Just a thought, but this thread has a very small number of views, and most of those are probably both of us coming back each time we reply!

            While this might be the most appropriate forum, I think due to it's emergency status maybe you should move (if possible) or repost this in the busier V7/V8/V9/V10 forum (as appropriate) where there is more traffic - and give it a more dramatic headline, like "Help: Sagepay stopped working this morning!".

            There are a lot of helpful and knowledgable people on the forum so the more interesting or urgent the title sounds the more likely one of them will read it and hopefully know the answer...

            I only found it because I was searching for the exact same problem before creating a new post myself.
            John

            Comment


              #7
              In OCCPROTXScriptTemplate.pl line 84 references the VPSProtocol version:
              Line 84: $sHiddenValues .= "<INPUT TYPE=HIDDEN NAME=\"VPSProtocol\" VALUE=\"2.22\">\n";

              Changing this however may create more harm than good because there are obviously differences between each version and therefore very likely the code used for that version in the perl file.

              Comment


                #8
                It seems to me that the only particular differences between 2.22. and 2.23 is the mandatory requirement of passing the Billing Details which I believe is done anyway and the additional integration of Paypal.

                If this is so then I assume that it may be worth trying a small change on line 84 to the 2.23 protocol and see if it works. Backup well first of course if you're going to try this and place the site in test mode first and check it works before going live with it.

                Comment


                  #9
                  Just found out its a V7 not V8 (my wifes website not mine), version
                  V7.0.7.0.0.0HCFA
                  Regards Steve

                  www.UltimateFightwear.co.uk
                  www.thedancersshop.co.uk
                  www.ice-dancer.co.uk


                  There must be a get rich quick scheme that works!

                  Comment


                    #10
                    Also note that Actinic v702 uses protocol v2.20 (not sure what the differences are from v2.20 to 2.23), v853, v905 and v10 use protocol v2.22. So this may only work for those running protocol v2.22.

                    Comment


                      #11
                      Originally posted by Paragon View Post
                      Just found out its a V7 not V8 (my wifes website not mine), version
                      V7.0.7.0.0.0HCFA
                      Best check in your OCCPROTXScriptTemplate.pl file and see what protocol version you're currently using.

                      Comment


                        #12
                        I'm on v2.20 / v7 also
                        John

                        Comment


                          #13
                          Originally posted by jxm28788 View Post
                          I'm on v2.20 / v7 also
                          Looking on the Sagepay forums a number of people have asked that question in the past and the replies indicate that there is no official differences document.

                          I suggest those affected (especially those on v7) call Actinic support.

                          All I know is that from around v2.21 onwards support for 3D was added.

                          Comment


                            #14
                            Actinic support are aware and will be posting advice on this thread when we've determined the correct course of action.

                            Chris

                            Comment


                              #15
                              Another reason why i dumped PROTX/SAGEPAY a long time ago

                              to many problems and a support system that does not give a shit.

                              My advise, get your site fixed then find another psp, AP works well for me reporting is crap but the payment side of things is good. (and lets be honest, Actinic are not going to break their own intergration are they )

                              Comment

                              Working...
                              X