How it works

How the coins model works

A hosted wall runs on two currencies, and mixing them up is where first integrations lose money.

• LootHQ Coins: the wall's native currency. Every offer pays out in coins at a consistent rate, which is what lets the wall run its own mechanics on top: leaderboards, lotteries, prize pools, streak bonuses. Coins are the user's score on the wall; the spendable reward lives in your app, in your currency.
• Your currency: gems, points, credits, whatever your app calls it. You set the points-per-coin rate, so your economy stays yours. Your postback fires the moment a conversion is approved and carries {points} already converted at that rate, so the user's reward shows up in your app with no action on their part.

Why two layers

• Rate control. Set the coin-to-currency rate that fits your economy, and change it without touching your integration.
• Retention mechanics you don't have to build. Leaderboards and lotteries give users a reason to come back to the wall, which means more completions without any engineering on your side. Leaderboards run network-wide across all LootHQ publishers, not per-app. That means the board is competitive from day one regardless of your traffic volume: your users compete for a prize pool LootHQ funds, not one drawn from your revenue. No publisher names, branding, or attribution appear on the board; users see display names and avatars only. Network Leaderboard ships off by default; toggle it on per placement under Dashboard → Placements → your placement.
• Reversals are mirrored to you at full value. When an advertiser reverses a conversion, we deduct the coins from the user's wall balance (it can go negative; the deduction comes out of their next earnings), and your reversal postback asks you to take back exactly what the approval postback credited. If you would rather never take a reward back from a user, hold risky offers on your own side and release them after your own window. See Handling reversals.

Negative balances work because the user's earning relationship lives on the wall. An SDK or iframe wall, where the publisher holds that relationship, can't do this at all.

This example is about what the user receives. See “When you earn” below for how your own wallet is credited (it's a different number, on a different schedule). Both levers are yours, in Publisher Dashboard → Placements: the points-per-coin rate is set when you create the placement, and the margin is an editable percentage on the same page: your cut, the share of each payout you keep before paying out to your users. If you'd rather skip the coin layer and render offers in your own UI with USD postbacks, see the Offers API below.

Integration flow

Where a click goes, and where the money comes back:

1. 1

   User opens your app or site

   You
2. 2

   Your app loads the LootHQ wall

   You

   iframe, script embed, modal, or hosted link, always with your sub_id

3. 3

   User clicks an offer on the wall

   LootHQ

   LootHQ records the click, then redirects to the advertiser

4. 4

   User completes the offer at the advertiser

   Offer network

   install, sign-up, purchase…

5. 5

   The advertiser/network posts the conversion back to LootHQ

   Offer network

   the tracking link is ours, so we always see it first. This is also the moment YOUR wallet is credited in full (see “When you earn” below)

6. 6

   LootHQ credits the user in LootHQ Coins

   LootHQ

   1 USD of payout = 1,000 coins, minus your placement margin; coins drive the wall's leaderboards and prizes

7. 7

   The completion is approved → LootHQ fires your postback

   LootHQ

   {points} arrives here: the amount to credit, already in your currency

8. 8

   Your backend credits the user and shows the completion

   You

When you earn

Your LootHQ wallet is credited the full listed payout for that conversion the moment it is approved, for both Hosted Wall and Offers API placements (each goal of a multi-goal offer credits separately as it lands). There's no proration and no waiting on the user.

• The postback is about your user, not your wallet. The approval-time postback tells you what to credit the user in your own currency. It has no effect on your LootHQ wallet; that is settled separately, at the same approval.
• Coins are a score, not a debt. A user's coin balance on the wall drives leaderboards and prizes. Nothing about it delays, reduces, or claws back what you're owed.
• Only an explicit reversal claws back. A genuine reversal (advertiser rejection, chargeback, fraud, void) is the one thing that debits your wallet. See Handling reversals below for exactly how that's delivered.

Users see earned coins instantly, but some categories and new accounts hold coins pending for a short window before they count as available. See Pending and available coins. That window gates only the user's coin display on the wall; it never delays your postback, which fires at approval regardless, and it never delays or reduces your wallet credit.

Track your running balance any time in Publisher Dashboard → Earnings.

Pending and available coins

Coins are credited to the user instantly and visibly the moment a conversion is approved. The wall always shows them right away, split into available (cleared) and pending (clearing soon). Some offer categories and brand-new accounts carry a short clearing window; logged-in users clear faster. The window gates only the user's coin display on the wall. It never touches your side: your postback fires at approval regardless, and your wallet is paid in full at approval regardless.

Clearing windows vary by offer category. A user's trust tier (built from account age, history, and a clean reversal record) shortens them over time, and a verified login shortens them immediately, which is the reason to prompt sign-in. Coins credited on a hosted wall count toward the user's lifetime and leaderboard totals immediately; only availability is gated.