There is one Ogone account. There are old web sites and new web sites. Old web sites are using old signature policy. New web sites are using TeaCommerce and new signature policy.
The client want to use one Ogone account for all websites.
So there is a posibility to use old signature policy with TeaCommerce?
Thanks!
-------
They have indeed upgraded the SHA-IN and SHA-OUT signature policy the
26/05/2010. But it is still possible to use the old signature policy.
In order to to that, the e-payment postfinance technical informations must be changed.
On the page "Global security parameters" the value of the field "Compose the string to be hashed by concatenating the value of:" should be "Main parameters only".
Could you send your email address to [email protected] and we will send you some screenshots of the Ogone payment provider setup fomr the partial finished blog post :) Maybe that can give you an idea if everything is setup correctly.
Thanks Anders for the screenshots. It was the SHA configuration on the Ogone side. It should use the SHA-512 with UTF-8.
But I have the same problem as Dmytro, the Ogone account is used by other websites using the old signature. Could be nice to have a choice of the algoritm used for encoding the signature inside the ogone provider ?
Dmytro have you done the custom payment solution ? If yes, could you share the code somewhere?
Ogone, old signature policy
Hi guys,
There is one Ogone account. There are old web sites and new web sites. Old web sites are using old signature policy. New web sites are using TeaCommerce and new signature policy.
The client want to use one Ogone account for all websites.
So there is a posibility to use old signature policy with TeaCommerce?
Thanks!
-------
They have indeed upgraded the SHA-IN and SHA-OUT signature policy the 26/05/2010. But it is still possible to use the old signature policy.
In order to to that, the e-payment postfinance technical informations must be changed.
On the page "Global security parameters" the value of the field
"Compose the string to be hashed by concatenating the value of:"
should be "Main parameters only".
Hi Dmytro
Tea Commerce only supports the new way Ogone do. Could your client upgrade to the new signature policy to have it work?
Hi Anders,
Thanks!
I will propose the client to upgrade old sites.
Super - feel free to contact us again if you need more help.
If you found my last answer helpful - could you please mark it as the solution so others can easily find the correct answer - thanks in advance
/Anders
Maybe there is some solution to support the old policy?
I think the solution will be to implement the old policy through a new payment provider that could be created by following the tutorial at
http://anders.burla.dk/umbraco/making-a-payment-provider-for-tea-commerce/
Helllo,
I have the same problem I am always receiving the " unknown order/1/s/ "answer.
I have double check all parameters of SHA-IN Pass phrase and OUT
The settings of ogone is: "Compose the string to be hashed by concatenating the value of: "
Do you have an idea ? I am stuck with this...
I've the last version of teacommerce.
Here is an example of the generated parameters:
<form action="https://secure.ogone.com/ncol/prod/orderstandard_utf8.asp" method="post"><br /><input id="PSPID" type="hidden" name="PSPID" value="MYID" /><br /><input id="LANGUAGE" type="hidden" name="LANGUAGE" value="fr_FR" /><br /><input id="ACCEPTURL" type="hidden" name="ACCEPTURL" value="http://mydomain/tcbase/teacommerce/PaymentContinue/Ogone/30CD1544ADBA50DED8AED781F009CE48.aspx" /><br /><input id="CANCELURL" type="hidden" name="CANCELURL" value="http://mydomain/tcbase/teacommerce/PaymentCancel/Ogone/30CD1544ADBA50DED8AED781F009CE48.aspx" /><br /><input id="BACKURL" type="hidden" name="BACKURL" value="http://mydomain/panier/validation-achat" /><br /><input id="ORDERID" type="hidden" name="ORDERID" value="ORDER-36" /><br /><input id="AMOUNT" type="hidden" name="AMOUNT" value="5000" /><br /><input id="CURRENCY" type="hidden" name="CURRENCY" value="EUR" /><br /><input id="CN" type="hidden" name="CN" value="NAME" /><br /><input id="EMAIL" type="hidden" name="EMAIL" value="[email protected]" /><br /><input id="DECLINEURL" type="hidden" name="DECLINEURL" value="http://mydomain/tcbase/teacommerce/PaymentCancel/Ogone/30CD1544ADBA50DED8AED781F009CE48.aspx" /><br /><input id="EXCEPTIONURL" type="hidden" name="EXCEPTIONURL" value="http://mydomaintcbase/teacommerce/PaymentCancel/Ogone/30CD1544ADBA50DED8AED781F009CE48.aspx" /><br /><input id="SHASIGN" type="hidden" name="SHASIGN" value="B6EFD6B0767D7CC0E2BF8511167A703198CD725305F5CE01C7CF4A7F4E5E498D0244833215E74575326724F53B84527CB2CCC65DDF4F9F3D5035991B8D3840BB" /><br /><input id="next" type="submit" value="" /></form>
Thank for your help!
MrFlo
Hi MrFlo
Could you send your email address to [email protected] and we will send you some screenshots of the Ogone payment provider setup fomr the partial finished blog post :) Maybe that can give you an idea if everything is setup correctly.
Kind regards
Anders
Hi,
Thanks Anders for the screenshots. It was the SHA configuration on the Ogone side. It should use the SHA-512 with UTF-8.
But I have the same problem as Dmytro, the Ogone account is used by other websites using the old signature.
Could be nice to have a choice of the algoritm used for encoding the signature inside the ogone provider ?
Dmytro have you done the custom payment solution ? If yes, could you share the code somewhere?
Regards,
MrFlo
is working on a reply...