Affiliate infrastructure for product teams

Run referrals like a system, not a spreadsheet.

AffiliateRails brings links, attribution, commission rules, reversals and payout operations into one explicit API-first layer.

IdempotentRetry-safe intake
TraceableDecision evidence
SeparatedSandbox and live
Live event rail healthy
01
Referral claimedExact code · sandbox
ACCEPTED
02
Conversion recordedorder:ord_01839
CANONICAL
03
Commission accruedRule v4 · net basis
PENDING
Designed forSaaS affiliate programmesReferral marketplacesAPI-first product teamsFinance-aware operators

One operating layer

Built around the hard parts after the click.

Marketing tools stop at a dashboard. AffiliateRails is designed around identity, retries, rule versions, refunds and the evidence finance teams need when an outcome changes.

01

Affiliate programmes with boundaries

Keep operator, affiliate, public-client and money-moving authority separate while the programme shares one durable identity model.

Explore capability
02

Attribution you can replay

Resolve codes, users and paid outcomes through stable identities instead of stitching together browser state after the fact.

Explore capability
03

Commission rules with history

Version future decisions and retain the exact rule evidence behind every existing commission.

Explore capability
04

Payout operations with fences

Draft, inspect and approve immutable commission sets before an external settlement is allowed to move.

Explore capability
05

A self-scoped affiliate portal

Give affiliates the assets and performance context they need without exposing tenant-wide configuration or approval authority.

Explore capability
06

Reporting tied to source events

Move from programme metrics to retained conversion and commission identities without putting analytics on the transaction path.

Explore capability
07

Signed, observable integrations

Connect provider lifecycles and tenant systems through explicit event identity, raw-body verification and durable delivery state.

Explore capability

From API call to audit trail

Make a paid outcome once. Keep its history for good.

Stable external identifiers and explicit reversal semantics turn retries and refunds into known state transitions, not repair work.

01

Record from trusted server code

Secret keys never need to enter a browser or mobile bundle.

02

Retry the exact semantic request

Idempotency returns the canonical committed outcome.

03

Reverse with journal evidence

Refunds preserve the original decision and post their inverse.

record-conversion.tsNode.js
const conversion = await referralRails.conversions.record({
  appUserId: customer.id,
  externalProductId: 'pro-monthly',
  grossMinor: 4900,
  currency: 'USD',
  externalTransactionId: order.id,
}, {
  idempotencyKey: 'order:' + order.id,
});

Built around your revenue model

One operating discipline, shaped for different products.

Start with the customer and provider identities your product already trusts. AffiliateRails keeps the programme mechanics consistent around them.

Start with the operating model

Give referrals the same engineering discipline as payments.

Talk to the team