Glossary

The affiliate terms that decide how money moves.

Definitions written from the perspective of the system that has to honour them. Where a term carries a real design decision, the entry says what that decision is.

Attribution window

The period after a referral during which a resulting purchase is still credited to the affiliate. A server-side claim tied to a stable customer identity outlives a browser cookie, so the window becomes a policy decision rather than a storage limitation.

How AffiliateRails handles this

Chargeback

A payment reversed by the cardholder’s bank rather than by the merchant. It arrives after the money was considered settled, so it produces the same commission reversal as a refund but usually later and with a fee attached.

Clawback

Recovering commission that has already been paid, after the underlying sale is refunded or charged back. If future earnings do not cover it, the balance carries as a negative adjustment rather than disappearing.

How AffiliateRails handles this

Commission basis

The monetary amount a commission was calculated from — gross, net of tax, or net of processing fees. Retaining the basis alongside the rate is what makes a historical commission explainable after the rule changes.

Conversion

A confirmed commercial outcome recorded against a referred customer. Recording it from trusted server code rather than the browser is what allows a renewal months later to still be attributed.

How AffiliateRails handles this

EPC (earnings per click)

Commission earned divided by clicks delivered, used by affiliates to compare programmes. It is only comparable between programmes that reverse refunded commissions the same way.

Idempotency key

A caller-supplied identifier that binds retries of the same request to one result. It is the difference between a timed-out conversion being retried safely and a duplicate commission being created.

How AffiliateRails handles this

Monthly attributed revenue (MAR)

The revenue an affiliate platform tracked as referred in a month. Many platforms price against it, which means a programme that succeeds automatically costs more.

How AffiliateRails handles this

Payout threshold

The minimum balance before an affiliate is paid. It exists because transfer fees make small payouts uneconomic, and it interacts with hold periods to determine when an affiliate actually receives money.

How AffiliateRails handles this

Postback (server-to-server)

A server-side notification of a conversion, sent instead of relying on a browser pixel. It survives ad blockers and privacy defaults, and it can carry a stable transaction identity that a pixel cannot.

Recurring commission

Commission paid on renewals rather than only the first payment. It requires the platform to keep receiving billing events for the life of the subscription, not just at checkout.

Reversal

The entry that undoes a commission when its underlying sale is refunded. Recording it as its own event, rather than deleting the original, is what keeps the ledger balanced and the history auditable.

How AffiliateRails handles this

Rule version

The specific commission rule in force when a commission was created. Retaining it lets a programme change its rates without silently rewriting what affiliates were already owed.

How AffiliateRails handles this

Sandbox environment

A separate application environment where test credentials, codes, conversions and commissions live. If test activity can reach live payouts, it is a test mode rather than a sandbox.

How AffiliateRails handles this

Self-referral

An affiliate using their own referral code to buy at a discount or earn commission on their own purchase. Most programmes prohibit it, which means the platform has to be able to detect that the buyer and the affiliate are the same identity.

Sub-affiliate

An affiliate recruited by another affiliate, where the recruiter earns a share of their earnings. It multiplies the reversal cases, because a clawback has to cascade through every level it was paid across.

Put the terms to work

See how each of these behaves in a running programme.

Request sandbox access