Re: [WebDNA] [OT] WebDNA Payment Processing Integration
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106793
interpreted = N
texte = Thanks for the detailed information. I really appreciate it! The development budget is definitely tight since it's a startup business and the monthly transaction processing cost is definitely an issue since it could be a while to market things to the point of generating decent online sales. The higher per transaction fee and lower monthly gateway fee would likely be the best way to start. Also, starting simple and growing the back-end capabilities over time will be the approach. Thanks again. I'll look at the options you suggest in more detail. Brian On 6/22/11 6:18 PM, "Aaron Michael Kaczmarek"
wrote: > 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 > > --------------------------------------------------------- > 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:
Thanks for the detailed information. I really appreciate it! The development budget is definitely tight since it's a startup business and the monthly transaction processing cost is definitely an issue since it could be a while to market things to the point of generating decent online sales. The higher per transaction fee and lower monthly gateway fee would likely be the best way to start. Also, starting simple and growing the back-end capabilities over time will be the approach. Thanks again. I'll look at the options you suggest in more detail. Brian On 6/22/11 6:18 PM, "Aaron Michael Kaczmarek" wrote: > 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 > > --------------------------------------------------------- > 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
Brian Wachter
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[WebDNA] XML Help (2009)
Sample Tearoom Search Error (1997)
WebMerchant crashing and other WebMerchant problem (2000)
Where is f2? (1997)
I'm new be kind (1997)
OPEN MARKET PATENTS SOUND ECOMMERCE ALARM (1998)
Showif, Hideif reverse logic ? (1997)
2.01 upgrade problems (1997)
Multiple Search Fields (1998)
Re:my First Ship table (1998)
[isfile] ? (1997)
File Uploads: WebCat/SiteEdit (1998)
Quantity * price (1997)
Amusement (2004)
Round up prices (2000)
[WebDNA] fastcgi 7+ & [cart]? (2010)
Emailer errors (1997)
How can I record purchases to a database? (1998)
Bad Cookie (1998)
Follow-up to listfiles bug report ... (2003)