No subject
We are considering your service for our mobile SaaS offering. How would we best incorporate your service, while keeping upfront development costs to a minimum?
Our pricing model offers 3 plans, 1 free and 2 paid. All users receive a 30-day trial with premium features unlocked. There are also added services that the user can order from within the application, which are pay-per-use.
We do not want to request payment information at sign up. (The user signs up in the app, and account creation is handled by our servers.)
Before the trial period ends, we want to offer the user to upgrade to a premium plan or the option to remain with the limited free version.
How can the end-user cancel or modify their service or update their payment information?
How do you handle failed payments or cards that are about to expire?
How can our server be up to date on account status? (Level of service, changes to level of service, and Payment standing)
We are looking for minimal upfront development costs. How can we implement this with CheddarGetter?
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 Dean on 17 Oct, 2012 08:19 PM
Hi Mendy,
First of all, thank you for exploring CheddarGetter for your business! I will do my best to answer your questions and get you moving in the right direction.
The answer to this question would depend on your development resources. We have a robust API and there are several developer tools that make integration to your site seamless and give you tons of control on your end, however this may not be the most attractive solution for everyone. CheddarGetter also supplies a Hosted Payment Page solution allowing for a simpler checkout option. It's important to note here that the Hosted Pages were built with flexibility in mind and therefore may not provide some of our more advanced features. All things considered, the Hosted Pages will keep development costs to a minimum, but the API will give you more control and more features.
CheddarGetter can handle all of these pricing plans. If you haven't already, you can read up on the pricing plans.
The added pay-per-use services you speak of can be achieved quite easily using Tracked Items. Or you can use custom charged or parallel one-time invoices to charge for pay-per-use items.
As for the free trials, you can achieve this by setting up a 'free' pricing plan and when your customers are ready to convert, simply move them to a paid plan. Or, you can use standard plans with a delayed initial first bill date. In the latter case, customers are required to provide a payment method to continue using the service after the first bill date. You could use that method in tandem with a "free" plan for an ongoing free level of service should they choose not to pay for the premium service after the trial period.
Again, you can use the API or Hosted Pages for this. The hosted pages can create, update, and cancel customers. Using the API for canceling customers is very simple.
E-mail notifications are available and are highly customizable with built in templates making it simple to tailor to customers.
Declined payments are retried automatically a few times. After too many declines, the subscription is auto-canceled. Subscriptions with an expired payment method are similarly canceled upon the first bill that cannot be transacted due to the expired payment method. In all cases, the email notifications can be used to automate the communication with the customer.
The API provides for this. You can pull the latest information from CG upon your customer's login and determine if the account is active. There's also webhooks to receive notification of account changes.
The Hosted Pages would seem attractive to keep initial development cost down. However, you will find that some additional development is required especially with tracked items, one-time transactions, etc. Also, you'll definitely want to use the API to determine level of service, etc.
We're here to help so just ask when you have questions.
Dean closed this discussion on 23 Jan, 2013 04:44 PM.