I'm developing an app that will have to process payments that can potentially even be international. The first payment gateway that comes to mind is PayPal. Is there a simple guide about how to integrate PayPal with Android Studio or Xcode with Firebase as the backend?
Also, how do I integrate Adaptive Payments?
If you think, PayPal doesn't fit the bill, please feel free to suggest other payment gateways and the way in which I should integrate it.
PS: I have seen the SDK for PayPal but I'd like some first hand knowledge from somebody.
You will find at the following URL an example (from Firebase) on how to implement Paypal payment with Cloud Functions (with the advantage that everything is done in the -serverless- backend):
https://github.com/firebase/functions-samples/tree/master/paypal
Related
I'm creating an app that works like a food delivery app. Until now all the functionalities are build and working, but to end the project I need to implement the "e-commerce" side. My issue here is what to do since I have a flutter coded application and Firebase as my Backend.
I have already tried Stripe, but it doesn't have support in my country. Now I'm trying with Square, but since it has no integration with Firebase, I would end up with 2 Servers (1 for the payment and 1 for the other stuff), because I would probably have to create a NodeJS server or something similar.
Please go and check for Paystack. They have also packages for flutter so you can choose according to your level of expertise
Google just released Firebase 2.0.
It seems they are completely separate platforms.
Firebase: https://www.firebase.com/
Firebase 2.0: https://firebase.google.com/
APIs are also different.
Firebase: https://www.firebase.com/docs/web/api/
Firebase 2.0: https://firebase.google.com/docs/reference/js/#firebase
Could someone explain the differences in the core concepts on both mobile and web?
I've been building an app using old Firebase.
Should I change my codes to use Firebase 2.0?
The new version of Firebase is the same platform - it just adds a whole range of new features, so the big change to the core concepts is an expansion of what you can do.
The Realtime Database offers the same functionality as before, but with a refreshed API and a new console. You can keep using the same approach and data model as before, and the API changes are largely cosmetic (renaming to be consistent with the newer features).
Authentication is pretty similar, but it has been expanded to include new features like account linking and customizable emails. You should be able to upgrade your application to the new SDKs and console pretty easily: take a look at our migration guides for Android, iOS and the web.
You can import your project at any time. Your applications and the existing SDKs will continue to work. You can then update your code when you are ready to use some of the new Firebase features in your application.
The new concepts are really around the new features:
Analytics is a new mobile-first analytics product that gives free and unlimited event reporting, and allows building audiences which can be used in many other services.
Storage allows you to store and serve user-generated content, such as photos or videos.
Remote Config allows you to change the behavior and appearance of your app without publishing an app update.
Cloud Messaging is a cross-platform messaging solution that lets you reliably deliver messages and notifications at no cost. Notifications gives you a tool in the Firebase Console to send re-engagement messages easily.
Crash Reporting lets you collect crash data from your Android and iOS apps, to find and fix problems more quickly.
Dynamic Links are smart URLs that dynamically change behavior to provide the best experience across different platforms. They allow you to use deep links that survive app installs on Android and iOS.
Several existing Google products have been integrated into Firebase as well
Invites replaced AppInvites, giving easy way to sending personalized email and SMS invitations. App Indexing gets your app into Google search.
Firebase now also integrates with AdWords to let you target ad campaigns with Analytics audiences, and AdMob to automatically track in-app ad effectiveness.
Its a lot of new features, but you don't have to try them all at once! Once you upgrade, its straightforward to pick and choose.
I'm working on an asp.net web application that has two types of users. Advertiser and Publisher. Both of them have credit(money) in their accounts.
I need to integrate Paypal payments so that an advertiser can add money to his balance. And also for the publisher to be able to withdraw money from his balance (money he made using the website).
I've gone through the Paypal REST and classic API's. Downloaded and browsed the .net code samples provided by Paypal themselves but I'm still having trouble deciding which SDK should I use to satisfy both scenarios with the best experience possible for the user. I'm inclined towards MassPay (in the MerchantSDK) for the withdrawals but I'm not 100% sure of this.
Any help or guidance is appreciated.
Many thanks.
The short answer is that you should use the REST SDKs if at all possible. PayPal's products are moving to that API and once everything is there, support for older SDKs will be discontinued.
I have an ASP.NET Razor / Web Pages site that I need to integrate with PayPal Express Checkout. Edit: this integration requires more than just a simple PayPal-generated button, e.g., I need to dynamically set the price, item description, tax etc.
I am quite new to both Web Pages and PayPal integration so would like to ask what the preferred approach would be.
So far, I have found there are these options:
Use PayPal Helper for WebMatrix
Just read the PayPal spec and create a form with hidden fields etc.
Use some of the NuGet packages from PayPal
Inspire in some custom code like this one
No. 1 is probably some outdated code (both the release date and recent reviews suggest that), no. 2 will certainly work but I'll be on my own, I'm hoping that no. 3 would be the best answer but there are many of those NuGet packages and I haven't found any good examples yet, and 4 is an option if no other works.
Any suggestions? The goal is to have a simple form, below it my custom "Pay Now" button (preferably; could be also a PayPal-provided button) and when user clicks it, the website should redirect him to PayPal, process the payment notification / approval etc.
I realize this question is old, but if you're looking for SDKs provided by PayPal that support Express Checkout, then you have the following two options:
PayPal .NET SDK
This SDK (formerly known as the "RestApiSdk") is built on the newer PayPal REST APIs and provides support for Express Checkout through the Payments API. All API calls use an OAuth token for security and the calls (and associated code) are a bit cleaner than its Classic counterpart. While some aspects of the REST services are still not quite up to par compared to Classic (e.g. Subscriptions), the Payments portion of the REST APIs is mostly at parity with Classic. Moving forward, this is the SDK that PayPal will be investing in and improving, so it's recommended that any new integrations use this SDK.
Recently, the .NET SDK repo on GitHub was updated with a Wiki that should hopefully make it easier to get started using the SDK. Also, a lot of work has also been put into the included samples project to help show how to use SDK with various use cases. And if there's a use case that's missing or needs better/more explanation, definitely don't hesitate to let me know on there. :)
PayPal Classic Merchant SDK
The Merchant SDK has been around for awhile and all the classes are auto-generated from PayPal's publicly-available WSDL schema files. While it provides support for every Express Checkout-related feature, using it is a bit more cumbersome than the REST-based SDK.
PayPal is no longer actively supporting the Merchant SDK and will only be providing bug fixes when necessary. For this reason, PayPal doesn't recommend using this SDK for new integrations.
If you find a feature that you enjoy using in this SDK that isn't available in the REST counterpart, please let me know here or on GitHub. One issue we've noticed for people looking to switch is the REST API does not provide payment history details for payments made via Classic calls. The PayPal SDK team is currently looking into ways this support can be added to the REST-based SDKs to make it easier for developers to make the transition.
The only option you have is to call rest api from asp.net web pages.
You can find the source code of rest api at following places.
https://github.com/paypal/rest-api-sdk-dotnet
http://paypal.github.io/sdk/
Borek,
if you just want PayPal Express Checkout the easiest way to do it is to simply create a PayPal "Buy It Now" button. You don't need to code anything.
You can find out how to do it here https://developer.paypal.com/docs/classic/paypal-payments-standard/ht_create-pps-buttons/ but the basic steps are:
Create the button inside PayPal.
Copy the button code inside PayPal.
Paste it into your website/email whatever.
Hope that helps!
I've been tasked with developing a website that requires a subscription fee to access certain areas of the website, to be paid quarterly. It may also be necessary to pay out to members a small amount but nothing is confirmed yet. The website will be built in ASP.Net. Does anyone know of any subscription systems I can build on top of? Preferably with a busy community.
You could try Spreedly; http://www.spreedly.com/
They have a fantastic subscription based system that's easy to modify and an API for you to introduce that functionality into any application you build. They handle all the payments and credit card bits and just fund a specified PayPal account.