How to pay affiliates internationally (RazorpayX + PayPal)

Paying one affiliate is easy. Paying two hundred — across a dozen countries, in different currencies, with tax paperwork and minimum thresholds — is where most programs grind to a halt. The good news: the operational problem is well understood, and two rails cover the vast majority of cases. Here’s how to set it up so payouts run without a monthly fire drill.

Choosing your payout rails

Most programs don’t need a dozen payment providers — they need two complementary ones that cover domestic speed and international reach.

• RazorpayX — ideal for paying Indian partners: fast bank transfers (IMPS/NEFT/UPI), low per-payout cost, and programmatic payout APIs.
• PayPal — the pragmatic default for international partners: broad country coverage, partners already trust it, and recipients only need an email address.

Handling currency and FX

Currency is where international payouts get messy. Pick a clear policy and apply it consistently so partners know exactly what they’ll receive:

1. Decide your base accounting currency (the one commissions accrue in).
2. Choose whether you pay partners in their local currency or your base currency.
3. If you convert, show the FX rate and any conversion fee transparently on the payout statement.
4. Reconcile the converted amount against the gateway’s settlement report so your books match what left your account.

Transparency here is a trust feature. Partners who can see exactly how their commission converted to a payout raise fewer support tickets and stay in your program longer.

Tax forms and compliance

Collect tax information before the first payout, not after. Depending on your jurisdiction and the partner’s, you may need the equivalent of a W-9 (domestic) or W-8 (foreign) and may have reporting obligations at year end. Gating the first payout on a completed tax form keeps you compliant and avoids awkward retroactive collection.

• Request tax details as part of partner onboarding, before any earnings are payable.
• Store forms securely and link them to the partner record.
• Block payout approval until the required form is on file.

Thresholds, cadence, and approvals

Two simple policies keep payout operations sane:

• Minimum payout threshold — e.g. don’t pay out balances under $50. This caps per-transaction fees and reduces tiny, noisy transfers.
• Fixed cadence — e.g. monthly on the 1st for all approved commissions past the clearing window. Predictability reduces support load and reconciliation effort.

Layer an approval step before money moves: commissions clear an attribution/refund window, you (or a reviewer) approve the batch, and only then does the payout fire. This is your last line of defence against paying out on fraudulent or refunded conversions.

Automating the flow

The end state is hands-off: a conversion is attributed, a commission is generated from the campaign rule, it clears the refund window, it’s approved (manually or by rule), and a payout is dispatched to the right rail in the right currency — with the tax form already on file and a statement the partner can see. This is exactly the pipeline Afflio automates: RazorpayX and PayPal payouts, tax-form collection, FX-aware statements, thresholds, and approvals, all driven from the same commission data so finance isn’t exporting spreadsheets and wiring money by hand.

The goal isn’t to make payouts possible — it’s to make them boring. A payout system that runs itself every month is one fewer reason a great partner leaves your program.