You pay affiliates. We never touch the money.
Commissions accrue in your ledger, you export a payout batch — CSV or API — and pay affiliates through whatever provider you already use. Mark it complete in Qanary and any clawback debt nets against the next batch automatically.
we never touch your money. not once.
- Free plan, no card required
- Pay through Wise, PayPal, ACH, wire — anything you already use
- Append-only ledger, tested every commit
Some platforms want custody of your money.
Fund a wallet up front, wait on their withdrawal schedule, pay a rail fee stacked on top of the subscription you already pay — a lot of affiliate platforms turn payouts into a second vendor relationship. Here's the difference not holding your money makes:
Custodial payout tools
Your funds sit in their wallet until a withdrawal window opens, often with a rail fee stacked on top of your subscription — and you're stuck with whatever payout methods they've integrated.
Qanary
Commissions accrue in your ledger; you export the batch and pay affiliates through the provider you already use for everything else. Qanary never sees your money.
From ledger to bank transfer. Three steps.
1. Commission accrues, then clears its hold — an approved conversion posts to the ledger, then carries a hold date if the campaign sets one.
2. You export a payout batch — once a balance clears its threshold, pull the batch as a CSV or through the REST API.
3. You pay, Qanary records it — pay through your own provider, mark the batch complete, and any clawback debt nets against the next one.
The accounting, without the custody.
Payout batches, not one-offs
Approved commissions group into a payout batch per campaign, currency, and rail —
export a CSV or fetch it with GET /payouts and GET /payouts/{id},
line items included.
Per-campaign thresholds & hold periods
Set a minimum payout amount and a holding period per campaign, so a two-dollar commission doesn't trigger a wire transfer and a fresh conversion has time to clear review.
Clawbacks net automatically
A refund or clawback doesn't need a manual adjustment — the debt nets against the affiliate's next payout batch the moment it posts to the ledger.
Four moments payouts have to hold up.
Monthly payout run
Export the batch of everyone who cleared their threshold and wire the whole roster in one sitting instead of processing affiliates one by one.
A two-dollar commission
The campaign's minimum payout threshold holds it back until the balance is actually worth wiring — no tiny transfer eating itself in fees.
A refund lands mid-cycle
The clawback nets against the affiliate's next payout batch the moment it posts — nobody has to chase money that already went out.
Reconciling with your finance stack
GET /payouts and GET /payouts/{id} return every batch with
line items — no asking Qanary for a report before month-end close.
See it side by side.
| Capability | Custodial payout tools | Qanary |
|---|---|---|
| Ever holds your funds in escrow | Often, yes | Never |
| Payment rail you're allowed to use | Limited to their supported rails | Any — Wise, PayPal, ACH, wire, whatever you use |
| Extra fee per payout, on top of the subscription | Often | Never — flat, event-based |
| Minimum payout threshold per campaign | Varies by vendor | Yes, set per campaign |
| Clawback debt nets against the next batch automatically | Manual, usually | Yes, automatically |
| Payout batches queryable via API | Varies by vendor | Yes, with line items |
| Tax forms gate a payout automatically | Not consistently | Yes, W-9 / W-8BEN |
"Custodial payout tools" describes any platform that holds affiliate funds itself and pays out on its own schedule and rails — the common model unless a platform explicitly routes payment through your own provider. See the full pricing for how Qanary's usage-based plans compare.
Your money never leaves your hands.
- Never in custody. Qanary tracks what's owed; it never becomes the vendor that pays it. Your provider, your bank, your money the whole way through.
- Any rail you already use. Wire, PayPal, Wise, ACH, a check if that's still how you do things — nothing new to integrate or trust with affiliate banking details.
- Clawbacks net themselves. A refund reverses at the original accrual rate and nets against the next payout batch automatically — no spreadsheet, no manual adjustment.
- Thresholds keep payouts sane. A minimum payout amount and a holding period, both set per campaign, so tiny balances and unreviewed conversions don't turn into a transfer.
- Queryable, not a black box. Every payout batch and its line items are available through the REST API, so your finance stack can reconcile without asking Qanary for a report.
Payouts only run on commissions that survived fraud review — see how Qanary catches bad clicks before a commission is owed. See every feature on the features hub, or the full mechanics in the REST API reference.
Fair questions.
Do you hold our money?
No. Rewards accrue in your ledger; you export a payout file, pay through your own provider, and record completion in Qanary. Clawback debt nets against the next batch automatically.
What happens if a clawback arrives after I've already scheduled a payout?
It nets against the next payout batch automatically the moment it posts to the ledger — no manual reconciliation, and no asking an affiliate to send money back directly.
Can I set a minimum payout amount or a holding period?
Yes, per campaign. A minimum payout threshold keeps small balances from triggering a transfer, and a holding period keeps a fresh commission from becoming payable before it's had time to clear review.
Can I pull payout data into my own systems?
GET /payouts lists payout batches and GET /payouts/{id}
returns a batch with every line item, so your finance or BI stack can reconcile
without living inside Qanary's dashboard.
Everything you need to run a batch.
Keep your money exactly where it is.
Set up payout batches tonight — free, on every plan, no card required.
Join the waitlist