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.

  • K.Garrein 164 posts 629 karma points
    Jul 18, 2014 @ 14:24
    K.Garrein
    0

    Using the Ogone 'Bank Transfer XX' payment method

    Hey.

    We're using Ogone successfully for many online Ogone payment methods (credit cards, ideal, giropay, paypal, etc.). 

    But now our client also wants to use some offline Ogone payment methods (Bank Transfer BE, Bank Transfer DE, etc.). Payment using those offline payment options do not seem to work... we get an error on the post-sale request "HTTP/1.1 500 Internal Server Error".

    Does anyone has a solution for this?


    Example Ogone feedback:

    ****************************************
    Process Error :
    ****************************************
    Probleem met online postsale http-verzoek 

    ****************************************
    Resultaat postsale request :
    ****************************************
    Verzonden parameters :
    orderID=Reference%2D195¤cy=EUR&amount=990%2E21&PM=Bank+transfer+BE&ACCEPTANCE=&STATUS=41&CARDNO=&ED=&CN=Kris+Garrein
    &TRXDATE=07%2F18%2F14&COLLECTOR_BIC=BBRUBEBB&COLLECTOR_IBAN=BE82320055803968&EMAIL=kris%40fbd%2Ebe
    &PAYMENT_REFERENCE=Reference%2D195&PAYID=33415830&NCERROR=0&BRAND=Bank+transfer+BE&CREDITDEBIT=&IPCTY=BE
    &CCCTY=&ECI=&CVCCheck=&AAVCheck=&VC=&AAVZIP=NO&AAVADDRESS=NO&AAVNAME=NO&AAVPHONE=NO&AAVMAIL=NO
    &IP=81%2E82%2E253%2E106&SHASIGN=FE9496601A58F9A0342748B22FA0B6AF0122E16C

    HTTP/1.1 500 Internal Server Error


    In the uCommerce log we see the following, which is weird since all the other online Ogone payment options use the same SHA keys:

    2014-07-18 12:27:18,320 [97] ERROR Umbraco.Core.UmbracoApplicationBase - [Thread 50] An unhandled exception occurred

    System.Security.SecurityException: Shasigns did not match. Please make sure that 'SHA-OUT Pass phrase' is configured in Ogone and that the same key is configured in Ogone.config.

       at UCommerce.Transactions.Payments.Ogone.OgonePaymentMethodService.ProcessCallback(Payment payment)

       at UCommerce.Transactions.Payments.PaymentProcessor.ProcessRequest(HttpContext context)

       at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


     

  • Morten Skjoldager 440 posts 1499 karma points
    Jul 22, 2014 @ 13:25
    Morten Skjoldager
    0

    You need to figure out how the SHA's are calculated for those transaction. It seems different to normal credit card SHA calculations. 

    Then in the processcallback method you need to take that into account. 

    So first see what fields should be included and then we can figure out how it should work.

    Hope that helps.

    Regards

    Morten

  • K.Garrein 164 posts 629 karma points
    Jul 28, 2014 @ 08:42
    K.Garrein
    0

    According to Ogone, the SHA is always calculated the same way for all their payment methods.
    So there shouldn't be a problem. 

    There is a difference thou, Bank Transfer XX returns status 41 (offline payment), how does uCommerce deal with that status?

    Thanks.
    Kris. 

  • Morten Skjoldager 440 posts 1499 karma points
    Jul 28, 2014 @ 08:59
    Morten Skjoldager
    0
               var keysOfInterest = new List<string>
                                    {
                                        "AAVADDRESS","AAVCHECK","AAVMAIL","AAVNAME","AAVPHONE",
                                        "AAVZIP","ACCEPTANCE","ALIAS","AMOUNT","BIC","BIN","BRAND","CARDNO",
                                        "CCCTY","CN","COMPLUS","CREATION_STATUS","CURRENCY","CVCCHECK","DCC_COMMPERCENTAGE",
                                        "DCC_CONVAMOUNT","DCC_CONVCCY","DCC_EXCHRATESOURCE",
                                        "DCC_EXCHRATETS","DCC_INDICATOR","DCC_MARGINPERCENTAGE","DCC_VALIDHOURS","DIGESTCARDNO",
                                        "ECI","ED","ENCCARDNO","FXAMOUNT","FXCURRENCY","IBAN","IP","IPCTY",
                                        "NBREMAILUSAGE","NBRIPUSAGE","NBRIPUSAGE_ALLTX","NBRUSAGE","NCERROR","NCERRORCARDNO","NCERRORCN",
                                        "NCERRORCVC","NCERRORED","ORDERID",
                                        "PAYID","PM","SCO_CATEGORY","SCORING","STATUS","SUBBRAND","SUBSCRIPTION_ID","TRXDATE","VC"
                                    };
    
    This is the list of keys we're looking for when we're calculating the hash. They should be the same. What version of uCommerce are you running BTW? Because we've had that list updated for the same error you saw. 
  • K.Garrein 164 posts 629 karma points
    Jul 28, 2014 @ 09:05
    K.Garrein
    0

    As suggested in your documentation, we included all keys  in Ogone (I just double-checked, they're all included).

    The version of uCommerce is 6.0.5.14183

    Regards.
    Kris 

  • K.Garrein 164 posts 629 karma points
    Jul 28, 2014 @ 09:31
    K.Garrein
    0

    In your list of keys are "alias", "bin", "creation_status", and some others that are not available from the posted ogone parameter list.
    "Alias" and "creation_status" do not even exist in the list of parameters you can select in the ogone configuration panel.

    We included all keys in the ogone configuration, but this is what one of the feedback lists looks like: 

    orderID=Reference%2D207&currency=EUR&amount=4457%2E64&PM=Bank+transfer+BE&ACCEPTANCE=
    &STATUS=41&CARDNO=&ED=&CN=kris%2Egarrein%40fbd%2Ebe+kris%2Egarrein%40fb&TRXDATE=07%2F28%2F14
    &COLLECTOR_BIC=BBRUBEBB&COLLECTOR_IBAN=BE82320055803968&EMAIL=kris%40fbd%2Ebe
    &PAYMENT_REFERENCE=Reference%2D207&PAYID=33584877&NCERROR=0&BRAND=Bank+transfer+BE&CREDITDEBIT=
    &IPCTY=BE&CCCTY=&ECI=&CVCCheck=&AAVCheck=&VC=&AAVZIP=NO&AAVADDRESS=NO&AAVNAME=NO&AAVPHONE=NO
    &AAVMAIL=NO&IP=81%2E82%2E253%2E106&SHASIGN=078ABDE91ABAD33AF8DEEB502F11D2FFC87549EA

     

  • Søren Spelling Lund 1797 posts 2786 karma points
    Aug 12, 2014 @ 11:44
    Søren Spelling Lund
    0

    Hi,

    Looking into this I have identified the parameters that we do not include in the SHA:

    • CY
    • COLLECTOR_BIC
    • EMAIL
    • COLLECTOR_IBAN
    • PAYMENT_REFERENCE
    • CREDITDEBIT
    It would seem that there are different parameters available depending on Ogone configuration. I'm contemplating changing the postive list to a negative list to make this more robust.
    Can you verify that it works if you turn off these in "Dynamic e-commerce parameters" in Ogone?
Please Sign in or register to post replies

Write your reply to:

Draft