A small network built around one honest row.

We sit between two businesses and one person. Advertisers — app and game studios, survey providers — want a defined action taken. Publishers — reward sites, apps, games — have an audience willing to take it. We carry the offers in one direction and the money back in the other, and keep the record that says what happened.

The person at the end is the publisher's user, not ours. They never have an account with us, and they are credited by the publisher in the publisher's own currency.

We run a reward site of our own. OpusWall began as the layer that site needed and could not buy comfortably: campaigns we could see the source of, a revenue share that did not change between the pitch and the invoice, and a conversion record both sides could read.

Being our own first publisher keeps us honest in a specific way. Every decision about how the wall behaves is a decision we live with on the other side of the same integration.

These are not aspirations bolted onto a finished product. They are the constraints the schema and the interface were built under, which is why they are cheap for us to keep.

• Pay for confirmed work only. A conversion exists when the advertiser's own systems say the goal was completed, and not before.
• Keep one ledger. Advertiser spend, publisher earnings and our margin are three views of the same conversion row, in whole cents.
• Say what is not built. Anything designed but unreleased is marked as planned, on the page where it matters, not in a footnote.
• No chance mechanics. No wheels, no boxes, no gambling advertisers. A user always knows what they have to do before they start.
• Accounts by application. There is no self-serve sign-up on either side, because we want to know who is sending traffic and who is buying it.

Applications are open and reviewed by a person, and an approved account opens a panel that works: campaigns and goals on one side, placements and their integration on the other, the same reports behind both. The wall is running, and so are the click redirect and the signed postbacks in both directions. The mobile SDK and the Offers API are not built, and each Solutions page marks exactly which parts exist.

We have no publisher counts, payout totals or logo walls to show you, because we have not earned them yet. When there are real numbers worth quoting, they will come out of the database and be dated.

There is no support maze. Applications, integration questions and billing all reach people who can act on them, and the addresses are on the contact page.