Drop one wall into your app or site and your users pick the task they want. Every conversion comes back over a server to server postback, is checked for fraud before a single coin moves, and shows on your statement the same second it happens.
Ios
Pc
Pc
Android
Ios
Pc
Pc
Android
One catalogue, two sides
Publishers put the wall in front of users who already open their app every day. Advertisers buy the finished action behind it. Nothing in the middle is guessed: the same click id travels from the tap, to the postback, to the line on your statement.
Put the wall in your app, game or site. Your users choose what they want to do, and you keep a share of everything they finish.
You pay when a real user finishes what you asked for. Set the budget, set the caps, and see the quality of the traffic before you are billed.
One campaign can carry several paid events. Each fires its own postback and credits on its own, so a user who stops halfway still earned something.
14 paid events in this campaign
# we call your endpoint the moment the event clears
GET https://your-site.com/postback
?user_id={user_id}
&transaction_id={transaction_id}
&offer_id=37355944
&event_name=Continue to City Hall Level 12
&payout=5.00
&status=1
# your server answers
200 OK ok
The path of one conversion
Six things happen between a user tapping an offer and the money reaching your statement. Here is what exists after each one.
We store the click against your placement with the user id you passed, the device and the country. Every decision after this one points back to this row.
# the moment your user taps an offer click_id 8f2c41a9 placement your-site.com user_id 91342 device Android 14 · Pixel 7 geo US · residential time 19:04:11 UTC
Install, sign up, reach a level, finish a survey. The advertiser decides what counts and tells us the second it clears on their side.
# the advertiser confirms, not the browser offer Mistplay US event reach level 12 source advertiser s2s payout $35.00 cleared 19:21:46 UTC
Device, network, duplicate and velocity checks run before a balance moves. Anything that fails is held with the reason attached, never dropped in silence.
device clean · no emulator network residential US · no proxy duplicate none on this device velocity 1 conversion / 24h score 12 / 100 verdict pass
A server to server call to the endpoint you configured, signed, with the user id, the transaction id and the payout. Retried until your server answers.
GET https://your-site.com/postback
?user_id=91342
&transaction_id=8f2c41a9
&reward=350&payout=35.00
&signature=5e1b9c…&status=1
# your server answers
200 OK
The conversion shows in your report the same second, with the offer, the country, the device and the exact amount you earned on it.
offer Mistplay US geo US · Android status credited you earn $35.00 balance $2,646.00
A fixed calendar, crypto or bank transfer, and a statement that reconciles line by line against what the report already told you.
period 1 – 31 October conversions 1,284 total $2,646.00 method USDT TRC20 · or bank due 30 November
Traffic quality
Every conversion is scored before it moves a balance. Advertisers are not billed for farms, and publishers do not get a chargeback three weeks later for something that could have been seen on day one.
Integration
Embed the wall wherever your users already are, then point us at the endpoint that credits them. There is nothing else to wire up, and no release needed to change what the wall shows.
ok and we mark it delivered. The same row appears in your report.<iframe src="https://www.pubsnest.com/offer/YOUR_KEY/USER_ID" width="100%" height="700" frameborder="0" allow="clipboard-write"> </iframe>
// Android Offerwall.open(context, "YOUR_KEY", userId); // iOS Offerwall.open(key: "YOUR_KEY", user: userId)
# we call you, you credit the user, you answer ok
GET https://your-site.com/postback
?user_id={user_id}
&transaction_id={transaction_id}
&payout={payout}
&signature={signature}
&status=1
Every parameter, the signature and the test calls are in the documentation.
FAQ
Short answers. The long ones, with every parameter and every edge case, live in the documentation.
Ask us anything elseApply with your app or site, get read by a person, and keep an integration you can actually read. No minimum volume to start.