The Gloebit production environment is for fully tested applications which are launching to the public. If you are testing out Gloebit or doing your initial integration, please see the integration guide and the sandbox walk-through which will instruct you on how to get set up in our sandbox environment for testing.
The production environment allows your application to tie into production accounts of Gloebit users. Once authorized, your production application will be able to utilize our services with those production user accounts. Your production application will be able to transact in Gloebits which can then be sold and your proceeds withdrawn.
The production environment resides at the domain https://www.gloebit.com/.
This production walk-through and guide takes you through the steps to get your application migrated from the Gloebit sandbox to production. Let's get started.
On the production server, you will need the following to be a Gloebit merchant:
You can either create your account using an email and password you provide specifically for the Gloebit production environment, or you can authenticate via one of our third-party ID providers (Google+, LinkedIn, Twitter, Facebook) to create your production account. Your production and sandbox accounts do not need to authenticate the same way.
The account you create here allows you to buy and spend Gloebits. The next steps upgrade your account to use the Gloebit merchant services.
After creating your account or authenticating via a third party, Gloebit will present its user terms of service. You will see this only when creating your production account or when you log in after we have updated the user terms of service.
After clicking, you will see the Account Settings page for your sandbox account. Now let's turn it into a production merchant account.
You will see a form here asking for a variety of information for your merchant account. On the production server, this information is required. Please fill in the form and click on the "Save" button.
While you will immediately receive access to our merchant tools, we must review and verify the information you have submitted before your application can utilize any gloebit transaction services or you can sell gloebits or withdraw proceeds. Please create your production account and submit your merchant upgrade request in advance of launching your product so there are no delays while we review your submission. In some cases, we may need to ask for additional information.
After clicking on "Save" to submit your merchant request, you will return to your Account Settings page. Notice that the alert icon (bell, top-right of page) has a red 1, indicating a new message.
The new message should be an alert that your merchant signup request has been submitted. Merchant approval on production requires a review of the information you've submitted before you gain full access to all merchant features.
Now that you have a merchant account, there is a new item in the menu:
The Merchant Tools page is where you will manage all of your merchant functionality and application details. Most important for integration, it is where you create OAuth keys and secrets for your applications.
Because this is the first time you are accessing a merchant page, Gloebit will present its merchant terms of service. You will see this only when first accessing one of the merchant pages or when you first access one after we have updated the merchant terms of service.
After clicking, you will see your Merchant Tools page.
Gloebit uses OAuth for authenticating you and your users. Your application will need the OAuth Key and OAuth Secret from this page when you send your users to Gloebit to grant access to your application.
And with that, you are ready to migrate your application from sandbox to production.
If you have not yet integrated your application with Gloebit, please see the integration guide and the sandbox walk-through which will instruct you on how to set up sandbox merchant account and integrate.
See the Gloebit Service Interfaces page for information about connecting to Gloebit over HTTP.