Rewards that post themselves. Exactly once.
Double-sided rewards write straight back to Stripe, Paddle, Lemon Squeezy, or Polar — coupons and account credits apply automatically the moment a conversion lands, even when a webhook fires twice.
"give $20, get $20" — and the credit posts itself.
- Free plan, no card required
- Works with Stripe, Paddle, Lemon Squeezy, Polar
- Rewards apply exactly once, even on retries
Somebody has to remember to pay it.
A double-sided referral or an affiliate commission is only as good as the reward that follows it. Most tools stop at telling you who's owed something — a person still has to open the biller, create the coupon or credit by hand, and hope the webhook that triggered it didn't already fire once today. Here's what changes when the reward posts itself:
Manual reward issuance
A report tells you who earned a reward. Someone on your team still opens Stripe or Paddle, creates the coupon or credit by hand, and hopes the webhook that triggered it didn't already fire once today.
Qanary
The reward posts straight to your biller the moment the ledger confirms it — idempotent by design, so a retried or duplicate webhook can't apply it twice.
From conversion to credit. Three steps.
1. Conversion lands in the ledger — the webhook from checkout or renewal lands the moment it arrives, deduplicated automatically.
2. Reward rule runs — your versioned rule computes what's owed, a commission or a "give $20, get $20" credit for both sides.
3. Reward posts to your biller — the coupon or account credit writes back automatically, no spreadsheet, no manual entry.
Rewards, handled end to end.
Double-sided rewards
"Give $20, get $20" — reward the customer who referred and the friend who joined, on both sides of the invite. Account credits post automatically to your biller, no manual matching.
Idempotent by design
Duplicate, shuffled, or out-of-order webhooks converge to the same ledger entry — a reward applies exactly once, no matter how many times the event fires.
Clawbacks reversed automatically
A refund reverses the reward at the original accrual FX rate, prorated to your provider's refund policy — nobody keeps a coupon or credit on money that came back.
Four moments the reward has to be exact.
"Give $20, get $20" referrals
Both sides get credited the moment the friend's payment clears — nobody has to remember who referred whom or manually issue two credits.
Free trial converts to paid
The reward only posts once the trial actually turns into a paying subscription — not the moment someone merely signs up.
A flaky webhook connection
Your biller retries a delivery after a timeout — the reward still applies exactly once, no double-paid coupon to notice and refund.
A sale gets refunded
The reward reverses automatically at the original accrual rate, prorated to your provider's refund policy — no spreadsheet tracking who owes what back.
See it side by side.
| Capability | Manual reward issuance | Qanary |
|---|---|---|
| Rewards post without a person in the loop | No | Yes, automatically |
| Double-sided credits ("give $20, get $20") | Varies by vendor | Yes, both sides post automatically |
| Safe against duplicate webhook delivery | Depends on your own dedup code | Yes, idempotent by design |
| Clawbacks reverse at the original accrual FX rate | No | Yes |
| Ledger replays to identical numbers on audit | Rarely | Yes, tested every commit |
| Works the same across Stripe, Paddle, Lemon Squeezy, Polar | Depends on the integration | Yes |
| Price tied to your affiliate-driven revenue | Often, past a tier | Never — flat, event-based |
"Manual reward issuance" describes any process where a person creates the coupon or credit by hand after seeing a report — the common baseline unless the reward is wired directly into the biller's API. See the full pricing for how Qanary's usage-based plans compare.
Because a person never has to remember to pay it.
- No missed rewards. Idempotent webhooks mean a reward posts exactly once whether the event fires once or five times — nothing depends on someone noticing a report.
- Clawbacks handled automatically. Refunds reverse at the original accrual FX rate, prorated to your provider's refund policy — nobody keeps a reward on money you gave back.
- Append-only ledger. Reward rules are versioned, never edited — replaying the event log yields the same numbers every time, tested on every commit.
- Works on both sides. "Give $20, get $20" rewards post to the referrer and the referred automatically, on the same pipeline as affiliate commissions.
- Isolated at the database. Row-level security, fail-closed, enforced by Postgres itself on every tenant table — not by an
ifstatement in app code.
A reward is only useful if it's trustworthy — Qanary also runs fraud checks before a commission is owed, not after it's paid. See every feature on the features hub, or the full mechanics in the REST API reference.
Fair questions.
What happens if a webhook fires twice for the same conversion?
Nothing extra happens. Qanary's ledger is idempotent, so duplicate, shuffled, or out-of-order webhooks converge to the same entry, and the reward applies exactly once — no double-paid coupon or credit.
How does a clawback affect a reward that already posted?
If the underlying sale is refunded, the reward reverses at the original accrual FX rate, prorated to your provider's refund policy — automatically, without you tracking it in a spreadsheet.
Do double-sided referral credits need separate setup from affiliate commissions?
No. Affiliate and double-sided referral programs run on the same attribution pipeline, so "give $20, get $20" credits post through the same ledger as affiliate commissions — one system, not two subscriptions.
Which billers can rewards post to?
Stripe, Paddle, Lemon Squeezy, and Polar — coupons and account credits write back automatically on all four, with webhooks provisioned for you.
Everything you need to wire it up.
Stop tracking rewards in a spreadsheet.
Set up double-sided rewards tonight — free, on every plan, no card required.
Join the waitlist