Re: [WebDNA] [OT] WebDNA Payment Processing Integration Recommendations?

This WebDNA talk-list message is from

2011

It keeps the original formatting. numero = 106792
interpreted = N
texte = Anything that has an API works well. I've worked with Authorize.net, GoogleCheckout, and PayPal.Authorize.net is the simplest I've worked with since you can send an HTTP POST with TCP Send with simply a string of name-value parameters. Its also the most flexible if you're building everything yourself and your developing a complete solution for your client.Some require you send all of the criteria wrapped in XML.It really depends though....I've worked with clients that don't do tons of online sales so a gateway where you pay a monthly subscription, like authorizeNet is not the most economic option. In those cases, Google Checkout(GC) or PayPal(PP) are best. Given your clients average online sales, the higher cost of the per-transaction percentage of GC or PP may in fact be more economic than the monthly + per transaction charge of a payment gateway. Plus you'll have to write more code to do the entire checkout process. It really depends on the volume of sales, the development budget, the nature of the product, and lastly the depth of back-end inventory management.With GC and PP, you can go really simple and send shopping-cart data in a form post using their name-value pair parameters. If you need more customization, you have to wrap the cart data into XML, TCP Post, then redirect the user to their checkout page. The nice thing is that you can create callback urls where you can receive XML data back about the processing and stages of the purchases. This allows you to update inventory based upon whether the transaction was approved or not, or any other database information if you need such a thing.On 6/22/11 5:43 PM, Brian Wachter wrote:> Perhaps slightly off-topic, so feel free to respond off-list.>> I'm wondering if anyone has a recommendation or list of online payment> processor gateways that work well with WebDNA. It's been a long time since I> did this, but have a potential commerce site to develop. In the past, I> integrated my WebDNA-enabled commerce site with AuthorizeNet and it worked> pretty well. I don't know if this is still a good choice or not.>> Thanks in advance,> Brian Wachter> Stoneport LLC>>> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list.> To unsubscribe, E-mail to:> archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us Associated Messages, from the most recent to the oldest:

Re: [WebDNA] [OT] WebDNA Payment Processing Integration Recommendations? (Aaron Michael Kaczmarek 2011)
[WebDNA] [OT] WebDNA Payment Processing Integration Recommendations? (Brian Wachter 2011)

Anything that has an API works well. I've worked with Authorize.net, GoogleCheckout, and PayPal.Authorize.net is the simplest I've worked with since you can send an HTTP POST with TCP Send with simply a string of name-value parameters. Its also the most flexible if you're building everything yourself and your developing a complete solution for your client.Some require you send all of the criteria wrapped in XML.It really depends though....I've worked with clients that don't do tons of online sales so a gateway where you pay a monthly subscription, like authorizeNet is not the most economic option. In those cases, Google Checkout(GC) or PayPal(PP) are best. Given your clients average online sales, the higher cost of the per-transaction percentage of GC or PP may in fact be more economic than the monthly + per transaction charge of a payment gateway. Plus you'll have to write more code to do the entire checkout process. It really depends on the volume of sales, the development budget, the nature of the product, and lastly the depth of back-end inventory management.With GC and PP, you can go really simple and send shopping-cart data in a form post using their name-value pair parameters. If you need more customization, you have to wrap the cart data into XML, TCP Post, then redirect the user to their checkout page. The nice thing is that you can create callback urls where you can receive XML data back about the processing and stages of the purchases. This allows you to update inventory based upon whether the transaction was approved or not, or any other database information if you need such a thing.On 6/22/11 5:43 PM, Brian Wachter wrote:> Perhaps slightly off-topic, so feel free to respond off-list.>> I'm wondering if anyone has a recommendation or list of online payment> processor gateways that work well with WebDNA. It's been a long time since I> did this, but have a potential commerce site to develop. In the past, I> integrated my WebDNA-enabled commerce site with AuthorizeNet and it worked> pretty well. I don't know if this is still a good choice or not.>> Thanks in advance,> Brian Wachter> Stoneport LLC>>> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list.> To unsubscribe, E-mail to:> archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us Aaron Michael Kaczmarek

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] [OT] WebDNA Payment Processing Integration Recommendations?

2011

Top Articles:

Related Readings: