Ptrash
08-20-2002, 03:04 PM
First, I've never understood while my posts on e-commerce questions are placed in this forum, since I'm not a reseller and don't own a web hosting biz. But since everytime I post on e-commerce topics in the main forum they're moved here, I thought i'd save the mods some work. So..
I'm just a lowly webmaster (and not too much of a master, either) for a small non profit. We want to process class and conference registrations, donations and publication and t shirt sales on-line. The guy who is doing the actual programming (which is partly paid work, but at a low rate since it's subsidized by his non profit) has tried to use a one size fits all solution, using a php shopping cart. This is an inelegant solution for us, especially since we're dealing with people who are not technically savvy and may not have ever bought anything on-line. Not only that, the project has also taken way too long; consequently we are looking for someone else to complete it. I had a referral to a PHP programmer, who I called and described my situation to. This guy started talking about needing two different systems for handling purchases and registrations, stating that some merchant accounts can process one system, while others are needed for the other. Now this is counterintuitive to me, since the only info the card processor should get is the purchase amount, name and address. The only reason it would have a bearing is if a shipping address was required, but as it's not (at least by my card processor), then I don't see the type of purchase coming into play.
Does anyone out there know what this guy could be possibly talking about? I can see how the front end might--no, should, be--different depending upon the type of transaction. He insisted the issue was card processing back end systems.
Sorry, I put this into the wrong forum. Should've been "Running a web-hosting biz."
I'm just a lowly webmaster (and not too much of a master, either) for a small non profit. We want to process class and conference registrations, donations and publication and t shirt sales on-line. The guy who is doing the actual programming (which is partly paid work, but at a low rate since it's subsidized by his non profit) has tried to use a one size fits all solution, using a php shopping cart. This is an inelegant solution for us, especially since we're dealing with people who are not technically savvy and may not have ever bought anything on-line. Not only that, the project has also taken way too long; consequently we are looking for someone else to complete it. I had a referral to a PHP programmer, who I called and described my situation to. This guy started talking about needing two different systems for handling purchases and registrations, stating that some merchant accounts can process one system, while others are needed for the other. Now this is counterintuitive to me, since the only info the card processor should get is the purchase amount, name and address. The only reason it would have a bearing is if a shipping address was required, but as it's not (at least by my card processor), then I don't see the type of purchase coming into play.
Does anyone out there know what this guy could be possibly talking about? I can see how the front end might--no, should, be--different depending upon the type of transaction. He insisted the issue was card processing back end systems.
Sorry, I put this into the wrong forum. Should've been "Running a web-hosting biz."
