3 ms·
ActiveMerchant, Rails SAAS kit, etc. The hard part isn't doing credit card payment. It won't take you fifteen minutes to integrate, e.g., single purchases of
by patio11 18y ago
ActiveMerchant, Rails SAAS kit, etc.
The hard part isn't doing credit card payment. It won't take you fifteen minutes to integrate, e.g., single purchases of Paypal content into a typical Rails app. Trust me.
The hard part is you just introduced requirements for users, authentication, logging, administration, bookkeeping, accounting, and reporting into your app. And those requirements are, necessarily, different for everybody.
Its the same reason Rails doesn't have a One Way To Do It user signup & administration feature: everyone's needs are different and the overhead added by standardization is greater than the engineering effort saved by it.
(Sidenote: if you don't need subscriptions www.e-junkie.com and don't look back. $5 a month, saves a lot of boring report & email integration when you're starting. It took me about ten minutes to set up "People click this button to pay me, e-junkie mails them a license key." when I started. I didn't add anything to their solution for about 2 years. These days they call a script on my server so I can do stat tracking to my own satisfaction, but the core loop hasn't changed much at all.)
- kortina 18y agoYou're right that the reporting stuff is hard to do and difficult to abstract. Google Analytics and Mint both seem like pretty good systems that work for wide userbases, though. I guess because payments are so intertwined with authentication/access levels is why just a custom reporting and easy to use credit card processor may still not be the entire answer.
- dasil003 18y agoThe OA won't load so I'm basically just commenting on the headline. The purpose of a web framework is to abstract all the numerous nuts and bolts issues of building an application on the web which was never designed with applications in mind. The reason Rails is so successful is because it identified the right interface to abstract for the maximum range of utility. As a counter-example I often cite Drupal. Drupal is not just a CMS, but also a framework. It's incredibly well thought out and strikes an awesome balance of out-of-the-box functionality and customisability. The problem is that it comes with a lot of baggage, so you always end up with a lot of complexity that you don't need. Adding high-level application features inevitably leads you down this road which—though appealing for projects without a proper budget (ie. most client work)—ends up forcing all kinds of small sacrifices in design, usability, performance, data modeling, and simplicity. Some projects could never get done without these sacrifices, so projects like Drupal are invaluable in terms of absolute value (especially to small businesses), but to add these features to something like Rails is to utterly destroy an incredibly useful general-purpose tool.
- jonnytran 18y agoI didn't mean in the core, necessarily. But it should be dead-simple to do -- a flip of a switch and a config file maybe.
- dasil003 18y agoDrupal ecommerce module is the perfect example. It tries it's best to be everything to everyone. I doubt you'll see a better turnkey solution that's not a standalone application.
- kolya3 18y agoWhen setting up with e-junkie can you do it in such a way that their name doesn't show up anywhere? (on the payment page, on the credit card bill, etc) I wouldn't want my customers seeing "e-junkie" anywhere where they are giving me a credit card number. It sounds shady and may make some customers put their credit card back in their wallet.
- patio11 18y agoe-junkie is just a wrapper around Paypal/Google Checkout/etc, so they don't show up on the credit card bill ever. I take minor steps to make sure their branding doesn't show on my website. See here: http://www.kalzumeus.com/2008/06/12/how-to-use-e-junkie-without-your-customers-seeing-it/ http://www.kalzumeus.com/2008/06/12/how-to-use-e-junkie-with...