Key takeaways
- The approval-to-payout pipeline runs from attributed conversion to commission to clearing window to approval to dispatched payout.
- Automating it removes the manual export-and-wire step that breaks down as a program grows.
- Keep an approval gate — manual or rule-based — as the last check against paying on fraudulent or refunded conversions.
- Clearing windows and thresholds run automatically so only earned, economical commissions reach a payout.
- Dispatch routes each payout to the right rail and currency, with tax forms already on file.
The end state every program wants is hands-off payouts: a conversion happens, and weeks later the partner is paid the right amount on the right rail without anyone touching a spreadsheet. Getting there means automating the chain from attribution to dispatch while keeping one deliberate human-or-rule checkpoint where it matters. This post walks the pipeline and shows where automation and judgement each belong.
What is the approval-to-payout pipeline?
The approval-to-payout pipeline is the sequence that turns an attributed conversion into a paid affiliate: a commission is generated, it clears a refund window, it's approved, and it's dispatched to the partner's payout rail. Automating that sequence is what lets a program pay hundreds of partners without finance manually wiring money to each one.
What are the stages, end to end?
Each stage feeds the next, and most of them can run without human intervention:
- Attribution: a conversion is attributed to a partner.
- Commission generation: a commission is created from the campaign rule (flat, percentage, or recurring).
- Clearing window: the commission waits out the refund/attribution window so reversible sales settle.
- Threshold check: the partner's balance is tested against the minimum payout threshold.
- Approval: the eligible batch is approved — manually or by a rule.
- Dispatch: the payout is sent to the right rail (RazorpayX bank/UPI or PayPal) in the right currency.
Why keep an approval step at all?
Keep an approval step because it's your last line of defence against paying out on fraudulent or refunded conversions. Even with a clearing window, an approval gate lets you (or a rule) catch suspicious patterns before money leaves your account — and money, once sent, is far harder to recover than a commission held back.
- Manual approval: a reviewer signs off each batch — maximum control, more effort.
- Rule-based approval: low-risk commissions auto-approve while edge cases route to a human — automation with a safety net.
- Either way, the gate sits after the clearing window and before dispatch.
Automate the rote, gate the risk
The right balance is to automate everything mechanical — commission generation, clearing windows, threshold checks, dispatch — while keeping a deliberate approval checkpoint over the risky moment: releasing money. You want the pipeline to run itself and still pause exactly where a mistake would be expensive.
How does dispatch pick the right rail and currency?
Dispatch routes each approved payout based on the partner's recorded method and currency policy — RazorpayX bank transfer or UPI for Indian partners, PayPal for international ones — using the payout details collected at onboarding. Because the tax form is already on file and the FX policy is already set, dispatch is the simple last step rather than a place where missing information stalls the run.
Automation doesn't mean removing humans — it means removing the manual export, the copy-pasted account numbers, and the monthly wire-by-hand ritual, while keeping the one human judgement that actually protects you.
How does Afflio automate this?
Afflio drives the whole pipeline from one source of truth: commissions accrue from your campaign rules, clear their window, get tested against the threshold, pass through approval, and dispatch to the partner's rail in the right currency — with the tax form already collected and an FX-aware statement produced for the partner. Because attribution, commissions, approvals, and payouts share the same data, finance approves a batch instead of rebuilding it from exports, and the partner sees a clean record of how their conversion became a payout.
Can affiliate payouts be fully automated?
The pipeline can run end to end automatically — commission generation, clearing window, threshold check, and dispatch — but most programs keep an approval step (manual or rule-based) as a deliberate checkpoint before money leaves the account, to guard against fraudulent or refunded conversions.
Where does the approval step sit in the pipeline?
After the clearing window and threshold check, and before dispatch. By then refundable sales have settled and only eligible balances remain, so approval is the final gate on releasing money rather than a review of every raw commission.
How does the system know which rail to pay a partner on?
From the payout method and currency policy recorded on the partner, captured at onboarding — RazorpayX bank/UPI for Indian partners or PayPal for international ones. With the tax form on file and FX policy set, dispatch is the simple last step of the automated flow.