A wall that starts as a link
A placement is your wall instance. It has an id, and that id is the URL. Open it in an iframe, a tab or a webview with your own user id, signed on your server with your wall key, and the wall is live for that user.
For publishers
Revenue from the users you already have.
OpusWall gives your reward site, app or game a wall of campaigns we agreed directly with the studios behind them. Your users complete offers and are credited in your currency, at your exchange rate. You keep an agreed share of every conversion.
- Revenue share
- Starting at 70%The share a new publisher starts on. It is recorded on your organization and applied to every conversion payout, in whole cents.
- Minimum payout
- $50Paid in US dollars against your balance once it is above this. The minimum exists so a payout costs less to send than it is worth.
- Application answer
- 2 business daysEvery application is read by a person, and every applicant gets an answer in writing — including the ones we turn down.
What you get
An offerwall that behaves like part of your product
Your users, your currency, your interface where you want it. What we own is the campaign supply and the record of what was completed.
A share that does not move
Your revenue share is set on your organization and applied to every conversion payout, in whole cents, rounded in a way that can never hand out more than came in. It is not renegotiated campaign by campaign.
Told when it settles
When a conversion settles we call your server with the user, the amount in your currency and a signature you verify; a reversal arrives the same way. A failed call is retried for about three days, and every attempt is in your panel with your server's answer.
Your currency, your users
Users see your points, coins or credits, converted from cents with the exchange rate on your placement. They never need an OpusWall account and never see ours.
Integration
Three ways to put the wall in front of someone
One of the three runs today — the hosted wall. The SDK and the Offers API are specified, not built. Whichever you use, the clicks, the conversions and the postback are the same.
Payouts and reporting
Where the money sits, and when it moves
Earnings are the sum of real conversion rows, not an estimate that gets corrected later.
Where the platform stands today
Applications are open and read by a person, and an approved account opens a working panel. The hosted wall, the click redirect and both server-to-server postbacks are running: a publisher's members open the wall, an advertiser's server confirms completed goals to our endpoint, and every settled conversion is signed and delivered to the publisher's server, retried until it is acknowledged. What is not built is marked Planned where it is described — today, the mobile SDK and the Offers API. The network is new, so there are no customer figures to quote, and this site quotes none.
How earnings accumulate
Every settled conversion adds your share of that payout to your balance, as an integer number of cents. Nothing is estimated and nothing is averaged: the balance is the sum of real ledger rows.
A reversed conversion subtracts the same amount it added. Reversals are rare, but they are part of an honest ledger and they are visible as their own movement rather than as a silent correction.
How and when you are paid
Payouts are made in US dollars against your balance, once it is above the minimum below. The minimum exists so that a payout costs less to send than it is worth.
Your own users are paid by you, in your own currency, on your own schedule. What you credit a user and when is your decision — the wall never touches your user balances.
What you can see
The publisher panel shows your clicks, conversions and earnings by placement, campaign and country, your ledger — one row per balance movement — and your payout requests, each figure computed by the database from real rows.
Each placement's page shows every postback attempt with the signed request and your server's answer, and sends a test postback through the real worker before a real conversion arrives. What your server acknowledged is the authoritative record on your side.
Traffic we cannot accept
Advertisers pay for people, so the wall only works if the people are real. Automated completions, incentivised misrepresentation and traffic your users did not choose are grounds for withholding a conversion and, if it continues, for suspending a placement.
- Bots, emulators and scripted completions
- Offers presented as something other than what they are
- Traffic sourced from adult, gambling or chance-based products
- Any placement your own users cannot see they are using
For publishers
Tell us where your users are
The application asks what you run, roughly how large your audience is, and how you monetize today. It takes a few minutes, and a person reads it.