dashCommerce

Just wondering if anybody started working to add Google Checkout on DC 3.0 ?

Since no one has replied, I assume no one is working on, or has worked on, integrating Google Checkout in DC 3.x.  If this is not true, please reply here.  I am subscribed to this thread.  You can also send an email via my profile...

I am going to begin work on this payment provider today.  After a quick review of the IPaymentProvider interface and the PayPalProPaymentProvider, it looks straight forward. 

I might add that the code is excellent and I am very much indepted to mr. Cyvas for his outstanding work and contribution. 

That being said, I'll be trying to mirror the architectural principles I've observed in dashCommerce.  If anyone would like to help, please let me know.  I'll be glad to share some of the tasks

My plan so far...

• create dashCommerceContrib library project
• build IPaymentProvider nunit test harness
• build GoogleCheckoutPaymentService class (derived from PayPalService class)
• build GoogleCheckoutPaymentProvider class (derived from PayPalProPaymentProvider class implementing IPaymentProvider)

levous,

You won't need to implement the GoogleCheckoutPaymentService - the PaymentService is generic, it just uses the IPaymentProvider to run the transactions. So, you only *need* to implement IPaymentProvider in your GoogleCheckoutPyamentProvider as you had planned and then create a user control that can be used to store the provider settings. That's about it. You can do this in a completely separate assembly or, if you like, just plop it into the code base.

Thanks for the kind words on the code - we are trying to keep this professional and useful to everyone.

HTH

I think I understand what you are saying:

• that paymentService uses IPaymentProvider, and everything could be wrapped up in that interface implementation. 
• that I'll need a user control for storing google checkout provider settings to config

Am I correct?

Regarding the service, I like the way you implemented PayPal providers using a service layer that knows how to translate orders into payment engine execution requests.  Looking at the Google Checkout architecture, I believe this will be a good design that can include the necessary notification handler logic.  In addition to the user control for storing provider settings, I think I will also need a handler for receiving notifications from Google.

So, the plan now:

• Test Harness
• GoogleCheckoutService (translates orders to Google CO protocol)
• GoogleCheckoutaymentProvider (implements IPaymentProvider using GoogleCheckoutService)
• GoogleCheckoutProvidersSettingsUserControl (for managing provider settings)
• Notification Handler (to be wired in web.config and will receive notifications from Google when customers complete checkout transactions)

I am curious as to why the Google Checout was removed recently.  I will likely go back and review that source code to see where you were headed.  However, I fear there is a good reason for the decision.  Can you enlighten me?

thanks very much!

It was removed because it wasn't at all complete and with the 3.0 release, we are looking to release only completed features. I'm not savvy on the specifics of Google Checkout, but you may be able to use the Synchronize method in IPaymentProvider and it sounds like you may be able to do something similar to the IPN and pdt handlers for paypal to support the communication from google. Just offering this up as some potential help - not sure if it's an apples to apples comparison.

Thanks very much for the reply. I'll look into synchronize but I am not exactly sure how that works by looking at it. Since I do not have a paypal account to debug with, I am putting off discovery for a minute. I have gotten a little stuck at the moment because I am not sure exactly when the transaction needs to be created and how to set up a pending order and set it in a state that indicates the user left the universe to go pay on google. Hmmm, wonder why you pulled that out :) For now, I am going to write the integration that works, including notification handler and such, and then try to weave that back into the IPaymentProvider. I'll post back and check back as I make progress. Thanks