Sagepay V3 protocol

Discussion in 'Payments processing' started by webproxylists, May 8, 2015.

  1. webproxylists

    webproxylists Member

    Joined:
    Mar 29, 2013
    Messages:
    30
    please can you advise how I change my sagepay form from V2.3 to be compliant with V3 ...

    Sagepay are stopping anything below V3 at then end of July and the test environment only accept V3
  2. webproxylists

    webproxylists Member

    Joined:
    Mar 29, 2013
    Messages:
    30
    ok i changed where it says the version number and added my IP to sagepay for the server ... now I can send the payment to the test site fine, however im now getting
    HTTP Status Code: 500
    HTTP Status Message: The request was unsuccessful due to an unexpected condition encountered by the server.
    Error Code : 5006
    Error Description : Unable to redirect to Vendor's web site. The Vendor failed to provide a RedirectionURL.
  3. webproxylists

    webproxylists Member

    Joined:
    Mar 29, 2013
    Messages:
    30
    im not sure if this has any bearing on it, but on the sagepay failure report it lists this
    Callback URL /members/payment/sagepay/ipn
    Im wondering if its the callback url its failing on rather than the success thanks url ?

    ive tried adding a After Purchase Redirect User to this URL in the product setup, but im still getting the above errors :/
  4. webproxylists

    webproxylists Member

    Joined:
    Mar 29, 2013
    Messages:
    30
    also I noticed this in the sagepay notes
    Full qualified URL (including http:// or https:// header) to which you’d like the customer redirected on completion of the transaction.

    If you wish to pass parameters back to your own site (such as the session id or transaction code), these should be included in RedirectURL.

    Screen Shot 2015-05-11 at 21.33.58.png
  5. webproxylists

    webproxylists Member

    Joined:
    Mar 29, 2013
    Messages:
    30
    5006 : Unable to redirect to Vendors web site. The Vendor failed to provide a RedirectionURL.
    Error number:
    5006
    Error message:
    5006 : Unable to redirect to Vendors web site. The Vendor failed to provide a RedirectionURL.

    Explanation:


    As part of the Server integration transactional process Sage Pay send a post to your notification URL with the status, and outcome of the transaction.

    We then need a response to the notification post from your system that includes a Redirect URL. This Redirect URL is used by Sage Pay to re-direct the shopper back from our payment pages to your website where they will be presented with either a Success or Failure page.

    If you have received this error it is due to the response to the notification post not including a re-direct URL, or the URL is not in the correct format.

    When this error is generated the transaction may not be visible within your MySagePay admin panel. Also the transaction may not be visible within your Successful, Failed, or Invalid logs.

    This is due to the transaction not being archived on our systems and still in an active state.

    We will attempt to notify your system of all transactions processed through your account, as the transaction is still active Sage Pay will attempt multiple times to notify you of the status of the transaction until it times out.

    Once the transaction has "timed out" it will then appear in your logs, and on the MySagePay transaction list.



    Solution:


    To resolve this error you must first ensure that :

    • You are supplying a Redirct URL to Sage Pay in the response to the notification post.
    • Your Redirct URL is in the correct format when it is returned to Sage Pay.
    • Check your server logs to ensure the notification post from Sage Pay has been received and a response including the Redirect URL has been sent.
    • Ensure your response is in line with the Sage Pay Server Protocol - Section B2.
    This will enable you to check that your platform is reacting to the Sage Pay notification post in the correct way. Normally the exclusion or format of the Redirect URL is the cause of this error. Your server logs will identify if the notification post is being received by Sage Pay and a response is being sent by your system.

    If the above has been checked, or unable to be checked look to the server for possible restrictions that could cause the transaction to encounter errors.

    • Ensure you have opened ports 80 and 443 on your Servers to allow posts from Sage Pay.
    • Ensure all Sage Pay IP Addresses have been added to your Server.
    • Check any additional firewall or security measures will allow contact from the Sage Pay systems.
    After checking, and validating all of the above you are still encountering this error you can change the Notification URL to another link on your server that can be tracked to ensure contact is being made by the Sage Pay system and a response is being generated.

    For information on the Server integration process, and the response that must be sent from your system please
  6. alexander

    alexander Administrator Staff Member

    Joined:
    Jan 8, 2003
    Messages:
    6,279
    Please contact us in helpdesk. If plugin needs to be updated, we will do this.
    webproxylists likes this.
  7. webproxylists

    webproxylists Member

    Joined:
    Mar 29, 2013
    Messages:
    30
    thanks done that, the file they sent over ... im still having issues with I will get my colleague to re contact them :/

    now Im getting this with their new form

    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: MALFORMED
    Status Detail: 3045 : The Currency field is missing.
  8. richard_giles

    richard_giles New Member

    Joined:
    Oct 17, 2011
    Messages:
    8
  9. alexander

    alexander Administrator Staff Member

    Joined:
    Jan 8, 2003
    Messages:
    6,279
    This just can't be solved via forum, post follow up to the ticket which you have in helpdesk.
  10. webproxylists

    webproxylists Member

    Joined:
    Mar 29, 2013
    Messages:
    30
    where do I enter my clients sagepay encryption password ?
  11. webproxylists

    webproxylists Member

    Joined:
    Mar 29, 2013
    Messages:
    30
    seems ive been entering my actual account password instead of sagepays encrypted password in amember admin

Share This Page