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.
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 looking for a simple library or script that I can use to make payments to PayPal. I downloaded a couple of libraries and they are all very complicated and have tons of features I dont need. I simply want a way to have a button(pay now) and when they click it, they get redirected to paypal, make the payment, and return to my site so I can save the data into the database. Can anyone recommend a good simple library or a tutorial even?
Also is that even still possible with the new PayPal API? Another words do I need to sign up for an API account to make this happen?
Thank you
These might not be as simple as you're looking for, but they work very well, are well documented in the code, and the developer is very responsive on the comments as well as here on SO.
http://www.binpress.com/app/paypal-adaptive-payments-pro-payflow-codeigniter-library/140
http://www.binpress.com/app/php-paypal-pro-adaptive-payflow-api-class/612
From what i've worked on, paypal is a pain in the wein, but these libraries help lessen the pain.
I have a small web app written in php / mysql that stores customer information and does various things with it.
One of my users has expressed interest in integrating my app with the custom software (also web-based) that they use for setting up customer appointments.
Basically they want a system where, when they create a new customer account using their online software, that information is automatically relayed to my application, to create the customer account on my end as well. This would save them having to enter the same information twice.
I am wondering what your suggestions are for the easiest way to approach something like this? Do I have to create a full-blown RESTful API? (I have never done anything like that before and am not really sure where to start with such a thing.) Or is there a simpler way?
Any ideas or suggestions would be much appreciated. Thanks (in advance) for your help!
In order for another application to communicate with yours, you will have to create some type of API, whether it be RESTful or not.
Personally, I recommend REST as it is fairly trivial to setup and there are LOTS of tutorials on the internet to show you how. If you use Zend Framework, it's 10x easier as they have a REST controller you can extend and quickly build an API with.
Something very simple, which has worked for me is to simply accept the information as a POST. The other application will send the information via POST, which you process in your php, and store it in mysql. if the data is sensitive, you can set up a cert and go over ssl.
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.
I'm new to the community and PHP, so my question may sound stupid to some, but let's get to the point.
I'm learning to use PHP at the moment, and part of it includes implementing an e-payment to an working site. I've read a lot on the net, but I can't figure out some things:
Is there a difference between Payment Gateway <-> Payment Processor, or they are used to describe a same thing?
When using a third party like Authorize, Paypal, Google Checkout, or something like this, do we really need some hard coding, or can you just stick to the information provided on their sites?
I looked through some of the (I think) major payment gateways and I haven't seen any mention of SOAP and WSDL. Are they really needed in a way that I can't find out, or are they are just used rarely and that's why I haven't found any mention of them?
Thanks in advance, and sorry if I sound like a noob. Hope to learn faster with your help, guys.
Generally speaking a Payment processor is a vendero that actually processes payments. Most Payment Processors offer gateways which is the interface you use to submit a payment for processing.
When using a payment processor how much code you have to write is goign to vary with the implementations of the gateway the processor offers and which one of those implementations you choose. Normally there are at least two - some kind of raw API which is the most flexible, and some kind of super simple link to the processor. PayPal Standard and Google Wallet are good examples of the latter, while typical usage of Authorize.net is a good example of the former. IF you use the API generally you need to implement your own order creation process/shopping cart and then you would jsut submit the payment and other details at the end. This allows you to keep everything on you site (not necessarily the data but the experience). The simple route usually involves sending user to the processors site one or more times during the shopping process usually resulting in limited customization and a clear break in user experience.
Some Gateways will use SOAP/WSDL some will use simple REST interfaces, and some will use other implementations. Its generally however they chose to implement in house, but most are going to offer a library to use it for the major scripting languges (PHP,Ruby, Python, C#.Net, VB.net) so odds are you wont have to manually make the calls you'll just utilize the library the provide and deal with the results returned.
well this a tricky business payment gateway differ from one site to another from different 3rd party implementation. u can find the easiest one for you to implement but be careful when u do this. and yes there is a difference between payment gateway and processor which is the processor is what make the payment go to the bank and transfer the money, the gateway make sure the credential that u have enter is correct
happy programing