Home / For Task Suppliers

B-side · Supply partners

Your offers, delivered by
real Vietnamese hands.

Kizivo runs a multi-supplier aggregation layer next to its self-operated task wall: offerwall networks, survey panels and PTC platforms feed their catalog into our users’ home feed through one adapter contract — while we handle geo-routing, attribution, user payouts and reconciliation.

Partnership flow Integration options Postback & money rail

🧩 WALL · NATIVE · SDK — live in as little as a day 🔐 Signed S2S postback · idempotent · reversal-aware 📊 Daily balance-API reconciliation

Why distribute through Kizivo

A demand pocket most networks fill poorly

Under-served geography, honestly served

Southeast Asian completions are expensive to source on generic walls — bots distort your quality metrics. Our pool is opt-in, device-attested (Play Integrity) and country-verified, with cloud-farm heuristics tuned for the Vietnamese device market.

Daily-habit traffic, not one-shot clickers

Users return for follow/comment/live-stay tasks and phone-credit redemptions. Your offers ride on top of that cadence inside the same feed — impression frequency you don’t get from a standalone wall.

Attribution you can trust line by line

Per-click subid ({uid}:{offerId}:{clickId}), click URLs fetched just-in-time (never cached), raw postback payloads archived before any processing. If a conversion is disputed, both sides look at the same bytes.

Integration options

Three ways in. Start narrow, scale on data.

Mode	How it works	Time to launch	Revenue-share implementation	Best for
WALL iframe / hosted	Your hosted wall embedded as a Kizivo tab (session URL or new tab); Kizivo balance bar stays on top	~1 day	Exchange-rate multiplier set on the placement; you confirm rewards via postback	Fast volume tests with zero API work
NATIVE offers API	We pull campaigns list / detail, render offers as Kizivo cards, request per-user click URLs, receive S2S postbacks	2–5 eng-days	Your payout field vs. our user share computed in our ledger — margin visible per offer	Networks with full APIs (Torox-style); best UX and highest completion
SDK survey / aggie	Your mobile SDK or client-side survey API inside our shell; callback amount credited to the user	1–3 eng-days	Callback value minus configured user share	Survey aggregators (BitLabs / TapResearch-style)

The adapter contract we implement

Every supplier joins the feed by mapping to one internal interface — whatever your docs look like, our side converges to:

interface OfferProviderAdapter {
  fetchOffers({os, geo, category})   // synced every 6–12h → offer pool
  fetchOfferDetail(offer, uid, geo)  // per-user pricing
  buildClickUrl(offer, uid, geo, subid) // just-in-time, never cached
  parsePostback(raw) → {conversionId, payout¢,
        coins, type: REWARD|REVERSAL, raw}
  verifySignature(raw)
  // optional: fetchUserActivity, fetchBalance
}

Offer-pool governance on our side

Geo × OS routing — your catalog filtered per user country and device
Cross-source dedup — the same app install live on two networks shows once (highest payout wins)
Health guards — API success rate, postback P95 latency, fill and reversal rates; breach the limit and a source auto-degrades out of the feed, never silently burns budget
Payout-change alarms — a >30% swing on an offer pauses its distribution and alerts ops

Postback & money rail

The boring part, done properly

Every conversion walks the same seven gates. No gate is optional.

postback in ─► IP whitelist ─► raw payload archived ─► signature verified ─►
idempotency (provider + conversion_id) ─► credit user coins as frozen ─►
release after hold window (default 30d · 7d for surveys/PTC) ─► daily reconcile vs balance API

Reversals

Negative postbacks claw back frozen or available coins; repeat offenders are down-weighted in the feed automatically.

Reconciliation

A nightly job diffs our Σ(payout) against your balance/activity API; differences >0.5% open a finance ticket — for both sides.

Settlement

Tipalti / PayPal / bank per network terms (Net-7/15/30). We treat your minimum thresholds and currency rules as configuration, not favors.

Share policy

We pass 50–70% of payout to users by geo×category matrix (VN 65%, T1 60%, PTC 75%). Changes sync to your placement multiplier via a checklist — no split-brain pricing.

Partner fit

Who thrives here — and who doesn’t

✓ Great fit

Offerwall networks with strong CPI/CPA fill for emerging markets and SEA-friendly gaming/app offers
Survey panels & aggregators needing reliable VN/SEA completions (CPX, BitLabs, TapResearch-style supply)
PTC / microtask platforms looking for daily-habit impressions at high frequency
Residential-line & verification buyers — our second supply product (idle real-device capacity, priced per device/day) turns our pool into contracted infrastructure

✗ Not yet

T1-only premium gaming offers — our pool is SEA-first today; a dedicated T1 app line is on the roadmap, talk to us if your payout survives VN pricing
Paid-review offers and “top-up to unlock” mechanics — we keep those out of the feed by policy (consumer-trust line)
Networks without S2S postback or with no reversal handling — the rail above isn’t negotiable

Partnership flow

From first email to first postback in two weeks

Outreach

Write team@kizivo.com with your network name, integration docs and geo/category coverage.

Commercial terms

Settlement method, net terms, thresholds, user-share band, placement(s) created on your side.

WALL A/B pilot

~1 week: hosted wall live for a user slice; we watch completion, EPC and reversal behavior on real traffic.

Scale or go native

Good numbers → full feed share; better numbers → NATIVE/SDK integration with per-offer routing weights.

FAQ

Supplier questions, answered

Are your users incentivized in a way that breaks our terms?

Reward-app users are inherently incentivized, and we only list offers whose network terms permit incentivized traffic (or run them as NATIVE with explicit consent flows). We flag the “incent” nature at click time where your policy requires it, and we never auto-click or auto-install — a human uploads the evidence or the activity API confirms the event.

How do you handle duplicate conversions across networks?

When the same app is live on two networks, our feed shows one (higher payout wins) and suppresses the other per user, so your inventory isn’t double-dipped by design.

What does the hold/freeze window do for my reversal exposure?

User coins from your postbacks are credited frozen (default 30 days, aligned to typical gaming windows; 7 days for surveys/PTC). A negative postback claws back frozen or available balance, and users with repeated reversals get feed-weight penalties before they cost you again.

Can we see funnel data?

We report impressions → clicks → starts → completions per offer family on a recurring basis, so you can tune payouts and geo bids with the same numbers we use for routing.

Do you buy traffic too, or only sell it?

Both directions are on the roadmap — as the pool grows, our self-operated advertiser tasks can be listed on your network, and we run acquisition CPA offers on GPT platforms. Ask about the advertiser-side listing when you write in.

Your offers, delivered byreal Vietnamese hands.