I've followed the tutorial on http://www.publicvoid.dk/IntegratingUCommerceWithAPaymentProvider.aspx to create a custom payment provider with Elavon, but I'm running into a few issues on uCommerce 2.0. I know that the Entities V2 are slightly different, and I'm not sure what are all the methods and return typesthat I should have in my class.For instance, on the method "AquirePayment(Payment paymentToAquire)", should I have a return type of PaymentStatus.
Also, how would I pass in the credit card and billing information (including billing state). I've been re-writing all of the XSLT macros as UserControls, as I understand how to validate input better using .NET than XSLT. I'm also having a hard time figuring out how to calculate sales tax (United States) on a state by state basis.
Is there any up to date documentation that would help me out, other than the API reference? http://www.ucommerce.dk/docs/.
Okay, I solved my one issues about the AcquirePayment(Payment paymentToAcquire). I got a warning and what I need to return from the Interface in Visual Studio.
I am curious however how I pass billing information to the AcquirePayment method. Does the Payment datatype somehow encapsulate that?
Is there a way to debug what happens in the "pipelines"? I'm having issues with NaN coming up in the order, and my price is showing up as a discount instead of the price. I am using PriceGroups to get the price.
Unfortunately there's no way to debug pipelines other than adding and removing pipeline tasks. In your case I believe the issue is related with one of the latest updates, which saw a change to the basket pipeline. Order Subtotal is calculated via a separate task in 2.1. Please make sure it's part of the baket pipeline. You can check see the default pipeline config in the package you download from our site.
I actually got the above issue resolved. I found that I wasn't UCommerce.Xslt.TransactionLibrary.ExecuteBasketPipeline(); in some of my modules. It was intermittent, and I fixed the issues. So yes, you were correct :)
Custom Payment Method with Entities V2
I've followed the tutorial on http://www.publicvoid.dk/IntegratingUCommerceWithAPaymentProvider.aspx to create a custom payment provider with Elavon, but I'm running into a few issues on uCommerce 2.0. I know that the Entities V2 are slightly different, and I'm not sure what are all the methods and return typesthat I should have in my class.For instance, on the method "AquirePayment(Payment paymentToAquire)", should I have a return type of PaymentStatus.
Also, how would I pass in the credit card and billing information (including billing state). I've been re-writing all of the XSLT macros as UserControls, as I understand how to validate input better using .NET than XSLT. I'm also having a hard time figuring out how to calculate sales tax (United States) on a state by state basis.
Is there any up to date documentation that would help me out, other than the API reference? http://www.ucommerce.dk/docs/.
Okay, I solved my one issues about the AcquirePayment(Payment paymentToAcquire). I got a warning and what I need to return from the Interface in Visual Studio.
I am curious however how I pass billing information to the AcquirePayment method. Does the Payment datatype somehow encapsulate that?
Is there a way to debug what happens in the "pipelines"? I'm having issues with NaN coming up in the order, and my price is showing up as a discount instead of the price. I am using PriceGroups to get the price.
Unfortunately there's no way to debug pipelines other than adding and removing pipeline tasks. In your case I believe the issue is related with one of the latest updates, which saw a change to the basket pipeline. Order Subtotal is calculated via a separate task in 2.1. Please make sure it's part of the baket pipeline. You can check see the default pipeline config in the package you download from our site.
Thanks Soren,
I actually got the above issue resolved. I found that I wasn't UCommerce.Xslt.TransactionLibrary.ExecuteBasketPipeline(); in some of my modules. It was intermittent, and I fixed the issues. So yes, you were correct :)
is working on a reply...