News for hackers. Stuff that matters.
Re:What Web Frameworks Are Missing - Credit Card Payment Out... by zhyder on Wednesday March 11, 2009 @02:35PM (#512199)
Somewhat off-topic, but we're using Authorize.net's Automated Recurring Billing (thru ActiveMerchant). The API is so simple, it's incomplete. There's no way to reattempt a declined transaction.

Here's what happens: (i) user signs up for paid account with 1-month free trial, but has a typo in the zip code (Authorize.net doesn't check this when the subscription is created); (ii) after the 1 month, the first charge is attempted and declined; (iii) we email user and user updates billing info, so future monthly charges should work but this current transaction is lost forever.

Authorize.net says we should manually charge the user but we (intentionally) don't save the credit card info. Any ideas? Or should we just switch to someone like TrustCommerce?

Re:What Web Frameworks Are Missing - Credit Card Payment Out... by aston on Wednesday March 11, 2009 @03:41PM (#512381)
We're on Authorize, too, and we didn't mess around with ARB at all because we anticipated that we'd need more flexibility around retries. The best I can recommend short of changing providers is to let Authorize hold on to the credit card info with CIM, and then run your manual charges through that system.