I have an app that is planning to integrate with Gemini to provide my client the investment capabilities with crypto currency.
I just registered a personal account in the Gemini sandbox environment and generated a master key api to work with Gemini API. https://docs.gemini.com/rest-api/#using-master-api-keys
I hope that all clients in my app can link to individual Gemini Account to buy, sell, and transfer crypto currency as they can. In order to do that, we are planning to use Gemini Sub-Accounts Features to create multiple Gemini accounts off of primary account and link them with our app's users. After that, our app's user can add a new bank, deposit funds to their Gemini account and make a crypto order.
I am not sure that sub-account features can adapt to my purpose. I am not sure that Gemini sub-account features are suitable for my purpose. I assume that your app's users could be up to approximately 1 million or higher.
Do I just need to register one Gemini Personal Account?
Can we create 1 million Gemini sub-accounts or higher off of the primary account and link them to each user in our application?
Add a new personal bank corresponding to each Gemini sub-accounts?
Related
I plan to develop an app for Amazon Selling Partner API (SP-API). The general idea of the app is that it will be the app, that different sellers can use to help them manage their stock on Amazon. I myself am not a seller on Amazon, and I don't work for a particular seller. The app, once ready, should be available to multiple sellers who are interested in using it.
Unfortunately, from what I found in SP-API documentation here and here it seems it's impossible to register as a developer, without being a seller yourself or having an existing seller that can register you as a developer. Is this correct? If yes, is there any way to overcome this issue? It seems a bit ridiculous that Amazon doesn't provide an easy way for third party developers to develop and test their apps on Amazon.
They would require a Seller Central account to be set up for public applications to allow you to register as a developer. The main account would be used to access the developer registration form and can be used to set up developer access. This would also allow support cases to be raised. Be aware that they will charge a monthly fee. Recent updates to documentation appears to suggest this will only affect Public application developers.
I am trying to get Amazon Seller Access keys from User Permissions page and it says
"Developer Central
Are you a software developer building applications using MWS?
If you need MWS API Access Keys because you are coding software applications for your own selling account or to be utilized by other sellers, you can provide information about your business and apply for access here. We will thoroughly review your submitted information. This process may take up to 30 days. ".
in Past i used to see MWS access keys (access key and secret key) for a Seller but this is my 3rd time i am not able to see keys so my question is: Amazon changed their policy or some one can help me how we can get MWS access API Keys for a Amazon FBA Seller Account ?
Basically, every seller with a pro account have MWS but if you wish to develop third-party system and access Amazon API, you will need to ask for Developer MWS Credentials.
After answering some questions about your need to use this MWS for development purpose, they with review and let you know (it takes about 30 days to get answer)
I have a pre-existing billing account for an earlier project, that works fine.
How can I associate a new project with that same account?
In the Google Developer Console, if I select the new project and try to enable billing it gives me the forms to create a new billing account. I did not find a way to associate the project's billing to the existing account.
If I look at the existing billing account I can see my earlier project in the list of projects but have found no way add a new project to the account.
If I have enabled billing for one of my applications already, why do I have to do it again for my other apps?
We want to provide developers with fine-grained control over each of
their applications. They may wish to have a separate budget for
different apps, or apps that run entirely on free quota, rather than a
single budget for each.
DOCUMENTATION
Try hitting cancel at the end when it asks you to choose a name for the news billing account. After I did that I was able to associate my second project with my primary billing account. I also noticed some weirdness with a billing account that was in trial mode. Once I "upgraded" this billing account I think I could associate other projects with it.
Of course make sure you are an admin for the billing account and all projects you wish to associate with that billing.
We want to develop a plugin for NewRelic, but we'd like to do it separately from the company we work for (which is who owns the NewRelic commercial account)
Is it possible to develop it without an account (and thus, independently from a company) or is it 100% required to have the plugin belong to a company with a NewRelic account?
Any New Relic account can consume, author, and publish plugins.
If you don't have an account, or want to publish from an account that is different from your primary or work account, simply signup for a new account - and if you do so via any of the plugin detail pages here http://www.newrelic.com/platform you'll get New Relic Standard for free, forever! (otherwise Standard is a paid tier, and Lite is free forever)
I have an App Engine web application (based on python) in which one I would like to offer a "Free" Version and a "Premium" one. I would like to charge a monthly fee to the users that want to use the Premium version of the app, blocking access to premium features to the free users, just as Grooveshark does.
Which is the best way to do this when you're using Google App Engine for developing? I mean, I know that Paypal let you to charge a monthly fee to users but, How can I restrict access between the two interfaces? I'm really lost in this field, Never made a "Paid Model App" before.
Authorization determines what your users are allowed to do in your application based on their roles/permissions.
Basically you would need the following things:
A flag membership status that indicates if a user is Premium or not; this should be set after the payment
A #is_premium decorator to check if, reading the membership flag value
, a given Web Handler can be called by the current user
Have a look to Web2py authorization, Django Auth or Tipfy acl extension for some pretty neat solutions.