Introducing Referalli
An attribution-first affiliate, partner and referral platform for SaaS, built around one append-only ledger.
Referalli is an affiliate, partner and referral platform for SaaS companies. It tracks who sent a customer, works out what that partner is owed from your real billing events, pays them through the payout provider you connect, and keeps every step on an append-only ledger you can audit and replay. This post explains what is in the platform today and how the pieces fit together.
Attribution you can inspect
Tracking starts with links, a browser snippet and a server-side API. Clicks, visits and identity associations are written as append-only facts, and referrals are derived from them rather than edited in place. A program can use one of four attribution models — last click, first click, position-based or time-decay — and can credit partners through coupon codes and hashed email identifiers as well as link clicks, with priority rules deciding which channel wins. Because attribution is a function over the recorded events, it can be replayed deterministically, and every referral carries a "why / why not" explanation that both merchants and partners can see (redacted on the partner side).
Beyond web links, Referalli also handles mobile-app installs and deferred deep links, Shopify discount codes used at purchase, on-chain conversions reported by indexers, and signups from auth platforms such as Clerk, Supabase and WorkOS.
Commissions from real billing events
Billing connectors for Stripe, Paddle, Lemon Squeezy, Polar, Chargebee, Shopify and a generic signed webhook normalize provider events into one canonical schema. A versioned rule engine turns those events into commission entries: percentage or fixed rates, recurring caps, tiers, per-product and per-partner overrides, bounties, multi-level sub-affiliates and split credit across several touches. Changing a rule never rewrites history. Refunds and chargebacks become new reversal entries rather than edits, and processing is idempotent per provider event, so a retried webhook is never paid twice. Money is stored as integer minor units throughout.
Payouts through your own providers
Payout runs group approved balances above a threshold and send them over rails the merchant connects: PayPal, Wise, Stripe Connect, Circle, Payoneer, Tremendous, or a CSV export. Referalli holds no platform payment keys — each merchant brings their own. Settlement outcomes come back through provider webhooks, and the payout ledger reconciles one-to-one with the commission ledger; drift is reported, not silently corrected. Partners submit W-9 or W-8BEN forms, identity verification can gate payouts, and the platform produces 1099-NEC exports and self-billing invoices.
Fraud controls
Every click is scored at ingest. Suspicious traffic is recorded but marked ineligible rather than dropped, so you can see what was filtered and why. Rate limits, self-referral detection with evidence, partner quality scores, ring detection across shared infrastructure and cases with hold, reverse, warn, suspend or ban actions are all built in, with an audit log behind them.
Dashboards for both sides
Merchants get a dashboard covering partners, referrals, commissions, payout runs, reports and a program designer. Partners get one portal account across every program they join, with links, assets, terms, stats and payout self-service. Both are white-labelable with per-organization themes and custom domains, and an embeddable widget lets you put the partner experience inside your own product. Sign-in for merchants and partners goes through Atlas.
Developer platform
Everything the dashboards do goes through the public /v1 REST API, described by OpenAPI at /v1/openapi.json, with a GraphQL read layer at /v1/graphql. Outbound webhooks are HMAC-signed, retried with backoff and replayable from delivery logs. There is a sandbox mode with a test clock and fake billing generator, CSV importers for Rewardful, FirstPromoter, Tolt and PartnerStack, an MCP server, and SDKs for TypeScript, Python, Ruby, Go, PHP, Swift and Kotlin.
Finding and working with partners
A marketplace lists programs with platform-computed performance and payout-reliability figures, and lets partners apply in one step. Discovery tools help merchants find prospective partners, with outreach that requires approval and respects a platform-wide do-not-contact list. Other tools include contract automation, double-sided referee rewards, incrementality measurement using holdout groups, and a portable reputation profile that partners own.
Getting started
The documentation covers concepts and the API reference, and the guides walk through setup step by step.
0 comments