Monetization
Ad revenue without the AdSense part. Vouch holds the Google Monetization partner relationship, so all you need is ad space and impressions, with a wallet you can read and payouts in stablecoin or bank transfer.
Doing this yourself means an application to Google AdSense, a traffic bar to clear, a policy review to survive, and your own payment problems to chase when a payout does not arrive. Vouch already holds that relationship, so you do not have to hold one of your own.
You apply once, a person reviews it, and an approved property gets a tag. Install it and our Google Monetization partner fills the space. What it earns lands in a wallet you can read and withdraw from. What you need to bring is impressions.
This module is opt-in per property and is never on by default. It is also the one part of Vouch that points away from the rest: every other module makes your product work better, and this one turns your audience into someone else's inventory. That is a fair trade for some apps and a bad one for others, which is why nothing here happens unless you ask for it.
Before you apply
Three things decide whether this is worth doing.
You need ad space. A banner slot in your app or on your site, which you are willing to give over to somebody else's creative.
Placement decides earnings, not just impressions. An ad below the fold earns a fraction of one visible without scrolling. Nobody will optimise this for you.
You need enough traffic to be approved. The partner sets a minimum and it is shown before you apply, so nobody applies into a refusal they could have predicted.
Finding your impression numbers
Traffic on the application is self-declared, and we would rather say why than pretend otherwise: there is no honest free way to measure somebody else's site from its address. The estimator services are paid, are estimates, and are worthless below meaningful traffic.
For a website, the real figure is in Google Analytics → Reports → Engagement → Pages and screens. For an app already sending events to Vouch, we show you our own monthly active device count beside the field, so at least one number on the form is not a guess.
The figure that actually matters is measured after the tag is installed, from real impressions.
The application
| Field | Notes |
|---|---|
| Property type | A website or an app |
| Name | The site address, or the app's name exactly as it appears on the App Store or Google Play. The partner matches on the published name, so an approximation costs you a review cycle |
| Category | Yours, from a fixed list |
| Declared traffic | Monthly impressions or sessions |
| Ad categories | Which advertisers you will accept. A fintech app often wants fintech advertisers only; a children's app must be able to refuse whole industries |
| Ad formats | A banner and an interstitial are different decisions |
| Payment frequency | Monthly, quarterly or yearly |
Submitting requires agreeing to the revenue share.
Vouch takes 5% of gross revenue. You receive 95%. The figure appears again on every statement, so you never have to remember it or work it out.
Review
- Submitted. Vouch staff are notified. Nothing reaches the partner automatically; a person looks first.
- Sent to partner. Dochase run their own diligence and scanning. You can see that it was sent and when.
- Approved or rejected.
On approval you get the script and where to put it. On rejection you get the partner's reason, in their own words, and whether you may reapply. A rejection with no reason is worse than none, so the API refuses one.
You are emailed at every state change. Somebody who applied and heard nothing assumes the product is broken.
Installing
For a website it is a script tag. For an app it is the partner's SDK, wrapped so you add one dependency and one initialisation call.
The dashboard reports whether impressions have arrived and when the last one was, so a tag pasted into the wrong place is found in minutes rather than at the end of a quarter.
A kill switch stops serving on a property immediately, without removing the tag and without an app release. If an ad appears that you cannot live with, you are not waiting on review.
Removing monetization affects nothing else. Your links keep working.
The wallet
Dochase pays Vouch, Vouch takes its share, and you draw the rest down. Because the money passes through us, the wallet is a ledger rather than a report, and it behaves like one.
Entries are append-only. The balance is the sum of them and is stored nowhere, so there is no number that can drift away from the truth. A correction is another entry, which means a mistake and its fix both stay visible rather than one quietly replacing the other.
Revenue is recorded as three figures, never two with the third implied:
| Gross | What the partner reported |
| Vouch's share | Rounded down, so rounding never favours us |
| Net | What lands in your balance |
A payout is reserved the moment you request it. The amount leaves the available balance straight away, so the same money cannot be requested twice and two requests made at once cannot both succeed. If a payout later fails, the exact amount returns and both movements stay in the ledger. If your balance moves twice you are owed an explanation, and two entries are that explanation.
Payout methods
| Method | Notes |
|---|---|
| USDT | Settles the USD amount one for one. The network must be named |
| USDC | The same |
| Bank transfer, local | Account name, number and bank |
| Bank transfer, foreign | In USD, with a SWIFT/BIC or IBAN |
A stablecoin payout to the wrong address, or on the wrong chain, is unrecoverable. Vouch requires the network explicitly rather than guessing it, and checks the address shape, but neither of those can save a correctly formatted address that belongs to somebody else. Check it.
Payout destinations are encrypted at rest and shown only as a mask. They are the most sensitive thing this product holds about you, and they never appear in the audit log.
A payout moves through requested → approved → processing → paid. Each step records who moved it and when, and a paid payout carries a transaction hash or bank reference you can quote. A failure carries its reason.
Reading the wallet screen
Four figures, and they mean different things:
| Available | What you can withdraw right now. The sum of the ledger |
| Earned all time | Every revenue credit since you started |
| Paid out | What has actually left, net of anything that failed and came back |
| In flight | Requested and not yet settled. Already deducted from available |
The ledger below them is the whole story, newest first, and it is the screen to read when a figure surprises you. Every movement is there, including the ones that cancel out: a failed payout shows both the reservation and its return, because a balance that moved twice deserves two rows rather than one net effect you have to infer.
The commission line carries no amount. It does not move your balance; it is there so the commission is auditable rather than inferred from the gap between gross and net.
Adding a payout destination
This is the fussiest form in Vouch, and deliberately. Everything else here can be corrected after a mistake; this one sends money somewhere it cannot be recalled from.
For a stablecoin you choose the network explicitly. It is never inferred from the address, because the same address string is valid on several chains and paying on the wrong one destroys the money with no recourse. You also type the address twice. That is not friction for its own sake: pasting twice is the only check available against a clipboard that changed under you, which is a real and common attack.
For a bank transfer, a foreign one needs a SWIFT/BIC or an IBAN and settles in USD.
Removing a destination archives it rather than deleting it. Payouts already sent there still reference it, and a payment history with a hole in it is not a payment history.
Requesting a payout
Pick an amount and a destination. The amount leaves your available balance immediately, which is what stops the same money being requested twice and stops two simultaneous requests both succeeding.
A payout moves through requested → approved → processing → paid. Each step records who moved it and when. A paid payout carries a transaction hash or bank reference you can quote when chasing. A failed one carries its reason and returns the exact amount to your balance.
A paid payout cannot be reversed in the wallet. The money has gone, and pretending otherwise by crediting the balance back would be inventing money. Corrections at that point are an adjustment entry, which a person makes with a reason attached.
Revenue reporting
Revenue figures are sample data until the partner exposes a reporting endpoint. Every screen showing them says so, and the API marks the responses. A dashboard quietly showing invented earnings would be the worst thing this module could do, so we would rather label it loudly than let a figure be mistaken for real.
Once the endpoint exists, figures are labelled with the partner as their source and the time they were last fetched. Vouch does not restate a number it cannot audit as though it were its own.
Monetization figures are reported separately from your growth figures and are never added into them. Ad revenue is not a conversion and must not appear in an attribution report as though it were.