I was reviewing your product, and while it does look very impressive, I don't understand why I would choose to use it as opposed to simply using Auth.net's native Automated Recurring Billing (API). Given the extra cost involved, I'm not seeing the value-add. Am I missing something?
Why use CG over Auth.net's ARB
Discussions are closed to public comments.
If you need help with Cheddar please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
#1 Posted by Marc Guyer Support staff on 09 Sep, 2009 06:16 PM
Frank -- Good question. The Auth.net ARB allows for a simple subscription model where you charge a customer a fixed amount on a recurring schedule. CG does this as well as manages your subscription definitions (pricing plans), tracks real-time item usage and allows pricing changes and grandfathering.
CG also sends fully customizable email notifications to customers on your behalf (from your defined from address) concerning new subscriptions, subscription changes, payment invoice receipts and declines, cancellations and expiring credit cards.
CG also includes an open API which can be utilized for retrieving historical customer subscription data enabling you to make informed decisions on price changes and features of your application based on item tracking and plan usage.
When it comes down to it, CG significantly reduces the development requirements to start billing your customers and creates a flexible environment for making pricing decisions.
Does that answer your question? I'd be happy to elaborate if you have any other specific questions.
#2 Posted by Frank Koehl on 09 Sep, 2009 06:57 PM
Alright, with that description in mind, reading through your materials makes more sense.
I'm thinking it's at least worth a shot, but I am currently in open beta, and bootstrapping to the max. I see that you have a free account. but it does not provide "full API access." What won't I be able to use with the free account?
With a customer cap at 20 (which I see as reasonable), why even have further restrictions?
#3 Posted by Marc Guyer Support staff on 09 Sep, 2009 07:12 PM
We're considering making the API available on the free plan. In the meantime, since we're still in private beta, beta users get a free plan that includes 100 customers and API access. Request a private beta account at https://cheddargetter.com/user/signup-beta.
Marc Guyer closed this discussion on 09 Sep, 2009 07:12 PM.
Frank Koehl re-opened this discussion on 09 Sep, 2009 07:15 PM
#4 Posted by Frank Koehl on 09 Sep, 2009 07:15 PM
I actually just did that before seeing your reply. :)
What's the wait time like on your beta invites? I'm ready to start coding my billing proc now, so the sooner the better.
#5 Posted by Frank Koehl on 09 Sep, 2009 07:25 PM
If it's a question of tester stability, the current status of my site and services should provide a clear enough picture.
http://fwdvault.com
#6 Posted by Marc Guyer Support staff on 09 Sep, 2009 07:31 PM
The next invite wont go out until next week. However, I've created a
single-serving beta code for you to use: FWDVAULT. When you signup
just enter that code. You might want to do it quick in case someone
gets in there ahead of you with your code.
#7 Posted by Frank Koehl on 09 Sep, 2009 07:38 PM
Thanks, Marc! Registered and on my way!
Marc Guyer closed this discussion on 11 Apr, 2010 10:25 PM.