Umbracians for Unicef - the friendly fundraising
In the spirit of holidays and humanity, we started a fundraising for Unicef. You won't believe what we could change if every visitor on Our Umbraco donated a dollar or euro. Click and find out!
I'm trying to implement Ogone as a payment provider for TeaCommerce, but I faced the following challenge:
There are two types of online payment processing Ogone supports: Direct payment, when you need to provide all required data about credit card to Ogone yourself, and this way supports a kind of transaction status calls, and other transaction maintenance calls, but I can't use that way because of some security reasons. :(
And there is another way to work with Ogone payments - e-Commerce standard, when you send prepared request to Ogone, then your user will be redirected to special Ogone payments page, where he should enter all data about credit card, and do the payment. After that you get a response on the URL you provided: acceptURL - for successful payments, cancelURL for cancelled payments, exceptionURL - if something went wrong, declineURL - if payment was declined.
So, the problem is that in Ogone e-Commerce standard way of payments processing you can't ask transaction status somehow - you just receive the status of your payment on one of defined URL's above in request params, and that's all. That's why after specifying acceptURL as teaCommerceContinueURL in my payment provider, I can get the status of my transaction in request variable in GetOrderNameFromContinueRequest, but I can't see the way to update the order in that function. Also, if I specify my acceptURL as teaCommerceCallBackURL, I can update my order status in ProcessCallback function, but how can I show to the user my Continue page in that case?
There is no any kind of NotificationUrl on Ogone, and I can't get transaction status in any way, that's why I unable to use default way as TeaCommerce payment provider works...
Could you give me any advice what I can do in that situation?
Thank you, Alexey
Your lucky - at the moment we are changing alot in the payment provider API and because we try to be able to support lots of these different payment gateways ways of doing payment. So if you wait a couple of days I can send you a beta og the newest version of Tea Commerce. Both fix different bugs and making the payment provider API better.
Thank you, Anders!
I'm looking forward to use newest beta! :) Let me know when it is available.
Ohh is that a Ogone payment provider I see in the new Tea Commerce beta..? Of yes it is :) Will send you the beta as soon as we have a clean build of it. Then you could test the provider for me? Have you got at Ogone test account? Hit me an email so I can send the beta when ready. info [at] teacommerce dot dk
@Alexey - hope you like the Ogone provider in the beta. If you found one of my previous answers helpfull, it would help others if you could mark that as a solution. Thanks
Sorry for late answer, I wasn't healthy last days to check how Ogone
payment provider works in new beta. But I'm doing it right now.
Really, you did a great job, it works fine, but... There is always
"but", unfortunately. What the specific settings should be applied for
Ogone account to allow payment provider to capture or cancel payments?
Because for now I always have the following error message for order: "Ogone - Error making API request: 50001111 - Some of the data entered is incorrect. Please retry."
I tried to play with default operation in Ogone, but even for Sale
operation, when I already have my order status as "Captured", I get that
error. Also I tried different "Default data capture procedure" settings
- also without any success.
Can you check what is going on? Or what settings should I use to allow capture/cancel funds without errors?
One little question in addition...
The default settings of Ogone payment provider in beta don't fit me completely - I need also ability to specify particular payment method and credit cart brand for Ogone processing, so I have to create my own payment provider based on yours. Did you add something specific to beta version of TeaCommerce, which should be taken to account during custom payment provider implementation, or all remains the same as it described here: http://anders.burla.dk/umbraco/making-a-payment-provider-for-tea-commerce/ ?
Hope you are well again. Yes the Ogone settings i a little difficult and I haven't had the time to do documentation. But sounds like you are missing to specify a SHA IN and SHA out password in the Ogone administration and also in Tea Commerce.
The payment API is updated since the blog post so not all is in that. But give me a little time and i will support it in our payment provider. You will just have to update the ogone.config file with some new parameters. So no need to inherit from ours.
I have sent you an email with a new beta build. Just add these two parameter to your ogone.config file. PM="CreditCard" and brand="VISA" and give it a try.
I have as a default option added PMList to the config file which can be used to specify what payment methods that is available
Thank you very much for your great work! TeaCommerce becomes better and better with every release. :)