Step 1. Create An Account
1. Go to http://gwallet.net/gwallet-network-
2. Fill in the fields on the Publisher Registration page.
3. Check our Terms and Conditions and click Register
if you accept them.
If the information you provided is correct, you will be
automatically logged into your account.
Login page will be available at:
If you are not incorporated (e.g. you are self-employed or a freelancer), please use your first and last name as your
We advise you to select the preferable method for getting your commission (PayPal, Check, Wire Transfer) when
you register. However, you can define it later by clicking Account link in the top right corner of any page.
U.S. residents are required by law to submit a W-9 Tax Form. Please send it to email@example.com. You do not
have to submit it during registration, but your payments will be unavailable until we receive it. W-9 Tax Forms can
be downloaded at http://www.irs.gov/pub/irs-pdf/fw9.pdf.
gWallet Quick Integration Guide (September 2010) Page 1 of 6
Step 2. Add Your Application
1. Click Add Application to setup a new application. The Add Application button is also available on the
My Applications screen.
2. Fill in the fields on the Add Application page.
Choose a unique name for your app, select
the platform (Facebook, MySpace or
Website), and specify your app ID on this
platform (or app URL for Websites).
Provide the name of your virtual currency
(in plural form) and specify its exchange
rate to one US dollar.
Choose through which systems you want
to permit your users to buy your virtual
This URL will be “called” upon user’s
completion of an offer.
Select offer categories that best suit your
3. Press Save.
gWallet Quick Integration Guide (September 2010) Page 2 of 6
The next screen will provide you with the iFrame code and Secret Key for your new application. See the next steps for
You’re all finished. Give us a few days to approve your application. When it is approved, you will receive an approval
confirmation letter. Until then, your iFrame will be unavailable.
Step 3. Integrate Our iFrames With Offers
1. Open the My Applications screen, choose your application, and click Edit.
gWallet Quick Integration Guide (September 2010) Page 3 of 6
2. Locate the iFrame code at the bottom of the Edit Application screen.
3. Place this code within your application’s code.
appId — a 32-character unique alphanumeric string that specifies your application and can be found inside iFrame
code on Edit Application screen (see screenshot above)
userId — an alphanumeric value you use to uniquely identify each of your users (for example, a Facebook User ID)
trackId — optional alphanumeric parameter that you can pass for your own tracking (we will save this and return
up to 100 characters)
panelId — optional parameter that defines the design of the offerwall (panelId=3 is used by default)
Note: Please refer to our Offerwall Guide if you want to build a custom representation of gWallet offerwall based
on XML/JSON feeds. In this document you will also find the full specification of request parameters.
At this moment we have 6 different designs of the offerwall which use the same offers’ list but differ in size and
You can choose either of them by simply adding an optional parameter &panelId=N to your iframe source URL.
panelId=1 panelId=3 (default value)
The same as basic but with
Basic offerwall design
offers’ images instead of icons
Preferred iframe settings: Preferred iframe settings:
width=”728” height=”2200” scrolling=”auto” width=”728” height=”2200” scrolling=”auto”
gWallet Quick Integration Guide (September 2010) Page 4 of 6
Brand bar with carousel scrolling
Customizable logo, call to action write copy and color scheme
(Direct Payments can be chosen by clicking “buy direct” icon)
Preferred iframe settings: width=”728” height=”90” scrolling=”no”
Similar to Brand bar but Direct Payments are always presented on the left
Preferred iframe settings: width=”960” height=”90” scrolling=”no”
One-place offerwall with carousel scrolling and
Four-place offerwall with carousel scrolling
no Direct Payments options
Preferred iframe settings: Preferred iframe settings:
width=”620” height=”520” scrolling=”no” width=”215” height=”415” scrolling=”no”
gWallet Quick Integration Guide (September 2010) Page 5 of 6
Step 4. Test Postback
1. On the Edit Application screen, confirm that the
Postback URL is defined and clickTest Postback.
2. Enter the User ID (e.g. 12345) and virtual
currency amount earned by the user (e.g. 2525).
3. Press Test.
You will see the actual postback URL with all of the
parameters we pass as well as your server response.
We will send a similar postback to your Postback URL every time a user completes an offer or payment.
Your reply must be a single character:
1 — if you received the postback and rewarded a user
0 — otherwise
If your server doesn’t respond, we will try to “call” it 10 times within 30 minutes. If you respond with 0, we will send
postbacks every 4 hours within 48 hours. Of course, this process will be stopped after you respond with 1.
appId — ID of your application in our system
userId — ID of your user
amount — amount of your virtual currency earned by this user (may be negative in case of a chargeback)
trackId — the value you passed to us on iFrame call
hash — hash code, calculated as md5(*USER ID+ + ":" + *APP ID+ + ":" + *SECRET KEY+), where “+” is string
concatenation and [SECRET KEY] is the Secret Key of your application, which can be found at the bottom of
Edit Application screen
chargeback — if present and equal to 1, denotes amount to be a chargeback (the value of amount will be negative)
In rare occasions you will receive a negative value in the amount parameter which, together with chargeback=1,
means that a certain transaction of the user was chargebacked, and you should adjust the amount of the virtual
currency the user has in your application. We understand that decreasing the quantity of virtual currency of a user
may be complicated in some cases, but we are working to make chargebacks as infrequent as possible.
Use the Secret Key to calculate the hash code and compare it with the hash parameter to verify the authenticity of
Another security option is to whitelist the following IP range of our servers: 18.104.22.168-22.214.171.124 (or 126.96.36.199/25).
gWallet Quick Integration Guide (September 2010) Page 6 of 6