News for hackers. Stuff that matters.
Re: Online Subscription Billing Is A Pain. Recurly Wants To... by jacquesm on Tuesday November 17, 2009 @05:49PM (#947404)
Fair warning: get your own merchant account, never ever use a service that does not use segregated merchant accounts.

All you are doing is to allow other people to reduce their chargeback rates by diluting their volume with your charges and sooner or later they'll go down and leave you swimming.

It will take you a bit longer to get approval and you will have to pay a fee but at least you will be building a business that will last.

All you need to do recurring is an IPSP.

Re: Online Subscription Billing Is A Pain. Recurly Wants To... by dangrossman on Tuesday November 24, 2009 @09:41PM (#960500)
You need your own merchant account to use Recurly or any of their competitors. They are not doing the processing for you. You have to provide them your payment gateway credentials, and they make the API calls to charge customers using your own gateway (and your own merchant account). They're only handling the technical side, none of your money ever touches theirs.
Re: Online Subscription Billing Is A Pain. Recurly Wants To... by johnrob on Tuesday November 17, 2009 @06:05PM (#947427)
What is an IPSP?
Re: Online Subscription Billing Is A Pain. Recurly Wants To... by jacquesm on Tuesday November 17, 2009 @06:08PM (#947433)
Internet Payment Service Provider

A company that registers your merchant account with a company such as paysquare, they will take care of scrubbing and fraud control (for a nominal fee per charge) and will deposit your money in your bank account, usually on a weekly basis.

I should probably do a post on how all the items in an e-commerce transaction go together.

Re: Online Subscription Billing Is A Pain. Recurly Wants To... by adriand on Tuesday November 17, 2009 @08:24PM (#947596)
I've got a contract for a web project right now where, if possible, I'd really like to integrate some fairly sophisticated e-commerce. The two big challenges:

1) The project deals with separate businesses that all have their own bank accounts. The money from transactions processed by the app has to be deposited into the bank accounts that belong to individual businesses. I believe this means that PCI requirements are substantially more onerous for an app like this because my client is classed as a payment service provider, rather than just a user.

2) The app must also be able to process card-present transactions, both credit- and debit-card based. Customers of the businesses (who are the customers of my client) that use the app will often be present to swipe their cards for their payments to be processed.

Are you aware of any services or technologies that would make this easier? So far I think my preference may be for partnership with a vendor who is already PCI-certified and has the pin pads for card-present transactions, whose software has a good API that I can interact with via this web application.

I'll be building this in Rails. I've got lots of experience with traditional e-commerce models, and I'm comfortable with the technical aspects of dealing with multiple bank accounts, but the certification requirements appear to be the major obstacle so far (costing approx $100k, according to my research, for hiring an independent security assessor and working with them to achieve compliance).

Re: Online Subscription Billing Is A Pain. Recurly Wants To... by megamark16 on Tuesday November 17, 2009 @08:18PM (#947586)
That would be a very helpful post! For some of us the whole ecommerce side is unknown and a bit scary.