Welcome to the Gloebit Sandbox Walk-Through. This page's purpose is to guide you through the all of the steps for getting your application up and running in our sandbox environment. It starts out with some background information and an overview. If you want to skip that and get right to work, click the button below. Otherwise, enjoy the introductory information. The walk-through starts immediately afterward.Skip introduction, go to the walk-through
Gloebit provides a sandbox server that lets you quickly start integrating Gloebit services. It provides access to all Gloebit merchant functionality so you can fully test your design before switching over to the production Gloebit server. Also, it immediately grants full merchant accounts privileges when you sign up. On the production server, some merchant privileges are granted immediatley and some are granted after Gloebit reviews. Thus, the sandbox server gets you into full testing as soon as you are ready.
On the sandbox server (as well as on the production server), you will need the following to be a Gloebit merchant:
Your merchant account allows you to receive Gloebits for you products and services. Integrating the Gloebit API makes it easier for your application to work with the Gloebit server on authenticating your users, having them grant access to your application, and accessing the Gloebit merchant services.
For testing purposes, you will need a Gloebit account separate from your merchant account, especially if you want to test your purchasing. Gloebit transactions move gloebits from one account to another.
Your company needs an account on the sandbox server. This account will have the same privileges as any user's account (to start). You can purhcase gloebits for the account and spend them. Later, when you sign up this account for merchant privileges, you will register your application(s) in it. But that comes later.
All Gloebit accounts are associated with email addresses. We offer the options of providing an email address and password or using one of four social identity providers (Google+, LinkedIn, Twitter, and Facebook). For your primary account on our sandbox server, you will probably want to use a sandbox-specific email address from your company's domain.
After creating your account or authenticating via one of the social identity providers, Gloebit will present its user terms of service. You will see this only when creating your sandbox account or when you log into the sandbox after we have updated the user terms of service.
After accepting the terms, Gloebit will take you to the Dashboard page for your account. Let's take a look at the header bar on the top-right of this page.
You will see that header bar on all Gloebit pages when you are logged in. It gives you access to your account's pages, lists Gloebit messages to your account, and shows your Gloebit balance. Clicking on it anywhere left of the bell icon activates a drop-down menu for you account pages. Clicking on the bell icon opens a drop-down list of Gloebit messages for your account. The number in the red circle indicates how many there are. Clicking on messages in the list will mark (or unmark) them for deletion. Lastly, the Buy button on the right end of the header is what your customers will use to buy gloebits.
You don't need to buy any gloebits because this account is intended to be one that will receive them. So let's turn it into an account that can receive gloebits, that is, a merchant account.
You will see a form here asking for a variety of information Gloebit needs for your merchant account. On the sandbox server, none of it is required. Go ahead and scroll down to the bottom of the form and click on the "SAVE" button.
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 approval for your merchant signup request. Merchant approval is automatic on the sandbox server and gives you full access to all merchant features. (The production server's merchant signup occurs in stages for the various features.)
If you click on the message, the check mark icon will change to an X, meaning the alert will be deleted. If you click on the message again, the X will change back to a check mark and the alert will not be deleted. And if you click again... it's a toggle.
The red number on the alert icon indicates how many alert messages you have queued up. The number changes only when you visit another page or reload the current page. It decreases only if you click on messages to have them deleted.
Now that you have a merchant account, there is a new page in the menu:
The Merchant Tools page is where you can add applications to your account, place sell orders for your gloebits, and request withrdrawals.
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. At the top left is your list of Applications connected to your account. It is empty. Let's add an application that you can use in integration and testing.
You have a merchant account in the sandbox. Now you need to add your application to your account. Applications are unique entities in the Gloebit services, each associated with the merchant account used to create it. The Gloebit services work with application IDs rather than merchant account IDs. This allows merchant accounts to have multiple applications associated with them.
You should already be on your Merchant Tools page, showing your empty list of applications. If not, go to the page menu on the header bar and select "Merchant Tools".
The page that comes up is the Gloebit application information page. For new applications, most of the fields are empty and awaiting your information. However, before filling out the empty fields, let's talk about the already-populated fields.
The OAuth Key is what identifies your application to the Gloebit services. You will need the value in this field because your application will send it to the Gloebit authorization service (the first step in using all of the Gloebit services). It is a read-only field.
Your application will also need an OAuth Secret if it is using the (recommended) "authorization code grant" flow for OAuth2. You can edit this secret if you would like. Most importantly, do not share this secret with anyone or store it someplace where it can be discovered. It is an important component in the authorization protocol to prevent cross-site forgeries and protect your customers.
Another important security aspect of the OAuth2 protocol is validating callback URIs. The Gloebit Authorization service compares provided callback URIs against any Callback URI Prefixes for your application. Any you enter will be listed here. We will enter a prefix later in this walk-through.
Let's get back to the empty fields.
Scroll back up to the top set of fields and fill them out. Filling in your application's name is the only required step here. (If your application's name happens to be "Unknown", then it's already done for you!)
Filling in the other fields is useful if you want to experience what Gloebit does with the information or if you want to test functionality. For example, if you have a logo for your application, you can upload it so you can see where Gloebit will display it; or if you want to see that Gloebit's trackback links will go to the proper webpage, enter a default Return-To URI and try out some of the links (on various account pages accessible from the header page menu).
And with that, you are ready to integrate a Gloebit API.
Unfortunately, this walk-through is still being developed and there is not much more below. We are continuing to work on this page and will be regularly checking in new information. Keep checking back. If what you need is missing, contact us and let us know what you urgently need added or what questions you have. We will gladly work with you to get you going that way too.
Skip this section and go to Connecting a Gloebit API if you followed the steps above for creating your merchant account.
Users and merchants create accounts on Gloebit's website. An application associated with a merchant account uses OAuth2 to get a user's permission to interacts with their account.
Users purchase gloebits on Gloebit's website -- Gloebit takes care of interfacing with various payment providers. Once a user has a balance of gloebits, an application can exchange entitlements or digital inventory for the user's gloebits.