Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


These support forums are now closed for new topics and comments.
Please head on over to http://eureka.ucommerce.net/ for support.

  • Phil Crowe 192 posts 256 karma points
    Sep 26, 2012 @ 13:21
    Phil Crowe
    0

    SagePay returning to orderfail url even when order is successful

    In simulator mode my SagePay would return the user to the correct url as specified in the SagePay.config

    <?xml version="1.0"?>

    <sagePayPaymentMethodService
      vendor="myVendor" 
    txType="AUTHENTICATE" 
    debug="true" 
    testMode="TEST" 
    successUrl="http://myurl.com/shop/checkout/orderconfirmation.aspx"
    abortUrl="http:// myurl.com/shop/checkout/orderfailed.aspx"
    failureUrl="http:// myurl.com/shop/checkout/orderfailed.aspx"
    notificationURL="(auto)" />

    When i switched to TEST, I go through to sagepay, put in my test card details and confirm the payment but get sent back to the order failed url. In SagePay the order has been successful and when i spoke to sagepay on the phone they said as far as their system is concerned the order was successful. They said SagePay posted status=registered to our server and the response from our server was 'OK' but the redirect url sent was the order-failed url. Can anyone help?! Really need to get this sorted ASAP. I have tried using the LIVE SagePay server and got the same issue. Tried accross different browsers. Could it be a domain or IP issue, i have swapped both and not sure if maybe there is an area of configuration i might not have updated?

     

    Regards

    Phil

  • Phil Crowe 192 posts 256 karma points
    Sep 26, 2012 @ 16:39
    Phil Crowe
    0

    Really urgent that i get this sorted. I've noticed there is no basket information in mysagepay. Should uCommerce pass these details through?

  • Phil Crowe 192 posts 256 karma points
    Sep 26, 2012 @ 16:52
    Phil Crowe
    1

    Notice the callback url that ends with PaymentProcessor.axd returns this:

    Could not find the Payment with PaymentId: 192, PaymentMethodName: 8

    ive checked and there is no paymentid 192....

  • Søren Spelling Lund 1797 posts 2786 karma points
    Oct 01, 2012 @ 11:40
    Søren Spelling Lund
    0

    Turns out that depending on environment and configuration SagePay could in some cases return a different status code for accepted payments. I updated uCommerce 2.6.1.0 to include a fix for this.

    Thanks for helping find it, Phil

Please Sign in or register to post replies

Write your reply to:

Draft