hi there,
Not sure if you're referring to a methodology or the code. I'm going to go by 1st principles and state that in your methodology, you should have a payment interface that all other payment gateways use with their API's (using an adaptor pattern or similar). something like the code below would be an appropriate interface:
public interface IPaymentMethod
{
#region Methods
void ProcessPayment(ShoppingCartCollection shoppingCart, PaymentInfo paymentInfo, Customer customer, Guid OrderGuid, ProcessPaymentResult processPaymentResult);
string PostProcessPayment(Order order);
#endregion
}
and then each resulting class would implement this interface (similar to below):
public class GoogleCheckoutPaymentProcessor : IPaymentMethod
As for the specifics of the google API, i'm not familiar with it, but there will be c# examples floating around.
hope this at least points to best practice, if not an definitive answer as such.
[edit] just looked at TBH payment gateway stuff. it's a little weak, so you might be better off re-writing it to conform to some kind of interface and then slot the google one in behind it. there's a great example of this in the nopSolutions cart which has a very similar structure to TBH, so will be easy to follow. give it a look at:
http://www.nopcommerce.com/
jimi
http://www.originaltalent.com