Has anyone implemented PayPal REST API on ColdFusion?
I would like to see some approaches, since there is no SDK or anything that could make the life of a CF developer easier with PayPal REST API.
Essentially, what I need is some starting point to help me implement Authorize, Capture, Refund and Void through ColdFusion.
Related
i m new to paypal integration can any one please help me with how i can find which request method is used for paypal itegration.
when i click on pay button following calles made :
logtimeout(GET)
auth?(GET)
setbuyer(POST)
p1(POST)
p2(POST)
So, i m confuse which method is actually making call to paypal for payment.
Paypal is Discontinuing GET method so i want to chang GET to POST
Thanks in advance ...
If you are using the PayPal Express omnipay gateway (PayPal_Express) then all of the calls in that gateway are POST calls. There are no GET calls in use, they were all converted to POST calls some time ago when PayPal announced that they were deprecating the use of GET calls.
In general I would advise use of the PayPal_REST gateway rather than PayPal_Express, the calls are more up to date and the documentation is better. You can go into your developer site for PayPal and obtain API keys for REST which you can use alongside your Express keys while you change over.
I am experienced with REST API development, but a newb to paypal's apis. A client asked me to add payments to a web game I am working on for him, the transaction will be done on a webpage, and my plan is to have a script put the item in a DB for later use.
Which Paypal API would I want to use for in game credits? there is just so many on their screen.
I'd recommend getting started with the basic client-side integration:
https://developer.paypal.com/docs/integration/direct/express-checkout/integration-jsv4/basic-integration/
I'm trying to create a Paypal Payment using its REST API (https://developer.paypal.com/docs/integration/direct/payments/paypal-payments/), but I couldn't find out how to send the payment to a third-party Paypal business account.
Is it possible using the REST API?
I know this can be done using Paypal SDK for Asp.net, but unfortunately there's no sdk available for asp.net core.
Thanks,
Bruno.
Yep, this is possible to do by setting the payee. Please see https://devblog.paypal.com/setting-payee/
I am looking into implementing Paypal Standard Payment product. The basic reason being "offsite payment" (i.e. we dont want payments being captured at our own site, but on paypal's own payment page via redirection).
However, previously I used to get it done via (now called) Classic API.. I wounder if the new REST API supports this offsite / paypal redirect standard payment method? This is because there is no mention of these classic products names on the REST documents (instead, they are listed in Classic API section only)
Secondly, does Paypal Standard (even via REST) support Direct Card payments? or only Paypal Account payment?
Thanks.
REST does not encompass all Classic API features. It's mainly for mobile development (although not exclusive to that), using OAuth, which is more familiar to mobile developers. Payments Standard is not an API product at all but it can be used in conjunction with API calls to a limited extent. Classic API has the Button Manager that lets you set up custom encrypted buttons that can start a Payments Standard payment.
REST does support direct payments and supports almost everything Classic does in that regard.
My company uses PayPal Payments Standard. Currently our checkout process works via the "cart upload" method and IPN to verify payment via PayPal's website. Should continue to use this method or if we should replace this with the REST API? From what I understand, the REST API is only to be used when the customer stays on our website for checkout, as opposed to going to the PayPal site and returning to our site after checkout. If this is true, I assume the cart upload with IPN method is still the best choice for us, since at this time we prefer to have PayPal handle credit card data. Am I understanding this all correctly?
The REST API is just a different way to integrate the payments programatically. The functionality is very similar and you'll be just fine sticking with what you're doing. No logical reason to spend the time redeveloping it if what you have is working fine for you. They won't be killing it or anything like that (at least not any time in the foreseeable future.)
As i see from a brief view, REST API for Paypal offers webhooks instead of IPN as a way to notify your system about payments and their progress. Each webhook describes which url gets notification request when some type of event takes place.