We are using Authorize.net's recurring billing service, and we are very happy with it. Mostly because we don't need to worry about the security issues you mentioned (encrypting, secondary processing server, etc...). Authorize.net stores the c/c info and takes care of it.
Paypal also does that, but we chose Authorize.net mainly because Paypal is not completely behind-the-scenes in the process (I don't remember exactly, but I think PayPal forces you to redirect the user to a PayPal page). Also, Authorize.net is cheaper in the long-run.
The downside of Authorize.net is the account set-up, which is a bit cumbersome. A provider will contact you and you need to describe them how you are going to use the account, etc... Also, I think you need to open a merchant account. It's not painful per se, but you should expect at least a week to get the whole thing up-and-running.
On the upside, Authorize.net gives you access to their test environment in the meantime, so you can do the integration while you wait for your account...
PayPal with Web Site Payments Pro can be completely behind the scenes. You create a recurring payments profile, that has a profile id, you use that to reference it in the future (to cancel it for example).
PayPal also does not require that you setup a merchant account. All you need is a bank account. It's $30/mo for Web Site Payments Pro. If you provide them with a URL that shows what you're selling that's all they need. Otherwise you have to fax them a brochure or similar, to show that you're doing something legitimate.
That's good to hear that the recurring billing is as pleasant experience. I pretty much assumed as much, given how smooth Auth.net is for single transactions.
Honestly, I'm quite pleased with using Auth.net and would indeed recommend it, moreso in hearing that their recurring billing is a simple process.
Paypal also does that, but we chose Authorize.net mainly because Paypal is not completely behind-the-scenes in the process (I don't remember exactly, but I think PayPal forces you to redirect the user to a PayPal page). Also, Authorize.net is cheaper in the long-run.
The downside of Authorize.net is the account set-up, which is a bit cumbersome. A provider will contact you and you need to describe them how you are going to use the account, etc... Also, I think you need to open a merchant account. It's not painful per se, but you should expect at least a week to get the whole thing up-and-running.
On the upside, Authorize.net gives you access to their test environment in the meantime, so you can do the integration while you wait for your account...