Earn Koins & measure

Since 31 July 2026, platform actions do not pay Koins. Kariant’s standing rule that gamification never mints Koins now covers partner action rewards too: completing your profile, publishing listings, receiving reviews, replying to reviews, and being active month to month are recognized with badges and XP — recognition on your gamification profile, never wallet credits. Action grants credited before that date stay in your wallet and remain Kash-convertible under the earned-Koin policy.

The referral bounty is unaffected — it is a commission on a partner you bring in, not an action reward — and so are affiliate earnings (Katalyst, Konsumer). Those rails still pay real Koins.

Below the program rules, the same page shows your Earn History — the actual server-side ledger. Events dated before 31 July 2026 show the Koin amounts the retired action program credited (and capped events are labeled capped instead of silently missing). Action events since then appear as badge credits: they count toward badges, carry no amount, and never touch your wallet.

The referral bounty pays 500 Koins for each partner you refer — credited when the referred partner publishes their first listing. The double condition (account + listing) is enforced server-side; a signup alone does not pay out. Track everything in Referral History on the Earn page.

Eligible early partners get 100% of their one-time fee back as Kash — bank-redeemable from day 366, counted from partner-profile creation. Eligibility is capped per region × category: 100 software / 100 AI-tool / 100 service partners in India, and 100 AI-tool / 100 service / 200 software for the rest of the world. There is no other refund window.

Kash redemption is processed manually under the platform’s payout rules — no KYC forms; requests are verified against your real payment track record. The platform-wide cash-out switch is LIVE (since 2026-07-20), so eligible redemptions are paid on manual review — India partners to bank/UPI via Razorpay/PayU payout rails, all other regions via PayPal.

One pause worth knowing about: if a payment anywhere on your account is under review with a payment provider — for example a bank has queried a card charge — Kash withdrawals are paused until that review resolves. Amounts already reserved for a withdrawal are not spendable while that request is unresolved. If you believe the review is a mistake, contact Support with the request reference.

Reconciliation required means the withdrawal outcome needs verification. Existing funds and records are preserved; it does not mean a new payout or an automatic refund. Do not submit a duplicate request. Keep any original bank or PayPal reference and ask Support for review. Support cannot mark a request paid, return its reserved funds, or change the financial outcome. Private internal review notes are not shown in your activity.

If the partner billing wallet shows Verify saved request, use that control before starting another withdrawal. It checks the same request reference, or permanently closes that reference if nothing was admitted. It does not cancel an admitted withdrawal. Do not clear site recovery data to work around an uncertain response. If verification is unavailable, give Support the reference, not passwords, tokens or full bank details.

A manually entered transfer reference is not independent bank confirmation. Compare your actual bank or PayPal history with the original approved payout amount and reference. A repeated status update is never a second transfer.

The billing wallet lists your own requests for the selected account. Partner HQ Earnings and Profile provide your own history across accounts, including legacy records with missing details. Use Load more in request-reference order and Refresh history to check new or changed records. Read errors do not mean there are no requests. Kash is shown in USD-equivalent units separately from the originally pinned payout currency; history is not a certified balance or proof of bank payment.