Flutter stripe SDK custom form - flutter

I need to add stripe to a flutter app where I can save a credit card with a custom form, but since I only found an unofficial sdk that provides a pre-built form (stripe_payments), is there a way to work with API requests without relying on an SDK?

All SDKs are essentially just wrappers for Stripe's API. You can make those calls yourself using something like curl or fetch: https://stripe.com/docs/api?lang=curl
Bear in mind that some of those calls require a secret key and some can be done with a publishable key. You should never use a secret key on your client, only on your server.

Related

How would I go about creating a product in the Stripe extension in Firebase using flutter?

I am building an event management app and am currently in the stage of adding payment funcionality to it. I have followed the firebase documentation and all seems to be in working order and I can easily add products to my firestore database when using the Stripe dashboard. I am just wondering how this could be done either client side (flutter) or using cloud functions?
I have tried watching tutorials, looking at the limited github examples and reading the documentation however all the products seem to be made through the stripe dashboard - obviously not ideal to have to manually create every one!
Creating Products via the Stripe API requires an Account's secret API key. You should never expose this since it provides full access to your account. So creating Products from the client-side is not something we will consider.
Additionally the Stripe Firebase Extension does not include any cloud functions for creating Products. The docs even have you create a restricted key to keep your account safe. All of that suggests to me that you will want to either
Create products from the Stripe Dashboard as previously indicated in tutorials and documentation.
Run local scripts to create products via the API using one of Stripe's client libraries which you can install locally.

Is it OK to store Google Map api key on Firestore ? (Calling from Flutter app)

TL;DL
Is it OK to store api key for Google map api on Firebase Firestore with security rules ?
Question
I'm working on map features using google_maps_flutter plugin. This package describes to store the key on source code on its document, but this seems to be insecure.
Many developers describing that the most secure way to manage api key is to store on server side and I agree with this idea.
I found the issue but it seems that the plugin does not have a way to provide the api key dynamically.
In the iOS sdk, they have GMSServices.provideAPIKey(Could not find same kind of methods on Android) and this allows to provide api key dynamically.
If the plugin support these features in future, is it OK to store the key on firestore with security rules?
Thank you
If your third-Party API Key are sensitive, they should stay on the server and never reach the User's device.
So, you could store them on Firestore with strong security rules (i.e. only readable with admin privileges) and then place the third-party API calls within Firebase Cloud Functions.

WooCommerce Integration in swift

how can I integrate WooCommerce in my swift code...I want to integrate Rest full API is my Application. I don't have any idea how to do this.
I got consumer key and secret key and don't know further how to do this.

Stripe implementation in flutter

I need to implement Stripe payment gateway in one of my application, is there any plugin or something I can use to add card and charge customers for some service. If anyone having any references please suggest.
I have gone through some tutorials and plugin but none of them are as per my requirement some plugin allows only to add a card but I am unable to find the plugin that can manage payments with the Stripe.
After successfully adding card, you will get a response with a token.
Pass that token to your backend server, you could call charge.create(it depends on your backend language, check stripe documentations) function to make the actual charge and other stuff.
You can use stripe_payment plugin
Here is an article showing you how to do implement payment in flutter using firebase and stripe
https://medium.com/#info_4766/build-a-marketplace-in-your-flutter-app-and-accept-payments-using-stripe-and-firebase-59f074201718
This is best done in Firebase using cloud functions, rather than from the app. Find links below for more info on how to do this:
https://github.com/firebase/functions-samples/tree/master/stripe
https://www.youtube.com/watch?v=JeyxolsJ3aE
https://www.youtube.com/watch?v=BrLTF4QdRrM
For these reasons:
There's the security aspect and one of these links explains it's not a great idea to have your stripe secret inside your client.
I want to be able to make this available from flutterweb, as well as other devices. Flutterweb is currently not yet supported by any plugin. The plugin that's best evolved and most used is https://pub.dev/packages/stripe_payment. Flutter-web has not been released yet (more, see https://github.com/jonasbark/flutter_stripe_payment/pull/147)

How to use PayPal API credentials?

I need to add PayPal button on client's website. It is first time I am doing this and I asked for credentials he gave me API signature, API username and API password. I was checking lots of tutorials how to add PayPal button, they use sandbox/live Client ID and Secret. Can I use this API credentials instead?
I searched a lot but couldn't find an answer.
I am coding in CodeIgniter 3.
Thanks
Username, Password, and Signature are related to Classic API integration.
Client ID and Secret are related to the REST API integration.
Which one do you want to work with?
Or, the easiest option is to use PayPal Standard Payment Buttons, but that will also be the most limiting.
We actually have a PayPal CodeIgniter Library that you might be interested in. It was built for the Classic API.
The general PayPal PHP SDK that it's based on is now available with Composer, so I would recommend installing it that way.
We'll be releasing an update to that library before the end of the year that adds all of the REST APIs. It's available in the dev branch on GitHub already.