I am not sure whether this is an appropriate question to ask in this board, but anyone with experience of integrating KashFlow or Xero with a zend-php application could help me. We are on the dilemma of selecting our invoicing system for our SaaS. I was going through all the reviews and trying out myself all the options in both the systems. It seems like Xero has a clean interface and gives you what you need at the right time. Apart from the user interface I am really concerned about the Integration side of things.
Xero gives oAuth integrating and KashFlow gives Web services. Our plan is to automate the invoicing process(rolling monthly invoicing) and payment processing with the Accounting software. Our existing system is build in php and zend framework. Could anyone please suggest me with some quick strong points which is really convincing to help us choose one of them.
Sorry for not tagging kashflow and xero as i do not have enough reputation.
Cheers...
I dont have a sheet that compares Xero & Kashflow (I havent worked with Kashflow) but this PDF provides a comparison between Xero & Sassu http://help.xero.com/help/resources/XerovsSaasuSumm.pdf << Online software is updated so frequently that both products have moved on since this link was first posted and now no longer exists. To think about how Xero compares to another product you're using or considering, ask yourself these questions: http://www.xero.com/compare/ (OG from Xero)
Sorry to further confuse things but have you looked at Saasu also? Possibly more powerful in terms of what you can store with their tags and activity system plus they do automated sales within the application itself.
Have you seen the PHP wrapper for the KashFlow API? http://accountingapi.com/examplecode.asp
The KashFlow API is very comprehensive, but if there are any missing functions that you need then email support#kashflow.com and we'll see if we can add them - we usually can, and pretty quickly too.
KashFlow have recently announced that they are going to revamp their api and add oAuth and REST support.
Related
I need to import all PayPal transactions (within a given time-period) into my own software. I know that I can download an account statement from the website but I need my software to do this automatically.
Since this is the first time I'm trying to integrate a PayPal API into my own software, I'm quite confused with all the information thrown at me.
As far as I understand, there are three PayPal APIs (NVP, SOAP and REST) - they all offer a lot of methods, but as of now, I'm not able to estimate which API and which method would be best for my rather simple task.
Are there any best practices for this I didn't manage to find on my own? Does someone have a hint for me?
I would recommend using the Classic API, specifically TransactionSearch and GetTransactionDetails.
This PayPal PHP SDK will make those API calls very quick and easy for you.
I am working in a application that helps companies manage their finances.
They can create invoice for clients, send with email to clients and now we wanted to implement the Paypal to let clients pay them through our platform.
While looking at the Paypay API's I can not figure out which is the best to be used in this case.
I am referring to the two options:
REST API
Classic API
Can anyone please recommend me which on of the options is the best one to be used in our case to enable our clients to receive payments in our platform?
Thanks in advance
I would recommend the Classic API. It's much more mature than the REST API, so it has more features that REST just doesn't have yet. They keep developing on it, too, so it's tough to say when REST might (if ever) catch up with it.
With a decent SDK the classic API is no more difficult than REST to implement. If you happen to be using PHP I'd recommend taking a look at my class library for PayPal. It will make all of the Classic API calls very simple for you.
I was starting to work with the LULU api and was trying to automate the whole process through our website, dont know why but they have discontinued their service by the end of APRIL this year. Here is a message on thir portal.
http://connect.lulu.com/t5/Frequently-Asked-Questions/Lulu-Developer-Portal-Update/td-p/289614
I tried to work without the API through PHP's curl but they have a very complex form wizard and dont know why its not working. I am now hoping if there is some kind of system which can automate the form submission just like a human.
Any help is appreciated.
The old publishing API needed support resources that we couldn't offer at the time unfortunately. The new version is out and has its own support team.
https://api.lulu.com/docs/
It would depend on what you are trying to accomplish. There are other players in the book world that have automated APIs. Here are some of them:
http://www.createspace.com/
http://www.ondemandbooks.com/
http://www1.lightningsource.com/
The closest matching to what Lulu's APIs used to do is probably Peecho:
http://www.peecho.com/
I'm currently developing a web application for one of my clients. This client requested a small billing module. The client istelf is small SIP provider. There are several pricing items, plans, etc. All they different types of payment like onetime, monthly, annual. Are there any best practices, good books, articles on blling systems architecure?
Btw the web app based on symfony framework.
Any help is appreciated!
There is usually nothing "small" about a billing system.
I just ran across something called citrusdb. You might want to go through it to decide if you want to build something or just integrate theirs.
Barring that, depending on their business they might be better served just using QuickBooks in combination with an online ordering / payment system.
Some Google Books? Some are available with extended previews, that can be helpful.
http://books.google.com/books?id=lOImNtO96L0C
Flow Charts?
http://www.google.com/images?q=billing+process+flow+chart
You can also get some useful info from audit programs, that describe the kind of things you (or your system, probably) will be asked to produce. Ctrl-F Billing:
http://www.dcaa.mil/standardguidance.htm
These are very general, and not very specific to any programming language. Hope it helps :)
I'm about set up my first eCommerce site. I was hoping you could recommend some shopping cart software. What are the perks of using pre-built software rather than developing some simple solution catered to my needs. Also, are there pre-written Terms and conditions for sites? Or templates that outline what aspects need to be addressed? What other things should I look out for when building this website?
Also, I develop in PHP server side, so software in that language would be best.
I use osCommerce a lot, but this software is a bit outdated. Magento is a good alternative for setting up a commerce website.
Google Checkout is probably a good starting point for a clean base to start from: http://checkout.google.com/sell/.
The hands down easiest all in one ecommerce platform IMO is the Yahoo Small Business platform - you have a number of options there, including using hosting and php. It's not free, but you get EVERYTHING you need to run an eCommerce store all in one painless spot - your cart, ssl, content management, integration for merchant gateway, shipping rules, integration with ups realtime rates... Order processing, the whole nine.
There are two ways to develop on this platform - using their proprietary RTML language, or use the hosting that you get with it and access the items in your catalog through what they call store tags.
So I wound up writing my own shopping cart software because the site is not based in the U.S. and services like PayPal and Google Checkout do not cover it. I coupled my cart with an API from a national bank to charge credit cards. This required SSL which was easy enough to set up.
I found a Terms and Conditions generator online and used that to lay out the basics of the document. Then I added site specifics myself and tried to sound as much like a lawyer as possible.
I second Yahoo! Small Business (although I would get a developer, their default template looks horrible). If you are looking for something that looks nice and is out of the box good to go, Bigcommerce would be my second choice. After that, I would go with 3dcart (it's a little more flexible, but the default themes are not as good as what Bigcommerce offers). Although, if you are a hardcore programmer, going with Drupal Commerce would probably be your best bet, but you will really need to know some programming to customize it. On the plus side, it is the only cart that I have mentioned that is free (minus hosting costs of course).