Quick Start

Complete guide for integrating our Postback and Web Offerwall system. Get started with seamless reward notifications and instant user crediting.

Key Information:

Our system sends HTTP GET requests to your postback URL whenever a user completes an offer. This enables real-time, automatic crediting of user rewards.

Phone

How does it work?

When a user successfully completes an offer on your platform, our system automatically sends a notification to your server with all the necessary information to credit the user. This creates a seamless experience where users are rewarded instantly for their actions.

User Completes Offer

User successfully finishes an offer or task on your platform

Postback Sent

Our server sends a GET request to your postback URL with reward details

User Gets Rewarded

Your system processes the request and credits the user automatically

Check

I am ready to start

Great! Let's get you set up with our postback system. Follow the integration guide below to start receiving automatic reward notifications.

Pro Tip:

Make sure to implement proper signature verification to ensure the security of your postback endpoint. This prevents unauthorized requests and protects your users' rewards.

Postback Integration

Whenever a user completes an offer, we will make a call to the Postback URL that you indicated in your app attaching all the information that you will need to credit your users.

HTTP GET Request

Our server will make a HTTP GET request to your server including all the following parameters.

Postback Parameters

Parameter	Description	Example
[USER_ID]	This is the unique identifier code of the user who completed action on your platform.	user123
[REWARD]	The amount of your virtual currency to be credited to your user.	100
[DEVICE]	Device information of the user who completed the action.	mobile
[TXID]	Unique identification code of the transaction made by your user.	tx_abc123def456
[PAYOUT]	The offer payout in USD.	2.50
[SIGNATURE]	MD5 hash that can be used to verify that the call has been made from our servers.	a1b2c3d4e5f6...
[OFFER_NAME]	Name of the completed offer.	Download Game App
[OFFER_ID]	Unique identifier of the completed offer.	offer_789
[STATUS]	Determines whether to add or subtract the reward. "1" for credit, "2" for debit.	1
[USER_IP]	The user's IP address who completed the action.	192.168.1.1
[COUNTRY]	Country (ISO2 form) from where the lead comes.	US

"REWARD" and "PAYOUT" parameters are always absolute values. You will need to check the STATUS parameter to see if you need to add or subtract that amount from your users.

Custom Postback Parameters

If you would like to receive custom parameter names in your postbacks, you can specify them in the postback URL like the following example:

Example URL


                                https://your-domain.com/postback?USER_ID=[USER_ID]&REWARD=[REWARD]&DEVICE=[DEVICE]&TXID=[TXID]&PAYOUT=[PAYOUT]&SIGNATURE=[SIGNATURE]&OFFER_NAME=[OFFER_NAME]&OFFER_ID=[OFFER_ID]&STATUS=[STATUS]&USER_IP=[USER_IP]&COUNTRY=[COUNTRY]

You can use any of the parameters from the "Postback Parameters" table. You will need to put them between square brackets [ ].

Security

Important Security Notice

You should verify the signature received in the postback to ensure that the call comes from our servers. Signature parameter should match MD5 of: USER_ID + TXID + REWARD + SECRET

You can find your secret in your app dashboard. The formula to be checked is as follows:

PHP Security Validation

Responding to the Postback

Our server will expect the following responses:

Success Response

OK

When you receive a new transaction.

Duplicate Response

DUP

When you receive a duplicate transaction. Our server will stop further attempts.

Timeout Information

Our servers wait for a response for a maximum time of 60 seconds before timeout. In this case, it will retry sending the same transaction up to 5 times during the following hours. Please check if the transaction ID sent to you was already entered in your database to prevent duplicate credits.