# Setting Up Reward Handling
Once you have determined your rewarding strategy, use the DT Console to set up your rewarding mechanism. For more information about how to reward your users for completing offers, see [Rewarding Your Users](https://app.gitbook.com/s/7drDlNSyycpmA7Zx8kgX/publishers/task-specific-guides/rewarding-your-users).
{% hint style="info" %}
In addition to setting up your rewarding mechanism in the DT Console, you must also integrate your rewarding strategy with the Offer Wall SDK.
{% endhint %}
Specify reward handling settings from the **Settings** tab of the **Application Details** screen.
To access the **Reward Handling** settings:
1. Log in to the [DT Console](https://console.fyber.com/applications), and go to **Monetization→Offer Wall**.
2. Select the app for which you want to set up reward handling.\
The **Application Details** screen opens.
3. Click the **Settings** tab, and locate the **Reward Handling** section.
## Setting Up Virtual Currency Server
When you add an app to Offer Wall, the default reward handling method is set to use the DT Virtual Currency Server.
To set up virtual currency server:
1. In the **Reward Handling** section, set the **Callbacks** setting to **Use Fyber virtual currency server**
2. Enter a security token in the **Security token (optional)** field. To locate the **Security token**, see [Locating Offer Wall Credentials](https://docs.digitalturbine.com/dt-console/offer-wall/locating-offer-wall-sdk-credentials) for more information.
3. Click **Save**.
## Setting Up Server-Side Rewarding
If you are using server‑side rewarding, specify the fully qualified endpoint where you want DT to send reward notifications (callbacks).
In each reward callback, DT can include parameters about the reward transaction, such as who and how much to reward, transaction security, and payout information. For more information about the parameters DT supports, see [Server‑Side Rewarding](https://app.gitbook.com/s/7drDlNSyycpmA7Zx8kgX/publishers/task-specific-guides/rewarding-your-users/server-side-rewarding).
To specify the parameters that you want DT to include in the reward callback, enter your endpoint and parameters in the following format:
```
https://myfungame.com/ofwrewards?¶meter1=¶meter2=…
```
The following sample entry specifies all of the additional parameters that DT supports:
```
https://myfungame.com/ofwrewards?&sid=&_trans_id_=&pub0=&pub1=&pub2=&offer_title=&payout_net=
&net_payout_eur=&payout_gross=&payout_currency=&lpid=&step_index=&vcs_enabled
=&placement_id=
```
A sample callback to this callback URL entry would look like this:
```
https://myfungame.com/ofwrewards?
uid=12345
&amount=10.50
¤cy_name=Coins
¤cy_id=coins
&sid=f3c1a97be8d52a61b40798fc3e15d6a42f89c550
&_trans_id_=f4a7c2d9-1e6b-4f58-9a23-8d7e45bfc012
&pub0=value0
&pub1=value1
&pub2=value2
&offer_title=Default+Offer
&payout_net=5.00
&net_payout_eur=4.50
&payout_gross=6.00
&payout_currency=EUR
&step_index=2
&lpid=123456
&vcs_enabled=false
&placement_id=default
```
{% hint style="info" %}
DT always includes the following parameters in the reward callback, whether or not you specify them.
* `uid`
* `amount`
* `currency_name`
* `currency_id`
If you want DT to return only these default parameters, enter just the endpoint URL.
{% endhint %}
To set up server‑side rewarding:
1. In the **Reward Handling** section, set the **Callbacks** setting to **Receive server‑side callbacks**.
2. In the **Callback URL** field, enter the fully qualified endpoint to which DT should send reward callbacks along with any additional parameters you want DT to include in the callback. Use the format described previously.
3. If you want DT to include the `sid` parameter in the reward callback, enter a security token in the **Security token (optional)** field.\
DT uses this security token to calculate the `sid` value.
4. Click **Save**.
5. To ensure that the endpoint is valid, send a test callback.\
For more information, see [Sending Test Callbacks](https://docs.digitalturbine.com/dt-console/offer-wall/setting-up-an-existing-app/setting-up-reward-handling/sending-test-callbacks).
