We need to integrate our custom in house applications with quickbooks. When I saw the QB REST API and the IPP I was like "Yay!!! Finally Qb offered us something useful!".
It was a happy moment.....
Then I read this in the FAQ
I want to integrate my custom (non-SaaS, single-tenant) solution with QuickBooks API. Can I do this?
Not today, but we are considering it.
What? Why?
were paying customers, we have integration problems....largely caused by YOU intuit!
You already built it...I assume it works...so there's no effort whatsoever on your part!
So now you offer an API on a silver platter....but...oh wait....you can't use it.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Somebody tell me that I'm simply misunderstanding this....
Your understanding is correct. IPP Intuit Anywhere is the new platform only for SaaS applications.
Intuit still provides the traditional QBSDK SDK v12, which is useful if you are creating a custom integration for one company, or focused entirely on desktop scenarios only.
QBSDK Ref - https://developer.intuit.com/docs/0025_quickbooksapi/0055_devkits/0250_qb
I'm not sure if this is a good option for you but we have created a pretty slick sync with QuickBooks using the SDK for the Method Integration platform. You can use our API with the sync engine to do what you need. You'll need a Method account though which is $40.00 per month.
I have done a lot of integration with QB, and prefer to use the RSSBus ADO.NET provider. It is infinitely easier than using Intuit's SDK, and has great documentation, such as - http://cdn.rssbus.com/help/RQ4/ado/pg_desktoptable-purchaseorders.htm. It works with the Desktop version and QB online.
I am not affiliated with them at all, just a happy customer!
Related
I'm going to be building a custom interface for a QuickBooks Enterprise install (with Ruby on Rails). For example, we need to a have custom Estimate ("Quote") generator and later perform other functions as well. Before committing too heavily to the QBWC (QuickBooks Web Connector), I am hoping to understand any limitations that might exist.
Is there anything that the QBWC cannot do that can only be accomplished through the QuickBooks Enterprise interface itself?
I assume that there may be some "administrative" tasks that might not be able to be done, but Intuit's developer support can't seem to succinctly answer this question and has left me with a "Just try it and find out!" approach. This, of course, isn't really acceptable in my situation since I must understand any constraints / limitations going into this planning and proposal before really digging...
One other peculiar note in the docs (old, 2009, QBWC documentation) is: "... for a developer to write their own go-between application, in effect, replacing QBWC with their own implementation." Is this viable and does anyone have any experience with this who could provide some context of what this means?
Is there anything that the QBWC cannot do that can only be accomplished through the QuickBooks Enterprise interface itself?
Yes, there are many things. A short list of examples:
QBWC cannot add users
QBWC cannot change passwords
QBWC cannot switch between single-user and multi-user modes
QBWC cannot change settings (e.g. it cannot change the QuickBooks company from accrual to cash basis, or enable/disable tax)
QBWC cannot tell QuickBooks to update to the newest version
QBWC cannot communicate with QuickBooks when you have two separate QuickBooks companies open at once
(I'm sure there are many more)
It's also important to understand that the Web Connector is built on the same tech that all integrations with QuickBooks are built on.
Which means if the Web Connector can't do what you need, then you're SOL - no other different method of integration will be able to do what you need either.
You'd be much, much better off spec'ing out what you actually need to do, and then making sure that functionality is there, vs. trying to weed out what you can't do.
I am looking to integrate any actively maintained and working payment plugin with my grails application.
Can anyone who has been through this before give some guidance.
My application need is simple: I need various subscription levels(monthly/annual) and I need to be able to retrieve the payment details.
Any help is appreciated
Bala
Bobby Warner just released the Grails Stripe plugin recently. I haven't used it personally, but I've heard very good things about Stripe's usability, and I know that Bobby is an active, helpful developer who would likely be very responsive to feature requests, feedback, and pull requests.
We have a website, and want to allow users on the site to chat with the providers (if they are online). To make it as simple as possible, we'd either ask the providers for their Google Voice/AIM username or just ask them to have our website open.
Any ideas on best ways to implement this (we are using HTML5/CSS3/RoR3 and don't support old browsers) or even better, perhaps a solution out there that does this. To my knowledge, olark, livechat, etc don't provide this...
FYI: I prefer an open source solution vs. building it myself.
There was a recent railscast regarding messaging where Ryan built a chat program with push support (not polling). Seems a decent place to start if your requirements are easy going:
http://railscasts.com/episodes/260-messaging-with-faye
Building advertising infrastructure for each website is somewhat bad, especially when the website is new and not much traffic. People will curious to advertise to website with low traffic.
I need ad server (like AdSense) which:
user can register, can create an ad
(advertiser), and can embed customizable ad codes in
their website
have text and image ads
all payment through paypal
I've found some example using Pylons but it rather outdated. It will be great if someone can guide me what to do and what I need to build it. Any recommendation are welcome.
if you are looking for good documented pylons framework you should look at PylonsProject aka Pyramid. Here you will find EVERYTHING up-2-date documentation. So i think this is a good start.
But if you are looking for a website that you install, login and start working this is not what you want. with pylons/pyramid you will have to write your own code.
Also if you are more explicit where you need guidance i will be more helpful.
I've been programming for years, and I've also done a few professional programming projects. I recently had a friend ask about creating an e-commerce site, but I had to turn her down because I had never worked on a web application that can bill. I also might need to write a subscription-based web service in the future. My question is, how do I even get started with billing? I've never found a guide about this, and I barely know how bank accounts work since I don't manage my own one (I have an excuse for this since I'm only 16).
I don't know if the answer is language dependent, but if it is the languages I'm interested in are Python, C/C++, and Java.
There are lots of ways to go about setting up e-commerce sites;
If you don't have any experience whatsoever, and don't want to get into anything "complicated", i would suggest going with a customizable web "storefront" hosted by someone else, pre-integrated with credit card processing, etc. There are tons of options for these online. Just search google for "web storefront". Yahoo! even has such a service:
http://smallbusiness.yahoo.com/ecommerce/sellonline.php
Going beyond that, It's pretty easy to integrate with someone like PayPal. They have all sorts of options from the most basic (use a link to send someone to their site with query string parameters to let paypal know what the user wanted to buy):
https://cms.paypal.com/us/cgi-bin/?&cmd=_render-content&content_ID=developer/home
Beyond that level, you will need to signup for a merchant account, or other similar sort of service, like the one offered by authorize.net (who I like):
http://www.authorize.net/
There are components you can buy for most major web development platforms like .NET, JSP, etc. Perfect example is dotnetcart. These components provide out-of-the-box, easy-to-setup integrations with major CC processing companies, as well as out-of-the-box shopping cart implementations:
http://www.dotnetcart.com/
Finally, most merchant services / payment gateways provide web services for direct integration.
PS.) Never ever ever store CC numbers ; )
I would look at paypal's api to get started. You might not want to stick with them but it is a good starting place to learn about dealing with credit card clearing houses and such.
Here ya go.
You'll typically interface with a 3rd-party for doing banking transactions. One that I've work with in the past is Authorize.Net but there's plenty out there (PayPal is another fairly popular one with a decent API).
Basically, the best approach is to do as little as possible and let the 3rd party handle all the "hard" stuff (such as security, managing credit card details and so on).