--- id: "index" type: "doc" url: "https://affitor.com/docs" kind: "concept" updated: "2026-11-07" --- # What is Affitor? > Affitor is an affiliate growth platform for SaaS: $0/month with a 3.5% fee only after each program's first $10,000 in affiliate revenue. Affitor is an affiliate growth platform for SaaS companies: run partner programs with click, signup, and sale attribution, then manage commissions and payouts through one workflow. These docs cover both sides of a program: - **Advertisers** (brands) are the SaaS companies running an affiliate program. They configure the program, integrate tracking, review commissions, and handle payouts. Start with the [advertiser quickstart](/docs/brand/quickstart). - **Partners** are the affiliates, creators, agencies, and other promoters sending traffic. They join programs from the **Marketplace**, share their referral links, and get paid. Start at [Become a partner](/docs/partners). Look up any term in the [glossary](/docs/support/glossary). ## Overview Run an affiliate program with partner applications, links, tracking, and commission operations. Track clicks, signups, and sales through Server-side tracking or Stripe integration. Commissions move through review, hold, and payout operations inside Affitor. Hand the integration to an AI coding agent with the `affitor` CLI (`npx affitor onboard`), the local MCP server it sets up, or the `skill.md` runbook. A self-verify loop fires a synthetic click, lead, and sale and reports `integration_verified: true` once every check passes. ## How it fits into your stack Affitor runs alongside your existing product stack. Partner shares link → visitor clicks → **Affitor tracks the click** Customer signs up → **lead linked to partner** Customer pays → **sale attributed** via `Server-side tracking` or `Stripe integration` **Commission + payout workflow** handled in Affitor You keep your own site and checkout. In the invoice billing model, you continue collecting payment through your own Stripe or payment setup. ## Performance-based pricing - No monthly subscription - No setup fee - 3.5% platform fee on partner-generated revenue - $10K fee-free threshold on affiliate-driven revenue, per program How the fee and the threshold work: [Pricing](/docs/getting-started/pricing-performance-model). ## Who this is best for Affitor fits SaaS teams that want: - A partner program without subscription-based affiliate software pricing - Clear attribution from click to revenue - A Stripe Checkout or backend sale-tracking path they can implement cleanly - An integration they can hand to an AI coding agent and get back proof it works - Commission and payout operations in one workflow ## Next steps Start the advertiser setup flow. Review the lifecycle from click to payout operations. Join a program from the Marketplace, share your referral link, and get paid. Ready to start? [Create your program at affitor.com](https://affitor.com) and explore the dashboard before you commit to anything: $0/month, no setup fee, and each program's first $10,000 in affiliate-driven revenue is fee-free. --- id: "api-reference/attribution" type: "doc" url: "https://affitor.com/docs/api-reference/attribution" kind: "concept" updated: "2026-11-08" --- # Attribution Mechanics > How Affitor assigns credit to partners: the cookie, the click ID, the attribution window, and what happens on re-click. > **Beta** — The Affitor SDKs and CLI are in active development. The documented happy-path works; edge cases may change. Report issues on GitHub. When a visitor clicks an affiliate link, Affitor creates a customer record for that click and the SDK writes a first-party cookie with its `click_id`. By default, the partner whose click created the customer keeps that customer: a later click from another partner in the same browser is logged, but it does not take the customer over. Leads and sales for that customer resolve to that first partner. --- ## Attribution model | Setting | Default | Range | Description | |---------|---------|-------|-------------| | Attribution window | `60` days | 1 – 365 | Maximum age of the click at the customer's signup. Also used as the cookie lifetime | Each program has **one** attribution window, set in your program settings. The click endpoint returns it as `cookie_window_days`, and the SDK uses it as the lifetime of the cookie it writes, so no SDK update is needed when you change the value in the dashboard. Program settings have no option for last-click or multi-touch (linear) credit. Credit goes to the partner whose click created the customer, as described above. --- ## The `affitor_click_id` cookie When a visitor lands on a URL containing `?aff=` or `?via=` (the program's **Partner link parameter**; `?aff=` wins if both are present), the SDK calls `POST /api/v1/track/click` and stores two first-party cookies: | Cookie | Purpose | |--------|---------| | `affitor_click_id` | The primary attribution token. Passed to lead and sale calls. | | `affitor_aff_url` | The full landing URL used to detect partner changes on re-click. | A legacy `customer_code` cookie is written alongside `affitor_click_id` for backwards compatibility with older integrations. On read, if only `customer_code` exists, the SDK migrates its value into `affitor_click_id` automatically. The cookie lifetime is the program's attribution window (default **60 days**), taken from the `cookie_window_days` value in the click response. --- ## Cross-subdomain cookie sharing The SDK auto-detects the broadest writable domain so attribution follows a visitor across subdomains (e.g. `app.example.com` and `www.example.com` share the same cookie). **Detection algorithm:** 1. Split `window.location.hostname` into parts. 2. Starting from the registrable domain (e.g. `.example.com`), attempt to write a probe cookie with each candidate domain. 3. The first domain that accepts the write becomes the cookie domain for the session and is cached in `cookieDomain`. 4. `localhost` and bare IP addresses are excluded — no domain is set, so the cookie is host-only. You can skip auto-detection by setting the cookie domain on the tracker script tag: ```html ``` The `@affitor/sdk` types do not include a cookie domain option (`loadAffitor()` takes `programId` plus `debug`, `env` and `scriptUrl`; `init()` takes only `programId` and `debug`), so use the script attribute when you need one. --- ## Re-click from another partner If a visitor already has an `affitor_click_id` cookie and clicks a **different** partner's link, the SDK sends the new click together with the existing `click_id` (as `existing_click_id`). The server finds the customer that already owns that `click_id` and keeps it: the new click is still recorded and counted for the new partner (a click event, plus that link's and partner's click counts), but the customer, its `click_id` and its partner do not change, so later leads and sales stay with the original partner. | Scenario | Outcome | |----------|---------| | No existing cookie, `?aff=` or `?via=` present | New click tracked, new customer created, new `affitor_click_id` written | | Same partner link clicked again | Existing cookie reused — no new click event | | Different partner link clicked | New click counted for the new partner; the customer and its `click_id` stay with the original partner | | No partner parameter in URL, cookie present | Existing attribution restored from cookie silently | | No partner parameter in URL, no cookie | No `click_id`. A lead call without a `click_id` or a known `customer_key` returns `400` and nothing is recorded | --- ## How the attribution window is checked There is one window per program (default **60 days**). It is used in two places: - **Cookie lifetime** — the `affitor_click_id` cookie expires after that many days. - **Click → signup check** — when the customer's first payment is attributed, the click must be at most that many days older than the customer's signup. If no signup was recorded, the click's age is measured at that first payment instead. The check runs once, at the customer's first payment. A customer who signed up inside the window can buy later and still be attributed, and once the first payment is attributed, later renewals and repeat purchases are not checked against the window again. ``` Click ──── at most N days ────► Signup ─────────────► First payment (window checked here) │ └──► Renewals (not re-checked) ``` --- ## Recurring revenue attribution For subscription products, every recurring charge can generate a commission within the commission duration below. Once the first payment is attributed, the attribution window is not checked again for renewals. | Commission type | `default_duration_months` | Behavior | |-----------------|--------------------------|---------| | `cps_recurring` | e.g. `12` | Commission paid on every payment until N months have passed since the customer's first click (not the first payment); later payments are recorded with a $0 commission | | `cps_lifetime` | `null` | Commission paid on every renewal indefinitely | | `cps_one_time` | `0` | Commission paid once on the first payment only | With Stripe connected, renewals need no call from you: Affitor records each renewal from the invoice events (`invoice.payment_succeeded`, `invoice.paid`) and matches it to the partner through the click in the subscription's metadata, or else by the buyer's email when Affitor has recorded it (from a lead your server sent or an earlier attributed payment), or by the Stripe customer ID saved when the first payment was attributed. If you report sales yourself with `/api/v1/track/sale`, a renewal is attributed like any sale, by `customer_key` and then `click_id`; `is_recurring: true` and `subscription_id` mark it as a subscription charge. --- ## Program-level attribution fields These program fields control attribution and commissions. The attribution window is set as one number in your program settings: | Field | Type | Default | Description | |-------|------|---------|-------------| | `attribution_window_days` | `integer` | `60` | Maximum click age at signup, and the cookie lifetime (1–365 days) | | `default_commission_type` | `enum` | — | `cpc`, `cpl`, `cps_one_time`, `cps_recurring`, `cps_lifetime` | | `default_duration_months` | `integer` | — | Recurring commission duration; `null` = lifetime, `0` = one-time | | `default_hold_period_days` | `integer` | `15` | Days a commission stays in hold before becoming payable (max 31) | --- ## Related pages Endpoint that creates the click record and returns the click ID. Record a sale and trigger commission creation against the attributed click. Check whether tracking is wired up correctly for your program. --- id: "api-reference/connect-ai-tool" type: "doc" url: "https://affitor.com/docs/api-reference/connect-ai-tool" kind: "guide" updated: "2026-11-10" --- # Connect your AI tool > Add the Affitor MCP server to Claude, Codex, ChatGPT, Cursor, VS Code, Grok, Muse Code or another MCP client, then sign in with Affitor. No API key needed. Add the Affitor MCP server to your AI tool, then sign in with your Affitor account. No API key needed. You will add the server, sign in on affitor.com, choose your programs and click **Allow**. ## Before you start - An Affitor account with a program, or a program you joined as a partner. - Access is read-only today: reading is always on, and money actions always happen in Affitor. ## Server URL ```text https://mcp.affitor.com/mcp ``` Every tool below uses this URL. For transport, sign-in and the full tool list, see the [MCP server reference](/docs/api-reference/mcp). ## Claude Claude on the web and Claude Desktop. 1. Add the server in one click: [Add to Claude](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Affitor&connectorUrl=https%3A%2F%2Fmcp.affitor.com%2Fmcp). Or add it by hand: 2. In Claude, open **Customize** › **Connectors**. 3. Click **+ Add**, then **Add custom connector**. Name it Affitor, paste the URL and click **Continue**. 4. Keep the detected sign-in settings. If Claude asks, pick **Register automatically** under **OAuth client**. 5. Click **Add** and sign in to Affitor. 6. As a brand, pick your programs; then click **Allow**. On Team and Enterprise plans, an owner adds the connector in **Organization settings** › **Connectors**, and members click **Connect**. **Check it works:** in a new chat, ask your AI tool "List my Affitor programs". It answers with your programs. ## Codex 1. Run this in your terminal: ```bash codex mcp add affitor --url https://mcp.affitor.com/mcp ``` 2. Sign in: ```bash codex mcp login affitor ``` **Check it works:** run `codex mcp list`: affitor is listed. Then ask your AI tool "List my Affitor programs". It answers with your programs. ## Other MCP clients Each section below matches a tab in the dashboard's **Connect an AI tool**, or a block under its **Other** tab. **Any other MCP client** also has steps for apps the dashboard does not list. ### ChatGPT 1. Go to [chatgpt.com/plugins](https://chatgpt.com/plugins), click the plus button, then **Add custom MCP server**. 2. Enter a name, and under **Connection** paste the URL. 3. Set authentication to OAuth, review the warning and click **I understand and want to continue**. 4. Click **Create as a plugin** and sign in to Affitor. 5. As a brand, pick your programs; then click **Allow**. Your workspace's policy may limit who can add custom MCP servers. **Check it works:** in a new chat, ask your AI tool "List my Affitor programs". It answers with your programs. ### Cursor 1. Add the server in one click: [Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=affitor&config=eyJ1cmwiOiJodHRwczovL21jcC5hZmZpdG9yLmNvbS9tY3AifQ%3D%3D). Or add it by hand: 2. Add this to `~/.cursor/mcp.json`: ```json title="mcp.json" { "mcpServers": { "affitor": { "url": "https://mcp.affitor.com/mcp" } } } ``` 3. In **Cursor Settings** › **MCP**, click **Connect** and sign in. **Check it works:** in **Cursor Settings**, open **MCP**: affitor shows its tools. Then ask your AI tool "List my Affitor programs". It answers with your programs. ### Claude Code 1. Install the Affitor plugin (recommended): ```text /plugin marketplace add Affitor/claude-plugins /plugin install affitor@affitor ``` 2. Open `/mcp`, pick affitor and sign in. Or add the server by hand: 1. Run this in your terminal: ```bash claude mcp add --transport http affitor https://mcp.affitor.com/mcp ``` 2. In Claude Code, type `/mcp`, pick affitor and sign in. Add `--scope user` to use Affitor in every project. **Check it works:** run `claude mcp list`: affitor shows `Connected`. Then ask your AI tool "List my Affitor programs". It answers with your programs. ### VS Code GitHub Copilot in VS Code. 1. Add the server in one click: [Add to VS Code](https://vscode.dev/redirect/mcp/install?name=affitor&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.affitor.com%2Fmcp%22%7D). Or add it by hand: 2. Add this to `.vscode/mcp.json` in your workspace, or to the `mcp.json` of your user profile (or run **MCP: Add Server** from the Command Palette): ```json title="mcp.json" { "servers": { "affitor": { "type": "http", "url": "https://mcp.affitor.com/mcp" } } } ``` 3. Start the server and sign in when VS Code asks. **Check it works:** in Copilot Chat in Agent mode, ask your AI tool "List my Affitor programs". It answers with your programs. ### Grok 1. Go to [grok.com/connectors](https://grok.com/connectors), click **New Connector**, then **Custom**. 2. Paste the URL and sign in to Affitor. 3. Pick your programs, or **All current and future programs**, then click **Allow**. **Check it works:** in a new chat, ask your AI tool "List my Affitor programs". It answers with your programs. ### Muse Code 1. Add this to `~/.config/muse/settings.json` (create the file if it does not exist). If it exists, add only the `affitor` entry under `mcpServers` and keep everything else. Keep one `mcpServers` section. Having both `mcpServers` and `mcp_servers` disables MCP. ```json title="settings.json" { "schema_version": 1, "mcpServers": { "affitor": { "type": "streamable-http", "url": "https://mcp.affitor.com/mcp", "enabled": true, "required": false } } } ``` 2. Sign in from your terminal: ```bash muse mcp login affitor ``` 3. Pick your programs, or **All current and future programs**, then click **Allow**. **Check it works:** in a Muse Code session, run `/mcp`: affitor shows its tools. Then ask your AI tool "List my Affitor programs". It answers with your programs. ### Any other MCP client 1. Add this to your client's MCP config: ```json { "mcpServers": { "affitor": { "url": "https://mcp.affitor.com/mcp" } } } ``` 2. Restart the client and sign in when it asks. Apps on your own computer connect through `http://127.0.0.1` or `http://localhost`. A web app connects only if Affitor accepts its return address; the [MCP server reference](/docs/api-reference/mcp) lists them. **Check it works:** ask your AI tool "List my Affitor programs". It answers with your programs. Some clients add the server with their own command or screen: #### Gemini CLI ```bash gemini mcp add --transport http affitor https://mcp.affitor.com/mcp # Then, inside Gemini CLI: /mcp auth affitor ``` #### OpenClaw ```bash openclaw mcp add affitor --url https://mcp.affitor.com/mcp --transport streamable-http --auth oauth openclaw mcp login affitor ``` #### Hermes Agent ```bash hermes mcp add affitor --url https://mcp.affitor.com/mcp --auth oauth # To sign in again later: hermes mcp login affitor ``` #### Perplexity 1. Open **Plugins** in the sidebar, or **Customize** › **Connectors** if you don't see Plugins. 2. Select **Add custom** › **Connector** › **Add MCP connector**, then **Remote**. 3. Enter a name, and under **MCP Server URL** paste `https://mcp.affitor.com/mcp`. 4. Under **Authentication** pick **OAuth** and under **Transport** pick **Streamable HTTP**. Affitor supports automatic registration, so no Client ID or Client Secret is needed. 5. Check the acknowledgement box, click **Add**, then click the connector card and sign in to Affitor. In an organization, members can add custom connectors only if an admin allows it. ## What the AI can do When you sign in, you choose the programs the AI can read. Access is read-only today: reading is always on, and money actions always happen in Affitor. To see or remove a connection, brands open **Program settings** › **Developers** › **AI agents**; partners open **Integrations** from the account menu. ## Next: set up tracking For brands: in the dashboard, **Program settings** › **Tracking** › **With AI** shows this prompt with your website, program ID and API base filled in. Paste it into your AI tool. It follows the [agent skill](/docs/skill.md): click tracking, sign-up leads, then sales. . Program ID: API base: https://api.affitor.com API key: read it from the AFFITOR_API_KEY environment variable. Never print it or put it in browser code. Follow https://affitor.com/docs/skill.md in order: click tracking (§4), signup lead (§5), then the sale (§6). For the sale, look at how the site takes payments and use the first mode in §6 that fits. If you can't read or change the code, ask me what you need and tell me exactly what to add, file by file. Then tell me when it's deployed.`} /> The prompt reads your program API key from the `AFFITOR_API_KEY` environment variable where the AI tool runs; never put the key in the prompt. Use a key with **Full access**: a **Tracking only** key cannot run the readiness check the skill ends with. If you do not have the key's value, an owner or admin creates or rotates one in **Program settings** › **Developers** › **API keys**. See the [tracking guide](/docs/brand/tracking/quickstart-integration). ## Related - [MCP server reference](/docs/api-reference/mcp): transport, sign-in, tools and limits - [AI agent setup](/docs/use-cases/ai-agent-setup): what an agent can do with your program --- id: "api-reference/errors" type: "doc" url: "https://affitor.com/docs/api-reference/errors" kind: "reference" updated: "2026-11-07" --- # Errors & Troubleshooting > All API error codes, their causes, and how to fix common integration problems. > **Beta** — The Affitor SDKs and CLI are in active development. The documented happy-path works; edge cases may change. Report issues on GitHub. This page lists the error responses of the click, lead, sale and refund tracking endpoints, the readiness endpoint and the CLI endpoints, and practical fixes for the most common integration issues. --- ## HTTP status codes Start from the status code. It tells you whose problem the request is and whether sending it again can help. | Status | Meaning | What to do | Retry? | |--------|---------|-----------|--------| | `400` | The request is invalid: a required field is missing or malformed, or an identifier resolved to nothing usable | Fix the request using `error.message`, then send it again | Not unchanged | | `401` | No usable credential: the `Authorization` header is missing or malformed, the key or login token matches nothing, or the key was [retired](#api_key_rotation_required) | Send a valid program API key, or run `affitor login` again for the account-session CLI routes | Not until the credential changes | | `403` | The credential is valid but not for this request: a `program_id` that belongs to another program, or an `advertiser_id` that is not yours. The CLI login callback also answers `403` [`ACCOUNT_BLOCKED`](#account_blocked) or [`PROVIDER_EMAIL_NOT_VERIFIED`](#provider_email_not_verified) | Use the key or account that owns the resource | No | | `404` | The thing the request points at does not exist: a sale to refund, or a CLI login session | Check the identifier you sent | Not unchanged | | `409` | A sale was already recorded under this `transaction_id` | Check `error.details.sale_id`: an id means your program's sale exists, so treat it as success; `null` means another program used this `transaction_id` and nothing was recorded for yours | No | | `410` | The endpoint is retired, or (`POST /api/v1/track/click`) the click is refused: `error.code` is `link_disabled` and no click was recorded. A click is refused when the referral link is turned off or when its program is not active (for example a draft or paused program) | For a retired endpoint, use the replacement named in `error.message`. For `link_disabled`, stop sending clicks for that link; clicks are recorded again once the link is on and its program is active | No | | `422` | `POST /api/v1/track/sale` only: the `currency` is not a [supported ISO 4217 code](/docs/api-reference/track-sale#request-fields) (`error.code` `unsupported_currency`). No sale, commission or fee was created | Send a supported code | Not unchanged | | `429` | [Rate limited](#rate-limits-429). The per-minute limit records nothing; the verification-run cap may already have prepared its test fixture (see [Rate limits](#rate-limits-429)) | Wait `Retry-After` seconds, then retry | Yes, after the wait | | `500` | Something failed on our side | Retry with backoff. If it persists, contact support with the [request ID](#request-ids) | Yes, with backoff (see [server errors](#server-errors-500) for the two cases to check first) | --- ## Error response shape `error` is always an object, never a plain string. Interpolating `body.error` straight into a message prints `[object Object]` — read a field off it. There are two envelopes. Which one you get depends on what rejected the request, not only on which endpoint you called — the tracking endpoints can return either. ### The platform envelope Validation, auth, and conflict errors raised by the tracking and CLI endpoints themselves come back like this. Read `error.message`: ```json { "data": null, "error": { "status": 400, "name": "BadRequestError", "message": "transaction_id is required and must be a string", "details": {}, "code": "invalid_request" } } ``` `data` is `null` on every error in this envelope. `error.status` repeats the HTTP status, and `error.name` is the error class for that status — `BadRequestError` (400), `UnauthorizedError` (401), `ForbiddenError` (403), `NotFoundError` (404), `ConflictError` (409), `GoneError` (410), `UnprocessableEntityError` (422), `InternalServerError` (500). `error.details` is an empty object unless noted below. `POST /api/v1/track/sale` and `POST /api/v1/track/refund` add a stable `error.code` to every error in this envelope: `invalid_request` (400), `no_attribution` (400), `unauthorized` (401), `not_found` (404), `duplicate_transaction` (409, with your program's earlier sale id in `error.details.sale_id`, or `null` when the earlier sale belongs to another program), `unsupported_currency` (422) and `internal_error` (500). Branch on it rather than on the message text. Most other errors in this envelope carry no stable machine code, so match on the HTTP status and, where you need the specific cause, on the `error.message` strings listed below. There are three exceptions, all in `error.details`: - A suspended account signing in to the CLI gets `error.details.code` set to [`ACCOUNT_BLOCKED`](#account_blocked). - A CLI sign-in whose email address the sign-in provider has not verified gets `error.details.code` set to [`PROVIDER_EMAIL_NOT_VERIFIED`](#provider_email_not_verified). - A CLI `500` carries `error.details.request_id` — see [request IDs](#request-ids). ### The typed envelope Four things answer with a typed envelope instead. It has no `data` key, and it carries a stable `error.code` you can branch on: ```json { "error": { "code": "invalid_key", "message": "Invalid API token." } } ``` You get it from: | Source | Where | Code | |--------|-------|------| | `GET /api/v1/programs/me/readiness` | all of its errors | `invalid_key` on a `401`, `internal_error` on a `500` | | [Rate limiting](#rate-limits-429) | every `/api/v1/` route in the [rate-limit table](#rate-limits-429) | `rate_limited` | | [A retired API key](#api_key_rotation_required) | every endpoint that key authenticates | `api_key_rotation_required` | | [`POST /api/v1/track/click`](/docs/api-reference/track-click) | a `410` for an inactive referral link | `link_disabled` (the body also keeps the older top-level `success: false` and `message`) | Only `code` and `message` are always present. The rest varies with the case: a rate limit adds `status` and `retry_after_seconds`, a retired key adds `hint` and `docs_url`, `link_disabled` adds `hint`, and a readiness `internal_error` adds `retry_after_seconds`. ### Handling both Read `error.code` first and fall back to `error.message` when it is absent: ```ts const body = await response.json(); const detail = body.error?.code ? `${body.error.code}: ${body.error.message}` : body.error?.message; ``` ### Request IDs Responses from the tracking, readiness and CLI endpoints carry an `X-Request-ID` header, except `GET /api/v1/cli/status`: its `200`, `401` and `429` have no request ID, and only its `500` does. On a `500` from a CLI endpoint the same ID is also in the body, both at the end of `error.message` and in `error.details.request_id`. Tracking and readiness `500`s carry it only in the header. When you contact support about a failed request, include the `X-Request-ID`. It is how we find the log line for your request; the error message itself is deliberately generic. --- ## Error reference ### Authentication errors (401) | Status | Error message | Condition | Fix | |--------|---------------|-----------|-----| | `401` | `Missing or malformed Authorization header. Expected: Bearer ` | `Authorization` header missing or does not start with `Bearer ` | Add `Authorization: Bearer YOUR_PROGRAM_API_KEY` to the request | | `401` | `Missing API token` (sale), `Empty Bearer token` (refund) | Header present but the token is empty after trimming | Check for trailing spaces or an empty env variable | | `401` | `Invalid API token` | The key is unknown, has been replaced, or is disabled | Compare what you are sending against the full key you stored when it was issued. If you no longer hold that value, ask an owner or admin to [rotate the key](/docs/brand/settings#step-3-rotate-the-key), copy it from **Copy your key** and deploy it: the dashboard never shows the full value again. If the key is disabled, an owner or admin can select **Enable key** | The rows above apply to the endpoints that require a Bearer token: `POST /api/v1/track/sale` and `POST /api/v1/track/refund`. ```json { "data": null, "error": { "status": 401, "name": "UnauthorizedError", "message": "Invalid API token", "details": {}, "code": "unauthorized" } } ``` `GET /api/v1/programs/me/readiness` fails the same three checks with the [typed envelope](#the-typed-envelope) instead, always with `error.code` set to `invalid_key`. Its messages end with a period: `Missing or malformed Authorization header. Expected: Bearer .`, `Missing API token.` and `Invalid API token.` The CLI's program-key routes word these differently; see [CLI endpoint errors](#cli-endpoint-errors). `POST /api/v1/track/lead` accepts a Bearer token for server mode but does not require one, so it answers differently. A missing header — or a header whose token is empty after `Bearer ` — falls back to browser mode: the lead is recorded from the `click_id` rather than refused. Only a token that matches no program returns `401` there. The success body is identical in both modes, so a `2xx` on its own does not prove your key was read. The one exception is a program configured with `lead_auth: server_required`, where a browser-mode lead comes back with `"provisional": true`. Such a lead settles when your backend sends the server-side lead. A qualifying Stripe payment webhook can also settle it, through the same path the lead endpoint uses, but only when Affitor can resolve the customer from that event: one-off payments through `checkout.session.completed`, and subscriptions through the invoice events (`invoice.payment_succeeded`, `invoice.paid`), because subscription checkouts are deliberately left to the invoice event. Send the server-side lead rather than relying on a payment to settle it. --- ### `api_key_rotation_required` Affitor can mark a specific program API key for mandatory rotation — for example, after the key was exposed outside your control. A marked key keeps authenticating requests until its rotation deadline, so tracking is never interrupted, but every response signals the change so you or your agent can act ahead of time. **Before the deadline**, requests with a marked key still succeed and pick up three standard headers: | Header | Value | |--------|-------| | `Deprecation` | `@` of when the key was marked for rotation, e.g. `Deprecation: @1789776000` ([RFC 9745](https://www.rfc-editor.org/rfc/rfc9745)) | | `Sunset` | HTTP-date of the rotation deadline, after which the key stops working ([RFC 8594](https://www.rfc-editor.org/rfc/rfc8594)) | | `Link` | `; rel="deprecation"` | The JSON body also gains a `warnings` array. No existing field is removed or renamed. `warnings` sits at the top level of the response body. On endpoints that wrap their payload in `data`, it is a sibling of `data`, not a field inside it, so read it before you unwrap: ```json { "success": true, "warnings": [ { "code": "api_key_rotation_required", "message": "This API key must be replaced by 2026-10-03.", "hint": "In Affitor → Program settings → Developers → API keys, rotate the key you use, then update AFFITOR_API_KEY on your server.", "rotate_by": "2026-10-03T00:00:00.000Z", "docs_url": "https://affitor.com/docs/api-reference/errors#api_key_rotation_required" } ] } ``` **After the deadline**, the key is retired and every request with it returns: | Status | Error code | Meaning | Fix | |--------|-----------|---------|-----| | `401` | `api_key_rotation_required` | The key passed its rotation deadline and no longer authenticates requests | Create a new key and update your integration | ```json { "error": { "code": "api_key_rotation_required", "message": "This API key was retired on 2026-10-03.", "hint": "In Affitor → Program settings → Developers → API keys, rotate the key you use.", "docs_url": "https://affitor.com/docs/api-reference/errors#api_key_rotation_required" } } ``` This body is the [typed envelope](#the-typed-envelope): no `data` key, and an `error.code` to branch on. **Fix:** In your Affitor dashboard, open the program menu and choose **Program settings**. Under **Developers** → **API keys**, open the **⋯** menu on the key's row and select **Rotate key**, copy the new value from **Copy your key**, then update `AFFITOR_API_KEY` on your server with it. See [Rotate your API key](/docs/brand/settings#step-3-rotate-the-key) for the full walkthrough. --- ### Validation errors (400) #### Track click | Status | Error message | Meaning | Fix | |--------|---------------|---------|-----| | `400` | `affiliate_url is required` | Body did not include `affiliate_url` | Pass the full URL that contains the `?aff=` or `?via=` parameter | | `400` | `Invalid affiliate_url` | URL could not be parsed by `new URL()` | Ensure the value is a fully-qualified URL (includes scheme) | | `400` | `No aff parameter found in affiliate_url` | URL was valid but had neither an `aff` nor a `via` query parameter | Only call this endpoint when `?aff=` or `?via=` is present in the URL | | `400` | `Unknown program_id` | The body sent a top-level `program_id` that is not a program | Send your program's id, or leave `program_id` out | | `400` | `Referral link not found` | No referral link matched the `aff` (or `via`) value | Verify the partner link exists and `short_link` matches that value | | `400` | `Invalid referral link configuration` | Link exists but has no linked partner or program | Contact Affitor support — the referral link record is incomplete | #### Track lead | Status | Error message | Meaning | Fix | |--------|---------------|---------|-----| | `400` | `click_id or customer_key is required` | Neither identifier was sent in the body | Send the `click_id` from the `affitor_click_id` cookie with your `customer_key` | | `400` | `click_id is required when no API key is sent` | A browser-mode lead (no Bearer key) sent `customer_key` without `click_id` | Pass the `click_id` from the `affitor_click_id` cookie with the `customer_key` (a server lead with only `customer_key` finds no customer on a first lead either) | | `400` | `Customer not found. Provide a valid click_id or customer_key.` | No customer matched the `click_id`, the `customer_key` is not saved on a customer yet (a first lead sent with only `customer_key`: Affitor saves the key only when a lead settles), or (browser mode) the customer does not belong to the `program_id` sent | Send the `click_id` from the `affitor_click_id` cookie on every lead. If you did, the click was not tracked or the cookie was cleared: check that the tracker loads on every page | | `400` | `Customer does not belong to this program` | Customer was found but is attributed to a different program (server mode only) | Use the API key for the program that originated the click | | `400` | `Customer status cannot be updated to lead. Current status: ` | Lead service rejected the status transition | A lead was already recorded for this customer, or the customer is at a later funnel stage — this is usually safe to ignore | #### Track sale | Status | Error message | Meaning | Fix | |--------|---------------|---------|-----| | `400` | `transaction_id is required and must be a string` | Field missing or not a string type | Always pass `transaction_id` as a string | | `400` | `amount_cents is required and must be a positive integer` | Field missing, zero, negative, or wrong type | Pass sale amount in smallest currency unit (e.g. `4900` for $49.00 USD) as a positive integer | | `400` | `occurred_at must be an ISO 8601 time within the last 30 days` | Not ISO 8601 with an offset, not a real date, older than 30 days, or more than 5 minutes in the future | Send for example `2026-10-16T09:30:00Z`, or omit it | | `400` | `provider must be one of: ...` / `provider_payment_id must be a string of 1 to 255 characters` / `livemode must be a boolean` | An optional field has the wrong shape | Fix the field or omit it | | `422` | `currency XXX is not supported` | The code is not a [supported ISO 4217 code](/docs/api-reference/track-sale#request-fields) | Send a supported code; no sale was created, so you can resend | | `400` | `Customer not found. Provide customer_key or click_id.` | Neither identifier resolved a customer | Ensure lead tracking ran first and the customer record exists | | `400` | `No affiliate attribution found for this customer in this program` | Customer exists but is attributed to a different program | Use the API key matching the program where the click originated | | `400` | `No partner-program relationship found for this customer` | Customer has no linked partner-program junction | The customer record is missing a partner relationship — check that the original click was tracked correctly | | `400` | `partnerId required to create commission` | Customer resolved but has no `affiliate_partner` relation | Internal data inconsistency — contact Affitor support | #### Track refund | Status | Error message | Meaning | Fix | |--------|---------------|---------|-----| | `400` | `transaction_id is required` | Body did not include `transaction_id` | Pass the same `transaction_id` used when recording the original sale | | `400` | `reason must be refund or chargeback` | `reason` has another value | Send `refund` or `chargeback`, or use free-text `refund_reason` | --- ### Forbidden errors (403) | Status | Error message | Meaning | Fix | |--------|---------------|---------|-----| | `403` | `program_id does not match the API key` | A test-mode click or lead (`additional_data.test_mode`) sent both a Bearer key and an `additional_data.program_id`, and the two name different programs | Send the `program_id` of the program the key belongs to, or leave `program_id` out and let the key decide | This applies to `POST /api/v1/track/click` and `POST /api/v1/track/lead` in test mode only. A browser-mode test event with no key is not checked this way. ```json { "data": null, "error": { "status": 403, "name": "ForbiddenError", "message": "program_id does not match the API key", "details": {} } } ``` --- ### Conflict errors (409) | Status | Error message | Meaning | Fix | |--------|---------------|---------|-----| | `409` | `Duplicate transaction_id. This sale has already been recorded.` | A sale event with this `processor_event_id` already exists; `error.details.sale_id` is its id when it belongs to your program, otherwise `null` | This is the intended duplicate-guard behavior — do not retry with the same `transaction_id`. If the original was a test, check if you need to clear test data. | Duplicate detection is keyed on `processor_event_id` (mapped from `transaction_id`). The check is scoped globally, not per-program. --- ### Not found errors (404) | Status | Error message | Meaning | Fix | |--------|---------------|---------|-----| | `404` | `Sale not found for transaction_id` | Refund was attempted but no sale with that `transaction_id` exists in the program | Verify the `transaction_id` matches exactly what was sent to `/track/sale` and that the Bearer token is for the same program | --- ### Rate limits (429) Every `/api/v1/` endpoint below is rate limited per minute. The click, lead, visit and config endpoints are bucketed by client IP, because they are called without a key; the rest are bucketed by the Bearer token they send (the API key, the `affitor login` token on the CLI's account-session routes, or the dashboard sign-in token on the settings routes), falling back to IP when no token is sent. | Endpoint | Limit per minute | Counted per | |----------|-----------------|-------------| | `POST /api/v1/track/click` | 60 | IP | | `POST /api/v1/track/visit` | 120 | IP | | `GET /api/v1/track/config` | 60 | IP | | `POST /api/v1/track/lead` | 30 | IP | | `POST /api/v1/track/sale` and `POST /api/v1/track/refund` | 120 combined | API key | | `GET /api/v1/programs/me/readiness` | 30 | API key | | `GET /api/v1/programs/me/analytics/sources` | 30 | API key | | `GET /api/v1/programs/:id/settings` | 30 | Sign-in token | | `PATCH /api/v1/programs/:id/settings` | 30 | Sign-in token | | `/api/v1/cli/*` | 60 | API key or login token | Each API server instance keeps its own counts in memory, so the limits apply per instance. Every response on these routes carries the current budget, not just the ones that are refused: | Header | Value | |--------|-------| | `RateLimit-Policy` | The bucket's quota as an IETF structured field: `"default";q=120;w=60` is 120 requests per 60-second window | | `RateLimit` | What is left: `"default";r=119;t=42` is 119 requests left, window resets in 42 seconds | | `X-RateLimit-Limit` | The limit for this bucket (same as `q`) | | `X-RateLimit-Remaining` | Requests left in the current window (same as `r`) | | `X-RateLimit-Reset` | Unix timestamp in seconds when the window resets | | `Retry-After` | Seconds to wait. Sent only on a `429` | `RateLimit-Policy` and `RateLimit` follow the IETF draft for RateLimit header fields; the `X-RateLimit-*` headers stay for existing clients. Over the limit, the request is refused with the [typed envelope](#the-typed-envelope) — no `data` key: ```json { "error": { "status": 429, "code": "rate_limited", "message": "Too many requests.", "retry_after_seconds": 42 } } ``` Wait `retry_after_seconds` (or read `Retry-After`) before retrying. The request is refused before it reaches the endpoint, so nothing was recorded and the retry is safe. The synthetic verification chain has a second, separate cap of 10 runs per program per hour. It reports the same `rate_limited` code on `POST /api/v1/cli/test-event`, with its own `retry_after_seconds`. That one is checked inside the endpoint rather than in front of it, so the "nothing was recorded" guarantee above does not carry over: the chain's test fixture is prepared before the cap is consulted. No chain runs, but the fixture records for your program may have been created or refreshed. --- ### Server errors (500) A `500` means the request failed on our side. The message is deliberately generic — the detail goes to our logs under the response's [`X-Request-ID`](#request-ids), so include that ID when you contact support. | Status | Error message | Meaning | Fix | |--------|---------------|---------|-----| | `500` | `Click tracking failed` | The click handler failed unexpectedly | Retry with backoff | | `500` | `Lead tracking failed` | The lead handler failed unexpectedly | Retry with backoff. If the first attempt did record the lead, the retry can answer `400` `Customer status cannot be updated to lead`, which is safe to ignore | | `500` | `Sale tracking failed` | The sale could not be recorded, or the server could not confirm that it was | A `500` does not prove that nothing was recorded. Retry with backoff and the **same** `transaction_id`. A retry can fail again with `500`; one that reaches the duplicate check answers `409` with your program's `sale_id` if an earlier attempt recorded the sale, so the sale is not recorded twice. If it keeps failing, contact support with the `X-Request-ID` | | `500` | `Refund tracking failed` | The refund handler failed unexpectedly | Retry with backoff. If it persists, contact support with the `X-Request-ID` | | `500` | `Failed to create commission` | The commission could not be created | Retry with backoff and the same `transaction_id`, as for `Sale tracking failed`. If it keeps failing, contact support with the `X-Request-ID` | | `500` | `Failed to compute readiness. Retry shortly.` | `GET /api/v1/programs/me/readiness` failed. [Typed envelope](#the-typed-envelope), code `internal_error` | Wait `retry_after_seconds` (10), then poll again | ```json { "data": null, "error": { "status": 500, "name": "InternalServerError", "message": "Sale tracking failed", "details": {}, "code": "internal_error" } } ``` The readiness `500` uses the typed envelope: ```json { "error": { "code": "internal_error", "message": "Failed to compute readiness. Retry shortly.", "retry_after_seconds": 10 } } ``` A metric update failure (step 10 in the sale flow) answers `500` `Sale tracking failed`. Handle it like any sale `500`: retry with the same `transaction_id`. For `500`s from the CLI endpoints, see [CLI endpoint errors](#cli-endpoint-errors). --- ### CLI endpoint errors The [Affitor CLI](/docs/brand/cli/commands) talks to the `/api/v1/cli/*` endpoints. They answer in the [platform envelope](#the-platform-envelope), except the [rate limits](#rate-limits-429) and a [retired key](#api_key_rotation_required), which use the typed one. This section is about what the API returns; for the codes the CLI itself prints with `--json`, see [CLI commands](/docs/brand/cli/commands). The routes authenticate in two different ways, and the fix for a `401` depends on which: - **Account session** — `init` and `programs` take the login token from `affitor login`. Fix a `401` by logging in again. Rotating a program key does not help. - **Program API key** — `status` and `test-event` take the program's API key. Fix a `401` as in [authentication errors](#authentication-errors-401). #### Login (`/api/v1/cli/auth/*`) These routes run the browser login that `affitor login` starts. They take no credential. | Endpoint | Status | Error message | Meaning | Fix | |----------|--------|---------------|---------|-----| | `POST /auth/start` | `500` | `Failed to start auth session (request_id: )` | The login session could not be created | Run `affitor login` again | | `POST /auth/callback` | `400` | `Missing required fields: state, id_token` | The body lacked the session `state` or the sign-in `id_token` | Complete sign-in from the link `affitor login` opened | | `POST /auth/callback` | `404` | `Session not found or already used` | No pending login session has that `state` | Run `affitor login` again for a fresh link | | `POST /auth/callback` | `400` | `Session expired` | The login link is older than 5 minutes | Run `affitor login` again and finish within 5 minutes | | `POST /auth/callback` | `403` | `Your account has been suspended.` | [`ACCOUNT_BLOCKED`](#account_blocked) | Contact Affitor support | | `POST /auth/callback` | `403` | `Your email address is not verified with your sign-in provider. Verify it there, then try again.` | [`PROVIDER_EMAIL_NOT_VERIFIED`](#provider_email_not_verified) | Verify the address with your sign-in provider, then run `affitor login` again | | `POST /auth/callback` | `500` | `Auth callback failed (request_id: )` | Sign-in could not be completed | Run `affitor login` again | | `GET /auth/poll` | `400` | `Missing state parameter` | The `state` query parameter was not sent | Poll with the `state` returned by `/auth/start` | | `GET /auth/poll` | `404` | `Session not found` | No login session has that `state` | Run `affitor login` again | | `GET /auth/poll` | `400` | `Session already consumed` | The login token was already handed out once | Run `affitor login` again. The token is returned only on the first poll after sign-in | | `GET /auth/poll` | `500` | `Failed to poll auth session (request_id: )` | The poll failed on our side | Poll again | An expired session is not an error on `/auth/poll`: it answers `200` with `"data": { "status": "expired" }`. ##### `ACCOUNT_BLOCKED` `POST /api/v1/cli/auth/callback` refuses to log in a suspended account. It carries a stable code in `error.details.code`: ```json { "data": null, "error": { "status": 403, "name": "ForbiddenError", "message": "Your account has been suspended.", "details": { "code": "ACCOUNT_BLOCKED" } } } ``` **Cause:** the Affitor account you signed in with is suspended. **Fix:** retrying or signing in again will not help. Contact Affitor support. ##### `PROVIDER_EMAIL_NOT_VERIFIED` `POST /api/v1/cli/auth/callback` also refuses a sign-in when the sign-in provider has not verified the email address it sent. The address is checked before it is used to find, create or link an account. The stable code is in `error.details.code`: ```json { "data": null, "error": { "status": 403, "name": "ForbiddenError", "message": "Your email address is not verified with your sign-in provider. Verify it there, then try again.", "details": { "code": "PROVIDER_EMAIL_NOT_VERIFIED" } } } ``` **Cause:** your sign-in provider does not report the email address as verified. **Fix:** verify the address with that provider, then run `affitor login` again. #### Account-session routes (`init`, `programs`) | Endpoint | Status | Error message | Meaning | Fix | |----------|--------|---------------|---------|-----| | `POST /init` | `401` | ``Authentication required — run `affitor login` first`` | No Bearer login token was sent | Run `affitor login` | | `POST /init` | `401` | ``Invalid or expired token — run `affitor login` again`` | The login token is invalid or expired | Run `affitor login` again | | `POST /init` | `401` | ``User not found — run `affitor login` again`` | The token's account no longer exists | Run `affitor login` again | | `POST /init` | `403` | ``No advertiser found for this account — run `affitor login` again`` | The account has no brand profile yet | Run `affitor login` again; logging in creates one | | `POST /init` | `403` | `advertiser_id does not match the authenticated account` | The body named another account's `advertiser_id` | Leave `advertiser_id` out. It is taken from your login | | `POST /init` | `400` | `Missing required fields: name, domain, commission_type, commission_rate` | One of the four fields is missing | Send all four | | `POST /init` | `400` | `Invalid commission_type: . Valid: percent, fixed, recurring_percent, recurring_fixed` | `commission_type` is not one of the four values | Use one of the listed values | | `POST /init` | `400` | `commission_rate must be a positive number` | `commission_rate` is not a number, or is zero or negative | Send a positive number, not a string | | `POST /init` | `400` | `commission_rate is a percentage for this type and cannot exceed 100` | `commission_type` is `percent` or `recurring_percent` and `commission_rate` is above 100 | Send a rate above 0 and at most 100 | | `POST /init` | `400` | `duration_months must be a whole number of months (0 = lifetime)` | `duration_months` was sent and is not a whole number of 0 or more | Send a whole number of months, `0` for lifetime, or leave it out | | `POST /init` | `400` | `cookie_duration must be a whole number of days from 1 to 365` | `cookie_duration` was sent and is not a whole number from 1 to 365 | Send a whole number of days from 1 to 365, or leave it out | | `POST /init` | `500` | `Failed to create program (request_id: )` | Program creation failed on our side | Run `affitor programs` before retrying, in case the program was created | | `GET /programs` | `401` | ``Missing Authorization header. Run `affitor login` first.`` | No Bearer login token was sent | Run `affitor login` | | `GET /programs` | `401` | ``Invalid or expired token. Run `affitor login` to refresh.`` | The login token is invalid or expired | Run `affitor login` again | | `GET /programs` | `401` | `User not found` | The token's account no longer exists | Run `affitor login` again | | `GET /programs` | `500` | `Failed to list programs (request_id: )` | Listing failed on our side | Retry with backoff | #### Program-key routes (`status`, `test-event`) | Endpoint | Status | Error message | Meaning | Fix | |----------|--------|---------------|---------|-----| | both | `401` | `Missing or malformed Authorization header. Expected: Bearer ` | The `Authorization` header is missing or does not start with `Bearer ` | Send `Authorization: Bearer YOUR_PROGRAM_API_KEY` | | both | `401` | `Missing API token` | The token is empty after `Bearer ` | Check for an empty env variable | | both | `401` | `Invalid API key. To get a working key for the program you already have, ask a workspace owner of that program to open Affitor → Program settings → Developers → API keys and create a key, then replace the key you are sending with the new one.` | The key matches no program, or it is disabled | Do as the message says. An owner or admin of the program can select **Create key** there and copy the new value from **Copy your key**; if the key is only disabled, they can select **Enable key** instead. Running `affitor init` does not help: it creates a second program | | both | `401` | [`api_key_rotation_required`](#api_key_rotation_required) | The key is retired | Create a new key | | `GET /status` | `500` | `Failed to get status (request_id: )` | Status lookup failed on our side | Retry with backoff | | `POST /test-event` | `400` | `Invalid event_type: . Valid: click, lead, sale` | Single-event mode got a missing or unknown `event_type` | Send `click`, `lead` or `sale`, or `{"type": "chain"}` for the full chain | | `POST /test-event` | `429` | `Too many synthetic chains (max 10/program/hour).` | The chain cap was hit. Typed envelope, code `rate_limited` | Wait `retry_after_seconds`; see [rate limits](#rate-limits-429) | | `POST /test-event` | `500` | `Failed to run synthetic chain (request_id: )` | The chain run failed on our side | Retry with backoff | | `POST /test-event` | `500` | `Failed to process test event (request_id: )` | The test event failed on our side | Retry with backoff | #### Retired endpoint | Endpoint | Status | Error message | Fix | |----------|--------|---------------|-----| | `POST /stripe-connect` | `410` | `This endpoint is retired. Connect Stripe from the Affitor dashboard: open the program, go to Settings, and use Connect Stripe.` | Connect Stripe from the dashboard | A CLI `500` puts the request ID in the message and in `details`: ```json { "data": null, "error": { "status": 500, "name": "InternalServerError", "message": "Failed to get status (request_id: 9f2c4e1a7b3d5f60a8c2e4b6d8f0a1c3)", "details": { "request_id": "9f2c4e1a7b3d5f60a8c2e4b6d8f0a1c3" } } } ``` --- ## Troubleshooting ### Cookies blocked by the browser The Affitor browser SDK stores the click ID in a first-party cookie named `affitor_click_id` (`SameSite=Lax; Secure` on HTTPS). Attribution is lost when: - The user has a browser extension or privacy setting that blocks first-party cookies. - The page is served over HTTP in production (the `Secure` flag is only set on HTTPS). - Safari ITP aggressively expires cookies set via JavaScript within 7 days for domains classified as trackers. **Fix:** The SDK auto-detects the root domain and sets the cookie there (e.g. `.example.com`) to share attribution across subdomains. For custom domains or cross-domain attribution, pass `cookieDomain` explicitly: ```ts init({ programId: 123, cookieDomain: '.example.com' }); ``` There is no server-side fallback for blocked cookies: if the cookie is missing when `signup()` fires, Affitor cannot find the customer, so no lead is recorded and that signup stays unattributed. --- ### CORS The tracking API (`api.affitor.com`) must allow your site's origin for browser-mode requests. If you see CORS errors: 1. Check that your site's domain is listed in the allowed origins on the Affitor program settings page. 2. Browser-mode tracking calls (`/track/click`, `/track/lead` without a Bearer token) are the only routes intended for direct browser fetch. Server-mode routes (`/track/sale`, `/track/refund`) should only be called from your backend — they do not need CORS. 3. In development, use `localhost` explicitly rather than `127.0.0.1` (or vice versa) — the two are treated as different origins. --- ### Attribution window edge cases The attribution window defaults to 60 days and is set per program (`attribution_window_days`, shown as **Attribution window** in the dashboard). The click response returns the value as `cookie_window_days`: ```json { "success": true, "click_id": "cust_42_1712345678901", "cookie_window_days": 60 } ``` The SDK applies this value as the cookie expiry. Edge cases: | Scenario | Behavior | |----------|----------| | User clears cookies before signup | Attribution is lost: with no `click_id`, the lead answers `400` and nothing is recorded. A `customer_key` alone cannot recover it, because the key is saved on the customer only when a lead settles | | User visits with a different partner's link after the first click | First-click attribution: the SDK detects a new `aff` value and sends a new click with the existing `click_id`. The click is logged for the new partner, but the customer stays with the first partner and the cookie keeps the same `click_id` | | Signup fires after cookie expiry | `click_id` from the cookie is null, so the lead answers `400` and no lead is recorded, even with a `customer_key` | | Sale fires with a `customer_key` for a customer whose window expired | The attribution window (`attribution_window_days`, default 60) is checked on each payment until one is recorded as a conversion: the click must be at most that many days older than the customer's signup (or than the payment, when no signup was recorded). If it is older, that sale is not attributed and nothing is recorded, so the customer's next payment is checked again. Once a conversion has been recorded for the customer, later payments are not re-checked | --- ### Duplicate `transaction_id` handling The sale endpoint uses `transaction_id` as a globally unique idempotency key stored as `processor_event_id`. The rules: - Sending the same `transaction_id` twice returns `409 Conflict` — the second request is a no-op. - A `409` with a non-null `error.details.sale_id` is **not** an error to retry: your program already recorded the sale, so treat it as recorded and proceed. A `409` with `sale_id: null` is not a recorded sale for your program: do not switch to a new `transaction_id`; contact support with the `X-Request-ID`. - `error.details.sale_id` is your program's earlier sale id, or `null` when the earlier sale belongs to another program. A `null` means nothing was recorded for your program under this `transaction_id`. - Test-mode sales use `test_txn_` when `transaction_id` is omitted, so test records are never duplicates unless you pass the same value explicitly. - On a `500` from the sale endpoint (`Sale tracking failed` or `Failed to create commission`), retry the same request with the same `transaction_id`. A `500` does not prove that nothing was recorded. A retry can fail again with `500`; one that reaches the duplicate check answers `409` with your program's `sale_id` if an earlier attempt recorded the sale, so the sale is not recorded twice. Never switch to a new `transaction_id` to get past a `409`. **Recommended pattern:** ```ts const response = await fetch('https://api.affitor.com/api/v1/track/sale', { method: 'POST', headers: { Authorization: `Bearer ${PROGRAM_API_KEY}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ transaction_id: chargeId, ... }), }); if (response.status === 409) { const body = await response.json(); if (body.error?.details?.sale_id != null) { // Your program already recorded this sale: safe to continue return; } // Another program used this transaction_id: nothing was recorded for yours throw new Error(`Affitor 409 without a sale_id, contact support: ${response.headers.get('X-Request-ID')}`); } if (!response.ok) { // On a 500, retry later with the same transaction_id: a 500 does not prove nothing was recorded. // Other errors: log and alert const body = await response.json(); // `error` is always an object. `code` is on the typed envelope and, for // track/sale and track/refund, on the platform envelope too; other platform // errors carry a message and no code. const detail = body.error?.code ? `${body.error.code}: ${body.error.message}` : body.error?.message; throw new Error(`Affitor error ${response.status}: ${detail}`); } ``` --- ### SDK `debug: true` for testing Pass `debug: true` to `loadAffitor()` while you test an integration. ```ts import { loadAffitor } from '@affitor/sdk'; const affitor = await loadAffitor(123, { debug: true }); ``` With `debug: true`, the SDK logs its `info` and `warn` messages to the browser console with the `[Affitor]` prefix, and `signup()` sends a [test event](/docs/api-reference/test-mode) instead of a lead: no real lead is recorded. Errors (`console.error`) are always logged. **Turn it off before production.** A site that ships with `debug: true` records no real leads from `signup()`. To check the current tracker state at any point: ```ts console.log(affitor?.getData()); // { // clickId: "cust_42_1712345678901", // programId: 123, // hasAttribution: true, // affiliateUrl: "https://example.com/?aff=abc123" // } ``` --- id: "api-reference/events" type: "doc" url: "https://affitor.com/docs/api-reference/events" kind: "reference" updated: "2026-09-24" --- # List Tracking Events > Retrieve paginated, merged tracking events (clicks, leads, conversions) for a program `GET /api/tracking/events/:programId` Returns a merged, reverse-chronological list of click, lead, and conversion events recorded for the specified program. Events from all three tables are fetched, normalized to a common shape, sorted by timestamp, and then paginated. --- ## Authentication This endpoint uses workspace-policy enforcement. The request must carry a valid authenticated session that has been granted the `tracking:list` action for the program. This is enforced by the `verify-program-access` policy on the Strapi backend. :::note This endpoint backs the Affitor dashboard. It accepts only a signed-in dashboard session for a workspace member of the program and does not accept a program API key (`aff_…`), so you cannot call it from a server integration with your API key. ::: --- ## Path Parameter | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `programId` | integer | **Yes** | Numeric ID of the affiliate program | --- ## Query Parameters | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | `page` | integer | No | `1` | Page number (1-indexed) | | `pageSize` | integer | No | `10` | Number of events per page | | `eventType` | string | No | *(all)* | Filter by event type. Accepted values: `click`, `lead`, `conversion` | | `dateFrom` | string (ISO 8601) | No | *(none)* | Inclusive lower bound on event timestamp | | `dateTo` | string (ISO 8601) | No | *(none)* | Inclusive upper bound on event timestamp | ### Example request ```bash GET /api/tracking/events/42?page=1&pageSize=10&eventType=click&dateFrom=2026-06-01T00:00:00Z&dateTo=2026-06-07T23:59:59Z ``` --- ## Response Returns a `data` array of normalized event objects and a `meta.pagination` block. ### Success `200` ```json { "data": [ { "id": 301, "event_type": "click", "timestamp": "2026-06-07T14:22:10.000Z", "click_id": "cust_42_1749305730000", "session_id": "sess_1749305730000", "page_url": "https://example.com/pricing?aff=PARTNER123", "referrer_url": "https://twitter.com", "geo_country": "US", "geo_region": "CA", "geo_city": "San Francisco", "device_type": "desktop", "device_os": "macOS", "browser_name": "Chrome", "converted": false, "createdAt": "2026-06-07T14:22:10.512Z" }, { "id": 87, "event_type": "lead", "timestamp": "2026-06-06T09:11:42.000Z", "click_id": "cust_42_1749218702000", "customer_key": "usr_abc123", "session_id": "sess_1749218702000", "page_url": "https://example.com/signup", "converted": false, "createdAt": "2026-06-06T09:11:42.301Z" }, { "id": 15, "event_type": "conversion", "timestamp": "2026-06-05T16:45:00.000Z", "click_id": "cust_42_1749131100000", "amount_cents": 9900, "currency": "USD", "sale_type": "payment", "payment_status": "paid", "processor_event_id": "txn_abc123", "is_recurring": false, "createdAt": "2026-06-05T16:45:01.000Z" } ], "meta": { "pagination": { "page": 1, "pageSize": 10, "pageCount": 3, "total": 28 } } } ``` ### Field notes - `event_type` is a normalized field added by the server: `"click"`, `"lead"`, or `"conversion"`. - `timestamp` is a normalized field set to the source event's native time field (`click_timestamp`, `lead_timestamp`, or `sale_date`). - Test events (`is_test: true`) are excluded from all three tables before merging. - Each event type is read newest-first, capped at 3 × `pageSize` rows per type, then merged and paginated. `total` is the size of that merged set, not the full event count: it is at most 3 × `pageSize` for one event type (9 × `pageSize` for all three), and pages beyond it come back empty even when older events exist. Narrow the window with `dateFrom` / `dateTo` to reach older events. --- ## Errors | Status | When | |--------|------| | `404` | `programId` does not match any program | | `403` | Caller does not have `tracking:list` access for the program | | `500` | Unexpected server error | --- id: "api-reference/mcp" type: "doc" url: "https://affitor.com/docs/api-reference/mcp" kind: "reference" updated: "2026-11-08" --- # Affitor MCP server > Reference for the hosted Affitor MCP server at https://mcp.affitor.com/mcp: which apps can connect, sign-in and consent, read-only tools, limits and removal. The Affitor MCP server lets an AI app read your Affitor data: a brand's program, partners, applications, commissions and billing, or a partner's programs, links, earnings, commissions and payouts. It is a hosted [Model Context Protocol](https://modelcontextprotocol.io) server. You sign in with your Affitor account, no API key needed, and the connection is read-only: it cannot change data or move money. ```text https://mcp.affitor.com/mcp ``` | | | |---|---| | Server URL | `https://mcp.affitor.com/mcp` | | Transport | Streamable HTTP | | Sign-in | OAuth 2.1 with PKCE (S256) and dynamic client registration | | Scope | `read` (the only scope) | | Access | Read-only. A connection reads the programs you choose when you connect: all current and future programs, or up to 50 you select. A partner connection sees only that partner | **Add the server** in your AI app **Sign in** with your Affitor account **Choose what to share** and click **Allow** **Ask your AI app** about your program or earnings --- ## Connect your AI app Server URL: `https://mcp.affitor.com/mcp`. [Connect your AI tool](/docs/api-reference/connect-ai-tool) has the steps for each app it lists and for any other MCP client. In the Affitor dashboard, **Connect an AI tool** shows the server URL and steps for Claude, ChatGPT, Cursor, VS Code, Claude Code and Codex, and under **Other** for Grok, Muse Code and any other MCP client. Brands find it in the program menu under **Program settings**, then **Developers** › **AI agents**. Partners click their name at the bottom of the left menu to open the account menu, then **Integrations**. ### Which apps can connect After you sign in, Affitor sends you back to the app. It accepts only these return addresses: - `claude.ai` and `claude.com` (Claude) - `chatgpt.com` (ChatGPT) - `www.cursor.com` (Cursor) - `grok.com/connectors-oauth-exchange-code/` (Grok) - `vscode.dev/redirect` and `insiders.vscode.dev/redirect` (VS Code) - `www.perplexity.ai/rest/connections/oauth_callback` and `enterprise.perplexity.ai/rest/connections/oauth_callback` (Perplexity, including Perplexity Enterprise) - `www.town.com/api/mcp/oauth/callback` and `town.com/api/mcp/oauth/callback` (Town) - `manufact.com/inspector/oauth/callback` (Manufact inspector) - apps on your own computer: `http://127.0.0.1` or `http://localhost`, any port An app that registers any other address is refused when it registers, with the error "redirect_uris must be https on a supported AI app host, or http on 127.0.0.1 or localhost". --- ## Sign in and allow access When your AI app connects, your browser opens **Connect an AI tool** on affitor.com. If you are signed out, you sign in first and come back to the same screen. 1. The title names the app: **Claude wants to access Affitor**, or **An app on this computer wants to access Affitor** for a desktop or terminal app. A desktop or terminal app also shows **Unverified** and the name it gives itself in quotes ("It calls itself …"), because any app on your computer can call itself "Claude". 2. Check the account shown, your name and email. To use another Affitor account, click **Switch**. 3. If you are both a brand and a partner, choose **As a brand** or **As a partner**. 4. Choose the programs the app can read: **All current and future programs**, or up to 50 programs you select. As a brand you need to be an active member of each program; as a partner you choose among the programs you are a partner in. 5. Under **Access**, **Read account data** is **Always on**. Click it to see what the app can read: programs and settings, partners and applications, clicks and leads, commissions and billing for a brand; the programs you joined, your links and clicks, your earnings and commissions, and your payouts for a partner. The screen also says **Money actions always happen in Affitor**. 6. Click **Allow**, or **Cancel** to refuse. A connection keeps the programs you chose. With **All current and future programs**, programs you join later are included; a selection stays as it is. To change it, connect again and choose again. --- ## Tools Every tool is read-only, and the server declares it so on each tool: `readOnlyHint: true`, `destructiveHint: false`, `idempotentHint: true`, `openWorldHint: false`. A brand connection gets the 8 brand tools across the programs it can read. A partner connection gets the 5 partner tools across that partner's programs it can read. Every tool takes an optional `program_id` to read one of those programs; `list_programs` lists them. A tool outside your connection's set is refused. ### Brand tools | Tool | What it reads | Inputs | |---|---|---| | `list_programs` | The programs this connection can read, in id order, up to 50 per page. | `program_id`, `limit`, `cursor` | | `get_program` | Each program, up to 25 per page: name, status, commission terms, setup checklist, 24-hour tracking counts, and the tracker install snippet with where to put it and how to verify it. | `program_id`, `programs_cursor` | | `list_partners` | Partners who joined, newest first, with lifetime clicks, leads and sales, and earned and pending money in the window. | `from`, `to`, `limit`, `cursor` | | `get_partner` | One partner by `partner_program_id`, with the same fields as `list_partners`. | `partner_program_id`, `from`, `to` | | `list_applications` | Partner applications, newest first, with the applicant's own messages. | `status` (`approved`, `pending`, `rejected`), `limit`, `cursor` | | `list_commissions` | Commissions, newest sale first, with what each still counts for after refunds. | `status`, `from`, `to`, `partner_program_id`, `limit`, `cursor` | | `get_commission_summary` | Count and amount of commissions per status in the window, plus earned and pending. | `from`, `to` | | `get_billing` | Affitor billing per program, up to 25 programs per page: what is due, this week's accrual, the platform fee and invoices, 20 per page. | `status` (`all`, `open`, `overdue`, `paid`, `void`), `page`, `program_id`, `programs_cursor` | ### Partner tools | Tool | What it reads | Inputs | |---|---|---| | `list_my_programs` | Programs you joined, newest first, with your commission terms, lifetime clicks, leads and sales, and your earned and pending money in the window. | `from`, `to`, `limit`, `cursor` | | `list_my_links` | Your referral links, newest first, with lifetime clicks, leads and sales. | `partner_program_id`, `status` (`active`, `inactive`), `limit`, `cursor` | | `get_my_earnings` | Your earnings per program and in total for the window: earned, ready, arriving, paid and pending. | `from`, `to` | | `list_my_commissions` | Your commissions across your programs, newest sale first. | `status`, `from`, `to`, `partner_program_id`, `limit`, `cursor` | | `list_my_payouts` | Your payout requests, newest first: amount, status, method type and dates. Payout account details, such as bank or Wise details, are never included. | `limit`, `cursor` | ### How results look - **Money** is an integer in an object keyed by unit, such as `{ "USD_cents": 4999 }` (`USD_cents`, `EUR_cents`, `VND_dong`), or in a `*_cents` field next to its currency (`get_billing`). - **Dates** are UTC sale dates, `YYYY-MM-DD`. `from` and `to` default to the last 30 days and cover at most 366 days. Commission lists cover all dates unless you give `from` or `to`. - **Pages** hold up to 50 items (`limit`, default 20). Pass `next_cursor` back as `cursor` for the next page. - **Links:** where an item has a `url`, it opens that page in the Affitor dashboard. Referral links come as `short_link` and `affiliate_url`. - **Commission statuses:** `pending`, `approved`, `invoiced`, `collected`, `paid`, `rejected`, `refunded`, `reversed`, `fraud`. - Each result comes as structured content and as JSON text that starts with a line saying the text fields are untrusted data, not instructions. --- ## Example prompts Brands: after you connect a coding agent (Claude Code, Cursor, Codex), give it this line to install the tracker. Replace example.com and 123 with your site and program id. For a brand connection: - "Who are my top partners by earned commission in the last 30 days?" (`list_partners`) - "Summarize the pending partner applications." (`list_applications`) - "How much commission is pending, approved and paid this month?" (`get_commission_summary`) - "What do we owe Affitor right now, and is any invoice overdue?" (`get_billing`) For a partner connection: - "How much did I earn this month across my programs, and how much is ready?" (`get_my_earnings`) - "Which of my links has the most sales?" (`list_my_links`) - "Show my last five payouts and their status." (`list_my_payouts`) The server cannot approve an application, change a commission, create a link or send a payout. Ask for any of these and the app finds no tool for it; do it in the dashboard. --- ## Limits and security | Limit | Value | |---|---| | Requests to `/mcp` | 120 per minute per connection, then `429` with `{ "error": "rate_limited" }` | | App registration | 300 per hour across all apps, then `429` with `{ "error": "rate_limited" }` | | Token requests | 60 per minute per app, and 600 per minute across all apps | | Access token | 1 hour, bound to `https://mcp.affitor.com/mcp` | | Refresh token | Rotates on every use, expires after 30 days | | Sign-in | Finish within 10 minutes of the page opening; each **Allow** is valid once, for 2 minutes | Each server instance keeps its own request counts in memory, so the request limits apply per instance. - **Read-only by design.** The only scope is `read`. There are no tools that write, delete or move money. - **Access is checked on every call.** A brand connection reads a program only while you are an active member of it; a partner connection, only while your partner account exists. A blocked account stops working at once. - **Only Affitor sign-in tokens work.** The server refuses program API keys, staff keys and dashboard sessions with `401`. Do not add an `Authorization` header with your API key. - **Untrusted text is marked.** Partner names, application messages and other free text are cut at 280 characters (the cut fields are listed in `truncated`), and every result says its text is data, not instructions. - **What is logged.** One row per tool call: the connection, the tool name, the program, the number of rows, whether it worked and how long it took. Never your prompts, the arguments or the results. These rows are deleted after 30 days. ### Remove access - **Brands:** program menu › **Program settings**, then **Developers** › **AI agents**, lists the program's connections under **Connections** with **Client**, **Connected by**, **Added**, **Last used** and **Access**. Click **Disconnect** on your own connection: the app loses every program in it. A program owner can click **Remove** on a member's connection: the app loses this program, and its other programs stay. - **Partners:** your name at the bottom of the left menu › **Integrations**, then **Disconnect**. **Disconnect** is immediate: the app's tokens are deleted and its next request gets `401`. After **Remove**, the app can no longer read that program. Removing the last available program from a selection ends the connection; an **All current and future programs** connection keeps its access to programs added later. --- ## Troubleshooting - **"This request has expired"** or **"This approval is no longer valid"**: the sign-in took too long. Start the connection again from your AI app. - **The app sees the wrong programs:** disconnect it and connect again, choosing the right ones. The install prompt above checks the program id for this reason. - **Signed in with the wrong account:** click **Switch** on the sign-in screen. - **"Too many rows for this window"**: ask for a shorter `from`/`to` window. - **`401` with "Program API keys are not accepted here"**: remove the `Authorization` header from your client's config and sign in instead. --- ## Legacy local server `@affitor/mcp` on npm is a separate **stdio** server that runs on your computer and uses your **program API key** (`AFFITOR_API_KEY`) instead of sign-in. It does tracking, not reporting: `affitor_readiness`, `affitor_track_click`, `affitor_track_lead`, `affitor_get_integration_plan` and `affitor_run_verification`, plus `affitor_track_sale` and `affitor_track_refund` only when you set `AFFITOR_MCP_WRITE=1`. The [Affitor plugin](https://github.com/Affitor/claude-plugins) for Claude Code and Gemini CLI (0.1.1 and later) connects to the hosted OAuth server with read access; this legacy local server is separate. For a coding project, use [Set up a coding agent](/docs/brand/cli/agent-setup) with CLI 0.4.5: ```bash npx affitor@0.4.8 agent setup --client claude_code --dry-run --json ``` The generated launcher keeps the program key out of MCP JSON and pins `@affitor/mcp@0.2.2`. It leaves sale/refund tools disabled. This local setup does not create a hosted OAuth connection or read account reports. Its `doctor` check is static; restart your client and call `affitor_readiness` to check the live session. Ask before running synthetic verification or other writes. Source and tool details: [Affitor CLI](https://github.com/Affitor/cli/tree/main/packages/mcp). --- ## Related - [CLI Quickstart](/docs/brand/cli/quickstart): `npx affitor init` writes `.affitor/AGENTS.md`, the instruction file coding agents follow to install tracking. - [Testing Integration](/docs/brand/tracking/testing-integration/): check that clicks, leads and sales arrive. - [CLI Command Reference](/docs/brand/cli/commands/): `npx affitor onboard` and the rest of the CLI. - [SDK Reference](/docs/api-reference/sdks/): the `@affitor/sdk` package. --- id: "api-reference/overview" type: "doc" url: "https://affitor.com/docs/api-reference/overview" kind: "reference" updated: "2026-11-08" --- # API Reference > Base URL, authentication, request/response envelope, and available endpoints for the Affitor Tracking API. The Affitor Tracking API lets your backend record affiliate events — clicks, signups, sales, and refunds — and retrieve program performance data. --- ## Base URL ```text https://api.affitor.com ``` All paths below are relative to this base. Strapi serves v1 routes under `/api`, so the full path for a tracking endpoint is: ```text https://api.affitor.com/api/v1/track/sale ``` :::note A machine-readable [OpenAPI 3.1 spec](https://affitor.com/docs/openapi.yaml) is available for the tracking endpoints — import it into Postman, Insomnia, code generators, or an AI coding agent. ::: --- ## Authentication Different endpoints use different auth modes. | Endpoint | Auth required | How to pass | |----------|--------------|-------------| | `POST /api/v1/track/click` | None | No token needed | | `POST /api/v1/track/lead` | Optional (server mode) | `Authorization: Bearer ` | | `POST /api/v1/track/sale` | Required | `Authorization: Bearer ` | | `POST /api/v1/track/refund` | Required | `Authorization: Bearer ` | Your **program API key** (`api_token`) is found in the Affitor dashboard under your program settings. ### Server mode vs browser mode (lead endpoint) `POST /api/v1/track/lead` supports two modes: - **Browser mode**: called by `affitor-tracker.js` from the customer's browser. No Bearer token. Attribution is proved by the `click_id` cookie value passed in the body. - **Server mode**: called from your backend. Include `Authorization: Bearer `. Send the `click_id` with your `customer_key`: a first lead with only `customer_key` answers `400`, because Affitor saves your key on the customer only when a lead settles. --- ## Response envelope All endpoints return JSON. A successful tracking call includes `"success": true`; the readiness endpoint returns its verdict object instead, with no `success` field. On an error, `error` is an object — never a plain string. **Success shape:** ```json { "success": true } ``` Sale and refund responses include additional IDs: ```json { "success": true, "sale_id": 42, "commission_id": 17, "message": "Sale tracked successfully" } ``` **Error shape:** ```json { "data": null, "error": { "status": 400, "name": "BadRequestError", "message": "transaction_id is required and must be a string", "details": {} } } ``` Read `error.message`, not `error` — interpolating the object prints `[object Object]`. The readiness endpoint uses a different envelope, and so does any endpoint refusing a key past its rotation deadline. Both shapes are laid out in the [error reference](/docs/api-reference/errors#error-response-shape). --- ## Endpoint families ### `/api/v1/track/*` — Tracking API (v1) The primary integration surface. Writes to the v1 event tables (`affiliate_click_events`, `affiliate_lead_events`, `affiliate_sale_events`). | Method | Path | Purpose | |--------|------|---------| | `POST` | `/api/v1/track/click` | Record an affiliate link click | | `POST` | `/api/v1/track/lead` | Record a customer signup | | `POST` | `/api/v1/track/sale` | Record a completed sale and create a commission | | `POST` | `/api/v1/track/refund` | Reverse the commission for a previously tracked sale | ### `/api/tracking/*` — Dashboard endpoints There is **no** `/api/tracking/` alias for click, lead, sale, or refund. The four `/api/v1/track/*` paths above are the only ones that accept tracking calls from your backend. The `/api/tracking/` paths that do exist back the Affitor dashboard, not a server-to-server integration. They authenticate with a signed-in dashboard session and require an active workspace membership on the program — taken from the path, or from `program_id` in the body on the two `POST` routes that have no path parameter. A Bearer program API key is not accepted on any of them: | Method | Path | Purpose | |--------|------|---------| | `GET` | `/api/tracking/status/:programId` | [Integration status](/docs/api-reference/status) for the program | | `GET` | `/api/tracking/events/:programId` | [Recent click, lead, and sale events](/docs/api-reference/events) | | `GET` | `/api/tracking/performance/:programId` | [Aggregated performance metrics](/docs/api-reference/performance) | | `GET` | `/api/tracking/readiness/:programId` | Readiness verdict for the program | | `POST` | `/api/tracking/test` | Create a test event from the dashboard verifier | | `POST` | `/api/tracking/check-test-events` | Check whether those test events landed | | `POST` | `/api/tracking/run-verification/:programId` | Run the synthetic click → lead → sale chain | To reach readiness from your own backend, call `GET /api/v1/programs/me/readiness` with your program API key instead — it derives the program from the key, so there is no program ID in the path. --- ## Test mode Pass `"additional_data": { "test_mode": true }` in a click, lead or sale request body to create a flagged test record without affecting real attribution or commission. Test records are marked `is_test: true` in the database. Refunds have no test mode. Details: [Test mode](/docs/api-reference/test-mode). --- ## Rate limits The `/api/v1/` endpoints listed in the [rate-limit table](/docs/api-reference/errors#rate-limits-429) have a per-minute limit: click and lead calls are counted per IP; sales, refunds, readiness and the CLI routes per Bearer token, falling back to IP when none is sent. Responses from those routes state the budget in `RateLimit-Policy` and `RateLimit` (plus the older `X-RateLimit-*` headers); over the limit they answer `429` with `Retry-After` and `retry_after_seconds`. The dashboard routes (`/api/tracking/...`) are not covered here. Limits per endpoint: [Rate limits (429)](/docs/api-reference/errors#rate-limits-429). --- ## Endpoint pages Record an affiliate link click and create the customer attribution relationship. Record a customer signup and link it to a prior click. Record a completed sale, create a commission, and update program metrics. Reverse the commission for a sale that was refunded. Check program integration status and health. Retrieve click, lead, and sale event records for a program. Retrieve aggregated performance metrics for a program. --- id: "api-reference/performance" type: "doc" url: "https://affitor.com/docs/api-reference/performance" kind: "reference" updated: "2026-10-16" --- # GET /tracking/performance/:programId > Retrieve daily performance aggregates and period-over-period trend metrics for a program Returns daily aggregated metrics (clicks, leads, conversions, revenue, partners, commissions) for a program, along with period-over-period trend comparisons. This endpoint is used by the Affitor dashboard performance chart. --- ## Endpoint `GET /api/tracking/performance/:programId` --- ## Authentication Requests must be authenticated. The authenticated user must be an active workspace member of the requested program. | Header | Value | |--------|-------| | `Authorization` | Session token (Affitor dashboard session) | An unauthenticated request, a request from a user who is not an active workspace member of the program, and a request for a program that does not exist all return `403`. :::note This endpoint backs the Affitor dashboard. It accepts only a signed-in dashboard session for a workspace member of the program and does not accept a program API key (`aff_…`), so you cannot call it from a server integration with your API key. ::: --- ## Path Parameter | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `programId` | integer | Yes | ID of the affiliate program | --- ## Query Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `period` | string | No | Preset time window. One of `7d`, `30d`, `90d`, `all`. Defaults to `7d`. Ignored when `dateFrom` and `dateTo` are provided. | | `dateFrom` | string (ISO 8601) | No | Start of a custom date range. Must be used together with `dateTo`. | | `dateTo` | string (ISO 8601) | No | End of a custom date range. Must be used together with `dateFrom`. | When `dateFrom` and `dateTo` are both present, the `period` parameter is ignored. The previous comparison period is automatically calculated as an equal-length window immediately before the custom range. --- ## Response HTTP `200` with the following shape: ```json { "data": [ { "date": "2024-05-31", "period": "2024-05-31", "clicks": 42, "leads": 5, "conversions": 2, "revenue": 199.98, "partners": 1, "sales": 0, "commission": 20.00 }, { "date": "2024-06-01", "period": "2024-06-01", "clicks": 18, "leads": 2, "conversions": 0, "revenue": 0.00, "partners": 0, "sales": 0, "commission": 0.00 } ], "metrics": { "totalClicks": 60, "totalLeads": 7, "totalConversions": 2, "totalRevenue": 199.98, "conversionRate": 3.33, "averageOrderValue": 99.99, "totalPartners": 1, "totalSales": 2, "totalPartnersCommission": 20.00, "clicksTrend": { "trend": 15.4, "trendDirection": "up", "previous": 52 }, "leadsTrend": { "trend": 0, "trendDirection": "stable", "previous": 7 }, "conversionsTrend": { "trend": null, "trendDirection": "up", "previous": 0 }, "revenueTrend": { "trend": null, "trendDirection": "up", "previous": 0 }, "partnersTrend": { "trend": 0, "trendDirection": "stable", "previous": 1 }, "salesTrend": { "trend": null, "trendDirection": "up", "previous": 0 }, "commissionTrend": { "trend": null, "trendDirection": "up", "previous": 0 } }, "meta": { "period": "7d", "dateFrom": "2024-05-25T00:00:00.000Z", "dateTo": "2024-06-01T23:59:59.999Z", "previousPeriod": { "dateFrom": "2024-05-18T00:00:00.000Z", "dateTo": "2024-05-24T23:59:59.999Z" } } } ``` ### `data` array Each entry covers one calendar day within the requested range. Days with no activity are included with all counts set to `0`. | Field | Type | Description | |-------|------|-------------| | `date` | string (YYYY-MM-DD) | Calendar date for the row | | `period` | string (YYYY-MM-DD) | Same value as `date` | | `clicks` | integer | Real (non-test) affiliate click events on this date | | `leads` | integer | Customers whose `signup_date` falls on this date and whose status is `lead` or `conversion` | | `conversions` | integer | Customers whose `first_purchase_date` falls on this date and whose status is `conversion` | | `revenue` | number | Total sale revenue in dollars from paid sale events on this date | | `partners` | integer | Partner-program records created on this date | | `sales` | integer | Always `0` (Affitor Pay checkout removed; revenue comes from sale events) | | `commission` | number | Total commission amount in dollars for commissions created on this date | ### `metrics` object Aggregated totals and trend comparisons for the full requested period. | Field | Type | Description | |-------|------|-------------| | `totalClicks` | integer | Total real click events in the period | | `totalLeads` | integer | Total lead-status customers in the period | | `totalConversions` | integer | Total conversion-status customers in the period | | `totalRevenue` | number | Total revenue in dollars (rounded to 2 decimal places) | | `conversionRate` | number | `(totalConversions / totalClicks) * 100`, rounded to 2 decimal places. `0` if no clicks. | | `averageOrderValue` | number | `totalRevenue / totalConversions`, rounded to 2 decimal places. `0` if no conversions. | | `totalPartners` | integer | Total partner-program records created in the period | | `totalSales` | integer | Total paid sale events in the period | | `totalPartnersCommission` | number | Total commission amount in dollars (rounded to 2 decimal places) | | `clicksTrend` | object | Trend vs previous equal-length period (see below) | | `leadsTrend` | object | Trend for leads | | `conversionsTrend` | object | Trend for conversions | | `revenueTrend` | object | Trend for revenue | | `partnersTrend` | object | Trend for partners | | `salesTrend` | object | Trend for sale count | | `commissionTrend` | object | Trend for commission amount | Each trend object: | Field | Type | Description | |-------|------|-------------| | `trend` | number or null | Absolute percentage change, rounded to 1 decimal place. `null` when the previous period is `0` and the current one is not | | `trendDirection` | string | `"up"`, `"down"`, or `"stable"` | | `previous` | number | The same metric's value in the previous period | Growth from nothing has no percentage. When the previous period value is `0` and the current value is greater than `0`, `trend` is `null` and `trendDirection` is `"up"`; use `previous` to show it as new. When both are `0`, `trend` is `0` and `trendDirection` is `"stable"`. A change that rounds to `0.0` is `"stable"`. ### `meta` object | Field | Type | Description | |-------|------|-------------| | `period` | string | The `period` query param value used (`"7d"` when none is sent) | | `dateFrom` | string (ISO 8601) | Actual start of the current period used in the query | | `dateTo` | string (ISO 8601) | Actual end of the current period used in the query | | `previousPeriod.dateFrom` | string (ISO 8601) | Start of the comparison period | | `previousPeriod.dateTo` | string (ISO 8601) | End of the comparison period | --- ## Errors | Status | When | |--------|------| | `403 Forbidden` | No signed-in session, the user is not an active workspace member of `programId`, or the program does not exist | | `500 Internal Server Error` | Unexpected server error | --- id: "api-reference/sdks" type: "doc" url: "https://affitor.com/docs/api-reference/sdks" kind: "reference" updated: "2026-11-08" --- # SDKs > Typed client libraries for browser tracking (@affitor/sdk) and server-side conversion reporting (@affitor/sdk/server). > **Beta**: the @affitor/sdk package and CLI are in active development. The documented happy-path works; edge cases may change. Report issues on GitHub. One package covers the full attribution chain via subpaths: the browser entry captures clicks and leads on the frontend; the `/server` entry reports conversions from your backend. Browser SDK: captures affiliate clicks, persists attribution in a first-party cookie, and reports lead events. Node SDK: reports leads, sales, clicks, and refunds from your backend with Bearer auth. --- ## @affitor/sdk (Browser) SSR-safe typed npm wrapper over the Affitor tracking endpoints. Captures `?aff=` (or `?via=`) attribution, persists a `affitor_click_id` first-party cookie (60-day default), and reports click and lead events. All methods are no-ops on the server, so it is safe to import in Next.js and other SSR frameworks without guards. ### Install ```bash npm install @affitor/sdk ``` Or include the script tag directly: ```html ``` ### Quick start ```ts import { loadAffitor } from '@affitor/sdk'; // On app load (client-side; resolves to null on the server) const affitor = await loadAffitor(123); // After the user completes signup await affitor?.signup('user_abc123', 'user@example.com'); ``` `loadAffitor` loads the tracker script once and resolves to the same instance on every later call. The tracker captures `?aff=` (or `?via=`) from the URL and sets the click id cookie by itself. The tracker sends events to `https://api.affitor.com`. To send them to a non-production API, set `window.AFFITOR_API_BASE = ''` before the first `loadAffitor` call, or use the script tag with `data-affitor-api-base`. --- ### `loadAffitor(programId, options?)` | Option | Type | Default | Description | |--------|------|---------|-------------| | `env` | `'production' \| 'local'` | `'production'` | Selects the tracker script URL. | | `scriptUrl` | `string` | none | Custom tracker script URL; overrides `env`. It only chooses where the script loads from. | | `debug` | `boolean` | `false` | For testing only: logs `info` and `warn` messages, and makes `signup()` send a [test event](/docs/api-reference/test-mode) instead of a lead, so no real lead is recorded. Turn it off before production. Errors always log. | --- ### Instance methods | Method | Signature | Description | |--------|-----------|-------------| | `signup` | `(customerKey: string, email: string) => Promise` | Report a lead (signup). Pass your internal user id as `customerKey`. | | `getClickId` | `() => string \| null` | The current click id from memory or the `affitor_click_id` cookie. | | `getVisitorId` | `() => string \| null` | The visitor id from Affitor's first-party cookie, or `null`. Put it in checkout metadata as `affitor_visitor_id`. With consent mode on, call it after `consent(true)`. | | `consent` | `(granted: boolean) => void` | With `data-affitor-consent="required"` on the script, nothing is stored or sent until `consent(true)`; `consent(false)` removes Affitor's cookies. | | `getData` | `() => AffitorData` | A snapshot of tracker state. | | `trackTest` | `(data?) => void` | Send a test event. | | `init` | `(options: { programId?: string \| number; debug?: boolean }) => void` | Starts the tracker. It runs on its own when the script loads (through `loadAffitor` or the script tag), so you do not need to call it. | | `trackLead` | `(data: TrackLeadData) => Promise` | Deprecated: use `signup`. Older alias that calls `signup` with the object's `customer_key` (or `user_id`) and `email`. | > `signup()` requires `customerKey`, your own user id. By default a browser `signup()` records a provisional lead, which does not bind your customer key to the customer record for later sale matching (the Lead tracking section shows "Browser leads: server/payment confirmation required"). Until the key is stored on a customer (by a server-verified lead or an attributed Stripe payment), a backend sale that sends only `customerExternalId` finds no customer and is refused with `400` `Customer not found`. Send the lead from your server as well (`trackLead` with `customerExternalId` and `clickId`), or pass `clickId` with the sale. ### `AffitorData` Returned by `getData()`. | Field | Type | Description | |-------|------|-------------| | `clickId` | `string \| null` | The active `affitor_click_id` (in memory or from the cookie). | | `programId` | `number` | The resolved program id. | | `hasAttribution` | `boolean` | `true` when a valid click has been tracked. | | `affiliateUrl` | `string \| null` | The affiliate URL that started the current attribution. | --- ### Full example (Next.js) ```tsx // app/affitor-tracker.tsx: client component 'use client'; import { useEffect } from 'react'; import { loadAffitor } from '@affitor/sdk'; export function AffitorTracker() { useEffect(() => { void loadAffitor(YOUR_PROGRAM_ID); }, []); return null; } // render once in app/layout.tsx ``` After a successful signup, call `signup(customerKey, email)` on the instance (or `window.affitor.signup(...)` for the script-tag path): ```ts import { loadAffitor } from '@affitor/sdk'; const affitor = await loadAffitor(YOUR_PROGRAM_ID); await affitor?.signup(userId, email); ``` React apps can also use `AffitorProvider` and `useAffitor()` from `@affitor/sdk/react`. `@affitor/sdk/pure` exports `loadAffitor` and the types `AffitorInstance`, `AffitorInitOptions`, `TrackSignupData`, `TrackLeadData` and `TrackTestData`. `@affitor/sdk` exports the same, plus the option types `AffitorEnv` and `LoadAffitorOptions`. Both inject the tracker script only when `loadAffitor()` runs; importing from `/pure` makes that explicit. --- ## @affitor/sdk/server (Server) Typed, Bearer-authenticated client over the Affitor conversion API. Use this from your backend to report leads, sales, and refunds for any payment provider (Stripe, Polar, Lemon Squeezy, Paddle, etc.). **Never ship the program API key to the browser.** ### Install ```bash npm install @affitor/sdk ``` ### Quick start ```ts import Affitor from '@affitor/sdk/server'; const affitor = new Affitor({ apiKey: process.env.AFFITOR_API_KEY! }); // On user signup: bind the customer to their affiliate click await affitor.trackLead({ customerExternalId: user.id, clickId }); // On payment success: report the sale await affitor.trackSale({ customerExternalId: user.id, amount: 4999, // cents invoiceId: inv.id, // idempotency key }); ``` --- ### `AffitorOptions` Constructor options for `new Affitor(opts)`. | Field | Type | Required | Description | |-------|------|----------|-------------| | `apiKey` | `string` | **Yes** | Program API key (Bearer). Find it in your Affitor dashboard under program settings. | | `apiUrl` | `string` | No | Override the API base URL. Defaults to `https://api.affitor.com`. | | `fetch` | `typeof fetch` | No | Custom fetch implementation. Required for Node versions below 18 that lack a global `fetch`. | --- ### `AffitorResponse` The `track*` methods return `Promise>`. [`readiness()`](#readinessopts) returns the verdict itself. | Field | Type | Description | |-------|------|-------------| | `ok` | `boolean` | `true` when the HTTP status was 2xx. | | `status` | `number` | HTTP status code. `0` on network error. | | `data` | `T \| null` | Parsed response body when `ok` is `true`; `null` on error. | | `error` | `string \| undefined` | Error message or HTTP status text when `ok` is `false`. | --- ### Methods #### `trackLead(input: TrackLeadInput)` Binds `customerExternalId` to `clickId`. Once bound, later `trackSale` calls need only `customerExternalId`, no click id required. The SDK throws synchronously only when both `customerExternalId` and `clickId` are missing. Send `clickId` on every lead: Affitor finds the customer through the click. A first lead with only `customerExternalId` returns `ok: false` with status `400` (`Customer not found. Provide a valid click_id or customer_key.`). | Field | Type | Required | Description | |-------|------|----------|-------------| | `customerExternalId` | `string` | Conditional | Your own user id. Binds the customer to the click for downstream sale attribution. | | `clickId` | `string` | Conditional | `affitor_click_id` cookie value from the browser. Send it on every lead. | | `email` | `string` | No | Customer email (hashed server-side). | | `eventName` | `string` | No | Custom event label for segmentation. | | `additionalData` | `Record` | No | Arbitrary metadata passed through to the event record. | --- #### `trackSale(input: TrackSaleInput)` Records a completed sale and creates a commission. Resolves attribution by `customerExternalId` first, then `clickId`. Idempotent by `invoiceId`. At least one of `customerExternalId` or `clickId` is required, and `amount` must be a positive integer. Both `amount` and `invoiceId` throw synchronously if invalid. | Field | Type | Required | Description | |-------|------|----------|-------------| | `customerExternalId` | `string` | Conditional | Your own user id. It resolves attribution when it matches a key already stored on a customer in your program, for example by a server-verified lead or an attributed Stripe payment. | | `clickId` | `string` | Conditional | `affitor_click_id` cookie value (fallback if no prior lead). | | `amount` | `number` | **Yes** | Sale amount as an integer in the currency's [minor unit](/docs/api-reference/track-sale#minor-units-and-conversion): cents for USD (`4999` = $49.99), whole units for JPY or VND. | | `taxCents` | `number` | No | The tax included in `amount`, same unit. Commissions are calculated on `amount - taxCents`. Requires `@affitor/sdk` 2.1.2 or later. | | `invoiceId` | `string` | **Yes** | Unique invoice or transaction id, used as an idempotency key to deduplicate retries. | | `currency` | `string` | No | A [supported ISO 4217 code](/docs/api-reference/track-sale#request-fields); another code returns `422`. Defaults to `USD`. Commissions and platform fees are calculated on the pre-tax amount [converted to USD](/docs/api-reference/track-sale#minor-units-and-conversion), and invoices are issued in USD. | | `saleType` | `'payment' \| 'subscription'` | No | Categorize the sale type. | | `isRecurring` | `boolean` | No | `true` for recurring subscription charges. | | `subscriptionId` | `string` | No | External subscription id from your payment provider. | | `subscriptionInterval` | `'monthly' \| 'quarterly' \| 'annual'` | No | Billing cadence for subscription sales. | | `eventName` | `string` | No | Custom event label for segmentation. | --- #### `trackClick(input?: TrackClickInput)` Track a click server-side. Click tracking is usually handled in the browser by `@affitor/sdk`; use this only for server-rendered flows or redirect-based affiliate links. This endpoint does not require authentication. | Field | Type | Required | Description | |-------|------|----------|-------------| | `affiliateUrl` | `string` | No | The full affiliate URL containing the `?aff=` or `?via=` parameter. | | `pageUrl` | `string` | No | The landing page URL. | | `referrerUrl` | `string` | No | The HTTP referrer. | | `existingClickId` | `string` | No | An existing click id. Affitor reuses the customer that has this click id, so that customer's partner does not change. `trackClick` sends no `program_id`, so this lookup is not limited to one program. When no customer has the click id, a new customer is created with it. | --- #### `trackRefund(input: TrackRefundInput)` Reverses the commission for a previously tracked sale. Call it once per refund, from your payment provider's refund webhook. - Omit `refundAmountCents` to refund everything not yet refunded → commission status set to `reversed`. Do not pass `0`: for a sale recorded from November 5, 2026 (16:00 UTC) with a commission to reverse, it answers `400` and nothing is refunded. - Pass **this refund's own amount** → it is added to what was already refunded on the sale. Once the total reaches the sale amount, the commission is `reversed`. Before that, a partial refund reduces a commission already approved and cancels one still `pending` (in its hold period, not yet approved); both end `refunded`. - Do not pass a running total (such as Stripe's `charge.amount_refunded`): each call with a new amount is added as a new refund. - A retry with the same amount is ignored. To report two separate refunds of the same amount, call the [HTTP endpoint](/docs/api-reference/track-refund) with a distinct `refund_id` for each. `invoiceId` is required and throws synchronously if missing. | Field | Type | Required | Description | |-------|------|----------|-------------| | `invoiceId` | `string` | **Yes** | The `invoiceId` you passed to `trackSale`; identifies which sale to refund. | | `refundAmountCents` | `number` | No | This refund's amount in the sale currency's minor unit (not the running total). Omit it to refund the rest of the sale; do not pass `0`. | | `refundReason` | `string` | No | Optional reason string passed through to the refund record. | --- #### `readiness(opts?)` Returns the program's readiness verdict from `GET /api/v1/programs/me/readiness`; the program comes from the API key. Pass `{ forceRecheck: true }` (`?force_recheck=true`) to check your site for the tracker again instead of using the cached result; a forced check runs at most once per minute per program. It resolves to the verdict object (`ReadinessResult`: `state`, `integration_verified`, `blocker`, `gates`, and more), not an `AffitorResponse`, and throws `AffitorApiError` (with `status`, `code` and `retryAfterSeconds`) on a non-2xx response. --- ### Full example (Stripe webhook) ```ts import Stripe from 'stripe'; import Affitor from '@affitor/sdk/server'; const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!); const affitor = new Affitor({ apiKey: process.env.AFFITOR_API_KEY! }); // The Tracking API reads ISO 4217 minor units. Stripe uses the same units except ISK and UGX // (sent with two extra decimals) and MGA (sent with none), so convert those three. function toIsoMinor(amount: number, currency: string): number { if (currency === 'isk' || currency === 'ugx') return amount / 100; return currency === 'mga' ? amount * 100 : amount; } // POST /webhooks/stripe export async function handleStripeWebhook(rawBody: Buffer, sig: string) { const event = stripe.webhooks.constructEvent( rawBody, sig, process.env.STRIPE_WEBHOOK_SECRET! ); if (event.type === 'checkout.session.completed') { const session = event.data.object as Stripe.Checkout.Session; const result = await affitor.trackSale({ customerExternalId: session.client_reference_id ?? undefined, amount: toIsoMinor(session.amount_total ?? 0, session.currency ?? 'usd'), invoiceId: session.payment_intent as string, currency: session.currency?.toUpperCase(), saleType: 'payment', }); if (!result.ok) { console.error('Affitor trackSale failed:', result.error); } } // One event per refund, carrying that refund's own amount. if (event.type === 'refund.created') { const refund = event.data.object as Stripe.Refund; await affitor.trackRefund({ invoiceId: refund.payment_intent as string, refundAmountCents: toIsoMinor(refund.amount, refund.currency), }); } } ``` --- ## Related - [Track Click](/docs/api-reference/track-click): raw HTTP endpoint reference - [Track Lead](/docs/api-reference/track-lead): raw HTTP endpoint reference - [Track Sale](/docs/api-reference/track-sale): raw HTTP endpoint reference - [Track Refund](/docs/api-reference/track-refund): raw HTTP endpoint reference - [Lead Tracking Guide](/docs/brand/tracking/lead-tracking-signup): implementation walkthrough --- id: "api-reference/status" type: "doc" url: "https://affitor.com/docs/api-reference/status" kind: "reference" updated: "2026-09-24" --- # Get Tracking Status > Returns integration step statuses and Stripe connection info for a program Retrieves the integration health of a program: whether each of the three setup steps (pageview, referrals, payments) is complete, a summary of recent test events for each step, and the connected Stripe account details. --- ## Endpoint `GET /api/tracking/status/:programId` --- ## Authentication This endpoint is protected by the `verify-program-access` workspace policy. The caller must be an authenticated dashboard user with `tracking:read` permission on the program. No Bearer API key is used. :::note This endpoint backs the Affitor dashboard. It accepts only a signed-in dashboard session for a workspace member of the program and does not accept a program API key (`aff_…`), so you cannot call it from a server integration with your API key. ::: --- ## Path Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `programId` | integer | Yes | The numeric ID of the affiliate program | --- ## Response ```json { "data": { "programId": "42", "stepStatuses": { "pageview": "complete", "referrals": "pending", "payments": "complete" }, "statistics": { "pageview": { "testEventCount": 3, "hasTestEvents": true, "latestTestEvent": { "id": 101, "timestamp": "2026-06-07T10:23:45.000Z", "createdAt": "2026-06-07T10:23:45.000Z" } }, "referrals": { "testEventCount": 0, "hasTestEvents": false, "latestTestEvent": null }, "payments": { "paymentTrackingMode": "stripe_connect", "methodReady": true, "stripeConnectionStatus": "connected", "isStripeConnected": true, "stripeAccountId": "acct_1AbCdEfGhIjKlMnO", "chargesEnabled": true, "payoutsEnabled": true, "detailsSubmitted": true, "connectionDate": "2026-05-01T08:00:00.000Z" } }, "hasPartners": true, "lastUpdated": "2026-06-08T12:00:00.000Z" } } ``` ### Response fields | Field | Type | Description | |-------|------|-------------| | `data.programId` | string | The program ID from the URL path | | `data.stepStatuses` | object | Status of each integration step: `"complete"` or `"pending"` | | `data.stepStatuses.pageview` | string | `"complete"` when at least one test click event exists for the program | | `data.stepStatuses.referrals` | string | `"complete"` when at least one test lead event exists for the program | | `data.stepStatuses.payments` | string | `"complete"` when the program's Stripe connection `stripeConnectionStatus` is `"connected"`, **or** when the program uses server-to-server sale tracking (`paymentTrackingMode` is `"s2s"`) | | `data.statistics.pageview.testEventCount` | integer | Number of test click events found (up to 10) | | `data.statistics.pageview.hasTestEvents` | boolean | `true` if at least one test click event exists | | `data.statistics.pageview.latestTestEvent` | object \| null | ID and timestamps of the most recent test click event | | `data.statistics.referrals.testEventCount` | integer | Number of test lead events found (up to 10) | | `data.statistics.referrals.hasTestEvents` | boolean | `true` if at least one test lead event exists | | `data.statistics.referrals.latestTestEvent` | object \| null | ID and timestamps of the most recent test lead event | | `data.statistics.payments.paymentTrackingMode` | string | `"stripe_connect"` (default) or `"s2s"` | | `data.statistics.payments.methodReady` | boolean | `true` when the payments step is complete | | `data.statistics.payments.stripeConnectionStatus` | string | Raw Stripe connection status of the program | | `data.statistics.payments.isStripeConnected` | boolean | `true` when `stripeConnectionStatus === "connected"` | | `data.statistics.payments.stripeAccountId` | string \| null | Stripe connected account ID (`acct_...`), or `null` if not connected | | `data.statistics.payments.chargesEnabled` | boolean | Whether the Stripe account can accept charges | | `data.statistics.payments.payoutsEnabled` | boolean | Whether the Stripe account can receive payouts | | `data.statistics.payments.detailsSubmitted` | boolean | Whether Stripe onboarding details have been submitted | | `data.statistics.payments.connectionDate` | string \| null | ISO timestamp of when Stripe was connected, or `null` | | `data.hasPartners` | boolean | `true` when at least one approved partner-program record exists for this program | | `data.lastUpdated` | string | ISO timestamp of when this response was generated | --- ## Errors | Status | When | |--------|------| | 404 | `programId` does not match any affiliate program | | 500 | Internal server error while querying step data | --- id: "api-reference/test-mode" type: "doc" url: "https://affitor.com/docs/api-reference/test-mode" kind: "concept" updated: "2026-11-07" --- # Test mode > How to send test clicks, leads and sales to the Tracking API with your real program API key, what a test event records, and what it never touches. Test mode lets you, or an AI agent, call the Tracking API against production with your real program API key and get real responses, without creating a real sale, commission or platform fee. There is no separate test server or test account: you send the same requests to `https://api.affitor.com` and mark them as test. --- ## Turn it on Add `"test_mode": true` inside `additional_data` on a click, lead or sale request. ```bash # Replace $AFFITOR_API_KEY with your program API key (Program settings > API keys). curl -X POST https://api.affitor.com/api/v1/track/sale \ -H "Authorization: Bearer $AFFITOR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "additional_data": { "test_mode": true } }' ``` ```json { "success": true, "message": "Test sale event tracked successfully", "data": { "eventId": 1234, "programId": 42, "test_mode": true } } ``` On a sale, `"livemode": false` does the same thing as `test_mode`. `"livemode": true` does not turn test mode off. | Endpoint | Test mode | Key | |---|---|---| | [`POST /api/v1/track/click`](/docs/api-reference/track-click) | `additional_data.test_mode` | Optional. Without a key, send `additional_data.program_id` so the event is linked to your program. | | [`POST /api/v1/track/lead`](/docs/api-reference/track-lead) | `additional_data.test_mode` | Optional, as for clicks. A key that is sent must be valid, or the call returns `401`. | | [`POST /api/v1/track/sale`](/docs/api-reference/track-sale) | `additional_data.test_mode` or `livemode: false` | Required. An invalid key returns `401`, in test mode too. | | [`POST /api/v1/track/refund`](/docs/api-reference/track-refund) | None: `test_mode` in the body is ignored | Required. A refund sent with your program API key is processed as a real refund, so `test_mode` does not protect a real commission. The outcomes are listed on [Track a refund](/docs/api-reference/track-refund). | ## What a test event records Each successful test call stores one event flagged `is_test: true` and answers with `test_mode: true` and the new `eventId`. - **Click:** a test click event. `affiliate_url` is not required. - **Lead:** a test lead event. `click_id` and `customer_key` are optional (placeholders are stored when they are missing). - **Sale:** a test sale event. `transaction_id` and `amount_cents` are optional (`amount_cents` defaults to `9999`). A test sale accepts the same [currency codes](/docs/api-reference/track-sale#request-fields) as a live sale (`422 unsupported_currency` otherwise). Sending the same `transaction_id` twice returns `409 duplicate_transaction`, as for a real sale. A test event is inserted directly. It does not resolve a partner, so it creates no commission and no platform fee, and it never takes over a real customer's attribution. Test sales are also left out of your revenue analytics. Test clicks and leads count toward your setup checklist: they are how the script and signup checks pass. When the request carries your program API key, it also starts a recalculation of your program's integration status in the background. The response does not wait for it, so the checklist can update a moment later. A test event sent without a key does not trigger it. A test sale never counts as your first real sale. ## Test the whole chain A successful test sale proves your key authenticates, because the sale endpoint refuses a missing or unknown key. A test click or lead can succeed without a valid key, so it proves only that the event was recorded. No single test event proves attribution. To run a synthetic click, signup and sale through the real attribution and commission pipeline, use one of: - `npx affitor onboard`, which runs the chain and then polls readiness ([CLI commands](/docs/brand/cli/commands)) - the MCP tools `affitor_run_verification`, then `affitor_readiness` - **Run check** on the **Payments** step of program setup The steps and limits are in [Testing your integration](/docs/brand/tracking/testing-integration). To send one test event from the terminal: `npx affitor test click`, `lead` or `sale`. ## Going live Remove `test_mode` (and `livemode: false`). Live calls use the same key and the same endpoints. A live sale needs a `transaction_id`, a positive `amount_cents` and a customer that already carries attribution: see [Track a sale](/docs/api-reference/track-sale). --- id: "api-reference/track-click" type: "doc" url: "https://affitor.com/docs/api-reference/track-click" kind: "reference" updated: "2026-11-07" --- # Track Click > Record an affiliate click event when a visitor lands via a referral link `POST /api/v1/track/click` records an affiliate click event from the Affitor tracker script. It resolves the referral link from the `?aff=` parameter (or its alias `?via=`; `aff` wins when both are present), creates or reuses the customer record, and returns the `click_id` that downstream lead and sale calls will use for attribution. This endpoint is called automatically by `affitor-tracker.js`. You only need to call it directly if you are building a custom tracker integration. --- ## Auth No API key is required. This endpoint is public — the referral link embedded in `affiliate_url` is the only credential needed. --- ## Request `POST https://api.affitor.com/api/v1/track/click` Full URL including the `?aff=` or `?via=` query parameter, e.g. `https://yoursite.com?aff=PARTNER123` Canonical page URL where the click occurred. `document.title` at time of click. `document.referrer` — where the visitor came from. Browser session identifier. User agent string; falls back to the HTTP `User-Agent` header. Screen dimensions, e.g. `1920x1080`. Browser viewport dimensions, e.g. `1280x800`. Browser language code, e.g. `en-US`. IANA timezone string, e.g. `America/New_York`. The `click_id` stored for this visitor (the tracker sends it when the visitor comes back through another partner's link). A customer that already has this click ID is reused and keeps its first partner; the click is still recorded for the new partner. With `program_id`, a click ID whose customer belongs to another program is not reused, and the click gets a new click ID and customer. When no customer has the click ID, a new customer is created with it. The program of the page (the tracker sends it). A numeric string such as `"42"` is accepted. When sent, the `aff` code is looked up only inside this program, and an id that is not a program returns `400` `Unknown program_id`. Without it, the lookup covers every program. Your visitor's IP address, when your server records the click for that visitor. Used for the click's location only when the request carries the Bearer API key of the program the link belongs to (not a key past its rotation deadline) and the value is an IP address; otherwise the request's own IP is used. It never causes the click to be refused. Pass `{"test_mode": true, "program_id": 1}` to create a test event that does not affect production attribution. ### Example request body --- ## Response ### Success ```json { "success": true, "click_id": "cust_42_1715000000000", "partner_code": "PARTNER123", "cookie_window_days": 60 } ``` | Field | Type | Description | |-------|------|-------------| | `success` | `boolean` | `true` on success | | `click_id` | `string` | Unique identifier for this click/customer relationship — store in a first-party cookie and pass to lead/sale calls | | `partner_code` | `string` | The short partner code resolved from the referral link | | `cookie_window_days` | `number` | Attribution window in days set by the program; `click_id` remains valid for this many days | ### Test mode response When `additional_data.test_mode` is `true`: ```json { "success": true, "message": "Test click event tracked successfully", "data": { "eventId": 101, "programId": 1, "test_mode": true } } ``` --- ## Errors | Status | Condition | |--------|-----------| | `400 Bad Request` | `affiliate_url` is missing | | `400 Bad Request` | `affiliate_url` cannot be parsed as a URL | | `400 Bad Request` | No `?aff=` or `?via=` parameter found in `affiliate_url` | | `400 Bad Request` | `program_id` was sent but is not a program (`Unknown program_id`) | | `400 Bad Request` | No referral link found matching the `aff` value | | `400 Bad Request` | Referral link configuration is invalid (missing partner or program) | | `403 Forbidden` | Test mode only: the Bearer key and `additional_data.program_id` name different programs (`program_id does not match the API key`) | | `410 Gone` | The referral link is turned off, or its program is not active (for example a draft or paused program). Body has `error.code: link_disabled`; no click is recorded | | `500 Internal Server Error` | Unexpected server error | --- ## What happens on success 1. The `aff` value is extracted from `affiliate_url` and matched to a referral link. 2. If `existing_click_id` is provided and a customer already has that click ID, that customer is reused and keeps its first partner. The exception: when `program_id` is sent and that customer belongs to another program, it is not reused and a new click ID is generated. When no customer is reused, a new customer record is created with `customer_status: click` under the returned `click_id`. 3. A click event is created in `affiliate_click_events` with geo, device, and browser data derived server-side. 4. The referral link's `clicks` counter and `last_clicked` timestamp are updated. 5. The partner-program click metrics are incremented. 6. `click_id`, `partner_code`, and `cookie_window_days` are returned for the caller to store in a cookie. --- ## Next steps After a click is tracked: - [Lead Tracking](/docs/brand/tracking/lead-tracking-signup/) — identify the customer when they sign up - [Payment Tracking](/docs/brand/tracking/payment-tracking-stripe/) — record a sale against the same customer - [Testing Integration](/docs/brand/tracking/testing-integration/) — verify the full flow end-to-end --- id: "api-reference/track-lead" type: "doc" url: "https://affitor.com/docs/api-reference/track-lead" kind: "reference" updated: "2026-11-07" --- # Track Lead > Record a signup or lead event that links a customer to an affiliate click. `POST /api/v1/track/lead` Records a lead event for a customer who signed up through an affiliate referral. Call this after a successful registration so Affitor can advance the attribution chain from click → lead. --- ## Authentication | Mode | When to use | How | |------|-------------|-----| | **Server mode** (recommended) | Your backend calls the API after a signup | `Authorization: Bearer ` | | **Browser mode** | The tracker's `signup()` call from the page | No `Authorization` header — the call carries only the `click_id` | The mode is decided by the header: a request with a valid Bearer key is server mode, and a request without one is browser mode. In server mode, Affitor validates the key and checks that the customer belongs to that program. ### Lead auth policy Each program has a lead auth policy. **Every program requires server-verified leads** (`server_required`) unless it is explicitly set to allow browser leads (`browser_allowed`). Under `server_required`, a browser-mode lead is recorded as **provisional**: - the API still returns `200`, with `provisional: true` in the body - the lead does not settle attribution, does not save your `customer_key` on the customer, and does not count in partner metrics or pay a per-lead commission - it settles only when your backend sends the same lead with a Bearer key, or when a Stripe Checkout payment for that customer arrives through your connected Stripe account. A sale sent to `/api/v1/track/sale` does not settle it, and a Bearer lead sent after that sale returns `400` A browser lead settles directly only on a program set to `browser_allowed`. A browser lead that did not settle answers `200` with `"provisional": true`. Send leads from your server with a Bearer key so the lead settles under either policy. --- ## Request ### Headers `Bearer ` — send it for server mode. Without it, the call is treated as browser mode. Must be `application/json`. ### Body fields The `affitor_click_id` value from the affiliate click cookie. Send it on every lead outside test mode: Affitor finds the customer through the click. Your internal customer or user ID. Send it with the `click_id`: when the lead settles, Affitor saves it on that customer, so later sales can find the customer by your own id. On its own it finds no customer on a first lead, because the key is saved only when a lead settles. Customer email address. Used for hashed/masked attribution support. Optional metadata. Supports `test_mode` (boolean), `program_id` (number), and `event_name` (string). The program of the page (the tracker sends it). Read only in browser mode; with a Bearer key, the key's program decides. When sent, the customer found by `click_id` or `customer_key` must belong to this program; otherwise the lead answers `400` `Customer not found. Provide a valid click_id or customer_key.` Outside test mode, send the `click_id` with your `customer_key`. A request with neither answers `400` `click_id or customer_key is required`. A first lead with only `customer_key` answers `400` `Customer not found. Provide a valid click_id or customer_key.`, because Affitor saves your key on the customer only when a lead settles. Without a Bearer key, `click_id` is always required. ### Request body example --- ## Response ### Success — 200 ```json { "success": true, "message": "Lead tracked successfully" } ``` ### Success — provisional browser lead (200) Returned for a browser-mode lead (no Bearer key) when the program requires server-verified leads. The lead is stored but not settled; see [Lead auth policy](#lead-auth-policy). ```json { "success": true, "provisional": true, "message": "Lead recorded as provisional. This program requires server-side (Bearer) lead tracking to settle attribution." } ``` ### Success — test mode (200) When `additional_data.test_mode` is `true`, the response includes the created event details: ```json { "success": true, "message": "Test lead event tracked successfully", "data": { "eventId": 456, "programId": 1, "test_mode": true } } ``` --- ## Errors | Status | Condition | |--------|-----------| | `400 Bad Request` | `click_id` and `customer_key` are both missing (outside test mode): `click_id or customer_key is required` | | `400 Bad Request` | Browser mode: `customer_key` was sent without `click_id` (`click_id is required when no API key is sent`) | | `400 Bad Request` | No customer record found for the provided `click_id` or `customer_key` (for example a first lead sent with only `customer_key`), or (browser mode) the customer does not belong to the `program_id` sent | | `400 Bad Request` | Customer does not belong to the authenticated program (server mode cross-program mismatch) | | `400 Bad Request` | Customer status cannot transition to lead (e.g. already converted) | | `401 Unauthorized` | `Authorization` header is present but the token is invalid or not found | | `403 Forbidden` | Test mode only: the Bearer key and `additional_data.program_id` name different programs (`program_id does not match the API key`) | | `500 Internal Server Error` | Unexpected error during lead event creation | --- ## Test Mode Send `additional_data.test_mode: true` to create a test lead event without affecting production attribution. In test mode: - a Bearer key is not required to store the test event, but only a test event sent with your program API key counts toward integration verification - pass `additional_data.program_id` to associate the test event with a specific program - the event is created with `is_test: true` ```json { "click_id": "test_lead_001", "customer_key": "test_customer", "additional_data": { "test_mode": true, "program_id": 1 } } ``` --- ## Related - [Click Tracking](/docs/brand/tracking/click-tracking/) — must run before lead tracking - [Lead Tracking Guide](/docs/brand/tracking/lead-tracking-signup/) — implementation examples (Node.js, Python, browser) - [Track Sale](/docs/api-reference/track-sale/) — next step after a successful lead --- id: "api-reference/track-refund" type: "doc" url: "https://affitor.com/docs/api-reference/track-refund" kind: "reference" updated: "2026-11-07" --- # Track Refund > Reverse or reduce the partner commission of a tracked sale when it is refunded, in full or in part. Send one call per refund. `POST /api/v1/track/refund` Reverses the affiliate commission tied to a previously tracked sale. Send one call per refund. Each call's `refund_amount_cents` is added to what was already refunded on the sale (capped at the sale amount). Once all of the sale is refunded, Affitor reverses the commission (`reversed`). A partial refund reduces a commission already approved and cancels one still `pending` (in its hold period, not yet approved); both end `refunded`. Omitting `refund_amount_cents` refunds everything that is left. This is the non-Stripe counterpart to the Stripe refund webhook: both use the same underlying reversal logic. --- Send refund amounts in the sale's original currency and minor unit, including tax. For a sale with a commission to reverse, a supplied amount must be a positive integer; `0` is rejected with `400 invalid_request`. Leave the field out to refund everything that remains. Older sales keep the legacy interpretation described below. ## Authentication All requests must include your program API key as a Bearer token. ```http Authorization: Bearer YOUR_PROGRAM_API_KEY Content-Type: application/json ``` The key is scoped to a single program. The refund lookup is restricted to sales that belong to the authenticated program. --- ## Request ### Fields The `transaction_id` originally passed to `POST /api/v1/track/sale`. Used to locate the sale record. For sales recorded from November 5, 2026 (16:00 UTC), this refund's amount is in the sale's original currency and minor unit, tax included. For a sale with a commission to reverse, it must be a positive integer when provided: `0`, `null`, negative values and non-integers return `400 invalid_request` with `refund_amount_cents must be a positive integer`. Omit the field to refund the rest. Send this refund's amount, not the running total refunded so far. For older sales, the legacy interpretation is unchanged: the amount is read in hundredths of the currency unit the sale was recorded in (cents for a USD sale); omission, `0` or a negative value refunds the rest. Your own id for this refund (for example the Stripe refund id). Recommended. A refund whose `refund_id` was already applied is ignored, so retries are safe. Without it, a second call with the same amount for the same sale is treated as a retry and ignored. Ignored for a whole-sale refund: omit the amount for new sales. For older sales, `0` or a negative amount also requests a whole-sale refund. Refunding the rest is already safe to retry. Human-readable reason for the refund. Recorded on the commission and included in partner/advertiser notifications. `refund` or `chargeback`. Recorded as the reason when `refund_reason` is not sent or empty. ### Example request body For sales recorded from November 5, 2026 (16:00 UTC), a VND 10,000 refund uses `refund_amount_cents: 10000`; a JPY 1,000 refund uses `1000`; a BHD 1.234 or KWD 1.234 refund uses `1234`. Do not convert these amounts to USD or subtract tax before sending them. ### Multiple refunds and retries - Two partial refunds of $30 and $20 on a $100 sale: send `3000` then `2000` (each with its own `refund_id`). A commission already approved is reduced by 50% in total; one still `pending` (in its hold period, not yet approved) is cancelled by the first refund. - Retries: resending a call with the same `refund_id` returns `status: "skipped"` and changes nothing. Without `refund_id`, the amount is used to detect the retry. --- ## Response ### Success: commission reversed or refunded ```json { "success": true, "status": "reversed", "deductionAmount": 25.00, "commission_id": 88 } ``` | Field | Type | Description | |-------|------|-------------| | `success` | boolean | Always `true` on a 200 response. | | `status` | string | `"reversed"` (sale fully refunded), `"refunded"` (partially refunded), or `"skipped"`: nothing changed, and `reason` says why. Usually the refund was already applied or the commission was already reversed. When `reason` is `refund history incomplete (manual review)`, this refund was **not** applied: contact support with the `transaction_id`. | | `reason` | string | Only with `"skipped"`: why nothing changed. | | `deductionAmount` | number | The commission share this refund covers, in the commission's currency: the refunded fraction of the commission, or all of what is left once the sale is fully refunded. Taken from the partner's balance only when the commission was already credited (past `pending`, not a test). A `pending` commission that is partly refunded is cancelled whole, so for it this number is informational. Present when `status` is `reversed` or `refunded`. | | `commission_id` | integer | ID of the affected commission record. | ### Success: sale has no commission ```json { "success": true, "status": "no_commission", "message": "Sale has no commission to reverse" } ``` ### Already-processed refund (idempotent) ```json { "success": true, "status": "skipped", "reason": "already reversed", "commission_id": 88 } ``` ### Test API key ```json { "success": true, "test": true } ``` A request with a test API key gets this answer before the body is checked or the sale is looked up. Nothing is refunded, so a test key cannot reverse a real commission. --- ## Errors Errors use the [platform envelope](/docs/api-reference/errors#the-platform-envelope) with a stable `error.code`, except a retired API key and rate limiting, which use the [typed envelope](/docs/api-reference/errors#the-typed-envelope). | Status | `error.code` | When | |--------|--------------|------| | 400 | `invalid_request` | `transaction_id` is missing, `reason` is not `refund` or `chargeback`, or a supplied refund amount for a new sale is not a positive integer (including `0`). The amount check applies when the sale has a commission to reverse. | | 401 | `unauthorized` | `Authorization` header is missing, malformed, or the API token is invalid. | | 404 | `not_found` | No sale record found for the given `transaction_id` in the authenticated program. | | 500 | `internal_error` | Internal error during commission reversal. Retry the same request with the same `refund_id`: a refund that was already applied is skipped. | --- ## Side Effects When a commission is reversed or refunded, Affitor: - transitions the commission to `reversed` or `refunded` status - if the commission was already credited to the partner (any status past `pending`, and not a test), deducts the proportional amount from the partner's balance in the same transaction as the status change; the balance can go negative, and open withdrawals are reduced to fit - sends an in-app notification to the partner - sends a manual-review warning to the advertiser if the commission had already been paid out The status change and the deduction are applied before the response. The notifications are sent afterwards and never change the response. --- ## Related - [Track Sale](/docs/api-reference/track-sale): record the original sale - [Payment Tracking](/docs/brand/tracking/payment-tracking-stripe/): Stripe webhook alternative --- id: "api-reference/track-sale" type: "doc" url: "https://affitor.com/docs/api-reference/track-sale" kind: "reference" updated: "2026-11-08" --- # Track Sale > Record an attributed sale and create the partner commission from your backend Call this endpoint from your server after a payment succeeds to record the conversion and trigger commission creation. The tax, currency and conversion rules below apply to API sales recorded from this time. Sales recorded earlier keep their existing pricing. ## Endpoint ``` POST https://api.affitor.com/api/v1/track/sale Authorization: Bearer YOUR_PROGRAM_API_KEY Content-Type: application/json ``` --- ## Authentication All requests require a program API key sent as a Bearer token in the `Authorization` header. The API key is found in your program settings in the Affitor dashboard. ``` Authorization: Bearer YOUR_PROGRAM_API_KEY ``` --- ## Request Fields Your unique payment identifier. Used for duplicate detection; re-sending the same value returns 409. Sale amount in the smallest currency unit (e.g. cents for USD). Must be a positive integer. The tax included in `amount_cents`, in the same unit. Used to calculate the pre-tax commission basis: `amount_cents - tax_cents`. If provided and not `null`, it must be an integer from `0` to `amount_cents`, inclusive. Otherwise, the API returns `400 invalid_request` with the message `tax_cents must be an integer between 0 and amount_cents`. If omitted or `null`, the whole amount is the basis. Your internal customer/user ID. It matches a key already stored on a customer in your program, for example by a server-verified lead or an attributed Stripe payment. By default a browser `signup()` alone records a provisional lead, which does not store the key, so send a matching `click_id` as well when the key has not been stored. At least one of `customer_key` or `click_id` must match an existing customer record. The Affitor click ID (`affitor_click_id` cookie value). Used as fallback attribution when `customer_key` is not provided. A supported ISO 4217 currency code. Defaults to `USD`. Codes without a numeric minor unit are unsupported, as are `BOV`, `CHE`, `CHW`, `COU`, `MXV`, `USN`, `UYI`, `UYW`, `VED` and `XAD`. An unsupported code returns `422 unsupported_currency` before creating a sale, commission or fee. `"payment"` (default) or `"subscription"`. Arbitrary line-item detail to store with the sale record. `true` if this is a recurring billing charge. Defaults to `false`. Your subscription identifier, stored with the sale. Affitor does not use it to find the customer or to calculate the commission: send each renewal as its own sale, with its own `transaction_id`. `"monthly"`, `"quarterly"`, or `"annual"`. Your product identifier. Used for per-product commission policy matching. When the payment happened, as ISO 8601 with an offset (for example `2026-10-16T09:30:00Z`), no more than 30 days old and at most 5 minutes in the future. Stored for reporting only: commissions, attribution windows and hold periods still use the time Affitor receives the call. Your payment provider. Stored for reporting. The provider's own payment id (1 to 255 characters). Stored for reporting; duplicate detection still uses `transaction_id`. `false` records a test sale, the same as `additional_data.test_mode: true`. `true` or omitted does not force a live sale: `additional_data.test_mode: true` or a test API key still records a test sale. --- ## Minor units and conversion Despite its name, `amount_cents` uses the currency's minor unit, not always hundredths. Use the same unit for `tax_cents`. | Currency | Decimal places | Sale amount | `amount_cents` | |----------|----------------|-------------|----------------| | USD | 2 | USD 49.00 | `4900` | | VND | 0 | VND 490,000 | `490000` | | JPY | 0 | JPY 490,000 | `490000` | | BHD | 3 | BHD 1.234 | `1234` | | KWD | 3 | KWD 1.234 | `1234` | For a supported non-USD currency, Affitor converts the pre-tax basis to USD using a stored daily rate dated on the UTC day it receives the sale or within the preceding seven days. USD uses a rate of 1. `occurred_at` does not change that rate-selection day. The sale record keeps the original currency, total, tax and pre-tax amount alongside its pricing result. Within that window, Affitor chooses the newest day with a quote or hold for that currency. On that day, it uses the primary source; the secondary source is considered only when the primary source has no entry for the currency. A held or invalid entry from the selected source blocks fallback to the other source and to an older day. If no usable rate is selected, an otherwise accepted sale is kept unpriced. That sale is kept with `money_status: "fx_pending"` and no commission or platform fee. It is not automatically priced later. Do not resend it: its `transaction_id` is already recorded, so another call returns `409 duplicate_transaction`. ## Request Body Example The USD example sends a total of 4900 minor units, including 400 of tax. The commission basis is 4500 minor units (USD 45.00). ### Subscription example ```json { "transaction_id": "inv_sub_001", "customer_key": "usr_9876", "amount_cents": 4900, "currency": "USD", "sale_type": "subscription", "is_recurring": true, "subscription_id": "sub_stripe_xyz", "subscription_interval": "monthly", "product_id": "prod_pro_plan" } ``` --- ## Response | Field | Type | Description | |-------|------|-------------| | `success` | boolean | `true` on success. | | `sale_id` | integer or null | ID of the created sale event record; `null` when the attribution window expired. | | `commission_id` | integer or null | ID of the created commission record; `null` when the attribution window expired or the sale was kept unpriced. | | `message` | string | Human-readable confirmation, when present. | | `money_status` | string | `fx_pending` in the unpriced response above. | Re-sending the same `transaction_id` returns `409 Conflict` with `error.code` `duplicate_transaction` and your program's earlier sale id in `error.details.sale_id`, or `null` when the earlier sale belongs to another program. Affitor does not create a duplicate sale, so you can safely retry on network failure. Retry a `500` the same way, with the same `transaction_id`: a `500` does not prove that nothing was recorded. A retry can fail again with `500`; one that reaches the duplicate check answers `409` with your program's `sale_id` if an earlier attempt recorded the sale, so the sale is not recorded twice. A `409` response with a `sale_id` means your program already recorded this sale. Do not retry a 409; treat it as a successful prior call and continue your payment flow normally. A `409` with `sale_id: null` means another program already used this `transaction_id`, so nothing was recorded for your program. --- ## Error Responses Most errors use the [platform envelope](/docs/api-reference/errors#the-platform-envelope) `{ "data": null, "error": { "status", "name", "message", "details", "code" } }`. A retired API key and rate limiting use the [typed envelope](/docs/api-reference/errors#the-typed-envelope) `{ "error": { "code", "message", ... } }`. Either way, branch on `error.code`; the message text may change. | Status | `error.code` | When | |--------|--------------|------| | `400` | `invalid_request` | `transaction_id` missing or not a string; `amount_cents` not a positive integer; a supplied non-null `tax_cents` not an integer from zero to the amount; an invalid `occurred_at`, `provider`, `provider_payment_id` or `livemode` | | `400` | `no_attribution` | Neither `customer_key` nor `click_id` resolved a customer, the customer belongs to another program, or no partner relationship was found | | `401` | `unauthorized` | Missing or malformed `Authorization` header, or the API key does not match any active program | | `401` | `api_key_rotation_required` | A retired API key (the body also carries `hint` and `docs_url`) | | `409` | `duplicate_transaction` | `transaction_id` already recorded; `error.details.sale_id` is your program's earlier sale id, or `null` when it belongs to another program | | `422` | `unsupported_currency` | `currency` is not supported; no sale, commission or fee is created | | `429` | `rate_limited` | Too many requests; wait `retry_after_seconds` | | `500` | `internal_error` | The sale could not be recorded, or the server could not confirm that it was. Retry with the same `transaction_id` | --- ## Test Mode Send `additional_data.test_mode: true` (or `livemode: false`) to create a test sale event without creating a live commission. The API key is still required but `transaction_id` and `amount_cents` are optional in test mode. From the time above, a supplied currency and amount must follow the same supported-code, minor-unit and tax rules. ```json { "additional_data": { "test_mode": true } } ``` Test mode response: ```json { "success": true, "message": "Test sale event tracked successfully", "data": { "eventId": 12, "programId": 3, "test_mode": true } } ``` --- ## Related - [Lead Tracking (Signup)](/docs/brand/tracking/lead-tracking-signup/) - [Tracking Overview](/docs/brand/tracking/tracking-overview/) - [Testing Integration](/docs/brand/tracking/testing-integration/) --- id: "brand/api-keys" type: "doc" url: "https://affitor.com/docs/brand/api-keys" kind: "reference" updated: "2026-11-07" --- # API key reference > Which credential each Affitor call needs, where the program API key lives, how to replace it, and how mandatory rotation is signalled. Affitor has one self-serve credential: the **program API key**. It authenticates server-side tracking calls for a single program, you manage it yourself from the dashboard, and it is the key the integration guides, the SDKs, the CLI's tracking setup, and the agent skill all refer to. CLI commands that create or list programs are different: they act as your account, so they authenticate with your CLI login rather than with this key. ## The program API key at a glance | Property | Value | |---|---| | Prefix | `aff_` | | Scope | One program. A key authenticates calls for the program it belongs to and nothing else. | | Permission | **Full access** sends tracking events and reads your stats. **Tracking only** sends clicks, signups, sales, refunds and chargebacks; the readiness check, analytics and the CLI's `status` and `test` answer `403 insufficient_key_permission` to it. The CLI and the [agent skill](/docs/skill.md) need **Full access**. You choose it in **Create key** or **Edit key**. | | Sent as | `Authorization: Bearer ` | | Created | Automatically, when the program is created. Owners and admins can create more keys and rotate any key at any time. | | Visibility | Never returned by a read. In the dashboard the full value is shown once, in **Copy your key**, right after **Create key** or **Rotate key**, so copy it there. | ```bash # Test mode: checks that the key authenticates, without creating a real sale or commission. curl -X POST https://api.affitor.com/api/v1/track/sale \ -H "Authorization: Bearer $AFFITOR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "additional_data": { "test_mode": true } }' ``` A `200` with `test_mode: true` in `data` means the key works. The call is not a no-op: it stores a sale event flagged as a test, writes a tracking log entry, and can move your integration checklist. It creates no commission and no platform fee. A real sale needs a `transaction_id` and a customer that already carries attribution — see [Track a sale](/docs/api-reference/track-sale). :::note Keys issued before the short prefix was introduced do not start with `aff_`. Authentication is an exact match on the key itself, so those keys keep working; rotating gives you an `aff_` key. ::: --- ## Where to find it 1. In the program menu (your program's name at the top of the left menu), choose **Program settings**. 2. Under **Developers**, select **API keys**. A program is given a key the moment it is created, but creating a program in the dashboard does not show you that value (`affitor init` writes the key of the program it creates to `.affitor/.env`). To get a key you can put in an environment variable, an owner or admin selects **Create key** on the **API keys** page, or **Rotate key** in the **⋯** menu on an existing key's row. The full value appears in **Copy your key**, and only there. Copy it then and store it server-side: ```bash # .env — server-side only. Never ship this key to the browser. AFFITOR_API_KEY=YOUR_PROGRAM_API_KEY ``` After that the **Key** column shows only a short hint of the key. If you no longer have the current value stored anywhere, you cannot recover it: rotate the key or create a new one instead. The full click-path, including the one-time reveal, is in [Manage program settings and your API key](/docs/brand/settings). Program read endpoints never return the key. They expose `api_token_masked` only, so a leaked read response cannot be used to forge tracking calls. The value itself comes back only in a response that issues a new key, such as **Create key**, **Rotate key**, or `affitor init` creating a program. --- ## Which calls need it | Call | Key required | |---|---| | `POST /api/v1/track/sale` | Yes | | `POST /api/v1/track/refund` | Yes | | `POST /api/v1/track/lead` — server mode | Yes. Sending the key is what makes the signup a server-attributed lead. | | `POST /api/v1/track/lead` — browser mode | No. The click cookie carries the attribution. On a program that requires server-side lead tracking, a browser lead is stored as provisional — the response says `provisional: true` — and a server-mode call is what settles it. | | `POST /api/v1/track/click` | No. Click tracking is public. | Every endpoint above is documented in the [API reference](/docs/api-reference/overview). --- ## Replace a key Rotate the key if it may have leaked, if it was committed to a repository, or as routine hygiene when someone with key access leaves. Only an owner or admin of the program can create or rotate a key. Other members do not see the keys table, so ask an owner or admin to rotate it and to hand you the new value through your secret manager. 1. Line up every place `AFFITOR_API_KEY` is stored — deployment environment, secret manager, CI — so you can update them the moment you have the new value. 2. In **Program settings** › **Developers** › **API keys**, open the **⋯** menu on the key's row, select **Rotate key**, then confirm with **Rotate key**. The old key stops working at that moment. 3. Select **Copy** in **Copy your key**, update those places, and redeploy. :::caution The two keys never overlap. **Rotate key** stops the old key at once, and you receive the new value only in **Copy your key**, so there is no way to deploy it in advance. Between the rotation and the redeploy, calls still sending the old key get `401`. Pick a window where a short gap in server-side tracking is acceptable. ::: --- ## When Affitor asks you to replace a key Affitor can mark a specific program key for mandatory rotation — for example after the key was exposed outside your control. Marking it sets a deadline, and the two sides of that deadline behave differently: - **Before the deadline**, the key still authenticates requests, so tracking keeps running until you are ready to swap it. Every response to a call made with that key carries `Deprecation` and `Sunset` headers plus a `Link` header pointing at the error reference, and the JSON body gains a `warnings` array carrying the code `api_key_rotation_required` and the deadline. - **At or after the deadline**, the key stops working. Requests come back as `401` with the same code in `error.code`, and the three headers are still there. That response has no `warnings` array — the warning only exists while the key still works. Replace the key before the deadline: past it, the old key is refused whether or not you are ready. Doing it early does not remove the changeover gap described under [Replace a key](#replace-a-key) — it only lets you choose when that gap happens. Branch on the code, not on the message text. The full header and body shapes are in [`api_key_rotation_required`](/docs/api-reference/errors#api_key_rotation_required). Rotating the key clears the flag: select **Rotate key** on its row in **Program settings** › **Developers** › **API keys**, deploy the new value, and the warnings stop. --- ## Agent API keys Separately from program keys, Affitor issues **agent API keys** (prefix `agt_`) to approved tools that read and update programs on a brand's behalf through the `/api/agent/v1/...` endpoints. These are issued by Affitor — there is no endpoint to create one yourself, and a program API key does not authenticate agent endpoints. Each agent endpoint also requires a specific scope on the key, so a valid agent key is still refused where it was not granted that scope. If you are building an integration that needs one, [contact support](/docs/support/contact). If you only want an AI coding agent to install tracking for you, you do not need an agent key: point it at [skill.md](https://affitor.com/docs/skill.md) with your program API key in the environment. From a terminal, `npx affitor onboard` uses the same key to wire in the tracking it can and verify it: see [`affitor onboard`](/docs/brand/cli/commands#affitor-onboard). --- ## Which key do I send? | Your task | Key to send | |---|---| | Report a sale, a refund, or a server-mode lead | Program API key (`aff_`), from **Program settings** › **Developers** › **API keys** | | Record a click, or a browser-mode lead | No key — both are public calls. See [Which calls need it](#which-calls-need-it). | | Read or update programs on a brand's behalf via `/api/agent/v1/...` | Agent API key (`agt_`), issued by Affitor | ## Verify it worked Send a test-mode call with the key in hand: it goes through the same authentication as a real sale, then stops before any commission or platform fee is created. Every cause of a `401`, and its fix, is listed in the [error reference](/docs/api-reference/errors). --- id: "brand/groups" type: "doc" url: "https://affitor.com/docs/brand/groups" kind: "guide" updated: "2026-10-18" --- # Organize partners into groups > Create partner groups so different partners earn different commission rates under one program. Every commission in Affitor is set per partner group: the group a partner belongs to decides their [commission rate and duration](/docs/brand/quickstart/define-commission). The hold period is set once for the whole program and applies to every group. This guide shows you how to create a group, set its policy, and move partners into it — so you can run a VIP tier next to your standard rate without per-partner bookkeeping. ## The flow at a glance **Create a partner group** **Set the group's commission policy** **Move partners into the group** Every program has a **Default** group; partners you haven't assigned elsewhere belong to it. Creating a second group is how you introduce a second rate. ## Step 1: Create a partner group A group is a pricing tier, not a folder. Create one for each set of terms you offer — for example, `Default` at your standard rate and `VIP` at a higher rate for your best-performing partners. 1. In the sidebar, open **Groups**. 2. Click **Create Group**. 3. Name the group after the terms it represents — `VIP`, `Agencies`, `Newsletter partners` — and save. The new group appears as a row in the Partner Groups list, with its own partner count, performance columns, and commission rate: ![The Partner Groups list — each row is a group with its own partner count, performance stats, and commission rate](/docs/brand/groups.png) ## Step 2: Set the group's commission policy The policy is the contract every member of the group earns under. Open the new group's row menu (**⋯**) in the Groups list and edit its policy. The policy sets the group's **commission rate**: what members earn per attributed result. Rate types and durations work exactly as described in [Set your commission](/docs/brand/quickstart/define-commission); a group simply carries its own values. Two settings are not part of a group's policy. They are set once for the whole program and apply to every group in it: - **Hold period** — how long a new commission stays on hold before it can clear. Set it under **Commission** in [program settings](/docs/brand/settings). Longer holds reduce refund risk; see [commission approval and cash flow](/docs/brand/quickstart/commission-approval-cash-flow). - **Commission approval** — there is no per-group approval mode. A commission approves automatically when the program's hold period ends (later, if you extend the hold), unless you approve or reject it first from the **Commissions** page. A test commission, a $0 commission on a payment after the commission term has ended, and one earned by someone on your own team (the brand owner or a workspace member) are not approved on their own. The **Approval mode** in program settings is for partner applications, not commissions. :::tip Set the policy before you move anyone in. Partners in the group earn whatever the policy says at the moment their sales are attributed — there is no separate "apply" step. ::: ## Step 3: Move partners into the group Partners earn their group's rate, so moving a partner is how you change what they earn — no per-partner rate fields to maintain. 1. Open **Partners** in the sidebar. 2. Find the partner you want to move and open their row's action menu. 3. Choose the change-group action. The **Change Partner Group** dialog opens. 4. Select the destination group and confirm. From their next attributed sale, the partner's commissions are created under the new group's policy. Commissions created before the move are not rewritten. Group policies are versioned. When you edit a group's commission terms, the update is recorded as a new policy version, and the previous version is preserved in the policy chain. That lets you change terms without rewriting history: existing commissions stay tied to the policy that was in effect when they were created, so your books stay auditable. ## Verify it worked The proof is a commission at the new rate. After a partner in the group drives a sale (or you run a [test conversion](/docs/brand/tracking/testing-integration)), check the dashboard: ## Next steps Rate types, durations, and what each component means for what partners earn. How commissions move through validation, hold, review, and payout. Approve the partners you'll organize into groups. --- id: "brand/partner-links" type: "doc" url: "https://affitor.com/docs/brand/partner-links" kind: "guide" updated: "2026-11-07" --- # Choose where partners can link > Allow page destinations, set an additional-link limit, and check what recent click activity tells you. Choose the pages partners can share and set how many additional links each partner can create in this program. Keep tracking installed on those destinations before partners send visitors there. ## Step 1: Open Partner links Select your program, open **Program settings**, and choose **Partner links** after **Tracking**. You need permission to update the program to save; a read-only member can view the settings. If the page says the program uses legacy link rules, the displayed controls are a draft until you save. That program has no new additional-link limit until it opts into these settings. Saving applies the policy without changing existing link keys or saved URLs.
Partner links settings with allowed destinations and a per-partner link limit Partner links settings with allowed destinations and a per-partner link limit
## Step 2: Add an allowed domain Under **Allowed destinations**, select **Add domain**. Enter an **HTTPS domain** that you manage, without a path, credentials, query string, or fragment: ```text https://brand.example ``` A subdomain or a different port is a separate origin and needs its own entry. For example, allowing `https://brand.example` does not also allow `https://shop.brand.example` or `https://brand.example:8443`. You can configure up to 20 domain rules. Choose a value for **Pages**: | Choice | What the partner can enter | | --- | --- | | **Any page on this domain** | A path or full URL on the exact allowed origin, including query parameters and a fragment | | **One specific page** | Only the **Allowed page** you save; the partner's path is filled in and locked | For one specific page, use a path beginning with one slash. You can include a query string but not a fragment: ```text /pricing?plan=pro ``` Check **I manage this domain and will ensure tracking is installed**, then select **Add domain**. This adds the rule to your form; it does not apply the program settings until you save the page. The acknowledgement does not install the tracker or verify conversions.
Add link domain dialog with One specific page and the tracking acknowledgement Add link domain dialog with One specific page and the tracking acknowledgement
## Step 3: Set the additional-link limit Under **Additional links**, enable **Allow partners to create links to your pages** and set **Additional links per partner** to a whole number from 1 to 100. The default program link is separate. Inactive additional links count toward the limit; deleted and test links do not. Lowering the limit preserves existing links and prevents new ones while the partner is at or above the new limit. Turning additional links off also preserves existing shared links. ## Step 4: Save Select **Save changes**. Wait for **Partner link settings saved.** before leaving. Page links use a query URL such as: ```text https://brand.example/pricing?plan=pro&via=partner-code ``` A program may use `aff` instead of `via`. The saved link is authoritative; partners copy it from their link list rather than building the URL by hand. ## Step 5: Check tracking on the destinations Install [click tracking](/docs/brand/tracking/click-tracking) on every allowed landing page. The activity text is an observation of a bounded recent sample: | Message | What it tells you | | --- | --- | | **Click seen on this site** or **Click seen on this page** | A qualifying click was observed on that origin or page in the last 30 days | | **No click seen in the last 30 days** | No matching click was found in the recent sample | | **Tracking activity unavailable** | The available data could not establish a result; it is not a zero-click guarantee | A click on one page does not verify the rest of the site, and none of these messages verifies signup or sale tracking. Use the [integration test guide](/docs/brand/tracking/testing-integration) to check the complete flow with the appropriate test tooling. ## Related - [Get your referral link](/docs/partners/quickstart/get-your-referral-link): the partner's create, copy, and QR flow. - [Click tracking](/docs/brand/tracking/click-tracking): install the tracker on each destination. - [Program settings](/docs/brand/settings): the rest of your program configuration. --- id: "brand/settings" type: "doc" url: "https://affitor.com/docs/brand/settings" kind: "guide" updated: "2026-11-09" --- # Manage program settings and your API key > Edit your program's terms after launch, and create or rotate the per-program API keys that authenticate your tracking integration. Everything you configured in the [setup wizard](/docs/brand/quickstart/setup-program) stays editable after launch, and Settings also hold the API key that every server-side [tracking call](/docs/api-reference/overview) authenticates with. This guide shows where each setting lives, how to change terms safely, and how to rotate the key with the shortest possible gap in tracking. ## What lives in Settings Settings belong to the program selected in the program menu. Open the program menu (your program's name at the top of the left menu, or in the top bar on smaller screens) and choose **Program settings**. The same menu also has **Members** and **Billing**. Everything on the Settings pages applies to that program. ![The program menu, opened from the program name at the top left: the current program with Program settings, Members and Billing, and beside it your programs with their status and Create program](/docs/brand/program-menu.png) **Program settings** include the setup pages and **Partner links**, which controls the destinations and number of additional links partners can create: | Page | What you edit there | |---------|--------------------| | **Business** | One card per field, each with its own **Save**: **Business name**, **Website**, **Program URL** (your public page), **Program ID** (read-only, with **Copy**), **Logo**, **Tagline**, **About**, **Terms of Service** and **Resources**. Saving a website suggests a logo, tagline and About for you to review | | **Commission** | Commission type, rate and duration, attribution window and hold period | | **Tracking** | Click and signup (lead) tracking on your website, and the **Partner link parameter** (`?via=` or `?aff=`) | | **Partner links** | [Allowed domains and pages, and an additional-link limit per partner](/docs/brand/partner-links) | | **Payments** | How sales are counted: two cards, **Stripe** and **Server API**, each with its own state. Either one is enough | | **Go live** (**Status** once the program is live) | What the program still needs to go live, its live state, and how new partners join (**Auto-approve** or **Manual review**) | The rest of the Settings menu: | Group | Item | What it is | |---------|------|------------| | **Team** | **Members** | Who can work on the program, and their [team roles](/docs/brand/team-roles) | | **Billing** | **Billing** | Platform-fee invoices | | **Developers** | **API keys** | The program's secret keys for server-side tracking calls | | **Developers** | **AI agents** | Connect Claude, Cursor and other AI tools to Affitor over [MCP](/docs/api-reference/mcp) with **Connect an AI tool**. Access is read-only, and the **Connections** list shows each connected tool | Your own settings are not part of a program. To change your profile, sign-in or payout details, click your name at the bottom of the left menu to open the account menu, then the gear for **Your account**: it has **Profile**, **Login and security** and **Payouts**. **Refer a brand**, your link for referring brands to Affitor ([how it works](/docs/partners/quickstart/get-your-referral-link#refer-a-brand-to-affitor)), is a row in the same menu. ## Step 1: Edit program terms after launch Programs evolve — rates get adjusted, branding gets refreshed, approval policies tighten or loosen. None of this requires recreating the program. 1. In the program menu, choose **Program settings**. 2. Open the page you want to change: **Commission** for the rate and hold period, **Go live** (**Status** once live) for how new partners join, or **Business** for the business name, website, logo and branding. 3. Make the change and save. On **Commission**, once terms are saved, select **Set new terms** before you change them. :::tip The **Commission** page sets your program-wide default. To pay different rates to different sets of partners, [organize partners into groups](/docs/brand/groups) — each group carries its own commission policy. ::: ## Step 2: Find your API key Every server-side call to the tracking API (sales, refunds, and server-mode leads) authenticates with a Bearer token that is unique to your program. Integrations, SDKs, the CLI's tracking setup, and AI coding agents all authenticate with a program API key. CLI commands that create or list programs act as your account instead, and authenticate with your CLI login. 1. In the program menu, choose **Program settings**. 2. Under **Developers**, select **API keys**. The dashboard shows each key only as a short hint in the **Key** column, and no read returns the full value. A key is shown once, in **Copy your key**, right after an owner or admin selects **Create key** or **Rotate key**. If you no longer have a key stored anywhere, you can't recover it from the dashboard; rotate it instead (Step 3). Store the key as a server-side environment variable: ```bash # .env — server-side only. Never ship this key to the browser. AFFITOR_API_KEY=YOUR_PROGRAM_API_KEY ``` :::note To have an AI coding agent install tracking for you, point it at [skill.md](https://affitor.com/docs/skill.md) with your program ID (on the **Business** page) and keep the key in `AFFITOR_API_KEY`. From a terminal, `npx affitor onboard` uses the same key to wire in the tracking it can and verify it: see [`affitor onboard`](/docs/brand/cli/commands#affitor-onboard). ::: ## Step 3: Rotate the key Rotate the key if it may have leaked, if it was committed to a repository, or as routine hygiene when a team member with key access leaves. Only an owner or admin of the program can rotate a key. Other members do not see the keys table, so ask an owner or admin to rotate it and to hand you the new value through your secret manager. :::caution Rotating never overlaps the two keys. **Rotate key** stops the old key at once, and you receive the new value only in **Copy your key**, so you cannot deploy it in advance. Between the rotation and the redeploy, every integration still sending the old key gets `401` responses. Copy the new value before you close **Copy your key**: it is shown one time only. ::: 1. Line up every place `AFFITOR_API_KEY` is stored — deployment environment, secret manager, CI — so you can update them straight away. 2. In **Program settings** › **Developers** › **API keys**, open the **⋯** menu on the key's row, select **Rotate key**, then confirm with **Rotate key**. The old key stops working at that moment. 3. Select **Copy** in **Copy your key**, update those places, and redeploy. ## Verify it worked Send a test-mode sale with the new key. It authenticates exactly like a real sale but creates no commission and no platform fee. Request — `POST /api/v1/track/sale`: ```bash curl -X POST https://api.affitor.com/api/v1/track/sale \ -H "Authorization: Bearer YOUR_PROGRAM_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "additional_data": { "test_mode": true }, "amount_cents": 9999, "currency": "USD", "sale_type": "payment" }' ``` Expected response: ```json { "success": true, "message": "Test sale event tracked successfully", "data": { "eventId": 789, "programId": 1, "test_mode": true } } ``` ## Next steps Base URL, auth modes, and every tracking endpoint your key unlocks. Put the key to work: get clicks, signups, and sales tracking live end to end. Hand the one-line instruction to an AI coding agent and let it wire up tracking for you. --- id: "brand/team-roles" type: "doc" url: "https://affitor.com/docs/brand/team-roles" kind: "concept" updated: "2026-11-09" --- # Team roles > What Owners, Admins, Members and Viewers can do in a brand's program, who can invite or change whom, how ownership moves, and who is in partner chats. Everyone on your brand's team has a permission level in each program they work on: **Owner**, **Admin**, **Member** or **Viewer**. Open **Members** from the program menu to see who is on the team and each person's level. Every level can open it; only Owners and Admins can change it. Each level can do everything the level below it can, and more. Partner chats are the one exception: **Chat access** decides which levels join them (see [Partner chats](#partner-chats)). ## What each level can do | Action | Owner | Admin | Member | Viewer | |---|---|---|---|---| | See the program's dashboard, partners, commissions, billing and team | Yes | Yes | Yes | Yes | | Approve or decline partner applications | Yes | Yes | Yes | No | | Rename groups, and add or move partners between them | Yes | Yes | Yes | No | | Change program settings: business details, tracking, partner links and how new partners join | Yes | Yes | Yes | No | | Run tracking checks (**Run check**) and **Go live** | Yes | Yes | Yes | No | | Change the commission type, rate or duration, for the program or a group | Yes | Yes | No | No | | Create or delete groups | Yes | Yes | No | No | | Approve, reject, extend the hold on, or mark a commission as fraud | Yes | Yes | No | No | | Create and manage API keys | Yes | Yes | No | No | | Choose who is in partner chats (**Chat access**) | Yes | Yes | No | No | | Invite, change and remove Admins, Members and Viewers | Yes | Members and Viewers only | No | No | | Make someone an owner | Yes | No | No | No | | Connect Stripe | Yes | No | No | No | | Pay an invoice by card, when card payment is available | Yes | No | No | No | | Read and reply in partner chats | Always | By default | When added | Read only, when added | The **Permission level** menu sums up three of the levels: **Admin**, "Manage the program, commissions, Members and Viewers"; **Member**, "Partners, chat and the program, no money"; **Viewer**, "Read only". A Member is in partner chats only once **Chat access** includes Members. ## Invite people Owners and Admins see **Invite people** on **Members**. 1. Select **Invite people**. 2. Enter one or more emails, separated by commas. 3. Choose a **Permission level**. An Owner can pick Admin, Member or Viewer; an Admin can pick Member or Viewer. It starts on Member. 4. Select **Send invite**. The invite email has an **Accept invitation** link that works for 7 days. The person signs in, or creates an account, with the email you invited, and the program opens. Until they accept, their row's **⋯** menu has **Resend invite**, which emails a new 7-day link, and **Cancel invite**, which stops the link working. An expired invite can't be resent: invite the person again. An invite depends on the person who sent it, or last resent it. If that person is removed, or can no longer give that level, before the invite is accepted, it stops working and the invitee needs a new one. ## Change or remove someone On a teammate's row, an Owner can move an Admin, Member or Viewer to another of those levels with the **Permission level** menu, or select **Remove from team** in the row's **⋯** menu. An Admin can do the same for Members and Viewers. Members and Viewers can't change anyone. No one can change their own level or remove themselves on **Members**, and Owner rows have no controls. Removing someone ends their access to the program, its partner chats included. ## Owners When a program is created, the person who created the brand becomes its Owner. No one on the team can change that person's level or remove them. An Owner can make an active Admin, Member or Viewer an owner too: open their row's **⋯** menu, select **Make owner**, and confirm. The new owner can do everything you can, and you stay an owner. Owner isn't a choice in **Invite people**, so to add an owner, invite the person at another level and select **Make owner** once they accept. **Members** has no control that changes or removes an Owner, so **Make owner** adds an owner. It doesn't hand yours over. ## Partner chats **Chat access**, on **Members**, sets which levels are in every chat with the program's partners: - **Owners**: always. - **Admins**: in by default. - **Members** and **Viewers**: in once an Owner or Admin ticks them and selects **Save**. Viewers can read but not reply. The setting belongs to the program and applies to all of its partner chats at once. Only Owners and Admins can change it. Unticking a level, or moving someone to a level that isn't ticked, takes them out of the program's partner chats. **Chat** shows in the left menu only for people who are in them. --- id: "faq" type: "doc" url: "https://affitor.com/docs/faq" kind: "faq" updated: "2026-11-08" --- # Frequently Asked Questions > Common questions about Affitor's pricing, tracking, commissions, and integration options. Quick answers about Affitor's pricing, tracking, commissions, and payouts, with links to the full guides where you need more depth. ## General ### What is Affitor? Affitor is an AI-native affiliate marketing platform for SaaS companies. It tracks partner-driven clicks, signups, and sales, and manages commissions and payout operations in one workflow. ### Who is Affitor built for? Affitor is designed for SaaS teams that want to launch or scale a partner program without taking on the full operational burden themselves. ### How is Affitor different from traditional affiliate tools? Affitor differentiates on: - performance-based pricing - first-party tracking for click → signup → sale flows - support for Stripe integration or server-side tracking - commission and payout operations in one workflow --- ## Accounts ### Can I use a personal email address to sign up? Yes, but a business email is recommended for team management: a shared address like `partnerships@yourcompany.com` keeps access simple as the team grows. Your sign-in email is shown read-only in **Your account** → **Profile** (click your name at the bottom of the left menu, then the gear). ### Is there a cost to create an advertiser account? No. Creating an account is free. The platform fee is $0 until your program earns its first $10,000 through affiliates, then 3.5% on affiliate-driven sales only. ### Do I need payment information to sign up? No. You connect your Stripe account later, when you set up your program and payment tracking. --- ## Pricing & Billing ### How much does Affitor cost? The platform fee is **$0 until your program earns its first $10,000 through affiliates, then 3.5%** on affiliate-driven sales only. - no monthly subscription - no setup fee ### What about the $10K fee-free threshold? The platform fee stays at $0 until your program's affiliate-driven revenue reaches $10,000. After that, the 3.5% fee applies to affiliate-driven sales only. It is never charged on the rest of your revenue or on the commissions you pay partners. ### When do I pay? Your approved partner commissions and the platform fee are billed together through **weekly invoices**, issued every Monday at 09:00 UTC and due 7 days after issue by default. You can download each invoice as a PDF from your Billing tab and pay it by Wise wire transfer to the account shown on the invoice. Card payment through Stripe Checkout is off by default; use it only if your invoice page offers it. If an invoice goes unpaid, your program can be paused: see the [overdue policy](/docs/brand/billing/overdue-policy). ### Does Affitor collect money from my customers? No. Affitor is **not** the merchant of record for your sales. You continue charging customers through your own Stripe or payment setup. The money that does pass through Affitor is your weekly invoice: you pay approved commissions plus the platform fee to Affitor LLC, and Affitor pays partners when they withdraw. --- ## Tracking & Integration ### What integration paths are supported? Three main paths are supported: 1. **Tracker install** for click tracking 2. **Browser signup helper** or **server lead API** for signup attribution 3. **Server-side tracking** or **Stripe integration** for revenue attribution ### What is the difference between `customerKey`, `customer_key`, and `affitor_customer_key`? They represent the same business concept in different integration contexts: - `customerKey`: browser helper argument for `signup(customerKey, email)` - `customer_key`: field used in the tracking API payloads - `affitor_customer_key`: Stripe metadata field Use the same internal user/customer ID across all three. ### Can I use Affitor without changing my checkout? Usually yes. If your backend can call `POST /api/v1/track/sale`, or if you take payments with Stripe and connect your Stripe account to the program, you can integrate without replacing your existing payment stack. On Stripe Payment Links, the Buy Button and the Pricing Table, the Affitor tracker passes the click to Stripe for you; with your own Checkout Session, your server adds `affitor_click_id` to the session metadata (and to `subscription_data.metadata` for a subscription). ### Does Affitor only work with Stripe? No. Stripe is the best-documented integration path, but server-side tracking works with any backend/payment provider that can send revenue events after payment succeeds. ### How does attribution work? Affitor uses: - first-party tracking - first-click attribution: the partner whose click first brings in a customer keeps that customer, and a later click from another partner is logged but does not take the customer over - a 60-day default attribution window, configurable per program The full model is documented in the [attribution reference](/docs/api-reference/attribution). For the most reliable results, install the tracker first, send a stable internal customer ID at signup, and reuse that identifier in sale tracking. ### What happens if the customer later pays on Stripe? Connect your Stripe account to the program and Affitor receives its payment events through Stripe Connect; you do not add a webhook. How Affitor finds the partner of each payment, renewals included, is on the [Stripe](/docs/brand/tracking/payment-tracking-stripe) page. --- ## Commissions & Payouts ### Who pays the partner? Affitor does. When a commission clears the program's hold period, it is added to the partner's balance. Once you pay the invoice that covers it, the partner can request a withdrawal by bank transfer or Wise, and Affitor approves and sends it. ### What happens after a sale is attributed? At a high level: 1. sale is recorded 2. commission is created 3. commission waits out the program's hold period, then is approved and added to the partner's balance 4. you pay the invoice that covers it 5. the partner requests a withdrawal, and Affitor sends it ### What happens if there is a refund? It depends on where the commission is. Before approval, the commission is removed before it reaches the partner. After approval, the amount is taken back from the partner's balance. If the commission was already collected, reconciling with the partner is a manual step and you get a dashboard notification. Platform fees already billed are not refunded. A refund lowers the revenue counted toward the $10,000 fee-free tier by the refunded amount, never by more than that sale added. See [commission approval and cash flow](/docs/brand/quickstart/commission-approval-cash-flow#refund-handling). --- ## Support & Troubleshooting ### What is the fastest way to self-serve an integration? Follow the manual docs flow in order: 1. [Install Tracking](/docs/brand/tracking/quickstart-integration) 2. [Lead Tracking](/docs/brand/tracking/lead-tracking-signup) 3. [Stripe](/docs/brand/tracking/payment-tracking-stripe) 4. [Testing Integration](/docs/brand/tracking/testing-integration) If your team prefers terminal-based setup, the [Affitor CLI](/docs/brand/cli/quickstart) is an alternative path for developer and agent-driven workflows. ### Why do sales fail to attribute even though click tracking works? The most common causes are: - signup used the wrong internal identifier - Stripe metadata used a different identifier than signup - Server-side tracking payload omitted `customer_key` / `click_id` - subscription metadata was only added to the initial checkout, not `subscription_data.metadata` ### How do I get help? After working through the integration and testing guides, contact the Affitor team with: - your program ID - the exact integration path you used - request/response samples or Stripe webhook evidence - screenshots of any relevant dashboard/test-event state --- id: "help" type: "doc" url: "https://affitor.com/docs/help" kind: "reference" updated: "2026-10-17" --- # Help center > Short answers to setup, tracking and payout questions. Full guides live in the docs. - [Frequently Asked Questions](https://affitor.com/docs/faq.md) (Getting started): Common questions about Affitor's pricing, tracking, commissions, and integration options. - [Create your advertiser account](https://affitor.com/docs/brand/quickstart/create-account.md) (Getting started): Sign up on Affitor, verify your email, choose Run a program, and start the five-step program setup. - [Glossary](https://affitor.com/docs/support/glossary.md) (Getting started): Common terms used across Affitor docs: server-side tracking, Stripe integration, invoice billing, and more - [Tracking Overview](https://affitor.com/docs/brand/tracking/tracking-overview.md) (Tracking and attribution): How Affitor links a partner click, your customer's signup and the sale into one attribution chain, step by step from referral link to commission. - [Testing Integration](https://affitor.com/docs/brand/tracking/testing-integration.md) (Tracking and attribution): Verify click, signup and sale tracking before going live, including the synthetic click, signup and sale chain that moves no real money. - [Connect a new Stripe account](https://affitor.com/docs/brand/tracking/connect-stripe-account.md) (Stripe and payments): Create a second Stripe account under your existing Stripe login, connect it to your Affitor program, test it in Stripe test mode, and check the connection. - [Commission Approval & Cash Flow](https://affitor.com/docs/brand/quickstart/commission-approval-cash-flow.md) (Commissions and payouts): Understand how attributed sales move into commissions, billing, and payout workflow. - [Getting Paid](https://affitor.com/docs/partners/payouts.md) (Commissions and payouts): How commissions turn into a payout: balances, payout methods, withdrawal, and timing. - [Partner FAQ](https://affitor.com/docs/partners/faq.md) (Partners): Common questions about joining programs, referral links, tracking, and getting paid. - [Account and Payout Settings](https://affitor.com/docs/partners/account-settings.md) (Account and login): Manage your profile, security, and the payout details that decide how you get paid. - [API key reference](https://affitor.com/docs/brand/api-keys.md) (Account and login): Which credential each Affitor call needs, where the program API key lives, how to replace it, and how mandatory rotation is signalled. - [Overdue Invoices & Program Pause Policy](https://affitor.com/docs/brand/billing/overdue-policy.md) (Billing): How Affitor handles unpaid commission invoices, when programs pause, and how to resume. - [Errors & Troubleshooting](https://affitor.com/docs/api-reference/errors.md) (Troubleshooting): All API error codes, their causes, and how to fix common integration problems. - [System Status](https://affitor.com/docs/support/status.md) (Troubleshooting): Check the current public status guidance and what to do if you suspect an issue. --- id: "getting-started/how-it-works" type: "doc" url: "https://affitor.com/docs/getting-started/how-it-works" kind: "concept" updated: "2026-11-07" --- # How Affitor Works > From affiliate click to attributed revenue and payout: the seven lifecycle steps, server-side or Stripe tracking, and a check you or an AI agent can run. Affitor layers on top of your existing stack — your site, signup flow, and checkout stay unchanged. It adds tracking, attribution, commission calculation, and partner payout workflow. ![How Affitor Works - 7 Step Affiliate Lifecycle](/docs/images/how-it-works-diagram.png) ## The affiliate lifecycle ### 1. Advertiser creates a program You define commission rules, partner approval criteria, and payout/hold settings. ### 2. Partner joins and gets a referral link Approved partners receive links that identify their traffic. ### 3. Partner promotes your product Partners share links through content, social, communities, newsletters, or direct outreach. ### 4. Customer clicks and is tracked Affitor records the visit and stores the click-to-customer relationship needed for attribution. ### 5. Customer signs up and pays You send signup attribution with your internal customer ID, then record revenue either through: - Server-side tracking — your backend calls POST /api/v1/track/sale, or - Stripe integration — Stripe metadata + webhook handling ### 6. Commission is created Affitor calculates commission from the program's applicable rules and moves it into the commission workflow. ### 7. Payout operations continue in Affitor Validated commissions move through review, hold, and payout operations for partners. ## Key points **Flexible integration paths** — Affitor supports browser-side signup tracking, server-side tracking vs Stripe integration, and server-side lead APIs. **Agent-completable integration** — `npx affitor onboard` (or the `@affitor/mcp` server for AI agents) detects your stack, installs tracking, and fires a synthetic click, lead, and sale through the live pipeline, returning `integration_verified: true` when the chain holds. **60-day default attribution window** — Affitor documents a 60-day default window for affiliate attribution. **Invoice billing model** — Advertisers charge customers through their own Stripe or payment setup. Affitor attributes conversions and manages billing and payout operations through its workflow. ## Next steps To see the flow for your setup, from a partner's link to a commission, with the guides for each step, open [Use cases](/docs/use-cases). Set up commission rules, partner approval criteria, and payout settings. Learn how Affitor's performance-based pricing model works. Or start now: [create your program at affitor.com](https://affitor.com) — $0/month, with a 3.5% fee only after your program's first $10,000 in affiliate-driven revenue. --- id: "getting-started/pricing-performance-model" type: "doc" url: "https://affitor.com/docs/getting-started/pricing-performance-model" kind: "concept" updated: "2026-11-07" --- # Pricing > Affitor pricing: $0/month, $0 setup, 3.5% of partner-generated revenue, and each program's first $10,000 in affiliate-driven revenue is fee-free. Affitor charges only when partners generate revenue — no subscription, no setup fee. ## Core pricing model - **Monthly subscription:** $0 - **Setup fee:** $0 - **Platform fee:** 3.5% of partner-generated revenue ## Example breakdown A partner drives a $100 sale with a 30% commission: | Item | Amount | |------|--------| | Gross revenue | $100.00 | | Stripe fee (example) | -$3.20 | | Partner commission (30%) | -$30.00 | | Affitor platform fee (3.5%) | -$3.50 | | **You keep** | **$63.30** | ## How billing works in the current public model Affitor's public docs currently describe an **invoice billing** model: 1. You keep collecting customer payments in your own Stripe/payment stack. 2. Affitor attributes validated affiliate conversions. 3. Affitor bills through its invoice workflow for partner commission + platform fee obligations. 4. Partner payout operations continue through Affitor. :::note Affitor is not the merchant of record for your sales: customer payments never pass through Affitor. Your weekly invoice (approved partner commissions plus the platform fee) is paid to Affitor LLC, and Affitor pays partners from it when they withdraw. ::: ## Cash flow and payout workflow Commissions wait out your program's hold period, then are approved and added to the partner's balance; once you pay the invoice that covers them, partners can request withdrawals, which Affitor sends. Timing varies by program settings, so treat your dashboard as the authoritative operational reference. [→ See full cash flow details](/docs/brand/quickstart/commission-approval-cash-flow) ## $10K guarantee Each program's first $10,000 in affiliate-driven revenue is fee-free. The threshold is counted per program, so every program you run gets its own $10,000. A refund lowers the revenue counted toward it by the refunded amount, never by more than that sale added. Confirm your exact commercial terms with the Affitor team before launch. ## What's included - Partner tracking from click → signup → sale - Partner program management - Commission operations - Payout workflow support - Analytics and reporting - Partner messaging and coordination ## Best fit Affitor works best when your team can cleanly do one of the following: - send revenue from your backend using `POST /api/v1/track/sale` - or attach Affitor metadata to Stripe Checkout via Stripe integration - or hand the integration to an AI coding agent via `npx affitor onboard` or the MCP server, and let the self-verify loop prove the chain works ## Next steps Define your commission structure. See how click, signup and sale tracking works. Starting costs nothing: [create your program at affitor.com](https://affitor.com) and pay only when partners generate revenue. --- id: "getting-started/quickstart" type: "doc" url: "https://affitor.com/docs/getting-started/quickstart" kind: "quickstart" updated: "2026-11-07" --- # How to Use Affitor > The end-to-end golden path: launch a program, install tracking, and run commissions through to payout. This is the shortest path from zero to your first attributed commission. Each step links to the detailed guide, so use this page as your map and follow the links when you need depth. ## The lifecycle at a glance Launch a program Partners promote Track referrals Commission created Payout ## Phase 1 — Launch your program Set up the program partners will join and get the API key your backend uses to report sales. Set up your advertiser account and open the dashboard. Define program basics, branding, and what partners see. Choose how partners earn — signups, sales, or subscription payments. Generate the program API key your server uses to authenticate tracking calls. ## Phase 2 — Install tracking Affitor attributes revenue from three signals across the customer journey. You install these once and they run continuously. Click Signup / lead Sale Follow the [3-Step Integration Guide](/docs/brand/tracking/quickstart-integration) to wire these up. Affitor can receive sales from connected Stripe Checkout sessions and paid invoices without a `/api/v1/track/sale` call from your backend. For sales outside those flows, report each sale **server-side** with your program API key. Here is that call: The `customer_key` you send at signup must equal the one you send at sale. That single identifier is how Affitor links a sale back to the original click and credits the right partner. ## Phase 3 — Commissions and payouts Once a sale is attributed, Affitor creates the commission and moves it through your review and payout workflow. Monitor clicks, leads, sales, and per-partner performance once you are live. Understand how commissions are reviewed, held, and cleared. Move cleared commissions through to partner payout. ## Your golden-path checklist --- id: "partners/account-settings" type: "doc" url: "https://affitor.com/docs/partners/account-settings" kind: "guide" updated: "2026-10-18" --- # Account and Payout Settings > Manage your profile, security, and the payout details that decide how you get paid. Your account settings hold two things that matter: how brands see you, and how your money reaches you. This page walks through both so nothing blocks a payout when you've earned one. ## Profile Your profile is what a brand sees when they review your application. Click your profile row at the bottom of the left rail to open your account menu, then the gear for **Your account**. It opens on **Profile**: - **Avatar**: the photo shown to brands and partners you work with. - **Your details**: **Full name**, **Email** (your sign-in email, shown read-only), **Username** (your Refer a brand link, `affitor.com/r/`, see below) and **Country**. **Save** saves this card. - **Website and social links**: your **Website** and your **YouTube**, **X (Twitter)**, **Instagram**, **TikTok** and **LinkedIn** links, where you promote. Brands running manual review use these to decide. This card has its own **Save**. A real name and photo help your applications get approved. A complete profile is the single cheapest way to raise your approval rate: brands approve partners they can size up. ### Username Your username makes your Refer a brand link `affitor.com/r/`. It is 3 to 30 characters: lowercase letters, numbers and single hyphens. The field checks right away whether the name is free and can suggest one. Usernames are unique and share one namespace with brands' program URLs: when a name is taken, Affitor suggests others such as `name-hq`, `get-name` or `try-name`. - **Changing it**: your first username is free, then you can change it once every 14 days. - **Your old name**: when you change your username, the old link stops crediting you at once. The old name stays reserved for you for 14 days, then anyone can take it. - **Not affected**: your partner link codes (`?via=` or `?aff=` on program links) never change when you rename. Older usernames you replaced before this rule started still credit you. ## Security Under **Your account** → **Login and security**, change your password with **Current password**, **New password** and **Confirm new password**, then **Update password**. Changing it signs you out everywhere else. Under **Devices**, **Sign out other devices** ends every other browser, phone and Affitor CLI session at once; this device stays signed in. If you signed up with Google, **Set a password** lets you also sign in with your email address. ## Payout details This is the part that blocks money if it's missing. Before your first withdrawal, finish **Get ready to be paid** under **Your account** → **Payouts**: your legal name, a payout method and a tax form (W-8BEN, W-8BEN-E or W-9). See [Getting paid](/docs/partners/payouts) for each step. - **Payout method**: where Affitor sends your earnings when you withdraw: Wise or a bank account. **Add payout method** adds one; **⋯** → **Edit** or **Remove** changes a saved one. Enter the details accurately: a typo in a payout address is the most common reason a withdrawal fails. PayPal is no longer supported: a PayPal method you saved before still shows, and you can remove it. - **Invoice details**: **Business name**, **Address** and **Postal code**, added to your payout invoices. ## Verify it worked ## Next steps - [Getting paid](/docs/partners/payouts): turn your balance into a withdrawal - [Promote your link and earn](/docs/partners/quickstart/promote-your-link): drive the commissions in the first place --- id: "partners/dashboard" type: "doc" url: "https://affitor.com/docs/partners/dashboard" kind: "reference" updated: "2026-11-07" --- # Your Partner Dashboard > Where to find your programs, each program's numbers and links, your Refer a brand referrals, messages, and your payouts. The partner dashboard has five items in the left rail: **Marketplace**, **Programs**, **Chat**, **Referrals** and **Payout**. This page shows what each one holds. ## Programs **Programs** is your partner home. It lists the programs you joined or applied to: | Column | What it means | | --- | --- | | **Status** | Active, or Pending while the brand reviews your application | | **Clicks** | Visits through your referral links | | **Signups** | Referred users who created an account | | **Paid Signups** | Referred users who became paying customers | | **Revenue** | Sales attributed to you | | **Total Commission** | What you've earned | **Search programs** and the **All** / **Active** / **Pending** filter narrow the list; the table footer shows how many programs you have. **Find programs** opens the Marketplace. On a pending application, **⋯** → **Withdraw application** removes it; you can apply again later from the Marketplace. Until your partner setup is done, a **Finish setup** card above the list shows how many of its three steps are done and a **Continue:** button naming the next one. Once setup is done, a **Start earning** card tracks three results, each with its date: **Someone clicked your link**, **You earned your first commission** and **You got paid**. While you have earned a commission and have no payout method, **You can get paid** sits on top of the card. **Hide this list** removes the card; it goes away by itself once all three are reached. ## A program's page Select a program to open its page. At the top, **Copy link** copies your referral link and **Message** opens a conversation with the brand. The page has four tabs: | Tab | What it shows | | --- | --- | | **Overview** | **Clicks**, **Signups**, **Paid signups**, **Revenue** and **Commission** for **7d**, **30d**, **90d** or **All**, a chart, and your **Top links** | | **Links** | Every link you made for this program with its clicks, signups, paid signups and revenue. **Create link** adds another | | **Customers** | The people you referred: **Customer** (masked email and signup date), **Last purchase** and **Lifetime value** | | **Commissions** | Each commission with its **Date**, **Type**, **Link**, **Sale**, **Commission** and **Status** (such as **Pending**, **Approved**, **Paid**, **Rejected** or **Refunded**) | ## Marketplace The **Marketplace** lists the programs you can join. Each card has **Apply**, or shows **Joined** or **Applied**. See [Find and join programs](/docs/partners/quickstart/find-and-join-programs). ## Referrals **Referrals** is the page for the Affitor Refer Program: your link for referring brands to Affitor, **Invite via email**, the brands you referred with their stage, and your **Earnings** (**On hold**, **Released**, **Lifetime**) with **Withdraw** and **Payout history**. See [Refer a brand to Affitor](/docs/partners/quickstart/get-your-referral-link#refer-a-brand-to-affitor) and [How referral rewards work](/docs/partners/referral-rewards). ## Chat **Chat** holds your conversations with brands. **New message** starts one with any program. While your application to a program is pending, you can send it 3 messages until the brand answers. ## Payout **Payout** shows your balance and **Payout history**, and **Withdraw** opens the withdrawal. It's covered next. ## Your account Your profile row sits at the bottom of the left rail. Click it to open your account menu; the gear next to your name opens **Your account**, with **Profile**, **Login and security** and **Payouts**. See [Account and payout settings](/docs/partners/account-settings). The same menu has **Integrations**. Under **Affitor MCP**, **Connect an AI tool** connects an AI app such as Claude or Cursor to your partner data, and **Connections** lists the apps you connected. See [Connect your AI tool](/docs/api-reference/connect-ai-tool). --- id: "partners/faq" type: "doc" url: "https://affitor.com/docs/partners/faq" kind: "faq" updated: "2026-10-17" --- # Partner FAQ > Common questions about joining programs, referral links, tracking, and getting paid. ## Getting started ### How do I find programs to promote? Browse the **[Marketplace](https://affitor.com/marketplace)**. It's public, so you can look before you log in. To apply, you'll need a partner account. ### Why don't I see any programs after signing up? Make sure you verified your email and chose **Join programs**. Both are required before the Marketplace and applications unlock. See [Create your account](/docs/partners/quickstart/create-account). ### Do I need to write a pitch to apply? No. Applying is one click: the **How will you promote it?** field is optional. ## Approval and links ### How long until I'm approved? It depends on the program. **Auto-accept** programs approve you instantly. **Manual-review** programs are approved by the brand — you'll see an **Applied** badge while you wait, and you're enrolled automatically once they accept. ### What if my application is declined? You can apply to other programs in the Marketplace anytime — there's no limit on how many you join. ### Where is my referral link? It's created for you automatically when you're approved for the program. Open the program from **Programs** and select **Copy link**. See [Get your referral link](/docs/partners/quickstart/get-your-referral-link). ### How is a click credited to me? Your link carries a unique code, as `?via=`, `?aff=` or `/r/` depending on the brand's setup. Affitor stores it in a first-party cookie on click and ties later signups and sales back to you. ## Getting paid ### How do I get paid? Finish **Get ready to be paid** under **Your account** → **Payouts** (legal name, payout method and tax form), then withdraw from the **Payout** page when you have an available balance. See [Getting paid](/docs/partners/payouts). ### What payout methods can I use? Wise, or a bank transfer (ACH in the US, BIC/SWIFT internationally), depending on your country and currency. PayPal is not supported. ### Do I need a tax form? Yes, every partner signs one before the first withdrawal: W-8BEN (a person) or W-8BEN-E (a business) if you are not a US citizen or US tax resident, otherwise a W-9 that Affitor's accountant emails you to sign. ### Is there a minimum payout? Yes, $20. You can withdraw any amount from $20 up to your available balance. ### How long do payouts take? After a withdrawal is reviewed and marked sent, the time for the funds to arrive depends on your bank or Wise. --- id: "partners" type: "doc" url: "https://affitor.com/docs/partners" kind: "concept" updated: "2026-10-18" --- # Become a Partner > Join a SaaS affiliate program on Affitor, get your referral link, and start earning commission. Partners promote SaaS products and earn commission on the customers they refer. This guide takes you from a brand-new account to your first shareable referral link. > **Key terms:** > - **Partner**: you: the affiliate, creator, agency, or promoter sending traffic > - **Brand**: the SaaS company whose program you join > - **Referral link**: your URL with a referral code; recording visits and later attribution depend on the brand's tracking setup ## Your path to earning ## How it works Find a program in the **Marketplace** → **apply** Get **approved** → you're enrolled Open the program → **copy your referral link** Share your link → **earn commission** ## Start here Sign up, choose Join programs and finish setup. Browse the Marketplace and apply. Copy your tracked link and share it. Set up payouts and withdraw your earnings. --- id: "partners/payouts" type: "doc" url: "https://affitor.com/docs/partners/payouts" kind: "guide" updated: "2026-10-18" --- # Getting Paid > How commissions turn into a payout: balances, payout methods, withdrawal, and timing. This page covers the money: how your commission becomes a balance, how to set up a payout method, and how to withdraw. ## Your balance The **Payout** page shows three numbers: - **Ready to withdraw**: the available balance you can cash out now - **Pending**: earned but not yet cleared for withdrawal - **Total paid**: your lifetime earnings paid out An approved commission is added to your balance, but you can withdraw it only once the brand has paid the invoice that covers it. Until then it shows on its own line, **Awaiting brand payment**, below **Ready to withdraw**. Commissions approved before October 9, 2026, 00:00 Pacific time (07:00 UTC) became withdrawable on approval. ## 1. Get ready to be paid Affitor pays partners through Wise. Before your first withdrawal, open **Your account** → **Payouts** (click your profile row at the bottom of the left rail, then the gear). The **Get ready to be paid** card lists what is still missing: 1. **Legal name**: **Add legal name**, as on your bank account and ID. It goes on your tax form and payout records and is not shown to brands. 2. **Payout method**: **Add payout method**, then pick the **Recipient country**, **Recipient currency** and **Type**, and enter the account details. For **Wise**, enter your **Wise account email**: Affitor sends USD, and Wise converts it if you hold another currency. A bank account must be in your legal name. 3. **Tax form**: **Fill in** and answer **Are you a US citizen or US tax resident?** - **No**: choose **A person · W-8BEN** or **A business · W-8BEN-E**, fill in your country of tax residence, address and the other fields, check the certification and sign. The form is valid for 3 calendar years; once it expires, the card shows **Tax form expired, sign a new one** with **Sign again**. - **Yes**: select **Declare W-9**. Affitor's accountant emails you a W-9 to sign, and payouts start once it is received. Affitor never asks for your SSN or EIN. If your email is not verified yet, the card shows **Verify your email** first. When everything is done, the card shows **Ready**. Brands never see your tax form. Available methods depend on your country and currency: | Country / currency | Methods | | --- | --- | | US / USD | Bank account (ACH) or Wise | | Vietnam / VND | Bank account (BIC/SWIFT) | | Vietnam / USD | Bank account (BIC/SWIFT) or Wise | | Other | Bank account (BIC/SWIFT) or Wise | ## 2. Withdraw Select **Withdraw** on the **Payout** page (or under **Earnings** on **Referrals**). On the **Payout** page it is turned off while less than $20 is ready. The withdrawal has three steps: 1. **Amount**: enter how much to withdraw. **To** shows your payout method (**Change** appears when you have more than one), and **Estimated fees** shows any processing fee 2. **Review**: check the details under **Confirm your withdrawal**, then select **Confirm** to submit it 3. **Pay**: the confirmation, with the net amount and fees If payout setup is not finished, the page says "Finish payout setup first" with what is missing, and **Go to Payouts** opens **Your account** → **Payouts**. :::note A processing fee may apply; the exact amount is shown before you confirm. The minimum withdrawal is $20, and you can withdraw any amount from $20 up to your available balance. ::: ## 3. When you get paid After you submit a withdrawal, the Affitor team reviews it, sends it through Wise and marks it as sent. Once it's sent, how long the funds take to reach your account depends on your bank or Wise. You can follow the status (pending, processing, completed) in **Payout history** on the **Payout** page. Search it, filter by status or type, and **Export** it as CSV; **⋯** → **View details** opens **Transaction details** with the timeline of that payout or commission. ## After a refund If a sale is later refunded, the related commission is reversed: before it is approved it never reaches your balance, and after approval the amount is deducted from your balance. If you had already withdrawn that commission, your balance can go negative: the **Payout** page shows it as **Balance owed**, and it is recovered from your next commissions. --- id: "partners/referral-rewards" type: "doc" url: "https://affitor.com/docs/partners/referral-rewards" kind: "explainer" updated: "2026-11-07" --- # How referral rewards work > Worked examples of the Affitor Refer Program: which brand earns you $50, $350 and 15%, what happens when a brand runs several programs, and who gets credit. The [Refer Program terms](https://affitor.com/legal/refer-program) are the rules. This page walks through them with examples, so you can predict exactly what a referral pays. ## The three rewards | Reward | Amount | Paid when | How often | | --- | --- | --- | --- | | First paid invoice bonus (M1) | **$50** | The brand pays its first invoice with partner commissions greater than $0, even if Affitor's fee is $0 | Once per referred brand | | Growth bonus | **$350** | The program reaches $10,000 in paid sales and the brand has paid the related Affitor invoices and its partners | Once per referred brand | | Revenue share | **15%** of Affitor's platform fee | Every platform-fee invoice the brand pays | For 12 months from the first platform-fee invoice the brand pays | Rewards are counted per referred brand, which is the person you brought to Affitor, not per program. Each reward is held for 30 days today (terms, [section 6](https://affitor.com/legal/refer-program#holds-and-payouts)). The revenue share then reaches your balance automatically; the $50 and $350 bonuses are reviewed one by one first. Your **Referrals** page shows each brand's stage and your **Earnings**: **On hold**, **Released** and **Lifetime**. ## Example: one brand, several programs You refer Minh. Minh signs up through your link and creates a program. 1. Minh pays the first invoice with partner commissions greater than $0. You earn **$50**, even if Affitor's fee is $0; the bonus still needs admin approval after its hold. 2. Minh creates and launches a second program. Nothing new: the $50 is paid once per brand. 3. The first program reaches $10,000 in paid sales, and Minh has paid the related Affitor invoices and its partners. You earn **$350**, once. 4. For the next 12 months you earn **15%** of every platform fee Minh pays, on every program Minh runs, including the second one. Affitor is free for a program until its partners drive its first $10,000 in sales, then the fee is 3.5% of affiliate-driven sales. The 12-month revenue-share period starts with the first invoice that carries a platform fee. An earlier paid commission invoice can qualify for M1 with a $0 Affitor fee without starting that period. ## Team members do not change who earns Credit belongs to the person you referred, who created the brand. When Minh invites teammates to the brand's programs: - your rewards from Minh's brand do not change; - the people Minh adds do not count as new referrals, and inviting them earns no one a reward; - if one of them later creates a brand of their own, that brand is a new referral, credited to whoever's link they used. ## Who gets credit These rules decide who earns Refer Program rewards for bringing a brand to Affitor. Customers you send to a brand's own affiliate program follow that program's [attribution rules](/docs/api-reference/attribution) instead. - **Last click wins.** If several partners' links were clicked, the partner whose link was clicked last before the person signed up earns the rewards. If they signed up without a link (for example as a partner first), the last link clicked before they create their first program counts. - **30 days.** A click counts for 30 days: the sign-up, or the first program when there was no link at sign-up, has to happen within 30 days of it. - **One brand, one partner.** Once a brand is credited to you, that does not change. - **No self-referrals.** Your own link used for your own brand earns nothing (terms, [section 5](https://affitor.com/legal/refer-program#self-referrals)). ## What never earns - A brand that was already on Affitor, adding another program. - Inviting a team member to a program. Only your Refer a brand link earns. - Your own brand: a self-referral (terms, [section 5](https://affitor.com/legal/refer-program#self-referrals)). --- id: "support/contact" type: "doc" url: "https://affitor.com/docs/support/contact" kind: "reference" updated: "2026-11-07" --- # Contact Us > Where to email Affitor: support@ for help with your program, tracking or payouts, partnerships@ for partnerships, and hello@ for general mail. Pick the address that fits your message, so it reaches the right people. ## Email | For | Address | |---|---| | Help with your program, tracking, payouts or your account | [support@affitor.com](mailto:support@affitor.com) | | Partnerships | [partnerships@affitor.com](mailto:partnerships@affitor.com) | | General mail and press | [hello@affitor.com](mailto:hello@affitor.com) | For help, include what the [support page](/docs/support) lists so we can look into it without asking again. For press, use the subject line **Press Inquiry**. ## For brands To set up a program, start at the [docs home](/docs). For a question about a program you run, email [support@affitor.com](mailto:support@affitor.com). ## For partners and creators To join a program, find it in the [Affitor marketplace](https://affitor.com/marketplace) and select **Apply to promote** on the program's page. For a question about a program you promote or your payouts, email [support@affitor.com](mailto:support@affitor.com). ## Connect with us Find us on [X @affitor_ai](https://x.com/affitor_ai) and [LinkedIn](https://linkedin.com/company/affitor) for product updates. ## Location San Francisco, CA --- id: "support/glossary" type: "doc" url: "https://affitor.com/docs/support/glossary" kind: "reference" updated: "2026-10-17" --- # Glossary > Common terms used across Affitor docs: server-side tracking, Stripe integration, invoice billing, and more ## A ### Advertiser The company running an affiliate program in Affitor. ### Affiliate Link A partner-specific referral link that includes tracking information, through the `?via=` or `?aff=` parameter (the program's **Partner link parameter**). ### Attribution The process of crediting a conversion to the correct partner. Current public docs describe first-party tracking with a 60-day default window and first-click attribution: the partner whose click first brings in a customer keeps that customer. ### Attribution Window The time period during which a tracked click can still receive credit for a later conversion. Public docs currently describe a 60-day default window. ## B ### Invoice billing The current public payment-tracking model where the advertiser keeps collecting end-customer payment in their own checkout/Stripe account, and Affitor attributes conversions then bills through its invoice workflow. ## C ### Click A tracked affiliate visit created when someone lands via a partner link. ### Commission The amount earned by a partner after a sale is attributed and processed through the commission workflow. ### Customer Key Your internal customer/user identifier. It appears as: - `customerKey` in the browser helper - `customer_key` in the tracking API payloads - `affitor_customer_key` in Stripe metadata ## H ### Hold Period The review/protection period before a commission becomes available for payout operations. ## P ### Partner Any individual or organization promoting an advertiser's product in exchange for commission. ### Payout The transfer of cleared partner earnings through Affitor's payout workflow. ### Performance-based Pricing A pricing model where fees are tied to partner-generated revenue rather than a monthly subscription. ### Platform Fee Affitor's fee on partner-generated revenue: $0 until a program's affiliate-driven revenue reaches $10,000, then 3.5% of each affiliate-driven sale. The threshold is counted per program. ### Program ID The identifier for your Affitor program. It is used in tracker setup, test flows, and Stripe metadata. Find it in the program menu under **Program settings** → **Business**, where **Program ID** is shown with **Copy**. ## R ### Recurring Commission A commission structure where a partner can keep earning on subscription renewals for a defined duration or lifetime, depending on the configured program rules. ## S ### Server-side tracking The server-to-server revenue tracking method — your backend calls `POST /api/v1/track/sale`. ### Signup Helper The browser-side helper call used after a successful signup: `signup(customerKey, email)`. ### Stripe metadata The metadata Affitor uses to attribute Stripe Checkout payments, typically: - `affitor_click_id` - `affitor_customer_key` - `program_id` ## T ### Test Mode A testing path that creates test events without affecting production attribution or commission data. ### Tracking The system that connects click, signup, and sale data so revenue can be attributed to the correct partner. ## W ### Webhook An automated event notification. Affitor uses Stripe webhooks to process payment attribution in the Stripe integration. ### Withdrawable Balance Partner earnings that have cleared the hold/review workflow and whose invoice the brand has paid, so the partner can withdraw them. ## Related resources - [What is Affitor?](/docs) - [How Affitor Works](/docs/getting-started/how-it-works) - [Pricing](/docs/getting-started/pricing-performance-model) --- id: "support" type: "doc" url: "https://affitor.com/docs/support" kind: "concept" updated: "2026-11-07" --- # Support > Get help with Affitor, follow the fastest self-serve path, and know when to contact the team. Choose the fastest support path before opening a request. ## Start here first ## Common support paths Read the high-level overview, pricing model, and workflow before jumping into implementation details. Follow the advertiser setup flow if you are still configuring your account, commissions, or payout workflow. Review click, signup, payment, and testing docs to isolate where attribution is breaking. Read the partner FAQ about joining programs, referral links, tracking, and getting paid. Reach out once you have gathered the right implementation details and evidence. ## What to include when you contact support - Your program ID, or as a partner, the program's name - The exact flow that is affected - Request/response samples or webhook evidence if relevant - Screenshots of dashboard state, console errors, or failed requests - A short summary of what you already tried --- id: "support/status" type: "doc" url: "https://affitor.com/docs/support/status" kind: "guide" updated: "2026-09-24" --- # System Status > Check the current public status guidance and what to do if you suspect an issue. Affitor does not currently publish a full real-time public status dashboard in these docs. ## What to do if you suspect an issue ## What to include - your program ID - the affected flow or page - screenshots, request logs, or webhook evidence where possible - whether the issue is reproducible --- id: "use-cases/ai-agent-setup" type: "doc" url: "https://affitor.com/docs/use-cases/ai-agent-setup" kind: "concept" updated: "2026-11-07" --- # Set up with an AI agent, connect your program in one sign-in > What an AI tool can do with Affitor today: read your account over the hosted MCP server with one sign-in, or create a program and add tracking with the CLI. An AI app can read your Affitor account through the hosted MCP server, after one sign-in. A coding agent can create a program and add Affitor tracking to your site's code with the Affitor CLI. | | MCP server | Affitor CLI | |---|---|---| | Best for | Asking an AI app about your program, partners, commissions and billing, or about your earnings as a partner | A coding agent that adds tracking to your site's code | | Sign-in | Your Affitor account, in the browser. No API key | `npx affitor login` opens your browser; `npx affitor init` saves the program API key in `.affitor/.env` | | What it can do | Read-only: it cannot change data or move money. With a brand connection, `get_program` returns the tracker install snippet, where it goes and how to verify it | Create a program and write `.affitor/AGENTS.md` for your coding agent. `npx affitor onboard` fires a test click, lead and sale, and exits with an error until the integration is verified | | Programs | All current and future programs, or up to 50 you select when you sign in | One program per API key: the new one `npx affitor init` creates, or one you already have when you pass its key with `--api-key` or `AFFITOR_API_KEY` | | Start here | [Connect your AI tool](/docs/api-reference/connect-ai-tool) | [CLI quickstart](/docs/brand/cli/quickstart) | In the dashboard, **Program settings** › **Tracking** › **With AI** gives you a prompt that has your AI tool add tracking with your program API key; [Connect your AI tool](/docs/api-reference/connect-ai-tool) shows it. [Set up a coding agent](/docs/brand/cli/agent-setup) gives Claude Code, Cursor or Codex Affitor's local tracking MCP server, which uses a program API key. It is separate from the hosted server: it does tracking, not reporting. ## Related - [Connect your AI tool](/docs/api-reference/connect-ai-tool): the steps for each AI app - [MCP server reference](/docs/api-reference/mcp): sign-in, tools, limits and removing access - [CLI quickstart](/docs/brand/cli/quickstart): create a program and add tracking from your terminal - [Set up a coding agent](/docs/brand/cli/agent-setup): the local tracking MCP server for Claude Code, Cursor or Codex --- id: "use-cases/any-payment-provider" type: "doc" url: "https://affitor.com/docs/use-cases/any-payment-provider" kind: "guide" updated: "2026-11-06" --- # Any payment provider, credit partners from your server > Your server reports each signup and sale with your program API key, and Affitor finds the partner who referred the customer and writes the commission. ```mermaid sequenceDiagram autonumber participant C as Customer participant W as Your site participant B as Your server participant A as Affitor C->>W: Opens a partner link W->>A: Tracker records the click C->>B: Signs up B->>A: Reports the signup with the click id and your customer key C->>B: Pays through your payment provider B->>A: Reports the sale A->>A: Finds the partner A->>A: Writes the commission Note over A: Approved after the hold period opt Refund B->>A: Reports the refund A->>A: Takes back the commission, in full or in part end ``` ## What you need If you take payments with Stripe Checkout or Stripe subscriptions, [Sell on Stripe](/docs/use-cases/sell-on-stripe) needs no sale calls. With Stripe connected and your server reporting too, send each payment one way only: the same purchase sent both ways can count twice. ## Steps --- id: "use-cases" type: "doc" url: "https://affitor.com/docs/use-cases" kind: "concept" updated: "2026-10-18" --- # Use cases > Each use case shows the flow from a partner's link to a commission, then the guides to set it up. - [Sell on Stripe, credit partners without a sales API call](https://affitor.com/docs/use-cases/sell-on-stripe.md): Connect Stripe once: Affitor gets each Checkout or subscription payment from Stripe, finds the partner who referred the buyer and writes the commission. - [Any payment provider, credit partners from your server](https://affitor.com/docs/use-cases/any-payment-provider.md): Your server reports each signup and sale with your program API key, and Affitor finds the partner who referred the customer and writes the commission. - [Subscriptions, credit partners on renewals](https://affitor.com/docs/use-cases/subscriptions.md): Each paid invoice of a Stripe subscription earns the referring partner for as long as your commission type says. Refunds and active or lost chargebacks reverse or adjust matched commissions. - [Partners get paid, without sending a transfer yourself](https://affitor.com/docs/use-cases/partner-payouts.md): Approved commissions go to the partner's balance; once you pay the invoice that covers them, the partner withdraws and Affitor sends the payout through Wise. - [Set up with an AI agent, connect your program in one sign-in](https://affitor.com/docs/use-cases/ai-agent-setup.md): What an AI tool can do with Affitor today: read your account over the hosted MCP server with one sign-in, or create a program and add tracking with the CLI. --- id: "use-cases/partner-payouts" type: "doc" url: "https://affitor.com/docs/use-cases/partner-payouts" kind: "guide" updated: "2026-11-07" --- # Partners get paid, without sending a transfer yourself > Approved commissions go to the partner's balance; once you pay the invoice that covers them, the partner withdraws and Affitor sends the payout through Wise. ```mermaid sequenceDiagram autonumber participant Y as You participant A as Affitor participant P as Partner participant W as Wise A->>A: Approves the commission after the hold period A->>P: Adds it to the partner's balance A->>Y: Invoices you weekly for approved commissions Y->>A: Pays the invoice Note over P: The commission is ready to withdraw P->>A: Sets up payouts: legal name, payout method, tax form P->>A: Withdraws $20 or more A->>W: Sends the payout in USD A->>P: Marks the payout completed (sent) W->>P: Pays the partner's Wise or bank account ``` ## What you need You never send partner transfers, collect bank details or see tax forms. Each partner adds their own payout details, and Affitor pays every partner in USD through Wise: to a Wise account email, or to a bank account in the partner's legal name. PayPal is not a payout method. Approval and payment are separate steps. An approved commission is added to the partner's balance at once, but it shows as **Awaiting brand payment** until you pay the invoice that covers it. Your weekly invoice covers the approved commissions plus the platform fee. ## Steps --- id: "use-cases/sell-on-stripe" type: "doc" url: "https://affitor.com/docs/use-cases/sell-on-stripe" kind: "guide" updated: "2026-11-07" --- # Sell on Stripe, credit partners without a sales API call > Connect Stripe once: Affitor gets each Checkout or subscription payment from Stripe, finds the partner who referred the buyer and writes the commission. ```mermaid sequenceDiagram autonumber participant C as Customer participant W as Your site participant S as Stripe participant A as Affitor C->>W: Opens a partner link W->>A: Tracker records the click C->>S: Pays on Stripe S->>A: Sends the payment event A->>A: Finds the partner A->>A: Writes the commission Note over A: Approved after the hold period ``` ## What you need Stripe events credit Checkout purchases and subscription payments. A payment outside them, such as a PaymentIntent your server confirms, is not credited from Stripe: report it from your server ([Track Sale](/docs/api-reference/track-sale)). ## Steps --- id: "use-cases/subscriptions" type: "doc" url: "https://affitor.com/docs/use-cases/subscriptions" kind: "guide" updated: "2026-11-08" --- # Subscriptions, credit partners on renewals > Each paid invoice of a Stripe subscription earns the referring partner for as long as your commission type says. Refunds and active or lost chargebacks reverse or adjust matched commissions. ```mermaid sequenceDiagram autonumber participant C as Customer participant W as Your site participant S as Stripe participant A as Affitor C->>W: Opens a partner link W->>A: Tracker records the click C->>S: Subscribes on Stripe S->>A: Sends the first paid invoice A->>A: Finds the partner and writes the commission Note over A: Approved after the hold period loop Each renewal S->>A: Sends the paid invoice A->>A: Same partner, a commission while the term lasts end opt Refund or active/lost chargeback S->>A: Sends the refund or chargeback event A->>A: Applies the refund or disputed amount to a matched commission end ``` ## What you need Each paid invoice of the subscription is a sale: the first one, then every renewal. Renewals go to the partner of the first payment ([how Affitor matches them](/docs/brand/tracking/payment-tracking-stripe#why-subscriptions-need-subscription_datametadata)). The attribution window applies only to that first payment: once the customer has paid, renewals are credited however old the click is. The rate is the same for every plan, price and billing interval. Canceling, pausing or changing the plan writes nothing in Affitor: a canceled subscription stops earning because it stops paying, and after a plan change each paid invoice earns at the same rate. A refund is applied to the matched commission: a full refund reverses it, while a partial refund marks it refunded, with balance adjustment based on its prior state. An active or lost chargeback applies the disputed amount; inquiries and prevented disputes do not trigger a reversal. Some older sales, such as one payment shared by several invoices, are held for manual reconciliation instead. A new invoice whose payment was already refunded, even in part, before Affitor processed it is not recorded as a sale. A new invoice paid by several charges, or by one payment that also paid other invoices, is not recorded automatically. If you bill subscriptions outside Stripe, your server reports each payment and each refund ([Any payment provider](/docs/use-cases/any-payment-provider)). ## Steps --- id: "api-reference/integrations/nextjs" type: "doc" url: "https://affitor.com/docs/api-reference/integrations/nextjs" kind: "guide" updated: "2026-11-08" --- # Next.js > Add Affitor tracking to a Next.js (App Router) app: clicks, signups, and sales, with signup steps for Clerk, NextAuth (Auth.js) and Supabase Auth. This guide wires Affitor into a Next.js App Router app with the three moves every integration needs: **capture the click**, **track the signup**, **track the sale**. Steps 1 and 3 are the same for every app. Step 2 has a tab for each auth setup: **No auth library**, **Clerk**, **NextAuth** (Auth.js) and **Supabase** (Supabase Auth). :::note The `@affitor/sdk` package is **Beta**. The documented happy-path works; report issues on GitHub. ::: ## Prerequisites - Your **program ID** (program menu → **Program settings** → **Business**) - A **program API key** for server-side calls (leads and sales) - A Next.js app on the **App Router** - If you use one, your auth provider configured: **Clerk**, **NextAuth (Auth.js)** or **Supabase Auth** ## 1. Capture the click Install the SDK and load the tracker once on the client. The tracker reads `?via=` or `?aff=` from the URL and stores a first-party `affitor_click_id` cookie. `AffitorProvider` (from `@affitor/sdk/react`) loads it in the browser; on the server it does nothing and `useAffitor()` returns `null`. ```bash npm i @affitor/sdk ``` Create a client component that wraps your app in the provider: ```tsx // app/affitor-provider.tsx 'use client'; import { AffitorProvider } from '@affitor/sdk/react'; export function Providers({ children }: { children: React.ReactNode }) { return {children}; } ``` Render it once in your root layout: ```tsx // app/layout.tsx import { Providers } from './affitor-provider'; export default function RootLayout({ children }: { children: React.ReactNode }) { return ( {children} ); } ``` ## 2. Track the signup Pick the tab for how your app signs users up. When a user finishes signing up, link them to their click from your server, with **your own stable user ID**: you'll reuse this exact value at sale time. Send it with the server SDK and your program API key (e.g. in a route handler or right after the DB write): ```ts // server only, e.g. app/api/signup/route.ts import { cookies } from 'next/headers'; import Affitor from '@affitor/sdk/server'; const affitor = new Affitor({ apiKey: process.env.AFFITOR_API_KEY! }); // after the user row is created const clickId = (await cookies()).get('affitor_click_id')?.value; if (clickId) { await affitor.trackLead({ customerExternalId: user.id, // same ID you'll send at sale time clickId, // affitor_click_id, forwarded from the cookie email: user.email, // optional }); } ``` A lead needs the click: without a `clickId` (or a `customerExternalId` Affitor already knows), the API returns `400` and records nothing, which is expected for visitors who did not come through a partner link. :::note[Browser `signup()` is provisional by default] The tracker also has a browser helper, `affitor.signup(user.id, user.email)` (from `useAffitor()` in `@affitor/sdk/react`). Every program requires server-verified leads unless it is set to `browser_allowed`, so a browser-only signup is stored as **provisional**: the API returns `200` with `provisional: true`, but the lead does not settle, does not save your user ID, and does not count or pay per lead until your server sends the lead above or a Stripe Checkout payment for that customer arrives through your connected Stripe account. A sale sent to `/api/v1/track/sale` does not settle it. See [Lead auth policy](/docs/api-reference/track-lead/#lead-auth-policy). ::: The `affitor_click_id` is stored in a **first-party browser cookie**. A server-side Clerk webhook (`user.created`) runs with no access to that cookie, so it cannot supply the click ID on its own. **Two paths are available. The webhook path (server-side, with your API key) is the one that settles the lead:** every program requires server-verified leads unless it is set to `browser_allowed`, and a lead sent only from the browser stays provisional. See [Lead auth policy](/docs/api-reference/track-lead/#lead-auth-policy). **Option A: Clerk webhook (`user.created`, recommended)** Track the signup server-side from Clerk's `user.created` webhook. You **must** forward the click ID yourself. The webhook fires with no browser context, so Affitor cannot attribute the lead without it. **Step 1.** On the client, read the click ID and store it on the Clerk user before sign-up completes (e.g. in a pre-submit handler or just before redirecting away from your sign-up form): ```tsx 'use client'; import { useSignUp } from '@clerk/nextjs'; import { useAffitor } from '@affitor/sdk/react'; // inside your sign-up form component const { signUp } = useSignUp(); const affitor = useAffitor(); // null until the tracker has loaded // during your sign-up form submit await signUp.update({ unsafeMetadata: { affitor_click_id: affitor?.getClickId() ?? null, }, }); ``` **Step 2.** In your Clerk webhook handler, read the forwarded click ID and call `trackLead`: ```ts // app/api/webhooks/clerk/route.ts import { Webhook } from 'svix'; import Affitor from '@affitor/sdk/server'; const affitor = new Affitor({ apiKey: process.env.AFFITOR_API_KEY! }); export async function POST(req: Request) { const payload = await req.text(); const headers = { 'svix-id': req.headers.get('svix-id')!, 'svix-timestamp': req.headers.get('svix-timestamp')!, 'svix-signature': req.headers.get('svix-signature')!, }; const wh = new Webhook(process.env.CLERK_WEBHOOK_SECRET!); const event = wh.verify(payload, headers) as { type: string; data: Record }; if (event.type === 'user.created') { const user = event.data; const unsafeMeta = (user.unsafe_metadata as Record | undefined) ?? {}; await affitor.trackLead({ customerExternalId: user.id as string, clickId: unsafeMeta.affitor_click_id ?? undefined, // forwarded from the browser email: (user.email_addresses as Array<{ email_address: string }>)[0]?.email_address, }); } return new Response('ok'); } ``` :::note If `affitor_click_id` is `null` (the user arrived directly, not via an affiliate link), Affitor returns `400` and records nothing, because there is no click to link the lead to. That is expected for non-referred users; `trackLead` resolves with `ok: false` rather than throwing. ::: **Option B: Client-side `signup()`** After Clerk completes sign-up, call the tracker's `signup()` from a client component. The tracker reads the `affitor_click_id` cookie automatically; you do not need to pass it explicitly. On programs that require server-verified leads (every program unless it is set to `browser_allowed`), this lead is **provisional**: it does not settle, does not save the user ID, and does not count or pay per lead until the webhook path above sends the lead or a Stripe Checkout payment for that customer arrives through your connected Stripe account. A sale sent to `/api/v1/track/sale` does not settle it. Use it alongside Option A, not instead of it. Use Clerk's `useUser()` hook to access the signed-in user and `useAffitor()` to access the tracker, then fire `signup()` once both are available: ```tsx // app/post-signup.tsx: render this on your post-signup or onboarding page 'use client'; import { useEffect } from 'react'; import { useUser } from '@clerk/nextjs'; import { useAffitor } from '@affitor/sdk/react'; export function AffitorSignup() { const { user, isLoaded } = useUser(); const affitor = useAffitor(); // null until the tracker has loaded useEffect(() => { if (!isLoaded || !user || !affitor) return; const email = user.primaryEmailAddress?.emailAddress; if (email) affitor.signup(user.id, email); }, [isLoaded, user, affitor]); return null; } ``` `user.id` is Clerk's stable `userId`: use this exact value as `customerExternalId` at sale time too. :::note Place `` only on the page a new user lands on right after registration (e.g. `/onboarding`, `/welcome`, or wherever your post-signup redirect goes). Rendering it on every page adds nothing: on programs that require server-verified leads, a repeat browser lead returns `200` with `provisional: true` and records nothing new, and on programs set to allow browser leads, a repeat after the lead has settled is rejected with `400`. ::: **The cookie gap** NextAuth's `events.createUser` callback fires **on the server**, once per new user, so it looks like the ideal place to call `trackLead`. It is, but with one important caveat: **The `affitor_click_id` is a first-party browser cookie.** A server-side callback has no access to it. If you call `@affitor/sdk/server trackLead` from `events.createUser` without a `clickId`, Affitor cannot find the click: the call returns `400` and no lead is recorded. **Recommended: a server route called after sign-in** Send the lead from your own route handler, with your program API key. A request from the browser to your route handler carries the first-party `affitor_click_id` cookie, so the server can read it directly. Stock Auth.js sessions do not include `user.id`. Expose it once in your auth config, and add the type so `session.user.id` compiles: ```ts // auth.ts export const { auth, handlers, signIn, signOut } = NextAuth({ // ...your providers and adapter callbacks: { session({ session, user, token }) { session.user.id = user?.id ?? token.sub ?? ''; return session; }, }, }); // types/next-auth.d.ts import type { DefaultSession } from 'next-auth'; declare module 'next-auth' { interface Session { user: { id: string } & DefaultSession['user']; } } ``` Then the route: ```ts // app/api/affitor/lead/route.ts import { cookies } from 'next/headers'; import Affitor from '@affitor/sdk/server'; import { auth } from '@/auth'; // your NextAuth (Auth.js) instance const affitor = new Affitor({ apiKey: process.env.AFFITOR_API_KEY! }); // Needs the session callback above; without it session.user.id is empty and no lead is sent. export async function POST() { const session = await auth(); const clickId = (await cookies()).get('affitor_click_id')?.value; if (!session?.user?.id || !clickId) return new Response(null, { status: 204 }); // user.id is the NextAuth user ID; use it as customerExternalId everywhere: // signup, sale, Stripe metadata. await affitor.trackLead({ customerExternalId: session.user.id, clickId, email: session.user.email ?? undefined, }); return new Response(null, { status: 204 }); } ``` Call it once from the browser after NextAuth confirms a new user session: ```tsx // app/auth-tracker.tsx 'use client'; import { useEffect, useRef } from 'react'; import { useSession } from 'next-auth/react'; export function AffitorAuthTracker() { const { status } = useSession(); const tracked = useRef(false); useEffect(() => { if (status !== 'authenticated' || tracked.current) return; tracked.current = true; fetch('/api/affitor/lead', { method: 'POST' }); }, [status]); return null; } ``` Render it inside your root layout, inside `SessionProvider`: ```tsx // app/layout.tsx import { Providers } from './affitor-provider'; import { AffitorAuthTracker } from './auth-tracker'; import { SessionProvider } from 'next-auth/react'; export default function RootLayout({ children }: { children: React.ReactNode }) { return ( {children} ); } ``` :::note A lead is recorded once per customer. A repeat call for the same customer (for example on a later sign-in) returns `400` from `trackLead`, which resolves with `ok: false` instead of throwing, so it is safe to ignore. ::: :::note[Browser `signup()` is provisional by default] The tracker's browser helper, `affitor.signup(id, email)` from `useAffitor()`, sends the lead without your API key. Every program requires server-verified leads unless it is set to `browser_allowed`, so a browser-only lead is stored as **provisional** and does not settle, save the user ID, or count until your server sends the lead or a Stripe Checkout payment for that customer arrives through your connected Stripe account. A sale sent to `/api/v1/track/sale` does not settle it. See [Lead auth policy](/docs/api-reference/track-lead/#lead-auth-policy). ::: **Alternative: server-side via events.createUser with click-id forwarding** If you need the lead recorded the moment the user row is created (before the client redirects), you can use `events.createUser`, but you **must** forward the click ID from the browser yourself. **Step A.** Read the click ID on the client before the user submits the sign-up form: ```tsx 'use client'; import { useAffitor } from '@affitor/sdk/react'; // In your sign-up form component, read the click ID and include // it in the request or store it on the user's session/metadata. const affitor = useAffitor(); // null until the tracker has loaded const clickId = affitor?.getClickId() ?? null; // the affitor_click_id cookie value ``` **Step B.** Pass it through to your NextAuth config and call `trackLead` in the event: ```ts // auth.ts (NextAuth config) import Affitor from '@affitor/sdk/server'; import type { NextAuthConfig } from 'next-auth'; const affitor = new Affitor({ apiKey: process.env.AFFITOR_API_KEY! }); export const authConfig: NextAuthConfig = { // ...providers, callbacks, etc. events: { async createUser({ user }) { // user.id is the NextAuth-generated user ID; use it as // customerExternalId everywhere: signup, sale, Stripe metadata. await affitor.trackLead({ customerExternalId: user.id, clickId: user.affitorClickId ?? undefined, // forwarded from the browser email: user.email ?? undefined, }); }, }, }; ``` :::note `user.affitorClickId` is illustrative: the forwarding mechanism depends on your auth flow. Common approaches: store the click ID in the sign-up form's hidden field and write it to a custom user attribute before `createUser` fires, or pass it through a custom `session` object. Without it, `clickId` is undefined and the lead call returns `400` with nothing recorded. ::: If you cannot reliably forward the click ID into `events.createUser`, **use the server route above.** Send the lead from your server with your program API key, which is what settles it: every program requires server-verified leads unless it is set to `browser_allowed` (see [Lead auth policy](/docs/api-reference/track-lead/#lead-auth-policy)). The `affitor_click_id` is a first-party browser cookie. A Supabase Edge Function or DB trigger runs with no access to that cookie, so you must forward the click ID yourself. **Recommended: Edge Function with a forwarded click ID** 1. On the client, read the click ID and store it on the user's metadata during sign-up: ```tsx 'use client'; import { useAffitor } from '@affitor/sdk/react'; // inside your sign-up form component const affitor = useAffitor(); // null until the tracker has loaded // during your sign-up form submit (disable the button until `affitor` is set) const clickId = affitor?.getClickId() ?? null; // the affitor_click_id cookie value await supabase.auth.signUp({ email, password, options: { data: { affitor_click_id: clickId }, }, }); ``` 2. In your Edge Function (for example, one you call after sign-up, or one fired by a database webhook on new users), read the forwarded click ID and call `@affitor/sdk/server`: ```ts // supabase/functions/on-signup/index.ts import Affitor from 'npm:@affitor/sdk/server'; const affitor = new Affitor({ apiKey: Deno.env.get('AFFITOR_API_KEY')! }); // `user` is the new Supabase user, from your request or webhook payload const clickId = user.user_metadata?.affitor_click_id; if (clickId) { await affitor.trackLead({ customerExternalId: user.id, // Supabase user.id clickId, email: user.email, }); } ``` `user.id` is the stable Supabase UUID. Use this exact value as `customerExternalId` everywhere: at sale time and in any Stripe metadata. Without a forwarded `clickId`, Affitor cannot find the click: the lead call returns `400` and nothing is recorded. That is expected for users who did not arrive through a partner link. **Browser `signup()` (provisional by default)** The tracker also has a browser helper, `affitor.signup(userId, email)`, which you can call from Supabase's client-side `onAuthStateChange` listener. It reads the cookie automatically, but it sends the lead without your API key. On programs that require server-verified leads (every program unless it is set to `browser_allowed`), that lead is stored as **provisional**: it does not settle, does not save the user ID, and does not count or pay per lead until your server sends the lead or a Stripe Checkout payment for that customer arrives through your connected Stripe account. A sale sent to `/api/v1/track/sale` does not settle it. Use it alongside the Edge Function path, not instead of it. ## 3. Track the sale Pick one of two paths. This is the real choice: **does Stripe tell us, or does your server?** Send the same user ID you sent at signup. With an auth provider: - **Clerk:** use `user.id` (the Clerk user ID) as `affitor_customer_key` in Stripe metadata and as `customerExternalId` in `trackSale`. - **NextAuth:** use `session.user.id` as `affitor_customer_key` (Stripe path) or `customerExternalId` (server SDK path). It must match the value you sent at signup. - **Supabase:** use `session.user.id` (your `customerExternalId`) as `affitor_customer_key` in Stripe metadata, or as `customerExternalId` in `affitor.trackSale()`. ### Option A: Stripe integration (recommended for Stripe Checkout) Connect your Stripe account under **Program settings** › **Payments**, then attach Affitor metadata when you create the Checkout Session in **your own** Stripe account. Affitor receives the account's events through Stripe Connect (you add no webhook) and attributes the sale automatically, with no extra call. ```ts // server: creating the Checkout Session const session = await stripe.checkout.sessions.create({ mode: 'subscription', // or 'payment' line_items: [{ price: 'price_xxx', quantity: 1 }], success_url: 'https://yoursite.com/success', cancel_url: 'https://yoursite.com/cancel', metadata: { affitor_click_id: clickId, // from the affitor_click_id cookie affitor_customer_key: user.id, // SAME id you used at signup program_id: 'YOUR_PROGRAM_ID', }, // subscriptions: the SAME metadata here reaches the subscription's invoices subscription_data: { metadata: { affitor_click_id: clickId, affitor_customer_key: user.id, program_id: 'YOUR_PROGRAM_ID', }, }, }); ``` ### Option B: Server-side tracking (any provider) Report the finalized sale from your backend. Works with any payment provider. ```ts import Affitor from '@affitor/sdk/server'; const affitor = new Affitor({ apiKey: process.env.AFFITOR_API_KEY! }); await affitor.trackSale({ customerExternalId: user.id, // SAME id as signup amount: 4999, // integer cents invoiceId: invoice.id, // idempotency key; a duplicate returns 409 }); ``` For a real server-side sale, `customer_key` matches a key already stored on a customer in your program, for example by a server-verified lead or an attributed Stripe payment. If the key has not been stored, send a matching `click_id`; otherwise the request returns `400 Customer not found`. ## Verify ## Common mistakes --- id: "api-reference/integrations/node-express" type: "doc" url: "https://affitor.com/docs/api-reference/integrations/node-express" kind: "guide" updated: "2026-11-08" --- # Node.js server > Server-side Affitor integration with @affitor/sdk/server: track signups and sales from your Express or Fastify backend, including a raw-body Stripe webhook in Fastify. This guide wires Affitor into a Node.js server app built with **Express** or **Fastify**. Because both are pure server runtimes, the click is captured by a frontend script tag, then the `affitor_click_id` is forwarded to your server so all tracking calls, lead and sale, happen server-side with `@affitor/sdk/server`. Where the two differ, the code has an **Express** and a **Fastify** tab. Building with Next.js? See the [Next.js guide](/docs/api-reference/integrations/nextjs). :::note The `@affitor/sdk` package is **Beta**. The documented happy-path works; report issues on GitHub. ::: ## Prerequisites - Your **program ID** (program menu → **Program settings** → **Business**) - A **program API key** for server-side calls (dashboard → API keys) - `@affitor/sdk` installed in your backend (the Fastify example also installs `stripe`) ```bash npm i @affitor/sdk ``` ```bash npm i @affitor/sdk stripe ``` ## 1. Capture the click (frontend) Add the Affitor script tag to every page of your frontend. It reads `?via=` or `?aff=` from the URL and stores the `affitor_click_id` as a first-party cookie automatically, with no JS call required. ```html ``` When your signup form submits, read the click id and send it to your server along with the form data: ```js // frontend: read the click id before submitting const clickId = window.affitor?.getClickId() ?? null; await fetch('/api/signup', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ email, password, affitorClickId: clickId }), }); ``` :::note The `affitor_click_id` lives in a **first-party browser cookie**. Your Express or Fastify handlers run with no access to that cookie, so you must forward the click id from the client explicitly. Without it, the lead has no partner to attribute to. ::: ## 2. Track the signup Instantiate the SDK once (module-level or via a shared singleton) and call `trackLead` as soon as you create the user record. ```js // lib/affitor.js import Affitor from '@affitor/sdk/server'; export const affitor = new Affitor({ apiKey: process.env.AFFITOR_API_KEY }); ``` ```js // routes/signup.js import express from 'express'; import { affitor } from '../lib/affitor.js'; import { createUser } from '../db/users.js'; const router = express.Router(); router.post('/api/signup', async (req, res) => { const { email, password, affitorClickId } = req.body; // 1. Create the user in your database const user = await createUser({ email, password }); // 2. Track the lead with Affitor const result = await affitor.trackLead({ customerExternalId: user.id, // stable internal ID; reuse at sale time clickId: affitorClickId, // forwarded from the browser (may be null) email: user.email, // optional but improves attribution }); if (!result.ok) { // Non-fatal: log and continue; the user is already created console.error('[affitor] trackLead failed', result.status, result.error); } res.json({ userId: user.id }); }); export default router; ``` ```js // routes/signup.js import { affitor } from '../lib/affitor.js'; import { createUser } from '../db/users.js'; export default async function signupRoutes(fastify) { fastify.post('/api/signup', async (request, reply) => { const { email, password, affitorClickId } = request.body; // 1. Create the user in your database const user = await createUser({ email, password }); // 2. Track the lead with Affitor const result = await affitor.trackLead({ customerExternalId: user.id, // stable internal ID; reuse at sale time clickId: affitorClickId, // forwarded from the browser (may be null) email: user.email, // optional but improves attribution }); if (!result.ok) { // Non-fatal: log and continue; the user is already created request.log.error({ status: result.status, error: result.error }, '[affitor] trackLead failed'); } return { userId: user.id }; }); } ``` `customerExternalId` is your **stable internal user ID**. Use the exact same value when you track a sale: this is what links a partner's click to a commission. :::note If you use a **server-side auth webhook** (e.g. a third-party identity provider firing a `user.created` event), that webhook runs with no browser context and therefore no `affitor_click_id`. In that case you must read `window.affitor.getClickId()` on the client at signup time, store the click id on the user record or pass it through your own API, and then forward `clickId` to `trackLead` from the webhook. The client-side path above is simpler and more reliable. ::: ## 3. Track the sale Sales must always be tracked server-side, never from the browser. ### Option A: Stripe integration (recommended for Stripe Checkout) Connect your Stripe account under **Program settings** › **Payments**, then attach Affitor metadata when you create the Checkout Session. Affitor receives the account's `checkout.session.completed` and invoice events (`invoice.payment_succeeded`, `invoice.paid`) through Stripe Connect (you add no webhook) and attributes the sale automatically, with no extra `trackSale` call needed. Attach `affitor_click_id`, `affitor_customer_key`, and `program_id`. For subscriptions, put the same fields in `subscription_data.metadata` too: only that copy reaches the Subscription and its invoices (the first payment and every renewal). ```js // server: creating the Checkout Session const session = await stripe.checkout.sessions.create({ mode: 'subscription', // or 'payment' line_items: [{ price: 'price_xxx', quantity: 1 }], success_url: 'https://yoursite.com/success', cancel_url: 'https://yoursite.com/cancel', metadata: { // first payment (checkout.session.completed) affitor_click_id: affitorClickId, // forwarded from the browser affitor_customer_key: user.id, // SAME id used at signup program_id: 'YOUR_PROGRAM_ID', }, // Subscriptions: only this copy reaches the Subscription and its invoices subscription_data: { metadata: { affitor_click_id: affitorClickId, affitor_customer_key: user.id, program_id: 'YOUR_PROGRAM_ID', }, }, }); ``` ### Option B: Server-side tracking (any payment provider) Call `trackSale` directly from your payment webhook or post-charge handler. ```js // routes/webhook.js (or wherever you confirm payment) import { affitor } from '../lib/affitor.js'; router.post('/webhooks/payment', async (req, res) => { const event = verifyAndParse(req); // your provider's webhook verification if (event.type === 'payment.succeeded') { const { userId, amountCents, invoiceId } = event.data; const result = await affitor.trackSale({ customerExternalId: userId, // SAME id as trackLead amount: amountCents, // integer cents, e.g. 4999 for $49.99 invoiceId: invoiceId, // idempotency key; duplicate returns 409 }); if (!result.ok) { if (result.status === 409) { // Already tracked; safe to ignore } else { console.error('[affitor] trackSale failed', result.status, result.error); } } } res.sendStatus(200); }); ``` This example tracks the sale from your own Stripe webhook (self-hosted sale tracking). It reads the Affitor metadata from the Checkout Session, so attach it as in Option A. In Fastify, the Stripe webhook route needs the **raw request body** so `stripe.webhooks.constructEvent` can verify the signature. Fastify parses JSON by default, which corrupts the signature, so register a raw-body parser **scoped to the webhook route**. **Configure the raw body** Add a content-type parser that hands Stripe the untouched `Buffer`. Keep it scoped so your other routes still get parsed JSON. ```js // server.js import Fastify from 'fastify'; const fastify = Fastify({ logger: true }); // Capture the raw body as a Buffer for the Stripe webhook only. // Stripe signature verification fails if the body is parsed/re-serialized. fastify.addContentTypeParser( 'application/json', { parseAs: 'buffer' }, (request, body, done) => { if (request.routerPath === '/webhooks/stripe') { // Leave the raw Buffer untouched for signature verification. done(null, body); } else { try { done(null, JSON.parse(body.toString())); } catch (err) { err.statusCode = 400; done(err, undefined); } } }, ); ``` :::note If you prefer not to override the global JSON parser, the [`fastify-raw-body`](https://github.com/Eomm/fastify-raw-body) plugin exposes `request.rawBody` on a per-route basis instead. Either way, the Stripe handler must receive the **unparsed** body. ::: **The webhook handler** ```js // routes/stripe-webhook.js import Stripe from 'stripe'; import { affitor } from '../lib/affitor.js'; const stripe = new Stripe(process.env.STRIPE_SECRET_KEY); // The Tracking API reads ISO 4217 minor units. Stripe uses the same units except ISK and UGX // (sent with two extra decimals) and MGA (sent with none), so convert those three. const toIsoMinor = (amount, currency) => currency === 'isk' || currency === 'ugx' ? amount / 100 : currency === 'mga' ? amount * 100 : amount; export default async function stripeWebhookRoutes(fastify) { fastify.post('/webhooks/stripe', async (request, reply) => { const signature = request.headers['stripe-signature']; let event; try { event = stripe.webhooks.constructEvent( request.body, // the raw Buffer from the content-type parser above signature, process.env.STRIPE_WEBHOOK_SECRET, ); } catch (err) { request.log.error({ err }, '[stripe] signature verification failed'); return reply.code(400).send(`Webhook Error: ${err.message}`); } switch (event.type) { case 'checkout.session.completed': { const session = event.data.object; // Skip $0 / setup-mode sessions (free trials, $0 invoices): the SDK rejects // a non-positive amount, and there's no revenue to attribute yet. if (session.amount_total && session.amount_total > 0) { const result = await affitor.trackSale({ // The click id the metadata step writes attributes the sale even when only the // browser sent the lead; the customer key matches once it is stored on the customer. clickId: session.metadata?.affitor_click_id, customerExternalId: session.metadata?.affitor_customer_key, amount: toIsoMinor(session.amount_total, session.currency), // ISO minor units (cents for USD) currency: session.currency, // Stripe sends lowercase; Affitor reads it case-insensitively invoiceId: session.id, // idempotency key; a duplicate returns 409 }); if (!result.ok && result.status !== 409) { request.log.error({ status: result.status, error: result.error }, '[affitor] trackSale failed'); } } break; } } return reply.code(200).send({ received: true }); }); } ``` :::note The handler above tracks the **first** subscription payment (`checkout.session.completed`). Subscription **renewals** arrive as a different event (`invoice.paid`) and need their own `case`: see [Subscription Renewals](/docs/api-reference/integrations/stripe#subscription-renewals) in the Stripe Checkout metadata guide. These handlers are only for self-hosted sale tracking. If your Stripe account is connected to the program, Affitor already records your Checkout payments and renewals from Stripe's events, so do **not** also call `trackSale`. A one-time payment or a renewal is recorded under the same id on both paths and Affitor refuses the second, but if your call lands first, its sale is not linked to the Stripe payment, so a refund in Stripe does not reverse its commission. A subscription's first payment can be counted twice: this handler records it under the Checkout Session id, and Stripe Connect records it again under the invoice id. ::: The `invoiceId` field acts as an idempotency key. If your webhook fires twice for the same payment, the second call returns `{ ok: false, status: 409 }`: handle it as a no-op, not an error. To track a refund, call `trackRefund` with the same `invoiceId`: ```js await affitor.trackRefund({ invoiceId: originalInvoiceId, }); ``` ### Raw API fallback (cURL / any HTTP client) If you cannot use the npm package, call the REST endpoint directly. All server-side endpoints require a `Bearer` token. ```bash curl -X POST https://api.affitor.com/api/v1/track/sale \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "transaction_id": "txn_abc", "customer_key": "user_123", "amount_cents": 4999, "currency": "USD" }' ``` :::note `customer_key` in the raw API, `customerExternalId` in `@affitor/sdk/server`, and `affitor_customer_key` in Stripe metadata are all **the same value**: your stable internal user ID. Keep it consistent. ::: ## Verify ## Common mistakes --- id: "api-reference/integrations/polar" type: "doc" url: "https://affitor.com/docs/api-reference/integrations/polar" kind: "guide" updated: "2026-11-07" --- # Polar > Canonical recipe for attributing Polar payments to Affitor partners: one-time, subscriptions, renewals, and refunds. No Stripe account needed. This guide is the **canonical reference for the Polar sale path**. Polar is a merchant of record, so there is no Stripe account to connect — instead, your app hosts a small webhook route that reports every paid order to Affitor. :::note The `@affitor/sdk` package is **Beta**. The documented happy-path works; report issues on GitHub. ::: ## Prerequisites - Your **program ID** and a **program API key** (run `npx affitor init`, or, in the program menu, **Program settings** → **Business** for the ID and **Developers** → **API keys** for the key) - A Polar organization with checkout working in your app - Access to your Polar organization's webhook settings. Sandbox is a separate environment with its own tokens and its own webhook endpoints (`sandbox-api.polar.sh`). ## What you will set up In your Polar organization, add a webhook endpoint delivering `order.paid`, `refund.created` and `refund.updated` to a route in your own app — `https:///api/polar/webhook` in the examples below — and store the signing secret Polar gives you as `POLAR_WEBHOOK_SECRET`. The rest of this page is the route that receives those deliveries, plus the click and signup steps that come before it. ## 1. Capture clicks and track signups Identical to the framework integration — follow [Step 1](/docs/api-reference/integrations/nextjs#1-capture-the-click) and [Step 2](/docs/api-reference/integrations/nextjs#2-track-the-signup) in the Next.js guide, or your framework's equivalent. Keep the `userId` you send at signup (`signup(userId)` / `trackLead({ customerExternalId: userId })`) — you will plant it on every Polar checkout as `user_id`. ## 2. Carry attribution into the checkout Polar copies checkout metadata onto the resulting Order **and** Subscription, so the webhook can resolve the partner days later. Two carriers work; use whichever fits your checkout: ### Server-created Checkout Sessions ```ts // When creating the Polar checkout server-side, attach metadata: metadata: { affitor_click_id: affitorClickId, // from the `affitor_click_id` cookie user_id: user.id, // SAME stable id you used at signup } ``` ### Checkout Links (zero server code) Append the click id to the link — Polar automatically copies a `?reference_id=` query param into the checkout's metadata, and it propagates to every resulting order, **renewals included**: ```text https://buy.polar.sh/polar_cl_xxx?reference_id= ``` If you use the `@polar-sh/nextjs` `Checkout` route handler instead, pass `customerExternalId` (your user id) and a URL-encoded `metadata` JSON query param — the adapter forwards both. ## 3. The webhook glue route Create `app/api/polar/webhook/route.ts` (Next.js App Router). The `Webhooks()` helper validates the Standard-Webhooks signature with `POLAR_WEBHOOK_SECRET` before any callback runs: ```ts import { Webhooks } from '@polar-sh/nextjs'; import { Affitor } from '@affitor/sdk/server'; const affitor = new Affitor({ apiKey: process.env.AFFITOR_API_KEY ?? '' }); export const POST = Webhooks({ webhookSecret: process.env.POLAR_WEBHOOK_SECRET!, onOrderPaid: async (payload) => { const order = payload.data; // Skip $0 orders (free tiers, 100%-off) — no revenue to attribute. if (!order.totalAmount || order.totalAmount <= 0) return; const res = await affitor.trackSale({ customerExternalId: (order.metadata?.user_id as string | undefined) ?? order.customer?.externalId ?? order.customerId, clickId: (order.metadata?.affitor_click_id ?? order.metadata?.reference_id) as string | undefined, amount: order.totalAmount, // minor units (cents for USD), after discounts, tax included taxCents: order.taxAmount, // the tax inside totalAmount; commissions use totalAmount - taxAmount currency: order.currency, invoiceId: order.id, // idempotency key; a 409 means this id was used before (the API's error.details.sale_id: yours, or null for another program) saleType: order.subscriptionId ? 'subscription' : 'payment', isRecurring: order.billingReason === 'subscription_cycle', subscriptionId: order.subscriptionId ?? undefined, }); if (!res.ok && res.status !== 409) { console.error('[affitor] trackSale failed', res.status, res.error); } }, // One call per refund, with that refund's own amount. Polar sends refund.created // "regardless of status", so report only once the refund has succeeded; a repeat // with the same amount (created + updated both succeeded) is ignored by Affitor. onRefundCreated: async (payload) => reportRefund(payload.data), onRefundUpdated: async (payload) => reportRefund(payload.data), }); async function reportRefund(refund: { status: string; orderId: string; amount: number; taxAmount?: number }) { if (refund.status !== 'succeeded') return; const res = await affitor.trackRefund({ invoiceId: refund.orderId, // the ORDER id you sent as the sale's invoiceId refundAmountCents: refund.amount + (refund.taxAmount ?? 0), // same basis as the sale (order.totalAmount includes tax) }); if (!res.ok) { console.error('[affitor] trackRefund failed', res.status, res.error); } } ``` :::note **Field names are the SDK's camelCase.** The `Webhooks()` helper (and `validateEvent` from `@polar-sh/sdk/webhooks`) parse the raw webhook JSON into typed objects: `order.totalAmount`, `order.subscriptionId`, `order.billingReason`. The wire format's snake_case names (`total_amount`, …) are `undefined` on the parsed payload — reading them silently loses the sale amount and attribution. ::: **Attribution resolution.** Affitor resolves the partner from, in order: `customerExternalId` matched against the lead you tracked at signup, then `clickId` (the planted `affitor_click_id`, or the checkout link's `reference_id`). Supplying both is the recommended default. ## Subscription renewals Nothing extra to wire: Polar fires `order.paid` on **every** billing cycle, and the metadata planted at checkout (or carried by `reference_id`) propagates to renewal orders. The handler above marks renewals precisely via `billingReason === 'subscription_cycle'` (first subscription payments arrive as `subscription_create`). ## Refunds Report each refund once, with **that refund's own amount**, after it has succeeded (the handler above does this from `refund.created` / `refund.updated`). Use the same tax basis as the sale amount you sent; amounts add up on the sale, and the commission is reversed once they reach the sale amount. Omit `refundAmountCents` to refund everything not yet refunded. Do **not** pass `order.refundedAmount` from `order.refunded`: it is a running total, and each call is counted as a new refund. A retry with the same amount is ignored; to report two separate refunds of the same amount, call the [HTTP endpoint](/docs/api-reference/track-refund) with a distinct `refund_id` for each. ## Verify ## Common mistakes --- id: "api-reference/integrations/stripe" type: "doc" url: "https://affitor.com/docs/api-reference/integrations/stripe" kind: "guide" updated: "2026-11-08" --- # Stripe Checkout metadata > Code that passes the partner click to Stripe Checkout, one-time and subscription, plus a renewal handler for a Stripe webhook you host yourself. This guide has the code for the Stripe sale path. How Affitor reads these payments (the events, the lookup order, subscriptions and repeat purchases) is on the [Stripe](/docs/brand/tracking/payment-tracking-stripe) page. Other framework guides (Next.js, Express, etc.) link here for Step 3. If you need click capture or signup tracking first, start with the [Next.js guide](/docs/api-reference/integrations/nextjs) or the framework guide for your stack. :::note The `@affitor/sdk` package is **Beta**. The documented happy-path works; report issues on GitHub. ::: ## Prerequisites - Your **program ID** (program menu → **Program settings** → **Business**) - A **program API key** (program menu → **Program settings**, then **Developers** → **API keys**) - Stripe Checkout or Stripe Billing already working in your app - Your Stripe account connected to the program (program menu → **Program settings** → **Payments**, **Connect Stripe**). Affitor then receives the account's events through Stripe Connect; you do not add a webhook ## 1. Capture clicks and track signups These two steps are identical to the framework integration. Follow [Step 1](/docs/api-reference/integrations/nextjs#1-capture-the-click) and [Step 2](/docs/api-reference/integrations/nextjs#2-track-the-signup) in the Next.js guide, or your framework's equivalent. The key thing to take away: when you call `signup(userId)` or `trackLead({ customerExternalId: userId })`, keep that `userId`: you will attach it to every Checkout Session as `affitor_customer_key`. ## 2. Attach Affitor metadata to the Checkout Session When you create a Stripe Checkout Session on your server, attach three metadata fields: `affitor_click_id`, `affitor_customer_key`, and `program_id`. **How to read `affitor_click_id` server-side:** the browser SDK stores the click id in a first-party cookie called `affitor_click_id`. Read it from the incoming HTTP request and forward it to your server. For example, in a Next.js Route Handler you can read `cookies().get('affitor_click_id')?.value`. In a plain Express handler you can read `req.cookies.affitor_click_id`. :::note `affitor_customer_key` must be the **same stable user ID** you sent at signup: `signup(userId)` on the client, `customerExternalId: userId` on the server, and `affitor_customer_key: userId` in Stripe metadata are all the same field. Mismatching them breaks attribution. ::: ### One-time payment (`mode: 'payment'`) ```ts const session = await stripe.checkout.sessions.create({ mode: 'payment', line_items: [{ price: 'price_xxx', quantity: 1 }], success_url: 'https://yoursite.com/success', cancel_url: 'https://yoursite.com/cancel', metadata: { affitor_click_id: clickId, // from the affitor_click_id cookie affitor_customer_key: user.id, // SAME id you used at signup program_id: 'YOUR_PROGRAM_ID', }, }); ``` Affitor listens to the `checkout.session.completed` webhook event and attributes the payment automatically. No extra call needed. ### Subscription (`mode: 'subscription'`) For subscriptions, put the same fields in `subscription_data.metadata`: an invoice carries the subscription's metadata, not the Checkout Session's ([why subscriptions need it](/docs/brand/tracking/payment-tracking-stripe#why-subscriptions-need-subscription_datametadata)). ```ts const session = await stripe.checkout.sessions.create({ mode: 'subscription', line_items: [{ price: 'price_xxx', quantity: 1 }], success_url: 'https://yoursite.com/success', cancel_url: 'https://yoursite.com/cancel', metadata: { affitor_click_id: clickId, affitor_customer_key: user.id, program_id: 'YOUR_PROGRAM_ID', }, // The subscription's invoices (first payment and renewals) read the click from here subscription_data: { metadata: { affitor_click_id: clickId, affitor_customer_key: user.id, program_id: 'YOUR_PROGRAM_ID', }, }, }); ``` ## 3. How Affitor attributes payments Which Stripe events record a sale and how Affitor finds the partner, from the click in the metadata to the customer key, are on the Stripe page: [the events](/docs/brand/tracking/payment-tracking-stripe#stripe-events-affitor-reads) and [the lookup order](/docs/brand/tracking/payment-tracking-stripe#how-affitor-resolves-attribution-from-stripe). ## 4. Alternative: server-side tracking (non-Stripe) If you are not using Stripe Checkout, or you need to report a sale from a different payment provider, report it from your server after the payment is confirmed: [server-side tracking](/docs/brand/tracking/payment-tracking-stripe#option-a-server-side-tracking) on the Stripe page, and [Track Sale](/docs/api-reference/track-sale) for every field. ## Verify ## Common mistakes ## Appendix: self-hosted webhook ### Subscription Renewals If you self-host the Stripe webhook and call `trackSale` yourself (rather than relying on Affitor's Connect webhook), renewals need their **own handler**. The first payment fires as `checkout.session.completed`; every subsequent renewal arrives as a separate `invoice.paid` event with `billing_reason: 'subscription_cycle'`. Without a dedicated `case`, every renewal commission is silently missed. Stripe copies the `subscription_data.metadata` you set at checkout creation onto the Subscription, and stamps it onto every renewal invoice. For a real server-side sale, `customer_key` matches a key already stored on a customer in your program. A default browser-only signup does not store it. Pass the subscription's `affitor_click_id` as `clickId` as well: a successful server-side sale does not save the customer key for later sales. Two nuances matter: - **Skip $0 renewals.** 100%-off coupons and fully credit-covered cycles produce `invoice.paid` events with `amount_paid` of `0`. The SDK rejects a non-positive amount, so guard against it. - **Stripe Basil metadata path.** Stripe API version Basil (`2025-03-31`+) moved `subscription_details` under `invoice.parent`. Pre-Basil accounts still expose it at the legacy top level (`invoice.subscription_details`). Read the Basil path first and fall back to the legacy one so the handler works on both. The handler calls the server SDK: ```ts import Affitor from '@affitor/sdk/server'; const affitor = new Affitor({ apiKey: process.env.AFFITOR_API_KEY! }); ``` Add this as a separate `case` in the **same** Stripe webhook handler that processes `checkout.session.completed`: ```ts case 'invoice.paid': { const invoice = event.data.object; // Only renewals: the first invoice is already counted at checkout.session.completed. if (invoice.billing_reason !== 'subscription_cycle') break; // Skip $0 renewals (100%-off coupons, fully credit-covered): the SDK rejects a non-positive amount. if (!invoice.amount_paid || invoice.amount_paid <= 0) break; // The Tracking API reads ISO 4217 minor units. Stripe uses the same units except ISK and UGX // (sent with two extra decimals) and MGA (sent with none), so convert those three. const c = invoice.currency; // lowercase from Stripe; Affitor reads it case-insensitively const amount = c === 'isk' || c === 'ugx' ? invoice.amount_paid / 100 : c === 'mga' ? invoice.amount_paid * 100 : invoice.amount_paid; await affitor.trackSale({ // Stripe Basil (2025-03-31+) moved subscription_details under invoice.parent; // read the Basil path first, fall back to the legacy top-level for pre-Basil accounts. customerExternalId: invoice.parent?.subscription_details?.metadata?.affitor_customer_key ?? invoice.subscription_details?.metadata?.affitor_customer_key, clickId: invoice.parent?.subscription_details?.metadata?.affitor_click_id ?? invoice.subscription_details?.metadata?.affitor_click_id, amount, // ISO minor units of invoice.currency (cents for USD) currency: c, invoiceId: invoice.id, // idempotency key; a 409 means this id was used before (the API's error.details.sale_id: yours, or null for another program) isRecurring: true, saleType: 'subscription', // Basil relocated the subscription id under invoice.parent.subscription_details; // fall back to the legacy top-level invoice.subscription for pre-Basil accounts. subscriptionId: invoice.parent?.subscription_details?.subscription ?? (typeof invoice.subscription === 'string' ? invoice.subscription : invoice.subscription?.id), }); break; } ``` :::note This handler is only needed when you **self-host** sale tracking via `trackSale`. If Stripe is connected, Affitor already records each renewal from Stripe's events, so do **not** also call `trackSale`. Both record the renewal under the invoice id and Affitor refuses the second, but if your call lands first, its sale is not linked to the Stripe payment, so a refund in Stripe does not reverse its commission. ::: --- id: "brand/billing/overdue-policy" type: "doc" url: "https://affitor.com/docs/brand/billing/overdue-policy" kind: "reference" updated: "2026-09-24" --- # Overdue Invoices & Program Pause Policy > How Affitor handles unpaid commission invoices, when programs pause, and how to resume. When a commission invoice is not paid by its due date, Affitor pauses the program until the balance clears. Tracking links keep working, partner data is preserved, and the program returns to active automatically once the overdue invoice is marked paid. ## The billing timeline Commissions approved Invoice issued Mon 09:00 UTC Pay within 7 days → **paid:** Status: paid · **past due:** Status: overdue Program paused Mark invoice paid Program auto-resumed | Stage | When | What happens | |-------|------|--------------| | **Invoice issued** | Every Monday at 09:00 UTC | Invoice includes every approved commission not yet on an invoice, whenever it was approved. Its billing period (the prior Monday–Sunday) is a label and does not limit what it includes | | **Invoice minimum** | Each Monday | If the approved commissions add up to less than the invoice minimum (currently $10), no invoice is issued that week. They carry forward and appear on a later invoice | | **Net terms** | 7 days from issue date | The default. Talk to your account contact if you need different terms | | **Overdue check** | Daily at 10:00 UTC | Invoices past their due date are marked overdue | | **Program paused** | Same overdue run | The program enters a paused state; an email is sent to the workspace owner | | **Auto-resume** | When the invoice is marked paid | The program returns to active on its own; you do not need to reactivate it. A wire transfer is marked paid by Affitor's billing team after they match it to the invoice | --- ## When a program is paused Pause is triggered automatically the first time a commission invoice passes its due date. ### What changes while paused - **Program status** flips to **Paused** in your dashboard and in partner-facing views. - **Marketplace visibility** — paused programs are hidden from public partner discovery. Existing partners keep their dashboard access. - **Audit log** records the transition with a reference to the originating invoice. ### What does not change while paused - **Existing tracking links** continue to resolve. Affitor never breaks partner URLs while you resolve billing. - **Click, lead, and sale events** continue to be recorded. Sales attributed while paused still create commissions and platform fees exactly as when the program is active, and they appear on your next invoice. Pausing does not stop charges from accruing. - **Partner data** — referrals, audience, and historic commissions are preserved in full. - **Stripe Connect and customer-facing checkout** continue to work. Pause is a billing state, not a checkout state. > Pause is a billing signal, not a tracking kill switch. Your customers are unaffected. Partners see the program as paused inside their dashboard and stop receiving new applications. --- ## How to resume A paused program returns to active automatically when the overdue invoice is marked paid. You do not need to reactivate it yourself. For a wire transfer, the invoice is marked paid once Affitor's billing team has matched your payment to it. ```mermaid sequenceDiagram Advertiser->>Affitor: Wire transfer arrives Affitor->>Affitor: Billing team matches payment to invoice Affitor->>Invoice: status = paid Invoice->>Program: status = active Affitor->>Audit: program_unpaused entry ``` Wire to the Wise account shown on the invoice page. Always include the invoice number in the transfer reference so we can match the payment. Affitor's billing team matches the transfer to your invoice and marks it paid. Marking the invoice paid resumes the program, and the audit log records the unpause with the invoice number. You don't need to reactivate anything. If you've paid and the program is still paused a business day later, contact billing — the most common cause is a missing invoice number in the transfer reference. --- ## How to pay an invoice Affitor bills through Wise wire transfers. Each invoice page shows the destination account, beneficiary, and the exact amount due. You pay the invoice to Affitor LLC, the beneficiary shown on the invoice; Affitor then pays partners their withdrawals. | Field | Where to find it | |-------|------------------| | Destination account | Invoice page in the advertiser dashboard | | Reference | Invoice number, e.g. `INV-2026-06-0042` | | Amount | Total due: the approved commissions on the invoice plus the platform fee | | Due date | 7 days after invoice issued | > Card payment through Stripe Checkout is off by default and is not available on every account. If your invoice page shows a pay-by-card option, you can use it for pending or overdue invoices as an alternative to wire transfer, and the invoice is marked paid when the checkout completes. Otherwise, pay by wire. --- ## Avoiding pause Check the Billing tab after each Monday's invoice run. A new-invoice email is not sent on every account, so don't wait for an email — and don't wait for the overdue email. Billing emails are sent from noreply@affitor.com with billing@affitor.com as the reply-to address. Add both to your AP allowlist so invoice and overdue emails reach the right inbox. If your AP cycle is longer than 7 days, talk to your account contact to align timing or extend net terms. --- ## Questions? - **Billing**: [billing@affitor.com](mailto:billing@affitor.com) - **General support**: [support@affitor.com](mailto:support@affitor.com) --- id: "brand/cli/agent-setup" type: "doc" url: "https://affitor.com/docs/brand/cli/agent-setup" kind: "guide" updated: "2026-11-08" --- # Set up a coding agent > Preview project-scoped Affitor MCP configuration, apply it for your coding agent, and check local files with doctor. Configure Claude Code, Cursor, or Codex to use Affitor's local tracking MCP server in your project. CLI 0.4.5 adds a preview, an explicit apply step, and a read-only static check. This uses a **program API key** for integration work. To read account reports through the hosted server with Affitor sign-in, use [Connect your AI tool](/docs/api-reference/connect-ai-tool) instead. ## 1. Preview the selected client Run from your app's project root. This example selects Claude Code; replace `claude_code` with `cursor` or `codex` for your client. ```bash npx affitor@0.4.8 agent setup --client claude_code --dry-run --json ``` The output has `status: "planned"`, file paths, operations, backup paths, and any manual instructions. It does not include existing config contents or write files. Repeat `--client` to select multiple clients from your own terminal. When a coding agent invokes setup, it can configure only itself. Without `--client`, a detected caller selects itself; otherwise an interactive terminal asks you to select clients. Finding a client directory alone never selects it. ## 2. Apply the reviewed plan After reviewing the preview, run: ```bash npx affitor@0.4.8 agent setup --client claude_code --yes --json ``` Unlike `onboard --json`, **`agent setup --yes --json` writes files**. Without `--yes` or `--auto-confirm`, an interactive run asks before applying; a JSON or non-interactive run returns `needs_confirmation` and exits `1`. | Client | MCP configuration | Installed skill | |---|---|---| | `claude_code` | Project `.mcp.json` | `.claude/skills/affitor/SKILL.md` | | `cursor` | Project `.cursor/mcp.json` | `.cursor/skills/affitor/SKILL.md` | | `codex` | Manual instructions in the output | `.agents/skills/affitor/SKILL.md` | Setup writes `.affitor/agent-mcp.cjs` and Git ignore rules for local credentials and backups. For Claude Code and Cursor, it preserves other MCP entries and sets the entry named `affitor`. Existing files it changes get a private first snapshot under `.affitor/backups/`; an earlier snapshot is kept on later runs. The generated MCP entry contains this machine's absolute project path. Keep it local or regenerate it on each teammate's machine. A successful apply reports `needs_human`, not a verified connection. For Codex, follow the printed manual MCP instructions after applying. On Windows, the output gives a command and exact argument for Codex MCP settings instead of a shell command. Setup does not edit Codex's MCP settings for you. ## 3. Configure the program key privately Make the program's `AFFITOR_API_KEY` available to the agent process, or keep one `AFFITOR_API_KEY` assignment in this project's `.affitor/.env`. Use a [program API key](/docs/brand/api-keys), not your account login token. Never paste the key into a prompt, MCP JSON, or Git. The launcher reads the environment first, then `.affitor/.env`. It starts the pinned `@affitor/mcp@0.2.2` server when your client launches it and keeps sale/refund tools disabled. Setup itself does not start an agent session or call the Affitor API. ## 4. Check the local files ```bash npx affitor@0.4.8 doctor --client claude_code --json ``` `doctor` reads local configuration without editing files or calling Affitor. It checks `AFFITOR_API_KEY` in the environment or `.affitor/.env`; the global `--api-key` and `--api-url` flags do not change this check. | Result | Meaning | Next step | |---|---|---| | `missing`, `stale`, or `invalid` client status | Local files need attention | Review a fresh setup dry-run | | `credential: "missing"` | No credential accepted by the local parser | Configure the program key privately | | `credential: "present_unverified"` | A credential has an accepted local format | Check the live session next; the key has not been authenticated | | `credential_tracked` warning | `.affitor/.env` is tracked by Git | Rotate the key and remove it from tracking/history through your repository process | | Codex client status `manual` | MCP settings need a separate manual step | Follow the setup output; static doctor cannot verify those settings | The top-level result is `aligned` with exit `0` only when every checked client has aligned files, a `present_unverified` credential, and no warnings. Otherwise it reports `needs_attention` and exits `1`. Codex stays `manual` in this static check, including after you configure it yourself. ## 5. Check the restarted agent Restart the selected coding agent so it loads the new configuration, then ask it: ```text Call affitor_readiness. Confirm the program identity and report the returned checks. Do not run synthetic verification or other writes without asking me first. ``` `doctor` always reports `mode: "static"` and `liveSession: "not_checked"`. File alignment, a working agent connection, and `integration_verified` are separate results. Follow the readiness checks before claiming the integration works. ## Related - [CLI command reference](/docs/brand/cli/commands): flags, JSON statuses, and exit codes. - [Program API keys](/docs/brand/api-keys): obtain and replace the program credential. - [Testing integration](/docs/brand/tracking/testing-integration): verify tracking after deployment. - [Hosted MCP server](/docs/api-reference/mcp): account sign-in and read-only reporting. --- id: "brand/cli/commands" type: "doc" url: "https://affitor.com/docs/brand/cli/commands" kind: "reference" updated: "2026-11-08" --- # CLI Command Reference > Reference for every npx affitor command, flag and option, the config file, and the error codes a failed command returns in --json output. Every `npx affitor` command, flag, and option in one place. The agent setup, doctor, and Stripe-aware onboarding behavior below require CLI 0.4.5. ## Global Flags Available on every command: | Flag | Description | |---|---| | `--json` | Output as JSON (for AI agents and scripts) | | `--no-interactive` | Skip all prompts, fail on missing values | | `--auto-confirm` | Auto-yes to confirmation prompts | | `--quiet` | Suppress non-essential output | | `--api-key ` | Override API key from config | | `--api-url ` | Override API URL | | `--verbose` | Show debug output | | `-V, --version` | Show version number | | `-h, --help` | Show help | --- ## Which commands need a login session Two different credentials are in play, and they are not interchangeable. | Credential | Where it lives | Which commands use it | |---|---|---| | Account session | `~/.affitor/credentials.json`, written by `affitor login` | `affitor init`, `affitor programs`, `affitor whoami` | | Program API key | `AFFITOR_API_KEY` in the environment or `.affitor/.env`, or `--api-key` | `affitor onboard`, `affitor status`, `affitor test` | Run `affitor login` before the first group. Without a session, `init` and `programs` stop and exit non-zero (`not_logged_in` in `--json` mode) — they never fall back to a program API key. --- ## `affitor login` Log in to your Affitor account from the browser. Required before `affitor init` and `affitor programs`. ```bash npx affitor login ``` The command prints a login URL and opens it, then waits while you sign in. Once the browser finishes, the session is written to `~/.affitor/credentials.json` and the token is good for 90 days. Takes no flags of its own. The session is per machine and per account, not per project, so you log in once and it covers every project directory. If you are already logged in, `login` reports the account and stops without starting a new session — run `affitor logout` first to switch accounts. --- ## `affitor logout` Remove the stored session from this machine. ```bash npx affitor logout ``` --- ## `affitor whoami` Show which account the stored session belongs to, and when its token expires. ```bash npx affitor whoami ``` With no session it exits non-zero. `whoami --json` prints `{"logged_in": false}` and also exits `1`. --- ## `affitor programs` List the affiliate programs on the logged-in account, with each program's ID, status, commission, and partner count. ```bash npx affitor programs ``` Needs a login session. This is how you find a program ID without opening the dashboard. --- ## `affitor init` Create a **new** affiliate program and generate config files. Requires a login session — run `affitor login` first. ```bash npx affitor init ``` `init` always creates a new program. It does not adopt a program you already have and it does not issue a replacement key for one: if a program's key stopped working, an owner or admin of that program rotates it, or creates a new key, in the Affitor dashboard (program menu → **Program settings**, then **Developers** → **API keys**). Running `init` in a directory that already has `.affitor/config.json` stops without changing anything. | Flag | Description | Default | |---|---|---| | `--name ` | Program name | (prompted) | | `--domain ` | Root domain | (prompted) | | `--commission-type ` | `percent`, `fixed`, `recurring_percent`, `recurring_fixed` | (prompted) | | `--commission-rate ` | Commission rate (% or $) | Prompt pre-fills 40 for the percent types only; no default for the fixed types | | `--cookie-duration ` | Cookie window in days | 60, applied in both modes | | `--duration-months ` | Recurring commission duration in months, saved on the program (see the warning below) | Prompt pre-fills 12, and is only asked for the recurring types | | `--no-wizard` | Skip the auto-install wizard and print manual setup steps | — | The 40 and 12 above are values the prompt offers, not values the CLI falls back to. :::warning `init` saves `--commission-type`, `--commission-rate` and `--duration-months` on the program, but it does not set what partners are paid. Payouts follow the program's **Default** partner group, which starts from Affitor's platform default commission. After `init`, open the program in the dashboard and set the commission on the Default group; that is the value used for every sale. In `affitor` 0.4.1 the duration prompt and the summary also label `0` as "lifetime". In Affitor, `0` means one-time (the first purchase, per product when the sale carries a product id) and an empty duration means lifetime. ::: With `--no-interactive` there is no prompt, so `--name`, `--domain`, `--commission-type` and `--commission-rate` must all be passed or the run stops with `missing_options`. **Example (non-interactive):** ```bash npx affitor init \ --name "My SaaS" \ --domain example.com \ --commission-type recurring_percent \ --commission-rate 30 \ --duration-months 12 \ --no-interactive ``` **Files created:** All four land inside `.affitor/`, not in the project root: | File | Purpose | |---|---| | `.affitor/config.json` | Program ID, domain, commission and cookie settings. No secrets | | `.affitor/.env.example` | The same variables as `.affitor/.env`, with the API key left empty. Gitignored | | `.affitor/AGENTS.md` | Tracking code snippets and AI agent instructions | | `.affitor/skills.md` | Backward-compatible copy of `AGENTS.md` | The API key goes only to `.affitor/.env`. `init` adds `.affitor/.env` and `.affitor/.env.*` to your `.gitignore`, which keeps both files out of Git. In a Git repository it also asks Git whether `.affitor/.env` is ignored, and adds `.affitor/.env` as the last line of `.gitignore` when it is not. If Git already tracks `.affitor/.env`, `init` tells you to run `git rm --cached .affitor/.env`. Running `init` again on a project that an older CLI set up empties the key that CLI left in `.affitor/.env.example`, and tells you to rotate the key if that file was ever committed or shared. --- ## `affitor agent setup` Preview and install project-scoped local MCP configuration and an Affitor skill. Run from your app's project root; no account login is required for this file setup. ```bash npx affitor@0.4.8 agent setup --client claude_code --dry-run --json npx affitor@0.4.8 agent setup --client claude_code --yes --json ``` | Flag | Behavior | |---|---| | `--client ` | `claude_code`, `cursor`, or `codex`; repeat to select more than one from your terminal | | `--dry-run` | Preview without writing files, even with `--yes` | | `--yes` | Apply the selected clients' plan; global `--auto-confirm` also applies it | | `--json` | One JSON result; does not prevent writes when apply is selected | A detected coding-agent caller defaults to itself and cannot select other clients. With no caller or explicit selection, an interactive run asks which clients to select; unattended runs need `--client`. | `status` | Exit | Meaning | |---|---|---| | `planned` | `0` | Dry-run only; no files written | | `needs_confirmation` | `1` | Not applied; review the preview and explicitly apply | | `needs_human` | `0` | Applied local files; restart the client and check readiness; Codex also needs the printed manual MCP step | | `error` | `1` | Setup failed; read `message` and run a fresh dry-run | A run with no selected clients and no `--dry-run` also exits `1`. The preview contains paths, operations, and backup paths, not the contents of existing configs. For file locations, private credentials, and Codex steps, follow [Set up a coding agent](/docs/brand/cli/agent-setup). --- ## `affitor doctor` Read-only static check of local agent configuration. It does not call Affitor, start an agent session, or verify integration readiness. ```bash npx affitor@0.4.8 doctor --client claude_code --json ``` Repeat `--client` to check selected clients. Without it, a detected coding-agent caller selects itself; otherwise the command checks existing Claude Code/Cursor config files, or both clients when neither file exists. Codex must be selected explicitly when there is no detected caller. Results contain `mode: "static"`, per-client `status`, `credential`, `warnings`, and `liveSession: "not_checked"`. Exit `0` and top-level `aligned` require every client to have aligned files, a `present_unverified` credential, and no warnings. Other static results produce `needs_attention` and exit `1`; caught command errors report `status: "error"` and `message`. Codex always reports client status `manual`, so its static check exits `1` even after manual configuration. A `present_unverified` credential has only passed the local parser, not authentication. Doctor reads `AFFITOR_API_KEY` or `.affitor/.env`, not global `--api-key`/`--api-url` flags. See the [doctor results and next steps](/docs/brand/cli/agent-setup#4-check-the-local-files). --- ## `affitor onboard` The recommended one-shot integration. Wires Affitor into this app end-to-end: detect the stack → install browser tracking → review sale tracking → verify. Run it from your project root after `affitor init`. ```bash npx affitor onboard ``` This is the flagship path for AI coding agents: a single command that finds your framework and payment provider, applies the integration, and proves attribution works — instead of pasting snippets by hand. | Flag | Description | Default | |---|---|---| | `--api-key ` | Program API key — overrides the env var / `.affitor/.env` | (from config) | | `--yes` | Auto-confirm all diffs (apply every change without prompting) | `false` | | `--json` | Machine-readable output for agents; never auto-edits files | `false` | | `--no-interactive` | Skip prompts and apply changes without confirmation | `false` | An API key is required. `onboard` resolves it from `--api-key`, the `AFFITOR_API_KEY` env var, or `.affitor/.env` (written by `affitor init`). If none is found it exits non-zero with `no_api_key`. ### What it does `onboard` runs four phases in order: 1. **Detect** — inspects the project to identify the framework (Next.js app/pages router, Fastify, Express, plain Node) and the payment provider (Stripe, Polar, Lemon Squeezy, Paddle). 2. **Browser tracking** — installs `@affitor/sdk` and wires the `` component via a diff-preview, scaffolding `lib/affitor.ts` (the same install wizard `affitor init` uses). 3. **Server sale** — for Stripe, reads the program's binding before deciding whether a sale call is appropriate (see below). Only an explicitly confirmed manual Stripe path can auto-edit a recognized `checkout.session.completed` handler. Other providers report `manual` and print a recipe outside JSON mode. It also attempts to persist `AFFITOR_API_KEY` into `.env` / `.env.local`; an existing value or uncertain env layers are left unchanged. 4. **Verify** — fires the synthetic click → lead → sale chain through the real attribution pipeline, then polls program readiness until `integration_verified` is reached. ### Stripe binding in 0.4.5 Before the install wizard, `onboard` reads `stripe_account_bound` from `GET /api/v1/cli/status` for the selected key, provided the app's env layers agree on that runtime key. It does not use `stripe_connected` as the sale-writer decision. | Binding decision | `server_sale` result | Webhook behavior | |---|---|---| | `stripe_account_bound: true` and runtime key is certain | `skipped` | No `trackSale` added; use the Connect metadata recipe | | `false`, missing field, failed status request, or uncertain runtime key | `manual` in `--yes`, `--auto-confirm`, `--no-interactive`, or `--json` runs | Webhook unchanged; confirm the runtime program and sale path yourself | | Unknown binding, interactive run without auto-confirm | Asks whether to keep the webhook unchanged | Keeping it is the default; only choose No after ruling out current Connect sales, shared accounts, and delayed events after disconnect | A current `false` binding does not prove that Connect cannot still record a payment. After explicitly choosing manual tracking, the CLI previews a recognized handler change and asks before applying it. It does not add subscription renewal handlers. Existing `trackSale` calls are not removed automatically. Inspect them before using Connect and manual tracking together; see the [Stripe integration guide](/docs/api-reference/integrations/stripe). ### Safety and idempotency `onboard` is **idempotent** — re-running it skips any step already applied (an existing `AFFITOR_API_KEY`, a webhook that already reports the sale). It **never force-edits payment code it can't place confidently**: when the webhook shape is not recognized, no webhook is found, or the provider is not Stripe, it reports `manual` and prints a recipe outside JSON mode rather than guessing an edit site. Auto-edits to the payment handler always show a diff and ask for confirmation first (unless `--yes` / `--no-interactive`). In `--json` mode `onboard` performs **no file edits**. Steps may report `manual`, `skipped`, or `already` according to the binding and existing files. It still fires the synthetic verification chain and polls readiness, so JSON mode is not a read-only API check. ### Example (agent / non-interactive) ```bash # Configure AFFITOR_API_KEY privately before running. npx affitor@0.4.8 onboard --yes --json ``` The JSON summary reports the per-step status and the final verdict: ```json { "program_id": "42", "steps": [ { "step": "detect", "status": "ok", "detail": "framework=fastify, provider=stripe" }, { "step": "browser_tracking", "status": "skipped", "detail": "json mode" }, { "step": "server_sale", "status": "skipped", "detail": "stripe connected: Affitor records the sale, no trackSale added" }, { "step": "env_key", "status": "manual", "detail": ".env: json mode (no auto-edit)" } ], "integration_verified": true } ``` This example has a confirmed Stripe binding and no runtime env file, so the sale step is `skipped` and the env step is `manual`. It shows the JSON shape, not a readiness guarantee for your program. Once `onboard` reaches the verification phase, `--json` always prints this summary. `program_id`, `steps` and `integration_verified` are always present, though `program_id` is `null` when no readiness verdict was obtained. `blocker`, `next_action` and `error` are omitted rather than sent as null, so read them with that in mind. The only way to get no summary is for `onboard` to stop before it runs: with no API key it prints `{"error": "no_api_key"}` and exits non-zero. `onboard` exits `0` only when `integration_verified` is `true`; otherwise it prints the summary and exits `1`. **What `integration_verified: false` means.** The verification chain and the readiness poll are separate: if the chain fails to run, `onboard` carries on polling anyway, so a chain failure never decides the verdict. Readiness does. Three cases produce `false`, and the other fields tell them apart: | Case | What the summary shows | What to do | |---|---|---| | Readiness answered, a gate has not passed | `blocker` and `next_action` name the gate | Resolve it and re-run `affitor onboard` | | No readiness verdict — every poll failed | No `blocker`, no `next_action`, no `error` | Nothing was determined. Check the API is reachable and re-run | | The API key is past its rotation deadline | `error.code` is `api_key_rotation_required` | Replace the key, then re-run | A readiness poll that succeeds after a failed chain still reports `integration_verified: true` — the chain is one way to generate events, not the thing being measured. --- ## `affitor setup stripe` Stripe is connected from the Affitor dashboard, not from the CLI: open the program menu, choose **Program settings**, open **Payments**, and use **Connect Stripe**. Affitor's own webhook then records sales, renewals and refunds for that account; nothing needs to be created on your Stripe account. To attribute each sale, add Affitor metadata to your Checkout Session, as described in the [Stripe integration guide](/docs/api-reference/integrations/stripe). ```bash npx affitor setup stripe ``` From CLI 0.4.3 this command only prints those directions and exits `1` (`{"error": "stripe_setup_moved", "message": "..."}` with `--json`). Earlier versions start a browser flow that cannot complete; do not use it. --- ## `affitor setup dns` ```bash npx affitor setup dns ``` DNS tracking is not available yet. This command only prints a "coming soon" notice (`"status": "not_implemented"` with `--json`) and changes nothing. It reads `.affitor/config.json` first and exits `1` without it (`no_config`). --- ## `affitor status` Check program health — tracking status, Stripe connection, and recent events. ```bash npx affitor status ``` **Example output:** ``` ╭──────────────────╮ │ My SaaS │ │ example.com │ │ │ │ Program ID: 42 │ ╰──────────────────╯ ✓ Stripe: connected ⚠ DNS: not configured Events (last 24h): Clicks: 142 Leads: 23 Sales: 8 Active partners: 5 Pending commissions: 3 ``` --- ## `affitor test [event-type]` Write one flagged test event for your program, to confirm your key works and that events reach your dashboard. ```bash npx affitor test click # Test click event npx affitor test lead # Test lead event npx affitor test sale # Test sale event ``` The event type defaults to `click`. Anything other than `click`, `lead` or `sale` stops with `invalid_event_type`. **What this does and does not prove.** The command creates a single record flagged `is_test: true`, which appears in your dashboard with a test badge. It confirms that your API key authenticates and that the program accepts events. It does **not** exercise attribution. The record is inserted directly rather than run through the attribution pipeline, so no partner is resolved and no commission is created — the response always reports `attributed: false`, for every event type, and that is expected rather than a fault. To check that attribution itself works, run `affitor onboard`, which fires a synthetic click → lead → sale chain through the real pipeline and then polls readiness. --- ## Config File Configuration is stored in `.affitor/config.json`: ```json { "version": 2, "program_id": "430", "domain": "example.com", "commission": { "type": "recurring_percent", "rate": 40, "duration_months": 12 }, "cookie": { "name": "affitor_click_id", "duration_days": 90 }, "stripe_connected": false, "api_url": "https://api.affitor.com" } ``` Secrets (the program API key, and provider webhook secrets) are **not** stored in `config.json` — they live in `.affitor/.env` (`AFFITOR_API_KEY`, `AFFITOR_PROGRAM_ID`), which the CLI adds to `.gitignore`. Legacy v1 configs that carried an inline `api_key` are migrated automatically on the next CLI run. --- ## When a command fails A command that cannot do its job exits non-zero. Since CLI 0.4.2 that includes `affitor onboard` when the integration is not verified (`integration_verified: false`) and `affitor whoami --json` when no session is stored; both still print their JSON first. One outcome is the exception, because it is a result rather than a failure, and it is reported in the output instead: | Command | Reports a negative outcome with exit `0` | Read instead | |---|---|---| | `affitor test` | The test event was not received | `received` in the JSON result | ### What `--json` puts on `error` `error` does not have one shape across the CLI. Check the command before you branch on it. `agent setup` and `doctor` instead report `status` and `message` on caught errors, as described above. | Shape | Where | Example | |---|---|---| | A machine code | Every check a command makes before it calls the API | `{"error": "not_logged_in"}` | | The API's message, with the HTTP status beside it | `init`, `status`, `test` when the API rejects the call | `{"error": "Invalid API token", "status": 401}` | | A code with the message in its own field | `setup stripe` | `{"error": "stripe_setup_moved", "message": "..."}` | `onboard` is different again. Once it gets past its own preflight checks it prints a summary object, and in that summary `error` is itself an **object** rather than a string — the one place the CLI hands you the API's own error code: ```json { "program_id": "430", "steps": [], "integration_verified": false, "error": { "code": "api_key_rotation_required", "message": "..." } } ``` Branch on `error.code` there; elsewhere, compare `error` as a string. Two gaps are worth knowing before you build on this output: - **`login` and `programs` do not convert failures into JSON.** If the API call inside them fails, they surface the raw error rather than an `{"error": ...}` object, so a script should not assume parseable JSON from them. - **`onboard` does not report a lost connection as an error.** If every readiness poll fails, it still prints a summary with `integration_verified: false` and no `error` field. Not verified is not the same as verified-as-broken — see [what that verdict means](#example-agent--non-interactive). ### Codes | Condition | `--json` code | Commands | What to do | |---|---|---|---| | Not logged in | `not_logged_in` | `init`, `programs` | Run `affitor login`, then re-run the command | | No config in this directory | `no_config` | `status`, `test`, `setup dns` | Run the command from the project root where you ran `affitor init`, or run `affitor init` to create a program here | | Already configured | `already_configured` | `init` | `init` found an existing `.affitor/config.json` and changed nothing. Use `affitor status` to check that program. Do not run `init` to recover a key — it only ever creates a new program | | Missing required options | `missing_options` | `init` with `--no-interactive` | Pass `--name`, `--domain`, `--commission-type` and `--commission-rate` | | Invalid event type | `invalid_event_type` | `test` | `affitor test` takes `click`, `lead`, or `sale` | | No API key | `no_api_key` | `onboard` | Pass `--api-key`, set `AFFITOR_API_KEY`, or run from a directory with `.affitor/.env` | | API rejected the call, account session | `error` is the API message, `status` the HTTP status | `init` | `init` authenticates with your account session, not a program key. A `401` here means the session is invalid or expired — run `affitor login` again. Do **not** rotate a program key for this: it will not fix the session, and it breaks whatever is still using the old key | | API rejected the call, program key | `error` is the API message, `status` the HTTP status | `status`, `test` | On a `401`, the key matches no program, was replaced, or is disabled. Compare it against the value you stored when it was issued; if you no longer hold that value, ask an owner or admin to rotate the key (program menu → **Program settings**, then **Developers** → **API keys**), copy it from **Copy your key** and deploy it. If the key is disabled, they can select **Enable key** | | Stripe is connected elsewhere | `stripe_setup_moved` | `setup stripe` | Connect Stripe in the dashboard: program menu → **Program settings** → **Payments**, **Connect Stripe** | | No usable response | `network_error` | `init`, `status`, `test` | See below | | Anything else | `unexpected_error` | `init`, `status`, `test` | Re-run with `--verbose` and keep the output | ### `network_error` does not mean the request was ignored The CLI makes at most three attempts in total — the first call plus two retries — before reporting `network_error`, so by the time you see it the request may already have been sent three times. (API errors, including `429`, are not retried; they surface on the first response.) `network_error` covers two different situations, and the CLI cannot tell them apart: a connection that never delivered the request, and a response that arrived with a success status but a body the CLI could not parse. In the second case the server may have done the work and only the reply was lost — a success status is not proof that the write completed. So treat the server state as **unknown, not untouched**, and verify the specific record before repeating anything that creates one: - **`init`** — run `affitor programs` and look for the program by name before running `init` again, or it will create a second one. There is no idempotency key on this call. - **`test`** — open your dashboard and look for the test event. The command sends no `transaction_id`, and the API generates a new event id on every call, so a repeat always writes another record. - **Ordinary sales you report yourself** through `POST /api/v1/track/sale` — resend the same `transaction_id`. The duplicate guard answers `409` for one already recorded, which is the one case here where a safe repeat is built in. A `409` with an id in `error.details.sale_id` confirms your program's sale exists; it does not confirm the commission was created, so check the sale in your dashboard if the first attempt may have failed partway. Test-mode sales follow the same guard when they carry a `transaction_id`: a repeat answers `409`. Without one, every test call gets a new id and writes another test record. A `409` with `sale_id: null` means another program already used this `transaction_id`, so nothing was recorded for yours. --- id: "brand/cli/quickstart" type: "doc" url: "https://affitor.com/docs/brand/cli/quickstart" kind: "quickstart" updated: "2026-11-08" --- # CLI Quickstart > Create your affiliate program from the terminal with npx affitor, add click, signup and payment tracking, and test the integration. Get your affiliate program running in under 5 minutes -- program creation and live tracking from your terminal. Stripe is connected in the dashboard, not the CLI. :::tip Prefer a UI? Use the [dashboard quickstart](/docs/brand/quickstart/create-account) instead. ::: ## Why CLI? | | Dashboard | CLI | |---|---|---| | Setup time | ~15 minutes | ~5 minutes | | Stripe | **Connect Stripe** under **Program settings** › **Payments** | Same: `affitor setup stripe` only points you there | | AI agent compatible | No | Yes (`--json` mode) | | Config files generated | No | Yes (`.affitor/`) | --- ## Step 1 -- Create Your Program Sign in first, then create your program: ```bash npx affitor login npx affitor init ``` `login` opens your browser to sign in to Affitor. Once it confirms you are signed in, return to your terminal and follow the `init` prompts. You'll be asked for: - **Program name** -- your product or company name - **Domain** -- your root domain (e.g., `example.com`) - **Commission type** -- percentage, fixed, or recurring - **Commission rate** -- default is 40% for recurring - **Duration** -- how long recurring commissions last (default: 12 months) - **Cookie window** -- attribution window in days (default: 60) After confirming, the CLI creates your program and generates: ``` .affitor/ AGENTS.md -- AI agent instructions (primary, universal standard) config.json -- program ID, settings .env -- API key and program ID (gitignored) .env.example -- the same variables, API key left empty (gitignored) skills.md -- same content as AGENTS.md (backward-compat) ``` `AGENTS.md` holds your program's values (program ID, domain, commission, cookie window, API base URL), the click, signup and sale snippets, the CLI commands, and the customer ID table from [Step 4](#use-one-customer-id-everywhere). It holds no API key, so you can commit it. `init` also adds `.affitor/.env` and `.affitor/.env.*` to your `.gitignore`, which keeps `.env` and `.env.example` out of Git. Only `.env` holds the key. :::tip[Works with any AI coding tool] Claude Code, Cursor, GitHub Copilot, Windsurf, Aider and other AI coding tools can follow `AGENTS.md`. It sits in `.affitor/`, not your project root, so name it in your prompt, as the line below does. ::: Using an AI coding agent? Run `init` first (it needs your login), then give your agent this line in the same project. `affitor onboard` wires in the tracking it can, prints the rest for your agent, fires a test click, lead and sale, and exits with an error until the integration is verified. --- For project-scoped MCP configuration in Claude Code, Cursor, or Codex, follow [Set up a coding agent](/docs/brand/cli/agent-setup). Since 0.4.5 the CLI includes a no-write preview and `doctor` for static local checks; neither proves a live connection. ## Step 2 -- Add Click Tracking Paste the script tag from the CLI output into your site's ``: ```html ``` Replace `YOUR_PROGRAM_ID` with the program ID from step 1. The script auto-detects `?via=PARTNER_CODE` or `?aff=PARTNER_CODE` in URLs and stores a first-party cookie for attribution (the window set on your program, 60 days by default). --- ## Step 3 -- Track Signups Call `signup()` when a user registers: ```javascript tab="Client-side (browser)" window.affitor.signup("user_123", "user@example.com"); ``` ```bash tab="Server-side (API)" curl -X POST https://api.affitor.com/api/v1/track/lead \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"click_id": "YOUR_TRACKED_CLICK_ID", "customer_key": "user_123", "email": "user@example.com"}' ``` By default the browser call alone is provisional; the server call settles the lead. Send the visitor's `affitor_click_id` as `click_id`: a first lead with only `customer_key` answers `400`, because the key is saved on the customer only when a lead settles. The server-side lead example that CLI 0.4.7 writes to `AGENTS.md` sends only `customer_key`, so add `click_id` as shown here. --- ## Step 4 -- Track Payments Choose your payment tracking method: **Server-side tracking vs Stripe integration**. ### Option A: Stripe integration (automatic) Connect Stripe in the Affitor dashboard: open the program menu, choose **Program settings**, open **Payments**, and use **Connect Stripe**. Affitor's own webhook then records sales, renewals and refunds. Add Affitor metadata to your Checkout Session so each sale is attributed; see the [Stripe integration guide](/docs/api-reference/integrations/stripe). The CLI does not connect Stripe (`affitor setup stripe` only points you to the dashboard). ### Option B: Server-side tracking (any payment provider) Your backend calls `POST /api/v1/track/sale`: ```bash curl -X POST https://api.affitor.com/api/v1/track/sale \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"transaction_id": "inv_123", "customer_key": "user_123", "amount_cents": 4900, "currency": "USD"}' ``` ### Use one customer ID everywhere Use your internal user ID as the customer key at signup and again with each sale. Each surface names the field differently: | Where | Field | |---|---| | Browser `window.affitor.signup()` | first argument (`customerKey`) | | Lead API (`/api/v1/track/lead`) | `customer_key` | | Sale API (`/api/v1/track/sale`) | `customer_key` | | Stripe Checkout metadata | `affitor_customer_key` | Full request contracts: [Track Lead](/docs/api-reference/track-lead) and [Track Sale](/docs/api-reference/track-sale). --- ## Step 5 -- Test Your Integration Send test events to verify your integration: ```bash npx affitor test click npx affitor test lead npx affitor test sale ``` Then check your program health: ```bash npx affitor status ``` --- ## Non-Interactive Mode For CI/CD and AI agents, pass `--no-interactive --json` to skip prompts and get machine-readable output: ```bash npx affitor init \ --name "My SaaS" \ --domain example.com \ --commission-type recurring_percent \ --commission-rate 30 \ --duration-months 12 \ --cookie-duration 90 \ --no-interactive \ --json ``` The commission flags are saved on the program, but partners are paid by the program's Default group commission: set it in the dashboard after `init` (see [CLI commands](/docs/brand/cli/commands)). Output is valid JSON, ready for AI agents to parse: ```json { "program_id": 430, "api_key_file": ".affitor/.env", "domain": "example.com", "status": "created", "tracking": { "script_tag": "", "signup_call": "window.affitor.signup(\"customer_id\", \"email\")", "sale_api": "POST https://api.affitor.com/api/v1/track/sale", "lead_api": "POST https://api.affitor.com/api/v1/track/lead" } } ``` :::warning[Common mistakes] - Running `npx affitor init` in a directory that already has `.affitor/config.json` -- delete it first or use a different directory. - Skipping the tracking script -- the CLI creates the program but does not modify your code. - Using an expired API key -- ask an owner or admin of the program to create or rotate a key in **Program settings › Developers › API keys**. `npx affitor init` creates a new program; it never replaces a key. ::: --- id: "brand/quickstart/commission-approval-cash-flow" type: "doc" url: "https://affitor.com/docs/brand/quickstart/commission-approval-cash-flow" kind: "concept" updated: "2026-10-24" --- # Commission Approval & Cash Flow > Understand how attributed sales move into commissions, billing, and payout workflow. This page traces the journey from an attributed sale through the commission hold, billing, and partner payout. ## Payment integration method | Method | Checkout ownership | How it works | |--------|--------------------|--------------| | **Invoice billing** | Your checkout | You collect customer payment, Affitor attributes conversions and bills through its invoice workflow | --- ## Invoice billing **Step by step:** 1. Customer purchases through your existing checkout. 2. You receive payment in your own payment stack. 3. Affitor attributes and validates the conversion. 4. Commission is created according to your program rules. 5. Advertiser billing is handled through Affitor's invoice workflow. 6. Commission moves through the hold period and, once approved, into the partner's balance. The partner can withdraw it once you pay the invoice that covers it. Customer money never passes through Affitor. The money that does move through Affitor is the weekly invoice (approved commissions plus the platform fee), which you pay to Affitor LLC, and the partner withdrawals Affitor sends out: B[Affitor attributes the sale] B --> C[Commission pending] C -->|hold period ends| D[Commission approved] D --> E[Partner balance credited] E --> F[Partner requests a withdrawal] F --> G[Affitor approves and sends it] D --> H[Weekly invoice to you] H --> I[You pay Affitor LLC] I -->|unlocks the withdrawal| F `} /> The partner's balance is credited when the commission is approved, but the partner can withdraw it only after you pay the invoice that covers it. --- ## Validation Before Commission Affitor validates each attributed sale before the commission workflow proceeds. Checks include: - Valid attribution - No duplicate sale event - In-window attribution - Matching program/customer relationship --- ## Approval and Hold Workflow ![The Commissions page tracks every commission through its lifecycle](/docs/brand/commissions.png) Every commission moves through the same lifecycle: B[Pending] B -->|hold period ends| C[Approved] B -->|you reject it| X[Rejected] B -->|partial refund| R[Refunded] B -->|full refund| V[Reversed] C -->|weekly invoice| D[Invoiced] D -->|invoice marked paid| E[Collected] class X,R,V do class E ok `} /> **Approved** is when the commission is added to the partner's balance. **Invoiced** and **Collected** track your side of the bill: the partner can withdraw the commission once it is **Collected**, which happens when you pay the invoice. The **Commissions** page shows a count for **All** and for each status that has commissions; select a count to filter the list, or use **All statuses** in the filter. Each row names the customer by a masked email, or by **Customer #** and its number when there is no email, or says **Customer not recorded**. **Customers** is no longer a separate page: old Customers links open **Commissions**. The program's hold period, set under **Commission** in [program settings](/docs/brand/settings), controls when commissions are approved. A commission approves automatically when the hold period ends (later, if you extend the hold), unless you approve or reject it first from the **Commissions** page. A test commission, a $0 commission on a payment after the commission term has ended, and one earned by someone on your own team (the brand owner or a workspace member) are not approved on their own. ### Common uses - Reduce refund risk: a refund that lands during the hold is removed before it ever reaches the partner's balance - Give yourself time to reject suspicious commissions before they approve - Extend the hold on a commission you are still checking --- ## Public-safe cash flow summary --- ## Refund Handling What happens depends on where the commission is when the refund arrives: - **Pending** — nothing reaches the partner's balance. A full refund marks the commission **Reversed**, a partial one **Refunded**. - **Approved or invoiced** — the refunded share is taken back from the partner's balance: all of the commission for a full refund, and the same fraction of it for a partial refund. The balance can go negative; the partner sees it as **Balance owed**, recovered from their next commissions. - **Already collected** — Affitor deducts it from the partner's balance, which can go negative, and sends you a notification: reconciling with the partner is a manual step. Platform fees already billed are not refunded. A refund lowers the revenue total that counts toward your program's $10,000 fee-free tier by the refunded amount, never by more than that sale added. See [Track refund](/docs/api-reference/track-refund) for the API details. --- --- id: "brand/quickstart/create-account" type: "doc" url: "https://affitor.com/docs/brand/quickstart/create-account" kind: "quickstart" updated: "2026-10-18" --- # Create your advertiser account > Sign up on Affitor, verify your email, choose Run a program, and start the five-step program setup. Create your Affitor brand account in about five minutes: sign up, verify your email, choose **Run a program** and name your program. Setup then walks you through the five steps to [set up your program](/docs/brand/quickstart/setup-program) and go live. :::tip Creating an account is free, and you don't need Stripe or payment details yet. The platform fee is $0 until your program earns its first $10,000 through affiliates, then 3.5% on affiliate-driven sales only. ::: ## The flow at a glance **Sign up** at affitor.com/signup: choose **I'm a brand**, then use your company email or Google, and verify the email. **Continue with Run a program** when Affitor asks how you will use it. **Name your program**, then follow the five setup steps up to Go live. ## Step 1: Sign up and verify your email Your email is your sign-in and where Affitor sends account notifications. 1. Go to [affitor.com/signup](https://affitor.com/signup) and choose **I'm a brand**. The form then reads **Create your brand account**; **Change** goes back to the choice. 2. Sign up with your company email address and a password, or continue with Google. 3. With email sign-up, open the verification email and confirm your address. :::tip A shared address like `partnerships@yourcompany.com` keeps team access manageable as your program grows. ::: ## Step 2: Choose Run a program Affitor has two sides: brands that run programs and partners who promote them. The welcome screen asks **How will you use Affitor?** It already has **Run a program** selected from your choice on the sign-up page; select **Continue**. **Join programs** is the partner side. ## Step 3: Name your program and finish setup Affitor asks for your **program name**, a **program handle** (your public page address) and your **website URL**, then opens setup. Setup has five steps: **Business**, **Commission**, **Tracking**, **Payments** and **Go live**. The logo on the Business step is optional. Everything is editable later in **Settings**; see [Set up your program](/docs/brand/quickstart/setup-program) for what each step needs and when you can go live. ## Verify it worked Setup opens right after you name your program. **Save and exit** on a step opens the matching **Settings** page, so you can leave and come back. Until the program is live, **Get started** in the left rail shows how many setup steps are done (for example **2 of 5**); after **Go live**, setup shows "**your program** is live" with **Open dashboard**. ## Next steps --- id: "brand/quickstart/define-commission" type: "doc" url: "https://affitor.com/docs/brand/quickstart/define-commission" kind: "concept" updated: "2026-11-07" --- # Define Commission > Set commission rates and durations for your affiliate program per partner group, and see how a commission is calculated from a sale. Commission determines what partners earn when they drive results. Configure the right type and duration to attract quality partners and align incentives with your business model. --- ## Commission Basics ![Partner Groups — each group carries its own commission rate](/docs/brand/groups.png) Commission is set per **partner group**: every partner belongs to a group (Default, unless you assign another), and the group's policy decides what they earn. That's how you run VIP tiers next to a standard rate without per-partner bookkeeping. Every commission has two components: | Component | Description | |-----------|-------------| | **Rate** | How much partners earn (percentage or fixed amount) | | **Duration** | How long partners earn from a referred customer | --- ## Commission Types ### Revenue Share Partners earn a percentage of each sale from customers they refer. **Example:** 30% commission means partner earns $30 on a $100 sale. Revenue Share is the default and recommended type for SaaS products. ### CPC (Cost per Click) Partners earn a fixed amount for each click they drive. **Example:** $0.01 per click. ### CPL (Cost per Lead) Partners earn a fixed amount for each qualified lead (signup) they refer. **Example:** $10 per lead. ### CPS (Cost per Sale) Partners earn a percentage of each sale they generate — the same calculation as Revenue Share. CPS is always a percentage of the sale amount; there is no fixed-amount-per-sale option. **Example:** 20% on a $100 sale = $20. ### Coming Soon | Type | Description | Example | |------|-------------|---------| | **Tiered** | Bonuses at milestones | $100 bonus after $100K revenue | | **Hybrid** | Combine multiple types | CPC + CPS + milestone bonuses | --- ## Commission Duration How long partners continue earning from a referred customer: | Duration | Description | Best for | |----------|-------------|----------| | **One-time** | First payment only | Simple products, one-time purchases | | **Recurring** | Every payment until the months in **For** (1 to 36) have passed since the customer's first click on the partner link, not since the first payment | Subscriptions with a set earning period | | **Lifetime** | All future payments | Maximum partner incentive | Payments after the duration ends are still recorded as sales; their commission is $0. **Recommendation:** For SaaS, use 12 months or lifetime to motivate partners to refer customers who stay, not just customers who sign up. --- ## Setting Your Commission ### During Setup In the setup wizard, you'll configure: 1. **Type**: **One-time**, **Recurring** or **Lifetime** 2. **Rate**: e.g., 30% 3. **For**, shown only for **Recurring**: e.g., 12 months This becomes your default commission for all partners. ### Example Configurations | Business Type | Rate | Duration | Why | |---------------|------|----------|-----| | B2B SaaS ($50-200/mo) | 30% | 12 months | High LTV justifies generous commission | | B2B SaaS ($500+/mo) | 20-25% | Lifetime | Lower % but longer duration | | Consumer SaaS ($10-30/mo) | 30-40% | 6 months | Higher % to attract volume partners | | One-time purchase | 20-30% | One-time | Simple, predictable | --- ## Commission Calculation **Formula:** `Commission = Sale Amount × Commission Rate` **Example with 30% commission:** | Customer Payment | Partner Earns | |------------------|---------------| | $100 one-time | $30 | | $100/month, subscribed the day of the click, **Recurring** for 12 months | $30/month × 12 = $360 total | | $1,000/year lifetime | $300/year ongoing | The 12 months count from the customer's first click, not the first payment: a customer who subscribes two months after the click earns the partner commissions only until 12 months after that click, so on fewer than 12 payments. **With Affitor's platform fee:** $0 until your program has earned its first $10,000 through affiliates, then 3.5% of each affiliate-driven sale. The free tier is counted per program. | Sale | Partner Commission (30%) | Platform Fee | You Keep | |------|--------------------------|--------------|----------| | $100, program still under $10,000 | $30 | $0 | $70* | | $100, program past $10,000 | $30 | $3.50 (3.5%) | $66.50* | *Before your own payment processing fees (for example Stripe's ~2.9% + $0.30) --- ## Changing Commission Rates You can update your default commission anytime in Program Settings. **Important:** A change does not rewrite commissions that already exist, but it does apply to every new commission from the date it takes effect — including recurring payments from customers referred before the change. Lowering the rate lowers what partners earn on their existing subscribers' future renewals. If you lengthen the duration, payments that earned nothing under the old duration (because it had run out) can be credited retroactively at the new policy. Those backpaid commissions go through the hold period again and carry the platform fee, so they appear on a later invoice. --- ## Different Rates for Different Partners Use [partner groups](/docs/brand/groups) to give different partner segments different commission rates — for example, a higher rate for top performers or a separate rate for agencies. Each group carries its own commission policy, and every partner belongs to exactly one group. --- ## Best Practices 1. **Be competitive** – Research what similar products offer. For AI SaaS, 30%+ is common. 2. **Think lifetime value** – A 30% commission on a customer with 24-month LTV is very profitable for you. 3. **Longer duration = better partners** – Lifetime commissions attract partners who promote quality, not just volume. 4. **Start generous, optimize later** – Reducing rates for new partners is easier than raising them after expectations are set. --- ## Verify it worked ## What's Next - **[Commission Approval & Cash Flow](/docs/brand/quickstart/commission-approval-cash-flow)** – How commissions are validated and paid - **[Payouts](/docs/brand/quickstart/payouts)** – Partner payout schedules and methods --- id: "brand/quickstart" type: "doc" url: "https://affitor.com/docs/brand/quickstart" kind: "concept" updated: "2026-11-07" --- # Launch Your Program > Set up your Affitor affiliate program in 20 to 30 minutes: account, program details, commissions, partner approval, and payouts. Get your affiliate program ready for launch with one clear setup flow. No account yet? [Create one free at affitor.com](https://affitor.com) — $0/month, no setup fee, and a 3.5% fee only after each program's first $10,000 in affiliate-driven revenue. ## Recommended setup flow Set up your advertiser account and get access to the Affitor dashboard. Define program basics, branding, and the information partners will see. Choose how partners earn from signups, sales, or subscription payments. Decide who can join and how applications are reviewed. Understand the payout flow and what needs to happen before partner funds are released. Know where to monitor clicks, leads, sales, and program performance once you are live. --- id: "brand/quickstart/partner-approval-quality-control" type: "doc" url: "https://affitor.com/docs/brand/quickstart/partner-approval-quality-control" kind: "guide" updated: "2026-11-07" --- # Partner Approval & Quality Control > Choose Manual review or Auto-approve, review partner applications, and monitor active partners to keep your program's quality high. Control who promotes your program by reviewing applications and monitoring active partners for quality. --- ## Approval Modes You set your approval mode during setup. You can change it anytime in Program Settings. | Mode | How it works | |------|--------------| | **Manual review** | Every application lands in your queue for review | | **Auto-approve** | Partners are approved instantly upon application | **Recommendation:** Start with Manual review. You can switch to Auto-approve once you understand what good partners look like for your program. --- ## Reviewing Applications ![Applications waiting for review — approve or decline each with an optional reason](/docs/brand/applications.png) You can review from two places: the **Applied** tab (full view with the applicant's message, shown above) or directly from the **All** partners table, where applications float to the top with quick ✓ Approve / ✕ Decline actions on hover. When a partner applies, you'll see: - **Name & contact info** – Who they are - **Website/social profiles** – Where they'll promote you - **Audience description** – Who they reach - **Promotion method** – How they plan to promote (content, ads, email, etc.) - **Message** – A short note explaining their interest or fit ### What to Look For **Green flags:** - Relevant audience (your target customers) - Established platform (active blog, YouTube channel, newsletter) - Clear promotion plan - Professional communication **Red flags:** - No website or social presence - Audience mismatch (e.g., gaming audience for B2B software) - Vague or generic responses - History of spam or policy violations --- ## Approving or Rejecting From the Applications tab: 1. Click on a pending application 2. Review their details 3. Choose **Approve** or **Reject** **When you approve:** The partner gains access to their dashboard, tracking links, and marketing materials. **When you reject:** The partner is notified their application was declined. > **Tip:** If you're unsure, approve them. You can always remove partners later if they don't perform or violate your terms. --- ## Managing Active Partners ### Partner Metrics Track partner quality from your dashboard: | Metric | What it tells you | |--------|-------------------| | Clicks | Traffic volume from partner's links | | Signups | Leads generated | | Paid customers | Conversions | | Revenue | Total sales attributed to partner | | Conversion rate | Quality of traffic (signups → paid) | ### Removing a Partner The dashboard does not have a self-serve action to remove a partner from your program yet. If a partner violates your terms, [contact support](/docs/support/contact) with the partner and program details. ### Warning Signs Watch for these red flags in active partners: - **High clicks, zero conversions** – May indicate low-quality traffic or fraud - **Refund rate above normal** – Could be misleading promotion - **Brand misuse** – Unauthorized use of your logo or false claims --- ## Best Practices 1. **Respond quickly** – Partners expect approval within 24-48 hours 2. **Set clear terms** – Define what's allowed in your Terms of Service 3. **Communicate expectations** – Let partners know what success looks like 4. **Review periodically** – Check partner quality monthly, not just at signup --- ## Coming Soon - **Blocklist** – Automatically reject applications from specific domains --- id: "brand/quickstart/payouts" type: "doc" url: "https://affitor.com/docs/brand/quickstart/payouts" kind: "concept" updated: "2026-11-07" --- # Payouts > How commissions move from hold to the partner's balance and, once you pay the invoice, to a withdrawal Affitor sends; payout methods and your role. When a commission clears its hold period, it is credited to the partner's balance. Once you pay the invoice that covers it, the partner can request a withdrawal, and Affitor approves and sends it. This page explains the lifecycle, payout methods, and your role as advertiser. ## How payouts work B[Affitor attributes the sale] B --> C[Commission approved after hold] C --> D[Partner balance credited] D --> E[Partner requests withdrawal] E --> F[Affitor approves and sends it] C --> G[Affitor invoices you weekly] G --> H[You pay the invoice] H -->|unlocks the withdrawal| E `} /> Partners can withdraw a commission only after you pay the invoice that covers it. An approved commission is added to the partner's balance right away, but it shows as **Awaiting brand payment** until that invoice is marked paid. Your weekly invoice covers the approved commissions plus the platform fee. Commissions approved before October 9, 2026, 00:00 Pacific time (07:00 UTC) became withdrawable on approval. See [Overdue invoices & program pause policy](/docs/brand/billing/overdue-policy). ![Billing — platform fee, outstanding balance, and your next invoice date](/docs/brand/billing.png) The platform fee follows the same principle: **$0 until your program earns its first $10,000 through affiliates, then 3.5% of affiliate-driven revenue.** You can see the fee accruing live on the Billing page. Sale attributed Commission created Hold period Commission approved You pay the invoice Partner requests withdrawal At a high level: 1. A sale is attributed. 2. A commission is created. 3. The commission waits out the program's hold period. You can approve, reject, or extend the hold on it from the **Commissions** page. 4. When approved, the commission is added to the partner's balance. It becomes withdrawable once you pay the invoice that covers it. 5. The partner requests a withdrawal; Affitor approves it and sends the transfer through Wise. You do not need to manage individual partner transfers yourself. --- ## Payout Methods Affitor pays partners through Wise. A partner can be paid to: | Method | Notes | |--------|-------| | Wise | The partner's Wise account email | | Bank transfer | ACH in the US, BIC/SWIFT elsewhere, in the partner's legal name | Before a first withdrawal, each partner adds a legal name, a payout method and a tax form (W-8BEN, W-8BEN-E or W-9) in their own account. You do not collect bank details or tax forms, and you never see a partner's tax form. The minimum withdrawal is $20. --- ## Payout Status States | State | Meaning | |-------|---------| | **Pending** | Withdrawal requested, awaiting approval | | **Approved** | Approved and ready to send (partners see this as **Processing**) | | **Completed** | Payout sent | --- ## Your Role as Advertiser | Do | Don’t | |----|-------| | Review transactions and commissions where needed | Manage individual partner bank transfers | | Configure commission and hold settings | Build a separate payout ops layer for each partner | | Monitor affiliate cost and performance | Send partner payouts yourself | --- ## Verify it worked ## Refunds A refund before the commission is approved removes it before it reaches the partner. After approval, the amount is taken back from the partner's balance. If the commission was already collected, the partner's balance can go negative and you get a notification: reconciling with the partner is a manual step. Platform fees already billed are not refunded. See [Commission approval & cash flow](/docs/brand/quickstart/commission-approval-cash-flow#refund-handling). --- --- id: "brand/quickstart/setup-program" type: "doc" url: "https://affitor.com/docs/brand/quickstart/setup-program" kind: "quickstart" updated: "2026-11-07" --- # Set Up Your Program > Complete the five setup steps (Business, Commission, Tracking, Payments, Go live) and publish your program on the marketplace. Setup takes your program from created to live in five steps: **Business**, **Commission**, **Tracking**, **Payments** and **Go live**. It opens at the Business step as soon as you [create your program](/docs/brand/quickstart/create-account), at `affitor.com/brand/setup/business`. ## The flow at a glance **Business**: business name, website, program URL and an optional logo. **Commission**: what partners earn, the attribution window, the hold period and how new partners join. **Tracking**: install the click tracker on your site. Optional for Go live. **Payments**: connect Stripe, or send one sale from your server. **Go live**: publish the program once Business, Commission and Payments are done. The top of each step shows **Step N of 5** and **Save and exit**. **Continue** saves the step and opens the next one. **Save and exit** saves Business or Commission first, then opens that page in Settings; the other steps have nothing to save and open their Settings page directly. On a wide screen the step list sits on the left, where a done step shows a check (Business also shows your website, Commission your rate), and **What partners see** previews your program card on the right. The same five pages are also **Program settings** (open the program menu and choose **Program settings**), so anything you set here stays editable there. Until the program is live, Program settings shows how many of the five steps are done. After launch the pages have no **Back** or **Continue**: **Business** and **Commission** have **Save**, **Payments** has nothing to save, the **Partner link parameter** on **Tracking** saves when you pick it, and **Go live** is named **Status**. ## Step 1: Describe your business The **Business** step (**Your business**) sets what partners see first. | Field | Required | Notes | |-------|----------|-------| | **Business name** | Yes | 1 to 80 characters | | **Website** | Yes | Your product or site URL. `example.com` is saved as `https://example.com` | | **Program URL** | Yes | Your public program page, `affitor.com/marketplace/`. Lowercase letters, numbers and dashes, up to 48 characters. You can change it later | | **Program ID** | Shown, not edited | Used by the tracking script, the API and AI agents. **Copy** copies it | | **Logo** | No | PNG, JPG or SVG, square, under 5 MB | | **Tagline** | No | In **Program settings** → **Business** only: one line on your marketplace card, up to 160 characters | **Continue** saves only the fields you changed and moves on once every save succeeds; an error shows under its field. The step is done once the program has a business name and a website. ## Step 2: Set your commission The **Commission** step sets what partners earn and how they join. ![Setup step 2 of 5, Commission: type (one-time, recurring or lifetime), rate and months, attribution window, hold period, and whether new partners are approved automatically or reviewed one by one, with a preview of what partners see](/docs/brand/setup-commission.png) | Field | Required | Notes | |-------|----------|-------| | **Type** | Yes | **One-time** pays on the first payment, **Recurring** on every payment until the months in **For** have passed since the customer's first click on the partner link, **Lifetime** on every payment | | **Rate** | Yes | Percent of the payment, 0 to 100 with up to 2 decimals | | **For** | Yes, for **Recurring** | How many months the partner keeps earning, counted from the customer's first click on the partner link (not the first payment): a whole number from 1 to 36. Later payments are still recorded, with a $0 commission. Shown only for **Recurring** | | **Attribution window** | Yes | How long after a click a signup still counts: 1 to 365 days | | **Hold period** | Yes | Days until a commission is payable, to cover refunds: 0 to 31 | | **New partners** | Yes | **Auto-approve** (Link right away) approves every application; **Manual review** (You approve first) lets you review each one | Once the rate is valid, a line shows what a $100 payment gives the partner, for example "$20 to the partner, monthly for 12 months". If your saved terms are ones this form cannot show exactly (for example a fixed amount), the step shows them as **Current terms** and keeps them unless you select **Set new terms**. The step is done once a sale commission is saved and a **New partners** choice is set. To pay some partners a different rate, use [groups](/docs/brand/groups). ## Step 3: Install tracking The **Tracking** step (**Install tracking**) puts the click tracker on your site. Pick an **Install method**: - **With AI**: pick your AI tool (**Claude Code**, **Cursor**, **Codex**, **ChatGPT** or **Other**) and select **Copy prompt**. The prompt carries your website, Program ID and API base; your AI tool reads the API key from the `AFFITOR_API_KEY` environment variable and follows the [agent skill](/docs/skill.md). - **By hand**: paste the script tag in `` on every page of your site. In **Program settings** › **Tracking**, **By hand** also offers **npm**: install the SDK and wrap your app in the provider. The snippets on the page already carry your Program ID (also shown on **Business**, with **Copy**): ```html ``` ```bash npm install @affitor/sdk ``` On Next.js App Router, put the provider in a client component and render it once in your layout: ```tsx // app/affitor-provider.tsx (a client component) 'use client'; import { AffitorProvider } from '@affitor/sdk/react'; export function Providers({ children }: { children: React.ReactNode }) { return {children}; } ``` ```tsx // app/layout.tsx (Next.js App Router): render it once around your app import { Providers } from './affitor-provider'; export default function RootLayout({ children }: { children: React.ReactNode }) { return ( {children} ); } ``` The provider runs in the browser, so it lives in a client component: in the App Router, `layout.tsx` is a Server Component. With the Pages Router, wrap your app in `AffitorProvider` in `pages/_app.tsx`. Below the snippets, **Tracker on** your site shows **Waiting for the first visit**, **Checking…**, **Tracker not found on your site yet**, **Tracker found on** your site, **Receiving events**, **Couldn't load** your site, or **First click** and how long ago it arrived. **Check now** asks Affitor to look for the tracker on your website again; it is gone once a first click arrives. **Continue** moves on to Payments at any time, and Affitor keeps checking. In **Program settings** › **Tracking**, **Partner link parameter** sets how partner links name the partner: `yoursite.com/?via=PARTNER` or `yoursite.com/?aff=PARTNER`. The tracker reads both. Programs created from October 16, 2026 (UTC) use `?via=` unless you pick `?aff=`; older programs keep `?aff=`. If you change it, links partners already shared keep working. If your own server reads the partner code, read both `?aff=` and `?via=`. The step is done once Affitor finds the tracker on your website or receives real tracking events. Signup tracking is a separate install: see [signup tracking](/docs/brand/tracking/lead-tracking-signup), and [click tracking](/docs/brand/tracking/click-tracking) for the full click guide. ## Step 4: Connect payments The **Payments** step sets how Affitor records your sales: **Connect Stripe, your server, or both.** It shows two cards, each with its own state, and there is no method to choose. Only the program owner can connect Stripe; other members see "Only the program owner can connect Stripe." | Card | States | What to do | |--------|-------------|------------| | **Stripe** | **Not connected**, **Not finished**, **Connected** | Select **Connect Stripe**. Stripe opens in a new tab; finish there and this page updates when you come back. If you started and did not finish, the button reads **Finish in Stripe** | | **Server API** | **No sale yet**, **Received** | Select **Send a test sale** to see the call, then run it once from your server. **Check again** reads the status now | If Stripe is connected and your server has also sent a sale, the page warns that sending the same purchase through both can count it twice: use one source per purchase. The Server API test sale uses your program API key ([where to find it](/docs/brand/settings#step-2-find-your-api-key)). With `"livemode": false` it is a test sale and creates no commission: ```bash curl -X POST https://api.affitor.com/api/v1/track/sale \ -H "Authorization: Bearer YOUR_PROGRAM_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "click_id": "clk_abc123", "customer_key": "user_123", "amount_cents": 4900, "currency": "usd", "transaction_id": "txn_test_001", "livemode": false }' ``` Replace `txn_test_001` with an id of your own, and use a new one for each run: a `transaction_id` that is already recorded answers `409` and records nothing. Once payments are connected, **Check Affitor's tracking** offers **Run check**: Affitor sends a test click, signup and sale through your program and shows each as **Matched**, **Not matched**, **Wrong partner** or **Waiting**. It is a pipeline check: it does not complete either card and does not count toward Go live. **Refunds and chargebacks**: with Stripe, Affitor reads refunds and disputes from your connected account. With the Server API, report each refund with [Track a refund](/docs/api-reference/track-refund). The step is done when either card is: Stripe is connected, or Affitor has received a sale from your server. **Continue** moves on to Go live, which shows what is still missing. ## Step 5: Go live **Go live** publishes your program on the marketplace. The page lists four rows: | Row | Needed to go live | Done when | |-----|-------------------|-----------| | **Business** | Yes | the program has a business name and a website (the logo is optional) | | **Commission** | Yes | a sale commission is saved | | **Click tracking** | No | Affitor finds the tracker on your website or receives real events; until then the row reads "Optional · no visit seen yet" | | **Payments** | Yes | Affitor can record your sales (see below) | A row that is not done has **Fix** (**Set up** for click tracking), which opens its step. The page also shows the address your program page opens at. **Go live** turns on once the three required rows are done, and Affitor checks them again when you select it. Payments counts as connected when either card on the **Payments** step is done: - **Stripe**: your Stripe account is connected to the program. - **Server API**: your server has sent at least one sale for this program to `POST /api/v1/track/sale`. A test sale counts (send it with `"livemode": false`), so you can go live before your first real customer. **Run check** does not count; the sale has to come from your server. Click and signup tracking are not required to go live. Install them before partners start sending traffic so it is attributed. If the program is paused for an overdue invoice, Go live stays blocked: selecting **Go live** shows the overdue notice with **Open billing**. Pay the invoice first. Once live, the page says your program is live and shows its link with **Copy link**, plus **Open dashboard**. ## Get the Verified badge Partners see a **Verified** mark on live programs that Affitor has checked, and can filter the marketplace to **Verified only**. You don't apply for it: Affitor rechecks your program automatically, and the mark shows while all of these hold (a change can take a few minutes to show on the marketplace): - The program is live, its website is a public `https://` address, and your Affitor account is not blocked. - Payments are connected: Stripe is connected to the program and can take charges, or your server has sent Affitor a real, paid sale in the last 90 days that earned a partner a commission. Test sales and sales you or your team refer yourselves don't count. - Affitor has recorded at least one real click, signup or sale. - No Affitor invoice is overdue. Once a partner has been paid a commission through Affitor, the mark also lists **Partners have already been paid through Affitor**. If a check stops holding, for example an invoice goes overdue, or (without Stripe connected) your server sends no real sale for 90 days, the mark goes away until it holds again. Affitor can also remove the mark from a program. The CLI's **Integration verified** message is a different check: it tests your install and does not count toward the mark. ## Before partners join ## Verify it worked In the program menu, choose **Program settings** and check that each page kept what you saved: --- id: "brand/quickstart/view-performance" type: "doc" url: "https://affitor.com/docs/brand/quickstart/view-performance" kind: "guide" updated: "2026-11-07" --- # View Performance > Track revenue, partners, clicks, sign-ups and paid customers on your dashboard, compare periods, and find your top-performing partners. Monitor program-wide metrics, identify top-performing partners, and spot issues before they impact revenue. --- ## Performance Overview ![The Dashboard: the Performance Overview with Revenue selected, showing its trend over the last 7 days](/docs/brand/dashboard.png) Your dashboard shows program-wide metrics at a glance: | Metric | Description | |--------|-------------| | **Revenue** | Total sales from affiliate traffic | | **Partners** | Partners who joined your program in the period | | **Clicks** | Visits from affiliate links | | **Sign Ups** | Leads captured (registrations, form submissions) | | **Paid Customers** | Conversions that generated revenue | The chart below shows the selected metric's percentage change compared to the previous period. It shows no percentage when the metric did not change, or when it was 0 in the previous period, since growth from nothing has none. Use the period menu to pick **Last 7 Days**, **Last 30 Days**, **Last 90 Days** or **All Time**. --- ## Performance Charts Click any metric to see its trend over time. The chart shows daily values across your selected date range. Hover over data points to see exact values for specific dates. Use charts to: - Spot growth or decline patterns - Identify your best-performing days - Correlate spikes with campaigns or launches --- ## Action Center The Action Center shows items that need your attention: - **Pending partner applications** – Review and approve or decline - Quick actions: Approve or Decline directly from the dashboard Click "View all" to see your full application queue. --- ## Partner Performance The Partners section breaks down results by individual partner: | Column | What it shows | |--------|---------------| | Partner | Name and contact info | | Clicks | Traffic sent to your site | | Signups | Leads generated | | Paid Customers | Conversions | | Revenue | Sales attributed to this partner | | Conversion Rate | Lead-to-customer percentage | ### Sorting & Filtering - **Sort by** any column to find top performers - **Filter by** date range to see recent activity - **Search** by partner name ### What the Numbers Tell You | Pattern | What it means | Action | |---------|---------------|--------| | High clicks, low signups | Traffic quality issue or landing page mismatch | Review partner's promotion method | | High signups, low paid | Leads aren't qualified or pricing friction | Check if partner targets right audience | | High conversion rate | Partner sends qualified traffic | Consider higher commission tier | | Zero activity | Partner hasn't started promoting | Send activation reminder | --- ## Tracking Performance Over Time Use date comparisons to spot trends: - **Week over week** – Short-term momentum - **Month over month** – Growth patterns Look for: - Which partners are growing vs. declining - Seasonal patterns in your conversions - Impact of promotions or product launches --- ## About Data Access Affitor operates as an affiliate network, not just a tracking layer. Your dashboard provides full performance and attribution reporting; exporting raw partner identity data is not supported. Affitor owns partner sourcing, recruiting, and management. The dashboard gives you the insights needed to monitor performance and make program decisions. --- ## Best Practices 1. **Check weekly** – Catch issues early before they impact revenue 2. **Identify top performers** – Your top 20% of partners likely drive 80% of results 3. **Spot inactive partners** – Re-engage or remove partners with no activity for 30+ days 4. **Compare conversion rates** – Partners with similar traffic but different conversion rates reveal quality differences --- ## What's Next - **[Partner Approval & Quality Control](/docs/brand/quickstart/partner-approval-quality-control)** – Manage your partner base - **[Payouts](/docs/brand/quickstart/payouts)** – See pending and completed partner payments --- id: "brand/tracking/click-tracking" type: "doc" url: "https://affitor.com/docs/brand/tracking/click-tracking" kind: "guide" updated: "2026-11-07" --- # Click Tracking > Install the Affitor tracker with the npm SDK or a script tag to record affiliate visits, then check clicks and cookies before tracking signups and sales. Click tracking is the first step in every Affitor integration. It detects affiliate visits, creates the click/customer relationship, and stores the browser identifier used by later signup and sale attribution. --- ## What It Does When someone lands on your site through an affiliate link such as: ```text https://yoursite.com?via=PARTNER123 https://yoursite.com?aff=PARTNER123 ``` the tracker: 1. detects the `?via=` or `?aff=` parameter (which one your links use is the **Partner link parameter** on **Tracking**; the tracker reads both, and `aff` wins when a URL has both) 2. sends click data to Affitor 3. creates or updates the tracked customer relationship 4. stores `affitor_click_id` in a first-party cookie 5. makes later signup and sale attribution possible That cookie value is later reused as: - `click_id` in API payloads - `affitor_click_id` in Stripe metadata --- ## Choose Your Installation Method | Method | Best for | Benefits | |--------|----------|----------| | **npm SDK** | React, Next.js, JS/TS apps | Promise-based loading, TypeScript support | | **Script tag** | Static HTML, CMS sites, no-build installs | Copy-paste setup, no build step required | --- ## npm SDK Install the tracker package: ```bash npm install @affitor/sdk ``` ### React / Next.js :::warning **Next.js 13+ App Router:** `layout.tsx` is a Server Component by default. `@affitor/sdk` uses browser APIs and cannot run in a Server Component. Wrap your app in `AffitorProvider` from a client component and render it once in your layout. ::: ```tsx // app/providers.tsx — client component 'use client'; import { AffitorProvider } from '@affitor/sdk/react'; export function Providers({ children }: { children: React.ReactNode }) { return {children}; } // wrap {children} with once in app/layout.tsx ``` Child components read the loaded tracker with `useAffitor()` from `@affitor/sdk/react`. It returns `null` while the tracker is loading and during server rendering. ### Any JS / TS app ```ts import { loadAffitor } from '@affitor/sdk'; const affitor = await loadAffitor('YOUR_PROGRAM_ID'); ``` `loadAffitor()` loads the tracker script once and resolves to the tracker instance (the same object as `window.affitor`). It resolves to `null` during server rendering. ### Astro Astro isn't React, so the React `` shown above doesn't apply. Load the tracker from a client ` ``` Prefer a no-build install? Drop the [Script Tag](#script-tag) into the same `` with Astro's `is:inline` directive, so Astro leaves the external script untouched: ```astro ``` Track referred signups the same way — call `signup()` from a client ` ``` ### Required attributes | Attribute | Required | Description | |-----------|----------|-------------| | `src` | Yes | tracker script URL | | `data-affitor-program-id` | Yes | your Affitor program ID | | `data-affitor-debug` | No | `true` only while testing: `signup()` then sends a test event instead of a lead. Remove it before production | --- ## How Affiliate Links Work The tracker reads `aff` first, then `via` when `aff` is absent. Use the saved referral URL so a page's unrelated campaign parameters are not mistaken for the partner code: ```text https://yoursite.com?aff=PARTNER123 https://yoursite.com/pricing?via=PARTNER123 ``` When a valid partner code is present and the tracker runs, it records the click and creates the customer relationship used by signup and sale attribution. ### Track every allowed destination If partners can create page links, install the tracker on each destination allowed in [Partner links](/docs/brand/partner-links), including any separately configured subdomain or port. Allowing a domain and acknowledging ownership does not install or verify its tracker. A recent-click status only describes observed activity in a recent sample. It does not prove every page is tracked or that signup and sale tracking work. A short homepage redirect such as `/r/CODE` also does not enable short page links by itself; Affitor does not yet verify a handler for short page links, so page links use the query format. --- ## Verifying Installation ### Enable debug mode **SDK:** ```ts import { loadAffitor } from '@affitor/sdk'; const affitor = await loadAffitor('YOUR_PROGRAM_ID', { debug: true }); ``` With React, pass `debug` to the provider: ``. **Script tag:** ```html ``` ### What to verify Open your browser console and network tab, then confirm: - The tracker loads without errors - Cookies can be written and read - Affitor debug messages appear in the console - Click or test-click activity appears in the dashboard or test-event tooling :::caution Debug mode helps with test verification, but a real affiliate landing flow using a real `?via=` or `?aff=` value still creates real attribution data. Do not mix synthetic tests and production affiliate links. ::: --- ## Common Issues ### No click data appears Check: - The tracker script loaded successfully - The page was visited through a saved link with a valid `?aff=` or `?via=` parameter - Your program ID is correct - CSP rules or browser extensions are not blocking the script ### Cookies are missing Check: - The site is served over HTTPS in production - Browser privacy tools are not blocking cookies - The affiliate landing page executed the tracker before the visitor continued ### Later signup/sale tracking fails This usually means one of the following: - Click tracking did not run before the signup or sale event - The browser session lost `affitor_click_id` between landing and conversion - Signup/payment identifiers do not consistently match your internal customer ID --- ## Next Steps Once click tracking is working, continue with: - [Lead Tracking](/docs/brand/tracking/lead-tracking-signup/) - [Payment Tracking](/docs/brand/tracking/payment-tracking-stripe/) - [Testing Integration](/docs/brand/tracking/testing-integration/) --- id: "brand/tracking/connect-stripe-account" type: "doc" url: "https://affitor.com/docs/brand/tracking/connect-stripe-account" kind: "guide" updated: "2026-11-08" --- # Connect a new Stripe account > Create a second Stripe account under your existing Stripe login, connect it to your Affitor program, test it in Stripe test mode, and check the connection. Create a second Stripe account under your existing Stripe login, activate it, connect it to your Affitor program, and test it before partners send real customers. Affitor connects through Stripe Connect, so you do not create an API key or a webhook for it. **Quick reference** 1. Stripe: account name (top left) › **New account**, then activate it. 2. Affitor: program menu › **Program settings** › **Payments** › **Connect Stripe**, and choose the new account at Stripe. 3. Make a one-time purchase in the new account's test mode through a partner link, then look for **Test** under **Commissions**. ## Step 1: Create the new account in Stripe In the Stripe Dashboard, click the name of your current account in the upper-left corner and select **New account**. The new account uses the same login, and you switch between accounts from the same menu. Each account can have its own business details and its own bank account for payouts. Stripe asks for a separate account for each project, website or business that runs independently ([Stripe: multiple accounts](https://docs.stripe.com/get-started/account/multiple-accounts)). ## Step 2: Activate it Complete Stripe's activation for the new account: your business details and the bank account Stripe pays out to ([Stripe: activate your account](https://docs.stripe.com/get-started/account/activate)). Do this before you connect it. Affitor shows a Stripe account as **Connected** only once Stripe lets it take charges and send payouts; until then the card reads **Not finished**. ## Step 3: Connect it to your program 1. In Affitor, open the program menu, choose **Program settings**, then **Payments**. 2. On the **Stripe** card, select **Connect Stripe**. Stripe opens in a new tab. 3. At Stripe, sign in, choose the new account from your accounts, and allow the connection. 4. Come back to the Affitor tab. The page reads the status again on its own. When it worked there is no confirmation message, the card itself changes; when it did not, the Stripe card says why. ![Program settings, Payments, before anything is set up: the Stripe card says Not connected, with a Connect Stripe button that opens Stripe in a new tab. The Server API card beside it has no sale yet.](/docs/brand/stripe/payments-not-connected.png) Only the program owner can connect Stripe. Other members see "Only the program owner can connect Stripe." Finish the Stripe steps within 10 minutes; if the card still shows **Not connected** after that, select **Connect Stripe** again. If the program is already connected to another Stripe account, there is no **Connect Stripe** button: [switch the program to the new account](#switch-a-program-to-the-new-account) first. If Stripe sends you back without connecting, the Stripe card shows one of these lines: | Message | What to do | |---|---| | "The Stripe connection was cancelled." | You did not allow the connection on Stripe. Select **Connect Stripe** again | | "Only the program owner can connect Stripe. Ask the owner to connect it." | Ask the program owner to connect | | "The Stripe connection changed while you were on Stripe. Refresh to see it." | Refresh the page | | "Stripe did not finish connecting. Try again, or contact support@affitor.com." | Select **Connect Stripe** again; if it keeps failing, write to support | One Stripe account can be connected to several programs, and each program connects to one Stripe account. ## Step 4: Test with Stripe test mode Affitor reads the test-mode purchases of the account you connected and keeps them apart from real money: a test purchase creates a sale and a commission marked **Test**, which is never approved on its own, never invoiced and never paid out. 1. Open one of your partners' referral links, so the Affitor tracker on your site records the click ([click tracking](/docs/brand/tracking/click-tracking)). 2. In Stripe, switch the new account to its test mode: the account's test mode sandbox, under **Sandboxes** in the account picker ([Stripe: sandboxes](https://docs.stripe.com/sandboxes)). A sandbox you create separately is a different environment, and it is not connected to Affitor. 3. Buy a one-time price through your checkout or Payment Link with a Stripe test card, such as `4242 4242 4242 4242` ([Stripe: testing](https://docs.stripe.com/testing)), and an email that no real customer uses. 4. In Affitor, open **Commissions**. The purchase appears with the status **Test**. ![Commissions table where the first row has a Test status pill, followed by Pending and Approved rows.](/docs/brand/stripe/commission-test.png) Use a one-time price for this test. In test mode, Affitor cannot always read the partner of a subscription bought through a Payment Link, Buy Button or Pricing Table, so a test subscription can show no commission. How the partner reaches Stripe depends on your checkout: | Checkout | What carries the partner | |---|---| | Payment Link, Buy Button, Pricing Table | The Affitor tracker on the page adds the click as `client_reference_id` ([how it works](https://affitor.com/changelog/stripe-payment-links-attribution)). Payment Links need a `buy.stripe.com` address. On all three, a `client_reference_id` you set yourself is kept, and if your tracker waits for consent, the visitor must have given it | | Your own Checkout Session | Your server passes `affitor_click_id` in the session metadata, and for a subscription in `subscription_data.metadata` ([Stripe](/docs/brand/tracking/payment-tracking-stripe)) | If Stripe is connected and your server also sends sales through the Server API, send each purchase through one of them only, or it can count twice. ## What you do not set up **No webhook.** Stripe sends the events of every connected account to Affitor's own Connect endpoint, so you do not add a webhook endpoint in the new account. The events Affitor acts on, and what each one does, are on the [Stripe](/docs/brand/tracking/payment-tracking-stripe#stripe-events-affitor-reads) page. **No API key.** Affitor never asks for a Stripe secret key or a restricted key. You approve the connection on Stripe's own page, and you can revoke it in Stripe at any time. ## Check the connection ![Payments after connecting: the Stripe card says Connected and shows the account ID, with a note to disconnect from the Stripe dashboard. A Check Affitor's tracking card now appears below.](/docs/brand/stripe/payments-connected.png) ## Switch a program to the new account If the program is connected to an older Stripe account, disconnect that one first. Affitor has no disconnect button; the card says "To disconnect, use your Stripe dashboard." 1. Sign in to the **old** account in Stripe and revoke Affitor's access under **Apps** › **Apps Overview** › **Installed Apps** ([Stripe: disconnect a platform](https://support.stripe.com/questions/disconnect-your-stripe-account-from-a-connected-third-party-platform)). 2. Affitor receives the disconnect, and every program connected to the old account shows **Not connected**. If the old account served several programs, connect each of them again. 3. Connect the new account as in [Step 3](#step-3-connect-it-to-your-program). Sales and commissions Affitor already recorded stay as they are. After the switch, Affitor no longer receives the old account's events: - Subscriptions that keep billing on the old account no longer create commissions. - Refunds and chargebacks on the old account no longer reach Affitor, so they do not reverse commissions, and a pending commission still becomes approved when its hold period ends. Review the old account's pending commissions under **Commissions** before you switch. ## Related - [Set up your program](/docs/brand/quickstart/setup-program#step-4-connect-payments): the Payments step during setup - [Stripe](/docs/brand/tracking/payment-tracking-stripe): metadata for your own Checkout Sessions, and the Stripe events Affitor reads - [Testing your integration](/docs/brand/tracking/testing-integration): the full click, signup and sale check - [Track a refund](/docs/api-reference/track-refund): refunds when you use the Server API instead of Stripe --- id: "brand/tracking/lead-tracking-signup" type: "doc" url: "https://affitor.com/docs/brand/tracking/lead-tracking-signup" kind: "guide" updated: "2026-11-07" --- # Lead Tracking (Signup) > Track referred signups with the browser helper or the server-side lead API Lead tracking connects a signup to the affiliate click that drove it — turning anonymous referral traffic into an identified customer record. --- ## What Lead Tracking Does When a lead settles, Affitor: 1. links the signup to the tracked click/customer relationship 2. stores your internal customer identifier for later payment attribution 3. advances the customer journey from click → lead A lead sent from your server with your program API key settles right away. By default, a lead sent only from the browser is stored as provisional and does none of the above until it is confirmed (see [Lead auth policy](#lead-auth-policy)). Use the same customer identifier across all three contexts: | Context | Field | |--------|-------| | Browser helper | `customerKey` | | Lead API | `customer_key` | | Stripe metadata later | `affitor_customer_key` | --- ## Prerequisites Before tracking a signup: - [x] the visitor arrived through an affiliate-tracked flow - [x] the tracker created a click/customer relationship first - [x] your signup flow has a stable internal user/customer ID to pass to Affitor A tracked click means the browser already has `affitor_click_id` from the pageview/click step. --- ## Option A — Server-side Lead API (recommended) Send the lead from your backend with your program API key. This is the path that settles the lead: every program requires server-verified leads unless it is set to `browser_allowed` (see [Lead auth policy](#lead-auth-policy)). ### Endpoint ```bash POST https://api.affitor.com/api/v1/track/lead Authorization: Bearer YOUR_PROGRAM_API_KEY Content-Type: application/json ``` ### Request body ```json { "click_id": "cust_42_1234567890", "customer_key": "usr_abc123", "email": "user@example.com" } ``` ### Rules Outside test mode, send the `click_id` from the `affitor_click_id` cookie: Affitor finds the customer through the click. Send your `customer_key` with it, so later sales can find the customer by your own id. A first lead with only `customer_key` answers `400` `Customer not found. Provide a valid click_id or customer_key.`, because Affitor saves your key on the customer only when a lead settles. ### Response ```json { "success": true, "message": "Lead tracked successfully" } ``` ### Node.js example ```ts app.post('/signup', async (req, res) => { const { email, password } = req.body; const newUser = await createUser({ email, password }); const clickId = req.cookies.affitor_click_id; await fetch('https://api.affitor.com/api/v1/track/lead', { method: 'POST', headers: { Authorization: `Bearer ${process.env.AFFITOR_API_TOKEN}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ click_id: clickId, customer_key: newUser.id, email: newUser.email, }), }); res.json({ success: true }); }); ``` ### Python example ```python requests.post( 'https://api.affitor.com/api/v1/track/lead', headers={ 'Authorization': f'Bearer {AFFITOR_API_TOKEN}', 'Content-Type': 'application/json', }, json={ 'click_id': request.cookies.get('affitor_click_id'), 'customer_key': str(new_user.id), 'email': new_user.email, }, ) ``` --- ## Option B — Browser-side `signup()` Use this when signup completes in the browser and the tracker script is loaded on the page. :::warning[Browser leads are provisional by default] On programs that require server-verified leads (every program unless it is set to `browser_allowed`), a browser `signup()` call is recorded as **provisional**. It does not settle the lead, does not save your `customerKey` on the customer, and does not count in partner metrics or pay a per-lead commission. It settles only when your backend sends the same lead (Option A) or a Stripe Checkout payment for that customer arrives through your connected Stripe account. A sale sent to `/api/v1/track/sale` does not settle it. Use `signup()` alongside the server-side call, not instead of it. ::: ### Basic example ```javascript if (window.affitor) { await window.affitor.signup('user_123', 'user@example.com'); } else { window.affitorQueue = window.affitorQueue || []; window.affitorQueue.push(['signup', 'user_123', 'user@example.com']); } ``` ### What the arguments mean | Argument | Required | Meaning | |----------|----------|---------| | `customerKey` | **Yes (recommended for all real integrations)** | your internal user/customer ID | | `email` | Recommended | customer email; used for hashed/masked attribution support | :::caution[Use a real internal identifier] The `customerKey` you pass here should be the same identifier you later use as: - `customer_key` in the tracking API - `affitor_customer_key` in Stripe metadata ::: ### Example inside a signup flow ```javascript document.getElementById('signup-form').addEventListener('submit', async function(e) { e.preventDefault(); const email = document.getElementById('email').value; // Your own signup logic first const result = await createAccount(email); if (result.success) { if (window.affitor) { await window.affitor.signup(result.userId, email); } else { window.affitorQueue = window.affitorQueue || []; window.affitorQueue.push(['signup', result.userId, email]); } } }); ``` ### When to use browser-side signup - your frontend knows when signup succeeds - the tracker is installed on the page - you also send the lead from your backend (Option A), or your program allows browser leads --- ## Browser Mode vs Server Mode | Mode | Best for | Auth | |------|----------|------| | `POST /api/v1/track/lead` | backend-driven signup flows (recommended) | Bearer program API key **required** for the lead to settle | | `signup(customerKey, email)` | frontend/browser signup flows | no Bearer key; provisional on programs that require server-verified leads | A call without a Bearer key is treated as browser mode, even when it comes from your server. Both modes must identify the same customer with the same internal ID. ### Lead auth policy Each program has a lead auth policy. Every program requires **server-verified** leads (`server_required`) unless it is explicitly set to allow browser leads (`browser_allowed`): - a browser-mode lead returns `200` with `"provisional": true` and is stored, but it does not settle attribution, save `customer_key`, count in partner metrics, or pay a per-lead commission - the lead settles when your backend sends it with a Bearer key, or when a Stripe Checkout payment for that customer arrives through your connected Stripe account (a sale sent to `/api/v1/track/sale` does not settle it) A browser lead settles directly only on a program set to `browser_allowed`. A browser lead that did not settle answers `200` with `"provisional": true`. --- ## Test Mode Create a test lead event to verify your integration without affecting production attribution. ```bash curl -X POST https://api.affitor.com/api/v1/track/lead \ -H "Authorization: Bearer YOUR_PROGRAM_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "click_id": "test_lead_001", "customer_key": "test_customer", "additional_data": { "test_mode": true, "program_id": "YOUR_PROGRAM_ID" } }' ``` ### Test mode behavior - creates a test lead event marked `is_test: true` - does not create a real production lead/customer transition - counts toward integration verification only when sent with your program API key; without the Bearer header the event is stored but does not advance verification ### Test mode response ```json { "success": true, "message": "Test lead event tracked successfully", "data": { "eventId": 456, "programId": 1, "test_mode": true } } ``` --- ## Common Failure Modes ### Lead not attributed Check that: - the visitor came through a tracked affiliate click - `customerKey` / `customer_key` matches your real internal user ID - `affitor_click_id` was available when expected - you are not testing only in debug mode ### Wrong identifier used later in payments Mismatched identifiers are the most common cause of broken attribution. The same internal ID must be used across: - `signup(customerKey, email)` - `customer_key` in server-side tracking calls - `affitor_customer_key` in Stripe metadata ### Duplicate signup tracking To prevent duplicates: - call signup tracking only after account creation succeeds - guard against duplicate frontend submissions - deduplicate your signup flow before retrying tracking calls --- ## What to Do Next Once lead tracking is working, set up sale tracking: - [Payment Tracking](/docs/brand/tracking/payment-tracking-stripe/) - [3-Step Integration Guide](/docs/brand/tracking/quickstart-integration/) - [Testing Integration](/docs/brand/tracking/testing-integration/) --- id: "brand/tracking/payment-tracking-stripe" type: "doc" url: "https://affitor.com/docs/brand/tracking/payment-tracking-stripe" kind: "guide" updated: "2026-11-08" --- # Stripe > Record partner sales after a customer pays, with server-side tracking through POST /api/v1/track/sale or with your connected Stripe account. Payment tracking records revenue after a customer pays. Affitor supports two sale-tracking paths: 1. **Server-side tracking**: your backend calls POST /api/v1/track/sale when revenue is finalized 2. **Stripe integration**: you keep charging in your own Stripe account, connect it to the program, and Affitor attributes sales from the payment events its own Stripe Connect endpoint receives --- ## Choose the Right Path | Path | Best for | |------|----------| | **Server-side tracking** | custom backend, any payment provider, Paddle/LemonSqueezy/manual revenue events | | **Stripe integration** | existing Stripe Checkout integration | Use server-side tracking when you control the exact moment revenue is finalized on your server. Use Stripe integration when you take payments on Stripe: connect your Stripe account under **Program settings** › **Payments**, and Affitor receives its payment events through Stripe Connect, with no webhook for you to add. --- ## Option A: Server-side tracking ### Endpoint ```bash POST https://api.affitor.com/api/v1/track/sale Authorization: Bearer YOUR_PROGRAM_API_KEY Content-Type: application/json ``` ### Minimum real-sale payload ```json { "transaction_id": "txn_abc123", "customer_key": "user_123", "amount_cents": 9999, "currency": "USD" } ``` For a real server-side sale, `customer_key` matches a key already stored on a customer in your program, for example by a server-verified lead or an attributed Stripe payment. If the key has not been stored, send a matching `click_id`; otherwise the request returns `400 Customer not found`. ### Full example ```js await fetch('https://api.affitor.com/api/v1/track/sale', { method: 'POST', headers: { 'Authorization': `Bearer ${process.env.AFFITOR_API_KEY}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ transaction_id: order.id, customer_key: currentUser.id, click_id: req.cookies.affitor_click_id, amount_cents: order.totalCents, currency: 'USD', sale_type: 'payment', line_items: [ { name: 'Pro Plan', amount_cents: order.totalCents, quantity: 1 }, ], }), }); ``` ### Runtime rules - `Authorization: Bearer ` is required - `transaction_id` is required and must be unique - `amount_cents` is required and must be a positive number - Affitor must be able to resolve the customer via: - `customer_key` - or `click_id` - If the same `transaction_id` is sent twice, Affitor returns `409 Conflict` ### Response ```json { "success": true, "sale_id": 42, "commission_id": 18, "message": "Sale tracked successfully" } ``` :::tip Use server-side tracking if you want one server-controlled source of truth for revenue events across all payment providers. ::: --- ## Option B: Stripe integration With the Stripe integration, you keep charging customers through your own Stripe account; Affitor does **not** become merchant of record. Connect the account under **Program settings** › **Payments** ([Connect a Stripe account](/docs/brand/tracking/connect-stripe-account)). Stripe then sends the account's payment events to Affitor's own Connect endpoint, so you do not add a webhook. Affitor attributes the conversion from those events and the metadata on each payment, then invoices you through its invoice billing workflow. Stripe refunds and active or lost chargebacks automatically reverse or adjust the related commission through Affitor's connected Stripe events; dispute inquiries and prevented disputes do not trigger a reversal. ### Stripe events Affitor reads The sale rows describe payments that pass attribution and payment-admission checks. Zero-paid subscription invoices create no sale. New invoices with unsupported payment allocations or payments refunded before admission are not recorded automatically; some older payment records require manual reconciliation. | Stripe event | What Affitor does | |---|---| | `checkout.session.completed` | Records a one-time purchase. A subscription checkout records no sale here: its first invoice does | | `invoice.payment_succeeded`, `invoice.paid` | Records a subscription's first payment and each renewal, at most once per invoice | | `charge.refunded` | Applies the refund to a matched commission: a full refund reverses it; a partial refund marks it refunded, with balance adjustment based on its prior state. Some older invoice payments require manual reconciliation ([refund handling](/docs/brand/quickstart/commission-approval-cash-flow#refund-handling)) | | `charge.dispute.created`, `charge.dispute.funds_withdrawn` | Checks the dispute's current status. For an active or lost chargeback, applies the disputed amount to the matched commission. Inquiries and prevented disputes do not trigger a reversal | | `charge.dispute.funds_reinstated`, `charge.dispute.closed` | Checks the dispute's current status. When it is won, sends a notification to review the matched commission; partner credit is not restored automatically | | `account.updated` | Updates the program's Stripe card (**Program settings** › **Payments**) between **Not finished** and **Connected** | | `account.application.deauthorized` | Marks every program on that account **Not connected** | Stripe events credit Checkout purchases and subscription payments. A payment outside them, such as a PaymentIntent your server confirms, is not credited from Stripe: report it from your server ([Track Sale](/docs/api-reference/track-sale)). ### Recommended metadata fields | Field | Required | Description | |-------|----------|-------------| | `affitor_click_id` | Recommended | tracked click ID from the browser cookie | | `affitor_customer_key` | Recommended | your internal customer/user ID | | `program_id` | Recommended | your Affitor program ID. Without it, the sale goes to the program of the customer Affitor matches. With it, only a customer of that program can be credited, which matters when one Stripe account serves several programs | ### One-time payment example ```js function getCookie(name) { const value = `; ${document.cookie}`; const parts = value.split(`; ${name}=`); if (parts.length === 2) return parts.pop().split(';').shift(); return null; } const clickId = getCookie('affitor_click_id'); const session = await stripe.checkout.sessions.create({ line_items: [{ price: 'price_xxx', quantity: 1 }], mode: 'payment', success_url: 'https://yoursite.com/success', cancel_url: 'https://yoursite.com/cancel', metadata: { affitor_click_id: clickId, affitor_customer_key: currentUser.id, program_id: 'YOUR_PROGRAM_ID', }, }); ``` ### Subscription example For subscriptions, `subscription_data.metadata` is the one that counts: Affitor records a subscription's payments from its invoices, which carry the subscription's metadata, not the Checkout Session's `metadata`. Copying the same fields to the Checkout Session's `metadata` does not create an additional subscription sale; Affitor records subscription sales from invoice events. ```js const session = await stripe.checkout.sessions.create({ line_items: [{ price: 'price_xxx', quantity: 1 }], mode: 'subscription', success_url: 'https://yoursite.com/success', cancel_url: 'https://yoursite.com/cancel', metadata: { affitor_click_id: clickId, affitor_customer_key: currentUser.id, program_id: 'YOUR_PROGRAM_ID', }, subscription_data: { metadata: { affitor_click_id: clickId, affitor_customer_key: currentUser.id, program_id: 'YOUR_PROGRAM_ID', }, }, }); ``` ### Why subscriptions need `subscription_data.metadata` - One-time payments are handled from Stripe checkout session completion - Subscription commissions, for the first payment and each renewal, are created from the invoice events (`invoice.payment_succeeded`, `invoice.paid`) - An invoice carries the subscription's metadata (`subscription_data.metadata`), not the Checkout Session's `metadata`, so that is where the click reaches the subscription - Renewals do not depend on it: once the first payment is attributed, Affitor saves the buyer's Stripe customer ID and matches each renewal by the buyer's email, when Affitor has recorded it, or else by that Stripe customer ID - On your own Checkout Session, put the click in `subscription_data.metadata` so it reaches the invoices. Without a click in invoice metadata, Affitor can still match an existing customer or use a valid Affitor `client_reference_id` from the subscription's Checkout Session, subject to account and program checks. The email matches only a customer whose email Affitor has recorded, from a lead your server sent with `trackLead` or an earlier attributed payment. --- ## Pay-as-you-go / Repeated One-Time Purchases Some products charge per usage event rather than via a subscription: independent checkout sessions for things like API credit top-ups, usage-based batches, or metered add-ons. ### How it works Every `checkout.session.completed` event with `mode: 'payment'` is processed independently by Affitor. Each one goes through the full attribution and commission calculation flow. :::note **The invoice events are not involved here.** Affitor uses the invoice events (`invoice.payment_succeeded`, `invoice.paid`) only for subscriptions: a subscription's first payment and each renewal. Pay-as-you-go purchases use `checkout.session.completed`, one event per purchase, each attributed and commissioned separately. ::: ### Attribution across multiple purchases The first purchase is straightforward: if the customer clicked an affiliate link recently, `affitor_click_id` is still in the browser cookie. Later purchases may arrive weeks or months after that click, and the cookie may be gone. Attribution still works if you pass a stable `affitor_customer_key` in every checkout's metadata. Affitor finds the customer by that key (saved on the customer when its signup lead settled) and links all subsequent purchases to the same partner. **Metadata to set on every checkout, including repeat purchases:** ```js const session = await stripe.checkout.sessions.create({ line_items: [{ price: 'price_xxx', quantity: 1 }], mode: 'payment', success_url: 'https://yoursite.com/success', cancel_url: 'https://yoursite.com/cancel', metadata: { affitor_click_id: getCookie('affitor_click_id') || '', // may be empty, that is expected affitor_customer_key: currentUser.id, // links repeat purchases; must be stable program_id: 'YOUR_PROGRAM_ID', }, }); ``` :::tip `affitor_click_id` may be absent for repeat purchases: that is expected and not an error. Affitor will fall back to `affitor_customer_key` for attribution. Still send it when it is available. ::: ### Pre-requisite: signup tracking Affitor creates the customer record when the partner click is tracked. Signup tracking saves your `customer_key` on it, so a later checkout that carries only `affitor_customer_key` finds the customer. Send the lead from your server with the `click_id` and your user ID ([Track Lead](/docs/api-reference/track-lead)), or call the browser helper at user registration: ```js await window.affitor.signup(currentUser.id, currentUser.email); ``` On a program that requires server-verified leads (the default), a browser signup is provisional: the key is saved only when your server sends the lead or a Stripe Checkout payment for that customer arrives ([Lead auth policy](/docs/api-reference/track-lead#lead-auth-policy)). If the key was never saved, a later purchase that carries no click is attributed only if the buyer's email or Stripe customer ID matches a customer Affitor already has. ### Attribution window and repeat purchases The customer's signup must fall within the program's attribution window after the partner click, 60 days by default. If no signup was recorded, the window is checked at the first payment instead. Once the customer's first attributed payment settles, later purchases and renewals are not checked against that window again. Legacy customers without a click timestamp pass the window check. If your commission **Type** is **Recurring**, the months in **For** (**Program settings** › **Commission**) limit how long a partner earns on a customer. They count from the customer's first click on the partner link, not from signup or the first payment. Later payments are still recorded as sales, with a $0 commission: the limit controls what a partner earns, not whether purchases are recognized. ### Troubleshooting pay-as-you-go | Symptom | Likely cause | |---------|--------------| | First purchase attributed, later purchases are not | `affitor_customer_key` is missing or inconsistent across checkouts | | No purchases attributed at all | Checkouts carry no `affitor_click_id` (the tracker is missing on the checkout page, or your Checkout Session does not set it), or Stripe is not connected to the program | | Commissions are $0 after N months | The commission is **Recurring** with **For** set to N months, counted from the customer's first click: later payments are still recorded, and earn $0. Expected, not a bug | --- ## How Affitor Resolves Attribution from Stripe When a Stripe event arrives, Affitor resolves attribution through a fallback chain. ### Simplified lookup order 1. click metadata (`affitor_click_id`) 2. customer email matching 3. Stripe customer ID 4. the click in `client_reference_id`, used only when the metadata has no click (the Affitor tracker writes it on Payment Links, the Buy Button and the Pricing Table) 5. customer key (`affitor_customer_key`) This is why the best production setup is: - install the tracker first - send a stable internal customer ID at signup - pass the same internal ID into Stripe metadata later --- ## Compatibility Notes The runtime accepts legacy metadata aliases for backward compatibility, such as older click/customer-key field names. Do **not** use them in new integrations. For new implementations, use only: - `affitor_click_id` - `affitor_customer_key` - `program_id` --- ## Test Mode for Server-side tracking Send a test sale event without creating a real commission or platform fee. ```bash curl -X POST https://api.affitor.com/api/v1/track/sale \ -H "Authorization: Bearer YOUR_PROGRAM_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "additional_data": { "test_mode": true }, "amount_cents": 9999, "currency": "USD", "sale_type": "payment" }' ``` ### Test mode behavior - still requires the Bearer token - creates a test sale event with `is_test: true` - does **not** create commissions, platform fees, or production metrics - does not require an existing customer record --- ## Troubleshooting ### Server-side tracking returns `401` Check: - the `Authorization` header is present - the value is `Bearer YOUR_PROGRAM_API_KEY` - the API key belongs to the same program you intend to track ### Server-side tracking returns `409` Check: - `transaction_id` is unique - retries are not resending the same completed sale without idempotency control on your side ### Stripe one-time sale not attributed Check: - `program_id` in metadata, if you set it, is this program's ID: with another ID, this program's customers are not credited - `affitor_click_id` and `affitor_customer_key` are passed when available - signup tracking used the same internal customer ID earlier - the program's Stripe card under **Program settings** › **Payments** reads **Connected**. Affitor receives the events through Stripe Connect, so there is no webhook of yours to check ([Connect a Stripe account](/docs/brand/tracking/connect-stripe-account)) ### Stripe pay-as-you-go second/third purchase not attributed Check: - `affitor_customer_key` is present in the metadata of every checkout session (not just the first) - the value is exactly the same stable ID used at signup: any mismatch means the customer record cannot be found - the customer's first lead or purchase was attributed through a click: Affitor saves `affitor_customer_key` on the customer only then, so a later checkout with only the key finds no customer if the first one carried no click ### Stripe renewals not attributed Check: - the subscription's first payment was attributed: renewals follow it through the buyer's recorded email or the saved Stripe customer ID - `subscription_data.metadata` contains all three fields - the program's Stripe card under **Program settings** › **Payments** reads **Connected**, and the subscription bills on that Stripe account. Affitor receives the invoice events (`invoice.payment_succeeded`, `invoice.paid`) through Stripe Connect; you do not add a webhook - the same customer key was used at signup and in Stripe metadata --- ## Related Guides - [3-Step Integration Guide](/docs/brand/tracking/quickstart-integration/) - [Tracking Overview](/docs/brand/tracking/tracking-overview/): the whole flow, from partner click to commission - [Connect a new Stripe account](/docs/brand/tracking/connect-stripe-account): connect and test the account - [Stripe Checkout metadata](/docs/api-reference/integrations/stripe): the code, and a renewal handler for a Stripe webhook you host yourself - [Testing Integration](/docs/brand/tracking/testing-integration/) --- id: "brand/tracking/quickstart-integration" type: "doc" url: "https://affitor.com/docs/brand/tracking/quickstart-integration" kind: "quickstart" updated: "2026-11-08" --- # 3-Step Integration Guide > Get Affitor tracking live with the supported click, signup, and server-side tracking flows Three steps get Affitor tracking live: clicks → signups → sales. Steps 1 and 2 establish attribution; step 3 records revenue. Using an AI coding agent? Set your program API key as the `AFFITOR_API_KEY` environment variable, then give your agent this line. It follows the [agent skill](/docs/skill.md) to add all three steps and verify them. In Settings, **API keys** shows the same line with your program ID filled in, under **Set up with your AI agent**. ## Before You Start Make sure you have: - Your **program ID** - Your **program API key** for server-to-server calls - A decision on how you will track sales (server-side tracking vs Stripe integration): - **Server-side tracking**: your backend calls `POST /api/v1/track/sale`, for any backend or payment provider - **Stripe integration**: attach Affitor metadata to Stripe Checkout sessions :::note Use one naming scheme consistently: - `customerKey`: browser helper argument (`signup(customerKey, email)`) - `customer_key`: tracking API field - `affitor_customer_key`: Stripe metadata field ::: --- ## Step 1: Install the Tracker Add the tracker to every page where affiliate traffic can land. :::tip[Verifying the pipeline] Once the tracker is live on your public site, Affitor detects it automatically, with no debug mode needed. To verify the full pipeline, run the synthetic `click → signup → sale` chain with `npx affitor onboard` or the MCP `affitor_run_verification` tool. See [Testing Integration](/docs/brand/tracking/testing-integration). ::: ```html ``` Replace `YOUR_PROGRAM_ID` with your program ID (program menu → **Program settings** → **Business** → **Program ID**, **Copy**). ### What this does - Detects affiliate visits through the `?via=` or `?aff=` parameter - Creates a tracked customer / click relationship - Stores `affitor_click_id` in a first-party cookie - Sends click/pageview tracking data to Affitor ### Verify Visit your site through a real affiliate link, or enable debug mode while testing. Debug mode also makes `signup()` send a test event instead of a lead, so turn it off before production. Then review: - browser console / network requests - Affitor dashboard → tracking/integration pages --- ## Step 2: Track Signups After signup succeeds, tell Affitor which internal user was created. ### Option A: Browser-side helper Use this when your signup flow runs in the browser and the tracker is already loaded. ```html ``` Or inside your signup flow: ```html ``` **Use this when:** - you already installed the tracker on the page - signup happens in the browser - you want the simplest supported flow By default a browser-only lead is provisional: it does not count as a signup until your server sends the lead (Option B) or a Stripe Checkout payment for that customer arrives through your connected Stripe account. See [lead auth policy](/docs/brand/tracking/lead-tracking-signup/). ### Option B: Server-side lead API Use this when signup logic lives on your backend or you want the server to own the tracking call. ```bash POST https://api.affitor.com/api/v1/track/lead Authorization: Bearer YOUR_PROGRAM_API_KEY Content-Type: application/json { "click_id": "cust_42_1234567890", "customer_key": "user_123", "email": "user@example.com" } ``` ```js await fetch('https://api.affitor.com/api/v1/track/lead', { method: 'POST', headers: { 'Authorization': `Bearer ${process.env.AFFITOR_API_KEY}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ click_id: req.cookies.affitor_click_id, customer_key: newUser.id, email: newUser.email, }), }); ``` ### Lead tracking rules - Outside test mode, send the `click_id` from the `affitor_click_id` cookie: Affitor finds the customer through it. From your server, a first lead with only `customer_key` answers `400` `Customer not found. Provide a valid click_id or customer_key.`; from the browser, `click_id` is always required. - For reliable payment attribution later, always send a stable internal customer ID: - `customerKey` in `signup()` - `customer_key` in the API - Browser-side `signup()` is the easiest to add, but by default it stays provisional until the server-side lead or a Stripe Checkout payment through your connected Stripe account - Server-side API is best when signup completes on your backend **Response:** ```json { "success": true, "message": "Lead tracked successfully" } ``` --- ## Step 3: Track Sales When a customer pays, choose **one** revenue-tracking path. ### Option A: Server-side tracking (works with any payment provider) Send a server-to-server request once payment succeeds. **Endpoint:** `POST https://api.affitor.com/api/v1/track/sale` ```json { "transaction_id": "txn_abc123", "customer_key": "user_123", "click_id": "cust_42_123456", "amount_cents": 9999, "currency": "USD", "sale_type": "payment", "is_recurring": false, "subscription_id": "sub_xyz", "subscription_interval": "monthly", "product_id": "prod_456", "line_items": [ { "name": "Pro Plan", "amount_cents": 9999, "quantity": 1 } ] } ``` | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `transaction_id` | **Yes** | string | Unique transaction identifier used for deduplication | | `amount_cents` | **Yes** | number | Positive integer amount in the currency's [minor unit](/docs/api-reference/track-sale#minor-units-and-conversion) (cents for USD) | | `tax_cents` | No | number | The tax included in `amount_cents`. Commissions are calculated on `amount_cents - tax_cents` | | `customer_key` | Conditional | string | Your internal customer ID | | `click_id` | Conditional | string | Tracked click identifier | | `currency` | No | string | A [supported ISO 4217 code](/docs/api-reference/track-sale#request-fields). Default: `USD` | | `sale_type` | No | string | `payment` or `subscription`. Default: `payment` | | `is_recurring` | No | boolean | Use `true` for recurring charges | | `subscription_id` | No | string | External subscription ID | | `subscription_interval` | No | string | e.g. `monthly`, `quarterly`, `annual` | | `product_id` | No | string | External product identifier | | `line_items` | No | array | Optional item breakdown | ```js await fetch('https://api.affitor.com/api/v1/track/sale', { method: 'POST', headers: { 'Authorization': `Bearer ${process.env.AFFITOR_API_KEY}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ transaction_id: order.id, customer_key: currentUser.id, click_id: req.cookies.affitor_click_id, amount_cents: order.totalCents, currency: 'USD', sale_type: 'payment', }), }); ``` **Response:** ```json { "success": true, "sale_id": 42, "commission_id": 18, "message": "Sale tracked successfully" } ``` :::note `transaction_id` must be unique. Reusing the same value returns `409 Conflict`. ::: ### Option B: Stripe integration If you already use Stripe Checkout, keep taking payment in your own Stripe account. Connect it under **Program settings** › **Payments** (Affitor receives its events through Stripe Connect, with no webhook to add), then attach Affitor metadata to the checkout session, and to `subscription_data.metadata` for a subscription. The code and the rules are on the [Stripe](/docs/brand/tracking/payment-tracking-stripe#option-b-stripe-integration) page. --- ## Which Sales Path Should You Use? | Path | Best for | |------|----------| | **Server-side tracking**: `POST /api/v1/track/sale` | Any backend, any payment provider, custom checkout, Paddle/LemonSqueezy/manual server events | | **Stripe integration** | Existing Stripe Checkout integration | Use server-side tracking when your backend controls the revenue event. Use Stripe integration when you want Affitor to attribute sales directly from the payment events of your connected Stripe account. --- ## Verify it worked ## You're Done All three steps working means your integration is live: | Step | Event | Outcome | |------|-------|---------| | Tracker installed | Click/pageview tracking | affiliate visit captured | | Signup tracked | Lead event | customer linked to partner | | Sale tracked | Sale + commission flow | revenue attributed | Next: - [Testing Integration](/docs/brand/tracking/testing-integration/) - [Stripe](/docs/brand/tracking/payment-tracking-stripe/) - [Tracking Overview](/docs/brand/tracking/tracking-overview/) --- id: "brand/tracking/testing-integration" type: "doc" url: "https://affitor.com/docs/brand/tracking/testing-integration" kind: "guide" updated: "2026-11-07" --- # Testing Integration > Verify click, signup and sale tracking before going live, including the synthetic click, signup and sale chain that moves no real money. Before going live, verify each layer in order to confirm that your identifiers, metadata, and revenue path line up correctly: 1. click tracking 2. signup/lead tracking 3. sale tracking --- ## The synthetic verification chain Once your tracking code is live on your **public site**, Affitor **detects it automatically** (no debug mode required). **Go live** publishes the program once its business details, commission and payments are set ([what each needs](/docs/brand/quickstart/setup-program#step-5-go-live)). It does not test your integration, and the sale in the synthetic chain below does not count as your payment connection: with the Server API, the sale that unlocks Go live has to come from your server. To check the whole pipeline without a real customer, run the synthetic `click → signup → sale` chain through Affitor's real attribution and commission pipeline, with no real money. Three ways run it: - **Run check** under **Check Affitor's tracking** on the **Payments** step of setup, once payments are connected (Stripe connected, or with the Server API, a first sale received from your server) - `npx affitor onboard`, which fires the chain and then polls readiness until `integration_verified` is reached (see [CLI commands](/docs/brand/cli/commands)) - the MCP `affitor_run_verification` tool, followed by `affitor_readiness` `affitor test click|lead|sale` sends one test event at a time; it does not run the chain. :::tip The chain needs an **active commission policy** (so the synthetic sale can produce a commission). Set your commission first, then run it. Limited to 10 runs per program per hour. ::: The manual, per-layer checks below are **optional** — useful when you want to confirm a specific layer is firing in the browser. --- ## 1. Test Click Tracking (optional, manual) ### Tracker debug mode Enable debug mode in your tracker install. **Script tag:** ```html ``` ### What to verify - the tracker script loads successfully - the page can set/read Affitor cookies - click/pageview-related requests are visible in the browser - your dashboard shows test/debug activity for the pageview step :::caution When testing with real affiliate links, remember that a real partner link (`?via=` or `?aff=`) can still create real attribution data. Use test/debug guidance carefully and avoid mixing production referral links into synthetic tests unless that is your intent. ::: --- ## 2. Test Lead Tracking ### Browser-side signup test After a successful signup in a tracked browser session, call: ```javascript await window.affitor.signup('user_123', 'user@example.com'); ``` Verify that: - the same internal ID you passed as `customerKey` is the one you plan to reuse later - the tracker emits the expected network/debug activity - the dashboard/test-event view reflects lead test activity where applicable ### Server-side lead API test ```bash curl -X POST https://api.affitor.com/api/v1/track/lead \ -H "Content-Type: application/json" \ -d '{ "click_id": "test_lead_001", "customer_key": "test_customer", "additional_data": { "test_mode": true, "program_id": "YOUR_PROGRAM_ID" } }' ``` **Expected response:** ```json { "success": true, "message": "Test lead event tracked successfully", "data": { "eventId": 456, "programId": 1, "test_mode": true } } ``` ### What test mode means for leads - creates a test lead event only - does not create a production lead/customer progression - helps verify that your program ID and endpoint wiring are correct --- ## 3. Test Sale Tracking You can test sale tracking in two different ways depending on your implementation: server-side tracking vs Stripe integration. ### Option A — Test Server-side tracking ```bash curl -X POST https://api.affitor.com/api/v1/track/sale \ -H "Authorization: Bearer YOUR_PROGRAM_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "additional_data": { "test_mode": true }, "amount_cents": 9999, "currency": "USD", "sale_type": "payment" }' ``` **Expected response:** ```json { "success": true, "message": "Test sale event tracked successfully", "data": { "eventId": 789, "programId": 1, "test_mode": true } } ``` ### What test mode means for sales - still requires the Bearer token - creates a test sale event only - does not create commissions - does not create platform fees - does not update production metrics ### Option B — Test Stripe integration If you use Stripe Checkout: 1. switch Stripe to test mode 2. complete a test checkout 3. check that the program's Stripe card under **Program settings** › **Payments** reads **Connected**. Affitor receives the events through Stripe Connect, so there is no webhook delivery to verify on your side 4. inspect the metadata on the checkout/payment objects Check that metadata includes: - `program_id` - `affitor_click_id` - `affitor_customer_key` For subscriptions, also confirm the same values exist in `subscription_data.metadata`. --- ## 4. Verify Test Events Were Received Each test-mode call above answers with `"test_mode": true` and an `eventId` when the event was recorded, so the response is your first check. The dashboard also looks up recent test events through `POST /api/tracking/check-test-events`, for every step or for one (`pageview`, `referrals` or `payments`). It is a [dashboard endpoint](/docs/api-reference/overview): it needs a signed-in dashboard session from someone on the program's team with the **Member**, **Admin** or **Owner** role (a **Viewer** is refused) and does not accept a program API key, so you cannot call it from your backend. --- ## 5. Recommended Real-World Test Scenarios ### Scenario A — Full tracked funnel 1. open a fresh browser session 2. land through an affiliate link 3. sign up 4. complete payment 5. verify click → lead → sale linkage ### Scenario B — Server-side tracking path 1. complete a backend-controlled purchase 2. send `POST /api/v1/track/sale` 3. verify the response contains `sale_id` and `commission_id` 4. confirm no duplicate retries reuse the same `transaction_id` ### Scenario C — Stripe subscription path 1. create a Stripe Checkout subscription in test mode 2. ensure `subscription_data.metadata` carries `affitor_click_id` and `affitor_customer_key` (Affitor reads the subscription's invoices, which carry it, not the session's `metadata`) 3. check that the subscription's first payment appears under **Commissions**, marked **Test** 4. confirm your renewal setup will preserve those identifiers --- ## Common Failure Modes ### Lead works but sales do not attribute Usually caused by one of these: - `customerKey` at signup does not match the later payment identifier - Stripe metadata uses the wrong customer key - `transaction_id` is duplicated or missing in the server-side tracking path - no tracked click/customer relationship exists for the customer ### One-time Stripe works but renewals do not Usually caused by: - missing `subscription_data.metadata`: the subscription's invoices carry it, not the checkout's `metadata`, so the first subscription payment never sees the click (renewals follow the first payment) - relying only on initial checkout metadata - mismatched customer key between signup and Stripe metadata ### Dashboard status is confusing The dashboard combines: - test event presence for click/lead verification - Stripe connection/configuration state for payment setup - real sale events for broader integration completeness Treat dashboard status, test-event checks, and the payments in your Stripe Dashboard as complementary signals: no single source is the full picture. --- ## Before You Send Partner Traffic Go live itself needs only business details, commission and payments ([Go live](/docs/brand/quickstart/setup-program#step-5-go-live)). Before partners start sending traffic, confirm all of the following: - tracker installed on all landing pages - signup tracking sends a stable internal customer ID - Server-side tracking or Stripe integration path is fully implemented - Stripe subscription metadata is duplicated correctly when relevant - one end-to-end test has succeeded with the exact path you will use in production Related guides: - [3-Step Integration Guide](/docs/brand/tracking/quickstart-integration/) - [Lead Tracking](/docs/brand/tracking/lead-tracking-signup/) - [Payment Tracking](/docs/brand/tracking/payment-tracking-stripe/) --- id: "brand/tracking/tracking-overview" type: "doc" url: "https://affitor.com/docs/brand/tracking/tracking-overview" kind: "concept" updated: "2026-11-08" --- # Tracking Overview > How Affitor links a partner click, your customer's signup and the sale into one attribution chain, step by step from referral link to commission. Affitor tracking links three events into one attribution chain: - **click**: a visitor arrives through an affiliate link - **signup/lead**: you identify the customer after registration - **sale**: revenue is recorded through Server-side tracking or Stripe integration --- ## The Core Model Every successful integration follows the same three-step shape: 1. A tracked affiliate visit creates a click/customer relationship. 2. Signup tracking attaches your internal user ID to that relationship. 3. Sale tracking records revenue against the same customer/partner relationship. Identifier consistency matters more than any single code snippet. --- ## The Tracking Flow >C: Shares referral link (?via=CODE or ?aff=CODE) C->>Y: Visits, the SDK stores the click C->>Y: Signs up, lead event with the click ID alt Stripe integration (Stripe connected) C->>S: Pays through your Stripe Checkout S->>A: Payment event, through Stripe Connect else Server-side tracking C->>Y: Pays Y->>A: POST /api/v1/track/sale end A->>A: Attributes the sale, creates the commission A->>P: Commission appears (pending, then approved) `} /> Partner shares link Customer clicks Tracker stores `affitor_click_id` Customer signs up Your internal customer ID sent to Affitor Customer pays Server-side tracking or Stripe metadata path **Revenue attributed** --- ## From Click to Commission ### 1. Partner shares a referral link A partner promotes your product with a referral URL such as: ```text https://yoursite.com?via=PARTNER123 ``` Programs created from October 16, 2026 (UTC) use `?via=` unless you pick `?aff=` in **Partner link parameter** under **Program settings** › **Tracking**; older programs keep `?aff=`. ### 2. Click tracking Install the tracker so affiliate visits are detected automatically: - Detects `?via=` or `?aff=` (`aff` wins when a URL has both) - Records the click and stores `affitor_click_id` in a first-party cookie - Links the visit to the correct partner/program, the initial relationship Affitor needs for attribution Guide: [Click Tracking](/docs/brand/tracking/click-tracking/) ### 3. Signup tracking Send your internal customer/user identifier after signup succeeds. - browser helper: `signup(customerKey, email)` - server API: `POST /api/v1/track/lead` with `click_id` and `customer_key` By default a browser `signup()` records a provisional lead, which does not bind your identifier to the customer record for later sale matching (the Lead tracking section shows "Browser leads: server/payment confirmation required"). Send the same lead from your server with your API key (`POST /api/v1/track/lead` with `click_id` and `customer_key`) so the identifier is stored for later matching. Reuse that same identifier as `customer_key` in server-side tracking and as `affitor_customer_key` in Stripe metadata. Guide: [Lead Tracking](/docs/brand/tracking/lead-tracking-signup/) ### 4. Sale tracking Choose one supported revenue path: | Path | Use when | |------|----------| | **Server-side tracking** | your backend controls revenue events | | **Stripe integration** | you already use Stripe Checkout / Stripe integration | With server-side tracking, your backend calls `POST /api/v1/track/sale` when payment succeeds. For a real server-side sale, `customer_key` matches a key already stored on a customer in your program, for example by a server-verified lead or an attributed Stripe payment. If the key has not been stored, send a matching `click_id`; otherwise the request returns `400 Customer not found`. With the Stripe integration, you keep charging in your own Stripe account and attach Affitor metadata. Guide: [Stripe](/docs/brand/tracking/payment-tracking-stripe/), for both paths ### 5. Affitor attributes the sale Affitor must be able to resolve the customer of a server-side sale via `customer_key` or `click_id`. A Stripe payment goes through a lookup order, from the click in the metadata to the customer key: [how Affitor resolves attribution from Stripe](/docs/brand/tracking/payment-tracking-stripe#how-affitor-resolves-attribution-from-stripe). ### 6. Commission and platform records are created After attribution and payment-admission checks pass, Affitor records the sale. Commission creation can be held when the payment cannot be priced. Eligible commissions follow the program's hold and approval rules; test, self-referral and other held commissions have separate rules. See the [cash-flow guide](/docs/brand/quickstart/commission-approval-cash-flow) for approval, invoice funding and withdrawal conditions. How you are billed for it: [Pricing](/docs/getting-started/pricing-performance-model). --- ## Recommended Identifier Mapping | Context | Field | |--------|-------| | Signup helper | `customerKey` | | Lead API | `customer_key` | | Server-side tracking | `customer_key` | | Stripe metadata | `affitor_customer_key` | | Browser click cookie | `affitor_click_id` | | Server-side tracking click field | `click_id` | Use one stable internal customer ID everywhere. --- ## Attribution Basics ### Default model Defaults: - first-party cookie tracking - **the first partner's click keeps the customer**: a later click from another partner in the same browser is logged but does not take the customer over - **attribution window**: 60 days per program by default, one setting. The click must be at most that many days older than the customer's signup (or their first payment, when no signup was recorded). It is checked once, at the first attributed payment; renewals are not re-checked. The same number is the cookie lifetime. See [Attribution Mechanics](/docs/api-reference/attribution/) for details. ### Why the signup step matters The click cookie is reliable, but the internal customer ID is what keeps attribution working across later payment events, especially when payment happens after signup or on a backend-controlled path. --- ## One-Time vs Subscription Payments ### One-time payment Choose either: - Send a server-side tracking event (POST /api/v1/track/sale) after payment succeeds. - Attach Stripe metadata for Stripe integration. ### Subscription payment If you use Stripe subscriptions: - Include metadata on the checkout session. - Include the same metadata on `subscription_data.metadata`. On your own Checkout Session, put the click in `subscription_data.metadata` so it reaches the invoices. Without a click in invoice metadata, Affitor can still match an existing customer or use a valid Affitor `client_reference_id` from the subscription's Checkout Session, subject to account and program checks. --- ## What Most Teams Choose ### Fastest path for Stripe Checkout teams (manual) 1. install tracker 2. send the lead from your backend with `POST /api/v1/track/lead` and your program API key (a browser-only `signup()` lead stays provisional by default) 3. attach Stripe metadata for payment + subscription flows ### Fastest path for custom backend teams (manual) 1. install tracker 2. send the lead from your backend with `POST /api/v1/track/lead` and your program API key 3. send `POST /api/v1/track/sale` from your backend --- ## Related Guides 1. [3-Step Integration Guide](/docs/brand/tracking/quickstart-integration/) 2. [Click Tracking](/docs/brand/tracking/click-tracking/) 3. [Lead Tracking](/docs/brand/tracking/lead-tracking-signup/) 4. [Stripe](/docs/brand/tracking/payment-tracking-stripe/) 5. [Testing Integration](/docs/brand/tracking/testing-integration/) --- id: "partners/quickstart/create-account" type: "doc" url: "https://affitor.com/docs/partners/quickstart/create-account" kind: "quickstart" updated: "2026-10-18" --- # Create Your Partner Account > Sign up, verify your email, choose Join programs, and finish the three-step partner setup. Your partner account is free and takes a few minutes to create. Two steps are easy to miss: **verifying your email** and **choosing Join programs**. ## 1. Sign up Go to **[affitor.com/signup](https://affitor.com/signup)** and choose **I'm a partner**. The form then reads **Create your partner account**. Create it with Google or your email. ## 2. Verify your email If you signed up with email, open your inbox and click the verification link. You're signed in and taken to the welcome page, or straight back to the program you applied to if you started there. :::note You must verify your email before continuing. If the message isn't in your inbox, check spam. ::: ## 3. Choose Join programs The welcome screen asks **How will you use Affitor?** It already has **Join programs** selected from your choice on the sign-up page; select **Continue**. If you open the verification link on another device, **Run a program** is selected instead, so pick **Join programs** yourself. :::warning Pick **Join programs**, not **Run a program**. Run a program puts you on the brand side, where you set up your own affiliate program. ::: If you started by applying to a program, signing in takes you back to that program to finish your application; the setup below can wait. ## 4. Finish partner setup Setup has three steps and opens right after you choose Join programs. You can leave with **Save and exit** at any point. Setup opens by itself once. After that, partner home shows a **Finish setup** card with how many steps are done and a **Continue:** button naming the next one. Once setup is done, a **Start earning** card follows your first click, first commission and first payout. 1. **Your profile**: your name, prefilled from sign-up, and an optional photo (an existing account photo shows when there is one). Your partner code is shown here; programs see it on your links and it does not change. 2. **Get paid**: add a payout method available for your country and currency: Wise or a bank account (ACH or SWIFT). **Skip for now** is fine: before your first withdrawal you also add your legal name and a tax form under **Your account** → **Payouts** (see [Getting paid](/docs/partners/payouts)). 3. **Pick your first program**: find a program on the Marketplace and apply from its page. ## What happens next Your next move is to **browse the Marketplace and join a program**; your links and earnings build from there. --- id: "partners/quickstart/find-and-join-programs" type: "doc" url: "https://affitor.com/docs/partners/quickstart/find-and-join-programs" kind: "quickstart" updated: "2026-10-18" --- # Find and Join Programs > Browse the Affitor Marketplace, apply to a program in one click, and get approved. Your first move after signing up: open the **Marketplace** and join a program. This is the step that turns a new account into an active partner. ## 1. Browse the Marketplace Open the **Marketplace** from your dashboard, or go to **[affitor.com/marketplace](https://affitor.com/marketplace)**. It's public — you can browse programs before you even log in. Each program card shows the commission in one line (for example *20% · 12 months*), how many partners have joined with the initials of its top partners, or **New program** when nobody has joined yet. On the right you see **Apply**, or **Joined** / **Applied** once you are in or waiting; a program your own brand runs says **Your program**. The **Affitor Refer Program** card says **Get link** where other cards say **Apply**: you refer brands to Affitor without applying (see [Refer a brand to Affitor](/docs/partners/quickstart/get-your-referral-link#refer-a-brand-to-affitor)). The **Featured** strip above the search box always starts with it. ### Search, sort and filter Search programs from the box above the cards. **Sort** orders the list by **Newest**, **Highest commission**, **Most partners** or **Longest cookie**. **Filter** narrows it to **Verified only** programs (see below), and by **Commission type** (recurring, one-time, per action), **Category** and **Cookie window** (30+, 60+ or 90+ days); you can tick several types and categories, and one cookie window. On a computer the menu shows how many programs each choice has. Your choices show as chips under the bar; remove one, or **Clear** them all. They are kept in the page address, so a reload or a shared link shows the same list. ### Verified programs A blue check mark after a program's name, or a **Verified** label on its program page, means Affitor has checked how the program runs on Affitor. It is not a review of the product. Hover or tap the mark to see what was checked: - Affitor has recorded real clicks or sales - The brand's payments are connected to Affitor - The brand is up to date on Affitor invoices Once partners of a program have been paid through Affitor, the list adds **Partners have already been paid through Affitor**. Affitor rechecks automatically, so the mark goes away by itself when a check stops holding. To see only these programs, choose **Verified only** in **Filter**. ## 2. Open a program Click any program to see its full details — commission terms, how long commissions last, and what the product does. ## 3. Apply Click **Apply to promote** (**Apply** on a Marketplace card). The only field is an optional **How will you promote it?** :::tip You can apply with **one click** — the message is optional. Don't let a blank field stop you. ::: ## 4. Get approved What happens next depends on the program: - **Instant approval** — the program auto-accepts partners. You'll see a **"You're in"** confirmation with your referral link right away. - **Manual review** — the brand reviews applications. You'll see **"Application sent"** and an **Applied** badge on the program card while you wait. Once the brand approves you, you're enrolled automatically. :::note Affitor doesn't email you at every step yet. Check **Programs**: a program waiting for review shows as **Pending**. ::: ## What happens next Once you're approved, you're enrolled in the program. Open it from **Programs** to **grab your referral link**: it's generated for you automatically. --- id: "partners/quickstart/get-your-referral-link" type: "doc" url: "https://affitor.com/docs/partners/quickstart/get-your-referral-link" kind: "quickstart" updated: "2026-11-07" --- # Get Your Referral Link > Find, copy, and share your tracked referral link, generated automatically when you join. Your referral link is the URL you share for a program. Affitor creates a default link for you; when the brand allows additional links, you can also send people to a specific page. Tracking must run on the destination for visits to be recorded. ## Where to find it Your referral link is created automatically the moment you're approved: no button to press, no setup. Open the program from **Programs** to find it. If you don't see a link, the brand hadn't set a website for the program when you were approved, so no link was created. Once the brand saves a valid website, open the program's **Overview** from **Programs** so Affitor can try again. If the link is still missing, ask the brand to check the program website and link settings. **Copy link** at the top of the program's page copies it. Your links are also under **Top links** on **Overview** and on the **Links** tab, where **Create link** adds another. ## What your link looks like Your link points at the brand's site with your tracking code attached. It takes one of these forms, depending on the brand's setup: ```text https://brand.com/r/YOURCODE https://brand.com?via=YOURCODE https://brand.com?aff=YOURCODE ``` The `/r/` form is used when the brand has set up a short-link redirect on their site; otherwise the link uses the program's parameter, `?via=` or `?aff=`. A short redirect must take the visitor to a page where the tracker runs. Query links carry the code directly to that page. The code identifies your link; the tracker records the visit and stores a browser identifier for later attribution when the brand's signup and sale integrations are connected. If the visitor was already referred by another partner, they stay credited to that first partner. ## Share it Drop your saved link anywhere you reach an audience: content, social posts, communities, newsletters, or direct outreach. The brand manages tracking on its site; you do not install a tracker to share a link. :::tip Share the URL copied from your saved link. Do not remove its tracking code or use an unsaved preview as the link you distribute. ::: ## Link to a specific page Open the program's **Links** tab and select **Create link**. Additional page links depend on the brand's [allowed destinations and link limit](/docs/brand/partner-links). 1. Enter a **Private label** to recognize the link later, such as `Pricing newsletter`. 2. Keep the generated **Link key** or choose an available one before saving. The key cannot be changed after creation. 3. Choose a **Domain** from the brand's list. For a domain that allows any page, enter a **Page path** or paste a full URL on that same domain. A path such as `pricing` is accepted; query parameters and fragments are preserved. 4. Check the **Query link preview**, then select **Create link**. After the form closes, copy the saved URL from the **Links** list or open its QR code and choose **Download PNG**. For example, a path and a saved query link can look like this: ```text /pricing?plan=pro#details https://brand.example/pricing?plan=pro&via=pricing-newsletter#details ``` Your program may use `aff` instead of `via`. Use the URL Affitor saves rather than adding the parameter yourself. The short-format preview uses `/r//`, such as `https://brand.example/r/pricing/pricing-newsletter`. A nested page keeps all its segments before the code, for example `/r/guides/getting-started/pricing-newsletter`. The default homepage short link remains `/r/YOURCODE`. Copy the saved URL; the preview does not install a short-link handler on the brand's website. If the brand allows **One specific page**, the **Page path** is filled in and locked. You cannot edit that rule's page path; you can choose another domain only if the brand also allows it. **Short format preview · not ready** is an example, not a shareable short link: page links use the query format because Affitor does not yet verify a short-link handler for pages. The example form below uses page `/p` and key `spring`: its query preview is `https://brand.example/p?via=spring` and its short preview is `https://brand.example/r/p/spring`. The short preview is marked **not ready**; copy the saved query link instead.
Partner page-link form with a locked allowed page and a query link preview Partner page-link form with a locked allowed page and a query link preview
The default link's destination belongs to the program; you can edit its private label. An additional link also keeps its key when you change its label. If **Create link** is unavailable because additional links are off or you have reached the limit, ask the brand about its settings. The default link is separate from that limit, and inactive additional links still count. A recent-click message is an observation, not a tracker installation check. A click seen on a site does not prove tracking runs on every allowed page, and no recent click does not prove tracking is broken. Ask the brand to check a destination before sharing if its tracking has not been verified. ## Refer a brand to Affitor Refer a brand has its own link, separate from your program links: `affitor.com/r/` once you set a username, otherwise `affitor.com/r/`. There is nothing to apply for. Get it on your **Referrals** page with **Get my link**, or with **Refer a brand → Get my link** on the Marketplace. On the brand side, **Settings** → **Refer a brand** shows the same link and the brands you referred, and **Refer a brand** in the account menu opens **Referrals**. **Set a username** (or **Edit username**) under the link opens [your username](/docs/partners/account-settings#username). When you are signed in, the **Affitor Refer Program** card (**Get link**), its slide in the **Featured** strip, and **Get your referral link** on its program page open **Referrals** with your link already loaded. A brand that opens it lands on Affitor's home page with "**your name** invited you" above an email field to start sign-up. A brand that signs up through it is credited to you under the [Affitor Refer Program terms](https://affitor.com/legal/refer-program). ### Invite a brand by email **Invite via email**, next to **Copy** on **Referrals** and on the brand side's **Settings** → **Refer a brand**, sends your link for you. In **Invite a brand**, type up to 5 addresses in **Send to**, check the **Preview**, and select **Send invite**. - Affitor sends the email from `noreply@affitor.com`, with the subject "**your name** invited you to Affitor"; replies go to your email. Its **Start your program** button opens your Refer a brand link. - Each address can be invited once every 30 days, whoever sends the invite. An address that already runs a brand on Affitor, or that is not valid (including your own), is not sent. - You can invite up to 20 addresses in 24 hours, skipped ones included. Past that, the dialog says "You've reached today's invite limit. Try again tomorrow." - After sending, a message lists who got the invite and why any address was skipped. ## What happens next As people click and convert, your **Clicks**, **Signups**, **Paid signups**, **Revenue** and **Commission** fill in on the program's **Overview**. Track them to learn what's working. --- id: "partners/quickstart/promote-your-link" type: "doc" url: "https://affitor.com/docs/partners/quickstart/promote-your-link" kind: "guide" updated: "2026-11-07" --- # Promote Your Link and Earn > Turn your referral link into commissions: where to share it, what converts, and how to read the results in your dashboard. Getting your link is step one; earning from it is the real work. This page covers where a referral link actually converts, how to promote it without burning your audience, and how to use your dashboard to double down on what works. ## The one rule that matters Recommend things you would recommend anyway. The partners who earn the most are not the ones who post the most links — they are the ones whose audience already trusts their taste. A referral link works when it sits inside genuinely useful content: a tutorial that happens to use the product, an honest review, a comparison, a workflow you actually run. It fails when it is bolted onto content that exists only to place the link. ## Where links convert Ranked roughly by how well they tend to convert, not by reach: 1. **Content that solves a problem the product solves.** A how-to, a setup guide, a "here's my stack" post. The reader is already in a buying mindset — the link is the natural next step, not an interruption. 2. **Honest reviews and comparisons.** "I tried X for six months — here's the good and the bad." Comparisons especially: people searching "X vs Y" are close to a decision. 3. **Your newsletter.** A warm audience that opted in to hear from you converts far above cold social traffic. One well-placed recommendation to an engaged list beats a hundred cold impressions. 4. **Communities where you are a known regular.** Answering a real question with a real recommendation converts. Drive-by link drops in communities you don't participate in do not — and often get you banned. 5. **Direct outreach.** For high-ticket products, a personal message to someone who has the exact problem outperforms any broadcast. ## What to avoid - **Spraying the link into unrelated threads.** It converts near zero and damages the trust that makes everything else work. - **Hiding that it's a referral.** A short "this is my referral link" line costs you nothing and keeps your audience's trust. Many regions require the disclosure anyway. - **Promising outcomes the product doesn't deliver.** A refund is a clawed-back commission and a lost reader. ## Use one link everywhere You can share the same saved referral link across channels, or [create a page link](/docs/partners/quickstart/get-your-referral-link#link-to-a-specific-page) when the program allows it. Recorded visits and later attribution depend on the brand's tracking setup. Copy the saved URL with its code intact and use your dashboard to compare the activity that is recorded. ## Read your dashboard and double down Each program's **Overview** shows clicks, signups, paid signups, revenue and commission for **7d**, **30d**, **90d** or **All**, with a chart and your **Top links**. Use them as a feedback loop, not a scoreboard: - **Clicks but no signups?** Your audience is curious but the offer or landing page isn't closing them — try a warmer context (a review instead of a mention) or a different audience segment. - **Signups but no sales?** People start but don't convert to paid: this is usually the product's funnel, not your promotion. Worth a note to the brand with **Message** on the program's page ([Chat](/docs/partners/dashboard#chat)). - **One channel outperforming?** Put more there. Most partners find that one or two channels drive the majority of earnings — the data tells you which before your intuition does. ## Verify it worked ## Next steps - [Getting paid](/docs/partners/payouts) — how commissions become a balance and how to withdraw - [Your dashboard](/docs/partners/dashboard): programs, each program's numbers, links and referred customers - [Refer a brand](/docs/partners/referral-rewards) — earn from brands you bring to Affitor --- id: "blog/agent-commerce-attribution-layer" type: "blog" url: "https://affitor.com/blog/agent-commerce-attribution-layer" updated: "2026-07-05" --- # The agent commerce stack is missing its attribution layer > Agentic commerce standards decide how an agent pays. Affitor decides who earned the commission, and lets the agent prove it. {/* Publish-time checklist (CONTENT-MAP guardrails): - Re-verify external stats before shipping: eMarketer $20.57B / 1.5% (Dec 2025 forecast), McKinsey $3-5T by 2030, protocol dates (ACP Sep 29 2025, AP2 Sep 16 2025 + FIDO Apr 28 2026, UCP Jan 11 2026). Last verified 2026-07-05 against the sources cited inline. - Gated on Open Question 3a (agent-native publishing GATE) per CONTENT-MAP. */} In the space of a year, agentic commerce got its payments stack: three standards that decide how an AI agent pays, who authorized the purchase, and how merchants expose themselves to agents. Not one of them decides who gets paid for causing the sale. That is the missing layer, and it is the one Affitor builds. Agentic commerce standards decide how an agent pays. Affitor decides who earned the commission, and lets the agent prove it. Because that claim is easy to inflate, every section of this post carries a label: **SHIPPED**, **BETA**, or **VISION** for Affitor claims, **CONTEXT** where the facts are the industry's. Agents check receipts. You should too. ## A payments stack materialized in twelve months **CONTEXT.** Three standards, three launches: - **ACP** (Agentic Commerce Protocol), from OpenAI and Stripe, launched September 29, 2025: payment execution inside AI surfaces. - **AP2** (Agent Payments Protocol), from Google, launched September 16, 2025 and donated to the FIDO Alliance on April 28, 2026: cryptographically signed mandates that prove who authorized a purchase. - **UCP** (Universal Commerce Protocol), announced January 11, 2026 at NRF and backed by Google, Shopify, Etsy, Wayfair, Target, and Walmart: discovery through post-purchase, including a `.well-known/ucp` merchant endpoint. "The standards are designed to stack, not to replace one another," as [DigitalApplied's merchant guide](https://www.digitalapplied.com/blog/agentic-commerce-standards-ucp-acp-ap2-2026-merchant-guide) puts it. Stacked, they solve checkout end to end: who pays, with what, under whose authority. That is real, useful infrastructure, and it shipped remarkably fast. What none of it solves is referral economics. When an agent recommends a product and the user buys, this stack can execute the payment and prove the mandate. It cannot tell the merchant which partner, publisher, or agent caused the sale, or what commission that work earned. ## The funnel collapsed to a single interaction **CONTEXT.** In agent-mediated commerce, discovery and consideration happen inside the chat. Agents bypass browser-based tracking, and as [DigitalApplied's attribution guide](https://www.digitalapplied.com/blog/ai-agent-commerce-revenue-attribution-guide-2026) describes it, "the entire purchase funnel collapses to a single interaction." [MetaRouter](https://www.metarouter.io/post/agentic-commerce-trends-statistics) notes that AI agents "do not trigger client-side JavaScript." The pixel never fires. Often there is no click at all. The money at stake is not hypothetical. A December 2025 [EMARKETER forecast](https://www.emarketer.com/content/faq-on-agentic-commerce-how-brands-should-act-now-compete-ai-driven-landscape) puts AI platforms at 1.5% of US retail ecommerce in 2026, $20.57 billion, "nearly quadruple 2025 figures." McKinsey projects $3 to $5 trillion in global agentic commerce by 2030, "with up to $1 trillion in US B2C retail alone." Coverage calls server-side tracking "the only reliable solution" and puts full attribution maturity 18 to 24 months out. Affiliate marketing feels this first, because affiliate attribution was built on exactly the primitives agents skip: the click and the cookie. ## The affiliate loop has five verbs **SHIPPED, PARTIAL, and VISION, verb by verb.** Every affiliate program, human-run or agent-run, is the same loop: discover a program, join it, promote it, attribute the sale, settle the commission. The claim here is not "agents will do commerce someday." It is that each verb is becoming an API call, and Affitor has already shipped the hard middle of the loop. B[Join] B --> C[Promote] C --> D[Attribute] D --> E[Settle] E --> A `} /> *The affiliate loop runs on five verbs, and the unglamorous one in the middle, attribution, is the verb agent commerce is missing.* 1. **Discover: SHIPPED** for programs. The [openaffiliate.dev](https://openaffiliate.dev) API returns commission type, rate, duration, cookie window, and payout terms as structured JSON. An agent can query it today with zero install. 2. **Join: PARTIAL.** Merchants create programs with `affitor init` today. Affiliate-side programmatic join and apply is not an agent API yet; that half is VISION. 3. **Promote: SHIPPED as tooling.** 52 open-source skills across research, content, landing pages, distribution, and analytics (`npx skills add Affitor/affiliate-skills`). VISION as autonomy: a standing agent running that flywheel unattended. 4. **Attribute: SHIPPED**, and it is the differentiated verb: signup-anchored, server-side tracking plus a synthetic verification chain the agent runs itself. The next section shows it. 5. **Settle: SHIPPED as rails.** Commission hold, then Stripe Connect payout. VISION as verifiable settlement: signed claims and a deterministic winner, covered below. ## What an agent can do today **SHIPPED** (with one Beta caveat, flagged where it applies). Start from discovery: `GET https://openaffiliate.dev/api/programs?q=...` returns live program terms. A real response today includes Framer at 50% recurring commission for 12 months with a 90-day cookie window, as fields, not prose. For integration, `npx affitor onboard` is a one-shot detect, install, inject, verify flow. The same contract is exposed to agents as an MCP server: `npx -y @affitor/mcp` registers five tools by default, covering readiness, click and lead tracking, the per-stack integration plan, and verification. Set `AFFITOR_MCP_WRITE=1` and it adds sale and refund tracking, for seven. `affitor_get_integration_plan` is a pure tool that reads the same recipe registry the CLI and the public guides read, so the integration contract cannot drift between surfaces. Then comes the part no other affiliate platform ships: proof. `affitor_run_verification` fires a synthetic click, lead, and sale chain through the real attribution pipeline, using isolated test rows that never create real commissions. The agent polls `affitor_readiness` until it reads `integration_verified: true`. If a gate fails, the response names the `blocker` and a `next_action`, so the agent self-corrects and reruns. The endpoint is rate-limited to 10 runs per program per hour, with `retry_after_seconds` telling the agent exactly how long to back off. ```json title="npx affitor onboard --json (final summary)" { "program_id": "430", "steps": [ { "step": "detect", "status": "ok", "detail": "framework=next-app, provider=stripe" }, { "step": "browser_tracking", "status": "skipped", "detail": "json mode" }, { "step": "server_sale", "status": "manual", "detail": "app/api/webhooks/stripe/route.ts: json mode (no auto-edit)" }, { "step": "env_key", "status": "manual", "detail": ".env: json mode (no auto-edit)" } ], "integration_verified": true } ``` That last line is the whole pitch: the only affiliate platform an agent can integrate and verify end to end. Not "installed and hopefully working." Verified against the same pipeline that pays real commissions. :::note `@affitor/mcp` and `@affitor/sdk` are labeled **Beta** in our docs, meaning the documented happy path works. The CLI, the tracking API, the readiness gates, [skill.md](https://affitor.com/docs/skill.md), and the skills registry are shipped and live. ::: ## What proof of attribution looks like **VISION.** Everything in this section is a draft specification, not a product. VSAL, the Verifiable Signup Attribution Log, is Draft v0.2 with an in-browser verifier demo. Nothing here is shipped, and we will keep saying so until it is. The design: attribution anchored at signup, the moment the referred user registers, rather than at a click that may never happen inside an agent conversation. Every touchpoint becomes a signed claim in an append-only log. The winner is picked by a public deterministic function, not by whoever runs the log. Operators work Certificate-Transparency style, so the operator is not a trusted party. The non-goals are explicit: no blockchain settlement, no payment rails. In the spec's words, "VSAL decides who is owed, once, provably." Why bother? Picture two networks claiming the same customer. Today the brand arbitrates blindly and somebody eats the clawback. Under VSAL, both networks submit signed claims, a public function picks the winner, and anyone can audit the outcome without seeing PII. Commissions settle from proof, not trust. That is the settlement layer this stack still needs. AP2 can prove who authorized a payment. Nothing in agentic commerce yet proves who earned the commission. ## Trust is one-shot with agents **Why the labels matter.** An agent that fails its first integration never defaults to you again. A human developer forgives a broken quickstart and files an issue. An agent records the failure and routes around you, permanently, at scale. That is why the honest SHIPPED, BETA, and VISION split above is not modesty, it is the strategy. Everything labeled SHIPPED, an agent can verify right now by firing the synthetic chain and reading `integration_verified` itself. Everything labeled VISION is labeled VISION because a platform whose entire pitch is verifiability cannot afford unverifiable marketing. If you run a SaaS and want the shipped part working today, point your agent at [skill.md](https://affitor.com/docs/skill.md) and let it integrate and verify on its own. If you want the tools and the readiness loop in detail, read the [MCP docs](/docs/api-reference/mcp). The pricing matches the labels: $0/month and $0 setup, with a 3.5% fee only on affiliate-driven sales after your first $10,000, which is fee-free, so testing the SHIPPED column costs nothing. [Create your program at affitor.com](https://affitor.com). --- id: "blog/best-affiliate-software-saas" type: "blog" url: "https://affitor.com/blog/best-affiliate-software-saas" updated: "2026-10-18" --- # Best Affiliate Software for SaaS 2026: Pricing, Fees and 19 Tools Compared (Checked Oct 2026) > Which affiliate software to choose for a SaaS, checked against each vendor's own pricing page in October 2026: what 19 tools cost before the first sale and after a program earns, which have no monthly fee and how their free plans are capped, what a second program costs, and who brings the affiliates.
## Most tools bill before the first sale. Affitor bills after the first $10,000. It depends on your affiliate revenue today. Checked Oct 12, 2026: [Affitor](https://affitor.com/pricing) has no monthly fee, $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales. [Endorsely](https://endorsely.com/pricing) is $0 up to $1,000 a month in affiliate revenue, [PromoteKit](https://www.promotekit.com/pricing) $0 for 3 referrals, [Rewardful](https://www.rewardful.com/pricing) and [FirstPromoter](https://firstpromoter.com/pricing) $49 a month, [Tolt](https://tolt.com/pricing) $69 and [Dub Partners](https://dub.co/pricing) $90. **We make Affitor, so weigh this page with that in mind.** We compared all 19 tools on what decides whether an affiliate program pays off for a SaaS that is just starting one: what you pay before affiliates send a sale, whether there is a cap on affiliate revenue, whether the vendor puts your program in front of affiliates, how partners get paid, and how sales come in from your billing. Every price comes from the vendor's own pricing page, and each tool name links to it. We re-check every number each month and date the change at the top of this page. The tables list tools by entry price, lowest first, with tools priced by quote last; the numbers are that order, not a score. Affiliate network = affiliate management + marketplace - **Network + subscription or quote:** Endorsely, Impact.com, Refersion, Awin, Partnero, Reditus, PartnerStack, Partnerize, Everflow, CJ Affiliate, Rakuten Advertising - **Network, no subscription:** Affitor - **Software + subscription:** PromoteKit, Rewardful, FirstPromoter, Tolt, Tapfiliate, Post Affiliate Pro, Dub Partners - **Software, no subscription:** none Horizontal position is the fixed monthly fee on each vendor's entry plan once a program earns, from its pricing page on Oct 12, 2026: the higher the fee, the further left. PartnerStack, CJ Affiliate, Rakuten Advertising, Partnerize and Everflow price by quote, so they sit at the left edge; Partnerize also offers a performance-based option. The right half is for tools with no fixed monthly fee at any revenue level. Vertical position scores whether the vendor lists your program where affiliates look and helps you recruit them, on the entry plan or on an upper plan, with a step up for established networks. A capability on an upper plan counts half, so Dub, whose marketplace and recruiting tools are on Enterprise, sits just below the line. Chips are nudged slightly where they would overlap. Among the tools that publish their prices, one sits in the top-right. Each chip jumps to the tool's row in the [price table](#prices).
## What you give up when you buy a tracker instead of a platform Most tools in this comparison sit in one of three groups, and each group has a predictable gap. Self-serve trackers are solid and quick to set up but bill monthly from day one and leave recruiting to you. Affiliate networks bring a large publisher base, but they are built for ecommerce, track SaaS sales through server-to-server calls, and charge a fee on every transaction or quote after a call. Enterprise platforms do everything on a contract. The columns are groups rather than single vendors, so the tools that beat their group are named in the rows further down. Hover any row for the detail behind it. | Capability | Affitor | Self-serve trackers
Rewardful, Tolt, Tapfiliate | Affiliate networks
Awin, CJ, PartnerStack | Enterprise platforms
Impact, Partnerize, Everflow | | --- | --- | --- | --- | --- | | Nothing to pay before affiliate revenue
A program can launch, recruit and track with no monthly bill. | Yes | $29 to $89/mo | From $49/mo + 3.5%, or quote | $30/mo or 2.5% of partner-driven revenue, whichever is greater (Starter), or quote | | No cap on affiliate revenue
The plan price does not step up as affiliates sell more. | Yes | Caps on most entry plans | Not published or ARR caps | Not published | | Program listed where affiliates look
The vendor puts your program in a marketplace or network affiliates browse. | Yes | Refersion, Partnero, Endorsely | Yes | Impact Essentials, $500/mo including $2,500 in partner payouts | | Reads sales from Stripe natively
Sales come in from Stripe without server-to-server work. | Yes | Typically | Server-to-server | Impact, Everflow | | Payouts sent to partners for you
The vendor moves the money to affiliates instead of you paying each one. | Yes | Upper plans or a fee | Typically | Varies | | No minimum contract
Start month to month and leave when you want. | Yes | Typically | 3 months at Awin, 1 year at PartnerStack | 12 months at impact.com, 6 months at Everflow | | Test sale before launch
A documented way to test tracking end to end before partners send real traffic. Most tools here have one. | Yes | Typically | Typically | Typically | | Published self-serve pricing
You can see the price and start without a sales call. | Yes | Typically | Awin, Reditus | Impact Starter |
Groupings describe the typical shape of each group, not every vendor. Among trackers, Endorsely's free Starter plan lists your program in its affiliate network while affiliate revenue stays under $1,000 a month, PromoteKit is free for your first 3 referrals, and Refersion charges 3% of affiliate sales on top of its plan. Among networks, Awin publishes $49 a month plus 3.5% per transaction, Reditus publishes its prices, and Rakuten Advertising is moving its advertiser programs to impact.com. Impact.com charges $30/mo or 2.5% of partner-driven revenue, whichever is greater (Starter) and needs an ecommerce integration on Starter; its marketplace starts on Essentials at $500/mo including $2,500 in partner payouts. Affitor is a percentage too: once a program passes $10,000 in affiliate-driven sales it pays 3.5% of those sales, and partners get paid by bank transfer or Wise after a review. Prices as listed on each vendor's pricing page on Oct 12, 2026 (impact.com checked October 17, 2026); the [cost table](#prices) links to each one.
## What each tool costs to start Headline prices hide the terms that matter: **when billing starts**, and what makes the price step up. A $29 plan with a $10,000 cap and a $49 plan with a $7,500 cap are different deals once affiliates sell, and a $49 network plan that adds 3.5% per transaction costs more than its sticker. Each figure below comes from the vendor's pricing page; the tool name links to it. | Tool / Platform | Entry price | Fee on top | Revenue cap
The most affiliate revenue, payouts or ARR the entry plan covers before you move up. | Minimum term
Shortest commitment on the entry plan, from the vendor's pricing page or terms. | Billing | | --- | --- | --- | --- | --- | --- | | [Affitor](https://affitor.com/pricing)
until a program has made $10,000 through affiliates | $0 | 3.5% of affiliate-driven sales
after the first $10,000 per program | None | None | Stripe with no code; other billing through the API or SDK | | [PromoteKit](https://www.promotekit.com/pricing)
then $29/mo on Pro | $0 for 3 referrals | None
PromoteKit-run payouts: 5% if funded by bank, 8% by card | $10,000/mo
affiliate revenue on Pro | None | Stripe required | | [Endorsely](https://endorsely.com/pricing)
affiliate revenue, then $39/mo on Pro | $0 up to $1,000/mo | None stated
pricing page says “No commission fees” | $1,000/mo on free Starter
$5,000 affiliate revenue on Pro | None | Not checked | | [Impact.com](https://impact.com/pricing/)
Starter; Essentials $500/mo including $2,500 in partner payouts; Pro $2,500 | $30/mo or 2.5%
of partner-driven revenue, whichever is greater (Starter) | No setup fee on Starter
setup and onboarding available at $250/hour on Essentials and up | Not published
payout tiers; Essentials $500/mo including $2,500 in partner payouts, with payouts above that billed à la carte | 12-month contract
per pricing FAQ; Starter's term not stated | Starter: Shopify, WooCommerce, BigCommerce and 6 more ecommerce platforms | | [Refersion](https://www.refersion.com/pricing/)
Launch, monthly; $29/mo billed annually | $39/mo | +3% of affiliate sales
Growth is +2%; Unified Payments adds 1% of each funding, max $6 | None
Unlimited affiliates, clicks and conversions on Launch | None | Shopify, WooCommerce; Stripe on Growth | | [Rewardful](https://www.rewardful.com/pricing)
Starter, 14-day trial | $49/mo | 0%
3% if Rewardful runs payouts | $7,500/mo
affiliate revenue on Starter | None | Stripe, Paddle Classic | | [FirstPromoter](https://firstpromoter.com/pricing)
Starter, 14-day trial, no card | $49/mo | None listed | $5,000/mo
affiliate revenue on Starter | None | Stripe, Paddle, Chargebee, Recurly, Braintree | | [Awin](https://www.awin.com/us/pricing)
Access plan, first month free | $49/mo | 3.5% of each transaction
Awin tracking fee on Access; 2.5% on Accelerate (from $99/mo) | None listed
3-month minimum term | 3-month minimum | Ecommerce platforms; others server-to-server | | [Partnero](https://www.partnero.com/pricing)
$49/mo billed annually | $59/mo | 7% if Partnero runs payouts | None
1 program, 1 seat on Starter | None | Stripe, Paddle, Chargebee | | [Tolt](https://tolt.com/pricing)
Basic, 14-day trial, no card | $69/mo | 2%
on automatic payouts | $10,000/mo
affiliate revenue on Basic | Not published | Stripe, Paddle, Chargebee | | [Tapfiliate](https://tapfiliate.com/pricing/)
Launch, monthly; $74/mo billed annually, 7-day trial | $89/mo | None listed
No setup, tracking or transaction fees; overage per extra 1,000 clicks or conversions | 500 conversions/mo
50 affiliates, 1 program, 5,000 clicks/mo on Launch | None | Stripe, Shopify, PayPal; others by webhook | | [Post Affiliate Pro](https://www.postaffiliatepro.com/pricing/)
Starter, monthly; $79/mo billed annually, 30-day trial | $89/mo | None listed
No transaction fees; $5 per extra 10,000 tracking requests | 10,000 tracking requests/mo
Unlimited affiliates, 1 campaign on Starter | None | Stripe, PayPal, Braintree and 200+ more | | [Dub Partners](https://dub.co/pricing)
Business, 14-day trial | $90/mo | 5% of payouts funded by ACH
8% if funded by card; 3% and 6% on Enterprise | $2,500/mo in payouts
500 partners on Business | None | Not checked | | [Reditus](https://getreditus.com/pricing)
$99/mo billed annually | $149/mo | 5% by card or 2% by invoice
on the commissions you pay | $60K ARR
on Growth | None on Growth | Stripe natively; Paddle, Chargebee and others through its Payments API | | [PartnerStack](https://www.partnerstack.com/pricing)
Entry plan | Quote after demo | Not published | Not published | 1-year renewing terms | Not checked | | [Partnerize](https://partnerize.com/pricing)
fixed license fee or percentage-based fee | Quote after demo | Not published
page says all-inclusive, no overage penalties | Not published | Not published | Shopify, Magento, Salesforce Commerce | | [Everflow](https://www.everflow.io/pricing)
6-month minimum commitment | Quote after demo | Not published
one-time onboarding service; Everflow Pay usage fee | Not published | 6-month minimum | Stripe, ReCharge, Shopify and more | | [CJ Affiliate](https://www.cj.com/support)
No public pricing page | Quote after consultation | Not published | Not published | Not published | Ecommerce plugins; others server-to-server | | [Rakuten Advertising](https://rakutenadvertising.com/affiliate/)
No public pricing page | Quote after contact | Not published | Not published | Not published | Not checked |
Pricing based on entry-level plans as listed on each vendor's pricing page on Oct 12, 2026 (impact.com checked October 17, 2026; its Starter billing rule is from the [impact.com help center](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/finance/finance-for-starter-edition-accounts/impactcom-starter-edition-billing-explained)). "Revenue cap" is the most affiliate revenue, partner payouts or ARR the entry plan covers. Affitor's $0 holds until a program has made $10,000 through affiliates; after that it charges 3.5% of affiliate-driven sales, with no subscription. Where a vendor gates payouts, seats or a marketplace listing behind an upper plan, the real monthly cost runs higher than the entry price shown.
## What you pay before your programs earn A new program can take months to bring in its first affiliate sale, and until it does the subscription is the whole bill. These are the fixed fees with no affiliate revenue at all, added up over 6, 12 and 18 months, for 1, 2, 5 and 10 programs, on each vendor's lowest monthly plan that holds that many programs. Hover any column for what sits behind it. | Tool / Platform | 1 program
Total fixed fees after 6 / 12 / 18 months with no affiliate revenue. | 2 programs
Total fixed fees after 6 / 12 / 18 months with no affiliate revenue. | 5 programs
Total fixed fees after 6 / 12 / 18 months with no affiliate revenue. | 10 programs
Total fixed fees after 6 / 12 / 18 months with no affiliate revenue. | | --- | --- | --- | --- | --- | | [Affitor](https://affitor.com/pricing)
No subscription; $0 until each program has made $10,000 | $0 / $0 / $0 | $0 / $0 / $0 | $0 / $0 / $0 | $0 / $0 / $0 | | [PromoteKit](https://www.promotekit.com/pricing)
Free for 1 campaign and 3 referrals; Pro $29/mo for more campaigns | $0 / $0 / $0 | $174 / $348 / $522 | $174 / $348 / $522 | $174 / $348 / $522 | | [Endorsely](https://endorsely.com/pricing)
Starter, $0 up to $1,000/mo in affiliate revenue; no program limit stated | $0 / $0 / $0 | $0 / $0 / $0 | $0 / $0 / $0 | $0 / $0 / $0 | | [Rewardful](https://www.rewardful.com/pricing)
Starter $49/mo, 1 campaign; Growth $99/mo | $294 / $588 / $882 | $594 / $1,188 / $1,782 | $594 / $1,188 / $1,782 | $594 / $1,188 / $1,782 | | [FirstPromoter](https://firstpromoter.com/pricing)
Starter $49/mo; Business $99/mo for 2 websites, Enterprise $149/mo for 3 | $294 / $588 / $882 | $594 / $1,188 / $1,782 | No published plan fits | No published plan fits | | [Awin](https://www.awin.com/us/pricing)
Access, $49/mo per program from month 2 | $245 / $539 / $833 | $490 / $1,078 / $1,666 | $1,225 / $2,695 / $4,165 | $2,450 / $5,390 / $8,330 | | [Partnero](https://www.partnero.com/pricing)
Starter $59/mo, 1 program; Partner $199/mo for 3; Enterprise from $599/mo | $354 / $708 / $1,062 | $1,194 / $2,388 / $3,582 | $3,594 / $7,188 / $10,782 | $3,594 / $7,188 / $10,782 | | [Tolt](https://tolt.com/pricing)
Basic $69/mo, 2 programs; Growth $99/mo for 5; Pro $199/mo | $414 / $828 / $1,242 | $414 / $828 / $1,242 | $594 / $1,188 / $1,782 | $1,194 / $2,388 / $3,582 | | [Tapfiliate](https://tapfiliate.com/pricing/)
Launch $89/mo, 1 program; Scale $179/mo | $534 / $1,068 / $1,602 | $1,074 / $2,148 / $3,222 | $1,074 / $2,148 / $3,222 | $1,074 / $2,148 / $3,222 | | [Post Affiliate Pro](https://www.postaffiliatepro.com/pricing/)
Starter $89/mo, 1 campaign; Pro $139/mo | $534 / $1,068 / $1,602 | $834 / $1,668 / $2,502 | $834 / $1,668 / $2,502 | $834 / $1,668 / $2,502 | | [Dub Partners](https://dub.co/pricing)
Business $90/mo; program limit not stated | $540 / $1,080 / $1,620 | $540 / $1,080 / $1,620 | $540 / $1,080 / $1,620 | $540 / $1,080 / $1,620 | | [Reditus](https://getreditus.com/pricing)
Growth $149/mo; program limit not stated | $894 / $1,788 / $2,682 | $894 / $1,788 / $2,682 | $894 / $1,788 / $2,682 | $894 / $1,788 / $2,682 | | [Impact.com](https://impact.com/pricing/)
Essentials, $500/mo including $2,500 in partner payouts, plus setup and onboarding available at $250/hour | $3,000 / $6,000 / $9,000 | $3,000 / $6,000 / $9,000 | $3,000 / $6,000 / $9,000 | $3,000 / $6,000 / $9,000 |
Monthly prices checked Oct 12, 2026; program limits checked Oct 13, 2026; each tool name links to its pricing page. Awin's first month is free and its $49 platform fee is charged per program. PromoteKit's free plan covers 1 campaign and 3 referrals, so a second program moves to Pro; this assumes your products can run as campaigns in one Pro account, which PromoteKit does not say. FirstPromoter's plans run up to 3 websites, so 5 or 10 programs have no published plan. Endorsely, Dub Partners, Reditus and impact.com do not state a program limit, so their rows assume one account holds every program, the lowest reading. Totals count recurring fees; on Essentials and up, impact.com setup and onboarding services are available at $250/hour (checked October 17, 2026). Refersion reads Stripe subscriptions on its Growth plan ($199/mo plus 2% of affiliate sales), impact.com Starter requires an ecommerce integration, and PartnerStack, Partnerize, Everflow, CJ Affiliate and Rakuten Advertising price by quote, so they are left out of both scenario tables. Rows follow the entry-price order of the [price table](#prices); impact.com is shown on Essentials, so it comes last.
## One program, $10,000 in 6 months, then $2,000 a month The second question is what a program costs once it works. This scenario follows one program whose affiliates bring in $500, $1,000, $1,500, $2,000, $2,500 and $2,500 in months 1 to 6, which adds up to $10,000, and then $2,000 a month. Partners earn a 20% commission, which sets the fees charged on payouts (Dub Partners, Reditus, impact.com), and each vendor is on its lowest monthly plan that fits. PromoteKit's free plan stops at 3 referrals, so the scenario assumes the program passes 3 referrals in month 1 and is on Pro from the start. Totals are cumulative, and rows keep the order of the table above. | Tool / Platform | 6 months
Total cost from month 1 to month 6. | 12 months
Total cost from month 1 to month 12. | 18 months
Total cost from month 1 to month 18. | | --- | --- | --- | --- | | [Affitor](https://affitor.com/pricing)
$0 until $10,000, reached in month 6; then 3.5% of $2,000 = $70/mo | $0 | $420 | $840 | | [PromoteKit](https://www.promotekit.com/pricing)
Pro $29/mo, up to $10,000/mo in affiliate revenue | $174 | $348 | $522 | | [Endorsely](https://endorsely.com/pricing)
$0 up to $1,000/mo, then Pro $39/mo, up to $5,000/mo | $156 | $390 | $624 | | [Rewardful](https://www.rewardful.com/pricing)
Starter $49/mo, up to $7,500/mo in affiliate revenue | $294 | $588 | $882 | | [FirstPromoter](https://firstpromoter.com/pricing)
Starter $49/mo, up to $5,000/mo in affiliate revenue | $294 | $588 | $882 | | [Awin](https://www.awin.com/us/pricing)
Access $49/mo from month 2, plus 3.5% of each transaction | $595 | $1,309 | $2,023 | | [Partnero](https://www.partnero.com/pricing)
Starter $59/mo | $354 | $708 | $1,062 | | [Tolt](https://tolt.com/pricing)
Basic $69/mo, up to $10,000/mo in affiliate revenue | $414 | $828 | $1,242 | | [Tapfiliate](https://tapfiliate.com/pricing/)
Launch $89/mo, 500 conversions/mo | $534 | $1,068 | $1,602 | | [Post Affiliate Pro](https://www.postaffiliatepro.com/pricing/)
Starter $89/mo, 10,000 tracking requests/mo | $534 | $1,068 | $1,602 | | [Dub Partners](https://dub.co/pricing)
Business $90/mo, plus 5% of payouts funded by ACH | $640 | $1,300 | $1,960 | | [Reditus](https://getreditus.com/pricing)
Growth $149/mo, plus 2% by invoice on the commissions you pay | $934 | $1,876 | $2,818 | | [Impact.com](https://impact.com/pricing/)
Essentials, $500/mo including $2,500 in partner payouts | $3,000 | $6,000 | $9,000 |
Monthly prices checked Oct 12, 2026; each tool name links to its pricing page. Affitor costs $0 for the first six months here; every other tool in the table has started billing by month 3. Its fee starts in month 7, at 3.5% of the month's affiliate-driven sales. By month 12, PromoteKit and Endorsely cost less than Affitor in this scenario. Their plans cap the affiliate revenue they cover: PromoteKit Pro at $10,000 a month, Endorsely Pro at $5,000 a month (Scale, $99 a month, runs to $20,000). PromoteKit lists no marketplace or recruiting help in its plan table; Endorsely lists your program in its affiliate network. Tapfiliate and Post Affiliate Pro cap conversions and tracking requests rather than revenue, and these rows assume the program stays under them. A different revenue path gives different totals, so treat the table as one worked example.
## What a second program costs **Each program gets its own $10,000 free, and a second program never forces a bigger plan.** On Affitor there are no plan tiers to move between: a new program starts at $0 and pays 3.5% of its affiliate-driven sales after its own first $10,000. Most flat-fee tools count programs, campaigns or websites per plan, so a second product moves you up a tier. | Tool / Platform | Entry plan holds
How many programs, campaigns or websites the entry plan runs. | A second program
What you need to run one more program. | In the vendor's words
From the vendor's plan table or help center, checked Oct 13, 2026. | | --- | --- | --- | --- | | [Affitor](https://affitor.com/pricing)
No subscription | No plan limit
one plan for every program | Nothing more
its own $10,000 at $0, then 3.5% | “First $10,000 of affiliate revenue per program, genuinely free. Not a trial.” | | [PromoteKit](https://www.promotekit.com/pricing)
Free plan | 1 campaign
up to 3 referrals | Pro, $29/mo
unlimited campaigns | Free: “1 Affiliate Campaign”. Pro: “Unlimited Affiliate Campaigns”. | | [Refersion](https://www.refersion.com/pricing/)
Launch $39/mo + 3% of affiliate sales | 1 brand
per account | A separate account
or Scale, with a one-time multi-domain setup fee | “it's likely best to create a separate account for each of your brands” | | [Rewardful](https://www.rewardful.com/pricing)
Starter $49/mo | 1 campaign | Growth, $99/mo
unlimited campaigns | Starter: “Campaigns 1”. Growth: “Campaigns Unlimited”. | | [FirstPromoter](https://firstpromoter.com/pricing)
Starter $49/mo | 1 website
no multiple websites on Starter | Business, $99/mo
2 websites; Enterprise $149/mo for 3 | “Manage multiple websites: Separate workspaces on different domains.” Starter No, Business 2, Enterprise 3. | | [Awin](https://www.awin.com/us/pricing)
Access $49/mo + 3.5% per transaction | 1 program
per advertiser ID | Its own application
and its own $49/mo platform fee | “Each program requires its own unique advertiser ID.” | | [Partnero](https://www.partnero.com/pricing)
Starter $59/mo | 1 program | Partner, $199/mo
3 programs; $159/mo billed annually | Starter: “1 Program”. Partner: “3 Programs”. | | [Tolt](https://tolt.com/pricing)
Basic $69/mo | 2 programs | No upgrade
a third needs Growth, $99/mo, for up to 5 | Basic: “2 programs”. Growth: “5 programs”. Pro: “Unlimited programs”. | | [Tapfiliate](https://tapfiliate.com/pricing/)
Launch $89/mo | 1 program | Scale, $179/mo
unlimited programs | Launch: “Affiliate Programs 1”. Scale: “Affiliate Programs Unlimited”. | | [Post Affiliate Pro](https://www.postaffiliatepro.com/pricing/)
Starter $89/mo | 1 campaign | Pro, $139/mo
unlimited campaigns | Starter: “Number of campaigns 1”. Pro: “Number of campaigns UNLIMITED”. |
Program limits from each vendor's plan table or help center, checked Oct 13, 2026; each tool name links to its pricing page. Endorsely, Dub Partners, Reditus, impact.com and PartnerStack do not state a program limit on their pricing pages, so they are left out. Rows follow entry price, lowest first; the numbers are that order, not a score.
## Which affiliate software has no monthly fee, and the caps on free plans As of October 12, 2026, Affitor has no monthly fee: $0 until a program makes $10,000 through affiliates, then 3.5% of each affiliate sale. Lemon Squeezy has none either but takes a fee on every sale, plus 3% on affiliate-referred ones. Endorsely and PromoteKit have capped free plans; others start with a trial, a plan or a quote. Free plans are rare: among these 19 tools, three let you start without paying, and each caps it differently. Revenue caps are the common catch, since a cap moves you to a bigger plan as soon as affiliates do well. Hover any column for what sits behind the mark. | Tool / Platform | Free plan
A free plan you can actually run a program on, not a time-limited trial. | No monthly fee
No fixed monthly fee at any level of affiliate revenue. The note is the entry plan's monthly price once a program earns. | No revenue cap
The entry plan has no cap on affiliate revenue, payouts or ARR. | No fee on top
No mandatory fee on sales or payouts on top of the plan. | Partners
No limit on affiliates on the entry plan. | Seats
No limit on team members on the entry plan. | Public pricing
Prices on the vendor's site, no sales call needed. | | --- | --- | --- | --- | --- | --- | --- | --- | | [Affitor](https://affitor.com/pricing) | Yes
$0 until $10k | Yes
3.5% after $10k | Yes
no cap | Partial
3.5% after $10K | Yes
unlimited | Yes
unlimited | Yes
full pricing | | [PromoteKit](https://www.promotekit.com/pricing) | Partial
3 referrals | No
$29/mo on Pro | No
$10,000/mo on Pro | Partial
5%/8% optional payouts | Yes
all plans | Yes
all plans | Partial
Enterprise: contact | | [Endorsely](https://endorsely.com/pricing) | Yes
to $1,000/mo | No
$39/mo on Pro | No
$1,000/mo Starter | Yes
no commission fees | Not checked | Partial
none on Starter | Partial
Enterprise: demo | | [Impact.com](https://impact.com/pricing/) | No
Starter $30/mo | No
$30/mo or 2.5%, whichever is greater | Not checked | Partial
$30/mo or 2.5%, whichever is greater | Not checked | Not checked | Yes
all four tiers priced, $30 to $10,000/mo | | [Refersion](https://www.refersion.com/pricing/) | No
free listing | No
$39/mo + 3% | Yes
none stated | No
+3% affiliate sales | Yes
Launch | Not checked | Partial
Scale: contact sales | | [Rewardful](https://www.rewardful.com/pricing) | No
14-day trial | No
$49/mo | No
$7,500/mo Starter | Partial
3% Managed Payouts | Yes
all plans | Partial
2 on Starter | Yes
Enterprise $149+ | | [FirstPromoter](https://firstpromoter.com/pricing) | No
14-day trial | No
$49/mo | No
$5,000/mo Starter | Yes
flat plans | Partial
1,000 on Starter | Yes
all plans | Yes
Enterprise $149 | | [Awin](https://www.awin.com/us/pricing) | No
1 month free | No
$49/mo + 3.5% | Yes
none listed | No
3.5% tracking fee | Not checked | Yes
all plans | Partial
Advanced: custom | | [Partnero](https://www.partnero.com/pricing) | No
30-day trial | No
$59/mo | Yes
all plans | Partial
7% managed payouts | Yes
all plans | Partial
1 on Starter | Yes
Enterprise $599+ | | [Tolt](https://tolt.com/pricing) | No
14-day trial | No
$69/mo | No
$10,000/mo Basic | Partial
2% auto payouts | Yes
all plans | Partial
3 on Basic | Partial
Enterprise: contact | | [Tapfiliate](https://tapfiliate.com/pricing/) | No
7-day trial | No
$89/mo | Yes
500 conversions/mo | Yes
except overage fees | Partial
50 on Launch | Partial
1 on Launch | Partial
Enterprise: custom | | [Post Affiliate Pro](https://www.postaffiliatepro.com/pricing/) | No
30-day trial | No
$89/mo | Yes
10k requests/mo | Yes
no transaction fees | Yes
all plans | Partial
multiple admins Ultimate | Yes
all four plans | | [Dub Partners](https://dub.co/pricing) | No
14-day trial | No
$90/mo | No
$2.5K/mo payouts | No
5% payout fee | Partial
500 on Business | Partial
10 on Business | Partial
Enterprise custom | | [Reditus](https://getreditus.com/pricing) | No
14-day trial | No
$149/mo | No
$60K ARR, Growth | No
5%/2% payout fee | Yes
Growth | Yes
all plans | Yes
Enterprise from $799 | | [PartnerStack](https://www.partnerstack.com/pricing) | No
No free tier | By quote | Not published | Not published | Yes
all plans | Yes
all plans | No
Demo for quote | | [Partnerize](https://partnerize.com/pricing) | No
by quote | By quote | Not checked | Yes
says all-inclusive | Not checked | Not checked | No
by quote | | [Everflow](https://www.everflow.io/pricing) | No
by quote | By quote | Not checked | Not checked | Yes
plan not stated | Yes
plan not stated | No
by quote | | [CJ Affiliate](https://www.cj.com/support) | Not checked | By quote | Not checked | Not checked | Not checked | Not checked | No
by consultation | | [Rakuten Advertising](https://rakutenadvertising.com/affiliate/) | Not checked | By quote | Not checked | Not checked | Not checked | Not checked | No
by contact form |
Plan terms from each vendor's pricing page, checked Oct 12, 2026 (impact.com checked October 17, 2026); each tool name links to it. "Not checked" means we could not confirm it on the vendor's own pages. Rows follow entry price, lowest first, with tools priced by quote last; the numbers are that order, not a score. Lemon Squeezy and Trackdesk are not among these 19. Lemon Squeezy's affiliate tools come with its own checkout, as merchant of record, and it has no monthly fee, so on the map it would sit in the right half. Both are covered in [the catch in each tool](#catch).
## The catch in each tool, ours included The tools that cost $0 at the start mean different things by it. The catch in each one, from each vendor's pricing page, checked October 12, 2026: **[Affitor](https://affitor.com/pricing).** $0, with no subscription and no setup fee, until a program passes $10,000 in affiliate revenue (all-time, per program), then 3.5% of each affiliate sale. The 3.5% has no cap, so the fee grows with affiliate revenue. No importer: partners join again through your program page and get new links; past sales and unpaid commissions are not imported. Payouts go by bank transfer or Wise after a manual review, not PayPal. Stripe is the native integration; Paddle, Lemon Squeezy and other billing systems send sales through the API or SDK. No bulk export of partners, clicks or commissions yet: each weekly invoice downloads as a PDF, and partners can download the transactions on their payout page as a CSV. **[Endorsely](https://endorsely.com/pricing).** $0 on Starter, up to $1,000 a month in affiliate revenue, then $39 a month on Pro (up to $5,000 a month) and $99 a month up to $20,000. The cap is monthly: after $1,000 in monthly affiliate sales, you upgrade to keep tracking. Payouts are a PayPal bulk file you send yourself. **[PromoteKit](https://www.promotekit.com/pricing).** $0 for your first 3 referrals, then $29 a month on Pro, up to $10,000 a month; above that, contact sales. 3 referrals is a trial in practice. Stripe is required. Optional payouts to affiliates' bank accounts add a [fee on top of the payout total](https://www.promotekit.com/docs/payouts/stripe-payouts#fees): 5% if you fund them from a bank account (ACH), 8% by credit or debit card. **[Lemon Squeezy](https://www.lemonsqueezy.com/pricing).** No monthly fee. Base fee of 5% + 50¢ per sale, as merchant of record, plus 3% on each affiliate-referred sale, from the first one. [Its fees page](https://docs.lemonsqueezy.com/help/getting-started/fees) adds 0.5% on subscription payments and 1.5% each on international and PayPal payments. Tracks sales made through its own checkout. Affiliates pay 2% on their payouts. **[Rewardful](https://www.rewardful.com/pricing).** 14-day trial, then $49 a month on Starter (up to $7,500 a month) and $99 on Growth (up to $15,000). A trial, not a free plan: $49 a month whether or not affiliates sell. Optional Managed Payouts cost 3%. **[FirstPromoter](https://firstpromoter.com/pricing).** 14-day trial, no card, then $49 a month on Starter (up to $5,000 a month) and $99 on Business (up to $15,000). [Its own site](https://firstpromoter.com/solutions/free-affiliate-marketing-software) says "There is no permanent free plan." Starter allows up to 1,000 affiliates. **[Trackdesk](https://trackdesk.com/pricing).** 14-day trial, then $299 a month on Business and $499 on Enterprise. Some articles still describe a free plan. [Its help center](https://help.trackdesk.com/en/articles/11405479-limits-of-the-deprecated-free-plan) says the Free plan is no longer available to new users; existing users keep it. The commissions you pay affiliates come on top with every tool.
## Finding and paying affiliates A tracker records what affiliates sell; it does not find them. Three ways vendors help: a marketplace where affiliates browse programs, a network or matching service that recruits for you, and payouts that move the money to partners so you are not paying each one by hand. Hover any column for what sits behind the mark. | Tool / Platform | Marketplace
The vendor lists your program in a marketplace or directory affiliates browse. | Finds affiliates
A network, matching or outreach service that recruits partners. | Payouts
The vendor sends money to affiliates for you. | PayPal
Affiliates can be paid by PayPal through the tool. | Tax forms
Collects W-9/W-8 forms or files 1099s. | | --- | --- | --- | --- | --- | --- | | [Affitor](https://affitor.com/pricing) | Yes
every live program | Yes
team service | Yes
bank or Wise | No
bank or Wise | Yes
W-8BEN, W-8BEN-E or W-9 | | [PromoteKit](https://www.promotekit.com/pricing) | No
not in plan table | No
not in plan table | Partial
Pro, 5-8% fee | Yes
CSV mass payments | Partial
Pro, Stripe payouts | | [Endorsely](https://endorsely.com/pricing) | Yes
Starter, free | Yes
15 on Starter | No
PayPal file | Yes
bulk file | Not checked | | [Impact.com](https://impact.com/pricing/) | Partial
Essentials, $500/mo including $2,500 in partner payouts | Yes
AI recs, Starter | Partial
payouts above the tier billed à la carte | Yes
partner pays 2% | Yes
W-9/W-8, Starter | | [Refersion](https://www.refersion.com/pricing/) | Yes
free, all plans | Yes
AI affiliate discovery | Partial
1% fee, US | Yes
Launch | Yes
1099, US | | [Rewardful](https://www.rewardful.com/pricing) | No
not in plan table | No
not in plan table | Partial
3% fee | Yes
mass payouts | Partial
Managed Payouts, 3% | | [FirstPromoter](https://firstpromoter.com/pricing) | No
not in plan table | No
not in plan table | Partial
Enterprise 2+ | Yes
direct on Business+ | Yes
collects, no 1099 | | [Awin](https://www.awin.com/us/pricing) | Yes
Join Programmes | Yes
Partner Discovery | Partial
table: Accelerate+ | No
bank, Payoneer | Yes
W-9/W-8, 1099-NEC | | [Partnero](https://www.partnero.com/pricing) | Yes
PartneroList | Yes
AI Discovery | Partial
7% managed fee | Yes
Starter | Yes
W-9/W-8 collection | | [Tolt](https://tolt.com/pricing) | No
not in plan table | No
not in plan table | Partial
Growth, 2% fee | Yes
auto on Growth | Partial
Growth, $99 | | [Tapfiliate](https://tapfiliate.com/pricing/) | Not checked | No
invite tools | Partial
Scale, Trolley $49 | Yes
mass payment file | Partial
Scale, Trolley Tax | | [Post Affiliate Pro](https://www.postaffiliatepro.com/pricing/) | No
editorial directory | No
not listed | No
export file | Yes
mass pay file | No
not listed | | [Dub Partners](https://dub.co/pricing) | Partial
Enterprise | Partial
Enterprise | Partial
5% payout fee | Partial
14 countries | Yes
Business plan | | [Reditus](https://getreditus.com/pricing) | Partial
Scale Up, annual | Yes
Affiliate Finder | Partial
5%/2% payout fee | Yes
PayPal, Wise, IBAN | No
no W-9 | | [PartnerStack](https://www.partnerstack.com/pricing) | Yes
Launch | Yes
Marketplace, Launch | Yes
fee not stated | Yes
direct deposit, PayPal | Not checked | | [Partnerize](https://partnerize.com/pricing) | Yes
Brand Discovery, opt-in | Yes
Discover, AI | Yes
Pay, fee unstated | Yes
partner payment setting | Not checked | | [Everflow](https://www.everflow.io/pricing) | Yes
plan not stated | Yes
Marketplace discovery | Partial
Pay usage fee | Yes
integration | Partial
Pay add-on, US | | [CJ Affiliate](https://www.cj.com/support) | Yes
all advertisers | Yes
Partnership Discovery | Yes
fee not published | Not checked | Not checked | | [Rakuten Advertising](https://rakutenadvertising.com/affiliate/) | Yes
Find Advertisers | Yes
Partnership Discovery | Yes
fee not published | Yes
except Brazil, Japan | Yes
W-9, 1099-K |
For Affitor, finding affiliates is a team service. The Affitor team helps you recruit, onboard and train partners: [affitor.com/join](https://affitor.com/join).
## Tracking, setup and switching Most of the SaaS-first tools read sales from Stripe natively; the big networks were built for ecommerce and take SaaS sales through server-to-server calls. Past that, the differences are other billing systems, coupon codes, an API and an MCP server for agents, and whether you can bring partners and history from the tool you use today. Hover any column for what sits behind the mark. | Tool / Platform | Stripe
Reads sales from Stripe natively. | Other billing
Native support for Paddle, Chargebee, Recurly, Braintree or others. | Coupons
Credits a sale to an affiliate by coupon or promo code. | REST API
A public REST API on the entry plan. | MCP
An official MCP server for AI agents. | Importer
Imports affiliates, links or history from another affiliate tool. | | --- | --- | --- | --- | --- | --- | --- | | [Affitor](https://affitor.com/pricing) | Yes
native, OAuth | Partial
via API/SDK | No
not stated publicly | Yes
every program | Partial
beta | No
partners rejoin | | [PromoteKit](https://www.promotekit.com/pricing) | Yes
native, required | No
Stripe required | Yes
Free plan | Partial
Pro, $29 | No
none in docs | Not checked | | [Endorsely](https://endorsely.com/pricing) | Yes
native, Stripe App | Partial
manual API | Yes
Starter | Yes
docs, Starter | No
none in docs | Yes
assisted, any tool | | [Impact.com](https://impact.com/pricing/) | Yes
native, Stripe App | Yes
Chargebee, Recurly beta | Yes
Starter | Yes
tagged Starter | Partial
beta | Yes
any network, CSV+team | | [Refersion](https://www.refersion.com/pricing/) | Partial
Growth, subscriptions | Partial
Chargebee on Growth | Yes
Launch | Partial
Growth, $199 | Not checked | Partial
Growth, CSV affiliates | | [Rewardful](https://www.rewardful.com/pricing) | Yes
native, Premier Partner | Yes
Paddle Classic | Yes
all plans | Yes
all plans | No
docs-search MCP | Partial
CSV via support | | [FirstPromoter](https://firstpromoter.com/pricing) | Yes
native | Yes
+4 billing systems | Yes
all plans | Yes
all plans | Partial
beta | Yes
assisted, 24-48h | | [Awin](https://www.awin.com/us/pricing) | Partial
server-to-server | Partial
S2S, Conversion API | Yes
Voucher Attribution | Partial
Accelerate+ | Yes
reports: Accelerate+ | No
invite, new links | | [Partnero](https://www.partnero.com/pricing) | Yes
native app | Yes
Paddle, Chargebee | Yes
Starter | Yes
Starter | Yes
all plans | Yes
Rewardful, FirstPromoter, Tolt | | [Tolt](https://tolt.com/pricing) | Yes
native | Yes
Paddle, Chargebee | Yes
Basic | Yes
no plan gate | Yes
v1, live | Yes
Rewardful, claimed | | [Tapfiliate](https://tapfiliate.com/pricing/) | Yes
native, API key | Yes
MoonClerk, PayPal, Memberful | Yes
Launch | Yes
Launch, all plans | Partial
beta, all plans | Partial
CSV affiliates | | [Post Affiliate Pro](https://www.postaffiliatepro.com/pricing/) | Yes
native, webhook | Yes
Braintree, PayPal | Partial
Pro, $139 | Yes
API v3 | Yes
OAuth, Oct 2026 | Yes
assisted + CSV | | [Dub Partners](https://dub.co/pricing) | Yes
native | Partial
Shopify; else API | Yes
Stripe promo codes | Yes
Business | Yes
Business | Yes
Rewardful, Tolt +4 | | [Reditus](https://getreditus.com/pricing) | Yes
native | Partial
via Payments API | Yes
Stripe | Yes
all plans | Not checked | Yes
White-glove, any tool | | [PartnerStack](https://www.partnerstack.com/pricing) | Yes
webhook | Yes
Chargebee, Recurly, Paddle | Not checked | Yes
plan not stated | Yes
Launch | Partial
CSV | | [Partnerize](https://partnerize.com/pricing) | Partial
no listing; S2S | Partial
no listing; S2S | Yes
voucher codes | Yes
public docs | Not checked | Yes
team-led migration | | [Everflow](https://www.everflow.io/pricing) | Yes
built-in | Yes
ReCharge | Yes
built-in | Yes
plan not stated | Yes
read access | Yes
Tune, Cake, HitPath | | [CJ Affiliate](https://www.cj.com/support) | Partial
server-to-server | Partial
S2S, New Orders API | Yes
Clickless Tracking | Partial
GraphQL, not REST | No
none in docs | Yes
assisted migration | | [Rakuten Advertising](https://rakutenadvertising.com/affiliate/) | Not checked | Not checked | Yes
linkless codes | Not checked | No
none in dev portal | Yes
assisted migration |
## Five ways affiliate software is priced Affiliate tools charge in five ways, and the price that matters is the one you pay at your stage. All prices checked Oct 12, 2026; each tool name links to its pricing page. **Flat subscription with a cap.** [PromoteKit](https://www.promotekit.com/pricing) ($29/mo on Pro, up to $10,000/mo in affiliate revenue), [Rewardful](https://www.rewardful.com/pricing) ($49/mo, $7,500/mo on Starter), [FirstPromoter](https://firstpromoter.com/pricing) ($49/mo, $5,000/mo on Starter), [Tolt](https://tolt.com/pricing) ($69/mo, $10,000/mo on Basic) and [Endorsely](https://endorsely.com/pricing) ($0 up to $1,000/mo, then $39/mo up to $5,000/mo). [Tapfiliate](https://tapfiliate.com/pricing/) caps conversions (500/mo on Launch) and [Post Affiliate Pro](https://www.postaffiliatepro.com/pricing/) tracking requests (10,000/mo on Starter). The bill is the same each month, and crossing a cap moves you to the next plan. **Subscription plus a percentage.** [Awin](https://www.awin.com/us/pricing) ($49/mo plus 3.5% per transaction on Access), [Refersion](https://www.refersion.com/pricing/) ($39/mo plus 3% of affiliate sales on Launch), [Dub Partners](https://dub.co/pricing) ($90/mo plus 5% of payouts funded by ACH) and [Reditus](https://getreditus.com/pricing) ($149/mo plus 5% by card or 2% by invoice on the commissions you pay). Tolt adds 2% on automatic payouts. **A minimum or a percentage, whichever is greater.** [Impact.com](https://impact.com/pricing/) Starter bills $30/mo or 2.5% of partner-driven revenue, whichever is greater ([billing help](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/finance/finance-for-starter-edition-accounts/impactcom-starter-edition-billing-explained)); Essentials is $500/mo including $2,500 in partner payouts, with payouts above that billed à la carte. **A percentage after a threshold.** [Affitor](https://affitor.com/pricing) costs $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales, with no subscription and no cap. **A quote.** [PartnerStack](https://www.partnerstack.com/pricing), [Partnerize](https://partnerize.com/pricing), [Everflow](https://www.everflow.io/pricing), [CJ Affiliate](https://www.cj.com/support) and [Rakuten Advertising](https://rakutenadvertising.com/affiliate/) price after a call or demo. Which one costs less depends on how much your affiliates sell and for how long, which is why the tables above show scenarios with their assumptions instead of a single number.
## So which affiliate software should you actually buy? Nearly everything here tracks a referral and pays a commission, so tracking is not what separates them anymore. What separates them is when you start paying, whether a cap moves you up a plan as affiliates sell, and who brings the affiliates. Rewardful, FirstPromoter and Tolt are solid flat-fee trackers if you already have partners and want a known monthly bill. PartnerStack, Reditus and Partnero bring a marketplace or network, on a quote or from $49 to $99 a month billed annually, and Endorsely lists free programs in its network while affiliate revenue stays under $1,000 a month. Awin, CJ and Rakuten Advertising are the big networks: huge publisher bases built around ecommerce, with a fee on every transaction or a quote; Awin and CJ have no native Stripe connection. Impact.com, Partnerize and Everflow are enterprise platforms on a contract (12 months at impact.com); impact.com's self-serve Starter, at $30/mo or 2.5% of partner-driven revenue, whichever is greater, needs an ecommerce integration. Affitor charges nothing until a program has made $10,000 through affiliates, lists every program where affiliates look, and then takes 3.5% of affiliate-driven sales with no cap. Prices as listed on each vendor's pricing page on Oct 12, 2026, linked in the [cost table](#prices). Below $1,000 in MRR, affiliate revenue is small and uncertain, so pick a tool that costs $0 while you find out whether affiliates work for you. **Affitor** if you'd rather not watch a monthly cap: there is no platform fee on the first $10,000 in affiliate revenue, however long it takes, and every feature is included from day one. **Endorsely** if you want a fixed plan later: free under $1,000 a month, then $39. **PromoteKit** if you sell through Stripe and want to try a few referrals before paying $29 a month. **Lemon Squeezy** if it already runs your checkout, since its affiliate tools need no extra product.
## Frequently Asked Questions What SaaS founders ask when they shortlist and price affiliate software: which tool fits, what it costs before the first sale, which tools have no monthly fee, what a second program costs, and how hard it is to switch. Want to see it running? [Launch your program](https://affitor.com/welcome): $0 until it has made $10,000 through affiliates. ### What is the best affiliate software for SaaS? It depends on how much affiliate revenue you have today. Affitor costs nothing until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales. Endorsely is free while affiliate revenue stays under $1,000 a month. PromoteKit ($29/month) and Rewardful ($49/month) offer flat plans on Stripe, FirstPromoter covers billing beyond Stripe, and Reditus and PartnerStack help you find partners. Prices checked October 12, 2026. ### How much does affiliate software cost in 2026? Entry prices on October 12, 2026: Affitor $0 (then 3.5% of affiliate-driven sales after the first $10,000 per program), Endorsely $0 up to $1,000 a month in affiliate revenue (then $39/month), PromoteKit $0 for 3 referrals (then $29/month), Rewardful and FirstPromoter $49/month, Partnero $59/month, Tolt $69/month, Tapfiliate and Post Affiliate Pro $89/month, Dub Partners $90/month plus a 5% payout fee, and Reditus $149/month. Impact.com starts at $30/mo or 2.5% of partner-driven revenue, whichever is greater (Starter), Refersion at $39/month plus 3% of affiliate sales, Awin at $49/month plus 3.5% per transaction, and PartnerStack, Partnerize, Everflow, CJ Affiliate and Rakuten Advertising price by quote. ### What does affiliate software cost before the program makes money? With no affiliate revenue, one program pays these fixed fees after 6, 12 and 18 months, at monthly prices checked October 12, 2026: Affitor, PromoteKit and Endorsely $0; Awin $245, $539 and $833; Rewardful and FirstPromoter $294, $588 and $882; Partnero $354, $708 and $1,062; Tolt $414, $828 and $1,242; Tapfiliate and Post Affiliate Pro $534, $1,068 and $1,602; Dub Partners $540, $1,080 and $1,620; Reditus $894, $1,788 and $2,682; and impact.com Essentials $3,000, $6,000 and $9,000. PromoteKit's $0 covers 1 campaign and 3 referrals, and Endorsely's covers up to $1,000 a month in affiliate revenue. ### Which affiliate software is free until the program makes money? As of October 12, 2026: Affitor charges $0 until a program reaches $10,000 in affiliate revenue, then 3.5% of each affiliate sale. Endorsely is free while affiliate revenue stays under $1,000 a month, then $39 a month. PromoteKit is free for your first 3 referrals, then $29 a month. Others offer trials, not free plans: 14 days at Rewardful, FirstPromoter, Tolt, Dub Partners, Reditus and Trackdesk, and 30 days at Partnero. ### Is there affiliate software with no monthly fee that charges per sale instead? Yes. As of October 12, 2026, Affitor has no subscription and charges 3.5% of each affiliate sale once a program passes $10,000 in affiliate revenue. Lemon Squeezy also has no monthly fee: its base fee is 5% + 50¢ per sale as merchant of record, subscription payments add 0.5%, international and PayPal payments add 1.5% each, and each affiliate-referred sale adds 3%. It tracks sales made through its own checkout. ### How much more does a second affiliate program cost? On Affitor, nothing: there are no plan tiers, and each program gets its own first $10,000 at $0 before the 3.5% applies. Elsewhere, as of October 13, 2026: PromoteKit moves from its free plan (1 campaign) to Pro at $29/month, Rewardful from Starter (1 campaign) to Growth at $99/month, FirstPromoter needs Business at $99/month for a second website, Partnero moves from Starter (1 program) to Partner at $199/month, Tapfiliate from Launch (1 program) to Scale at $179/month, and Post Affiliate Pro from Starter (1 campaign) to Pro at $139/month. Tolt's Basic plan holds 2 programs, and Awin charges its $49 monthly platform fee per program, each with its own application. ### Which affiliate tools take a percentage of sales or payouts? As of October 12, 2026: Awin charges 3.5% per transaction on its Access plan, Refersion 3% of affiliate sales on Launch, Dub Partners 5% of payouts funded by ACH (8% by card), Reditus 5% by card or 2% by invoice on the commissions you pay, and Tolt 2% on automatic payouts. Impact.com Starter bills $30/mo or 2.5% of partner-driven revenue, whichever is greater. Rewardful (3%), Partnero (7%) and PromoteKit (5% if funded by bank, 8% by card) charge a fee when they run payouts for you. Affitor charges 3.5% of affiliate-driven sales after a program's first $10,000, with no subscription. ### Is a percentage fee better than a flat subscription? It depends on how much your affiliates sell and for how long. A flat plan bills the same amount every month from the first day, and most plans cap the affiliate revenue they cover, so the price steps up as affiliates sell more. A percentage costs nothing while affiliates sell nothing and grows with the sales they bring. The scenario tables on this page show both, with every assumption stated. ### What does Affitor's 3.5% include? Every feature, on every program: Stripe sales read through OAuth with no code, other billing systems through the API or SDK, a listing on the Affitor marketplace where affiliates browse programs, payouts to partners by bank transfer or Wise after a review, and help from the Affitor team to recruit, onboard and train partners. ### What happens when a program passes $10,000 in affiliate revenue? The sale that takes a program past $10,000 still carries no Affitor fee. From the next sale on, each affiliate sale costs 3.5% of the sale. Nothing else changes: same product, same features, no plan to upgrade to. The $10,000 counts all-time and per program, so it never resets, and a second program gets its own $10,000. ### Can I switch affiliate software without breaking my partners' links? Reditus offers white-glove migration from any affiliate platform. Dub Partners imports partners from Rewardful, PartnerStack, FirstPromoter, Tolt, Tapfiliate and Lemon Squeezy, and Partnero imports from Rewardful, FirstPromoter and Tolt. Affitor has no importer today: partners join again through your program page and get new links, so most teams run both tools side by side for a while. ### Which affiliate software works with Paddle or Chargebee? FirstPromoter supports Stripe, Paddle, Chargebee, Recurly and Braintree. Partnero lists Stripe, Paddle and Chargebee, Reditus connects Stripe natively and takes Paddle and Chargebee through its Payments API, Tolt works with Stripe, Paddle and Chargebee, and Rewardful with Stripe and Paddle Classic. PromoteKit requires Stripe. Affitor reads Stripe sales with no code and takes other billing systems through its API or SDK. ### Launch your affiliate program Connect Stripe and run a test sale. Pay nothing until your program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales. [Read the docs](/docs) · [Create your program](https://affitor.com/welcome)
## More comparisons Every head-to-head and alternatives page is on the [comparison hub](/blog/compare). Head-to-heads: [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter), [Tolt vs Rewardful](/blog/tolt-vs-rewardful), [PartnerStack vs Rewardful](/blog/partnerstack-vs-rewardful) and [Rewardful vs Dub](/blog/rewardful-vs-dub). Alternatives: [Rewardful](/blog/rewardful-alternatives), [FirstPromoter](/blog/firstpromoter-alternatives), [Tolt](/blog/tolt-alternatives) and [PartnerStack](/blog/partnerstack-alternatives).
--- id: "blog/compare" type: "blog" url: "https://affitor.com/blog/compare" updated: "2026-10-13" --- # Affiliate Software Comparisons: Every Head-to-Head and Alternatives Page (Updated Monthly) > Every affiliate software comparison on the Affitor blog in one table: head-to-heads like Rewardful vs Dub, alternatives pages and the 19-tool roundup, with one line on who each tool suits. Prices checked October 12, 2026; updated monthly. Pick the pair you are weighing. Each row links the full comparison and says in one line who each tool suits, with the price and the limit that decide it. Prices in the table were checked on Oct 12, 2026 against each vendor's pricing page, which the tool name links to. We update this hub monthly. Each linked page shows its own check date at the top; where a page is older than this table, the table is the newer check. We make Affitor, which appears in these comparisons: $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales. ## All comparisons | Comparison | Who each tool suits | | --- | --- | | [Rewardful vs Dub](/blog/rewardful-vs-dub) | [Rewardful](https://www.rewardful.com/pricing): a Stripe or Paddle Classic SaaS that wants a flat plan, $49/mo with a 0% transaction fee, up to $7,500/mo in affiliate revenue. [Dub Partners](https://dub.co/pricing): teams that want payouts and tax forms on the entry plan, $90/mo plus a 5% payout fee, up to $2,500/mo in payouts. | | [FirstPromoter vs Dub](/blog/firstpromoter-vs-dub) | [FirstPromoter](https://firstpromoter.com/pricing): billing beyond Stripe (Paddle, Chargebee, Recurly, Braintree), $49/mo for up to $5,000/mo in affiliate revenue. [Dub Partners](https://dub.co/pricing): payouts and tax forms on the entry plan, $90/mo plus a 5% payout fee. | | [Dub vs PartnerStack](/blog/dub-vs-partnerstack) | [Dub Partners](https://dub.co/pricing): a published self-serve price from $90/mo, cancel any time. [PartnerStack](https://www.partnerstack.com/pricing): B2B programs that want marketplace access on the entry plan; quote after a demo, on 1-year renewing terms. | | [Dub vs Tolt](/blog/dub-vs-tolt) | [Tolt](https://tolt.com/pricing): unlimited affiliates on Stripe, Paddle or Chargebee, $69/mo for up to $10,000/mo in affiliate revenue with manual payouts; automatic payouts start on Growth at $99/mo, plus 2%. [Dub Partners](https://dub.co/pricing): payouts and tax forms on the entry plan, $90/mo plus a 5% payout fee. | | [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter) | Both start at $49/mo. [Rewardful](https://www.rewardful.com/pricing): up to $7,500/mo in affiliate revenue on Starter and unlimited affiliates. [FirstPromoter](https://firstpromoter.com/pricing): up to $5,000/mo on Starter, unlimited team members and five billing systems. | | [Tolt vs Rewardful](/blog/tolt-vs-rewardful) | [Rewardful](https://www.rewardful.com/pricing): $49/mo with a 0% transaction fee, up to $7,500/mo in affiliate revenue. [Tolt](https://tolt.com/pricing): $69/mo for up to $10,000/mo, and automatic payouts on Growth at $99/mo with a 2% fee. | | [PartnerStack vs Rewardful](/blog/partnerstack-vs-rewardful) | [Rewardful](https://www.rewardful.com/pricing): a self-serve Stripe program from $49/mo. [PartnerStack](https://www.partnerstack.com/pricing): B2B programs beyond affiliates (resellers, co-sell partners), with its marketplace on Launch; quote after a demo. | | [Rewardful alternatives](/blog/rewardful-alternatives) | For SaaS outgrowing [Rewardful](https://www.rewardful.com/pricing) Starter ($49/mo, up to $7,500/mo in affiliate revenue): Affitor, FirstPromoter, Tolt, Dub Partners and PartnerStack. | | [FirstPromoter alternatives](/blog/firstpromoter-alternatives) | For SaaS past [FirstPromoter](https://firstpromoter.com/pricing) Starter ($49/mo, up to $5,000/mo in affiliate revenue): Affitor, Rewardful, Tolt, Dub Partners and PartnerStack. | | [Tolt alternatives](/blog/tolt-alternatives) | For SaaS weighing [Tolt](https://tolt.com/pricing) ($69/mo on Basic with manual payouts; automatic payouts from Growth at $99/mo, plus 2%): Affitor, Rewardful, FirstPromoter, Dub Partners and PartnerStack. | | [PartnerStack alternatives](/blog/partnerstack-alternatives) | For teams that want a published price instead of [PartnerStack](https://www.partnerstack.com/pricing)'s quote after a demo: Affitor, Rewardful, FirstPromoter, Tolt and Dub Partners. | | [Best affiliate software for SaaS: pricing and fees](/blog/best-affiliate-software-saas) | All 19 tools on what you pay before the first sale and after a program earns, revenue caps, program limits, who brings affiliates, payouts and tracking, plus the tools with no monthly fee and the cap on each: [PromoteKit](https://www.promotekit.com/pricing) covers your first 3 referrals, [Endorsely](https://endorsely.com/pricing) stays $0 up to $1,000/mo in affiliate revenue, and [Affitor](https://affitor.com/pricing) is $0 until $10,000 per program, then 3.5%. | | [Stripe affiliate tracking tools](/blog/stripe-affiliate-program) | Eight tools compared on what they read from Stripe, price, fees and revenue caps. | ## How we compare Every price, fee and cap comes from the vendor's own pricing page or docs, with the date we checked it. Where a vendor does not publish something, the page says so instead of guessing. Caps are named for what they count: affiliate revenue for Rewardful, FirstPromoter and Tolt, partner payouts for Dub Partners. To start a program on Affitor, [create your program](https://affitor.com/welcome), or read the [docs](/docs) first. --- id: "blog/dub-vs-partnerstack" type: "blog" url: "https://affitor.com/blog/dub-vs-partnerstack" updated: "2026-10-17" --- # Dub vs PartnerStack: Pricing, Contracts and Features Compared (Checked Oct 2026) > Dub Partners publishes its prices, from $90 a month plus a 5% payout fee, and you can cancel any time. PartnerStack prices after a demo, on one-year renewing terms, and includes its partner marketplace on the entry plan. Checked on both vendors' pages on October 12, 2026. Pick [Dub Partners](https://dub.co/pricing) if you want to start self-serve: $90 a month on Business plus 5% of the payouts you fund by ACH, a native Stripe integration and no minimum term. Pick [PartnerStack](https://www.partnerstack.com/pricing) if you run a B2B partner program beyond affiliates and want its partner marketplace on the entry plan; the price comes after a demo, on one-year renewing terms. Both checked on October 12, 2026. | Tool / Platform | Entry price | Fee on top | Revenue cap
The most affiliate revenue, payouts or ARR the entry plan covers before you move up. | Minimum term
Shortest commitment on the entry plan, from the vendor's pricing page or terms. | Billing | | --- | --- | --- | --- | --- | --- | | [Dub Partners](https://dub.co/pricing)
Business, 14-day trial | $90/mo | 5% of payouts funded by ACH
8% if funded by card; 3% and 6% on Enterprise | $2,500/mo in payouts
500 partners on Business | None | Stripe, Shopify; others through the API | | [PartnerStack](https://www.partnerstack.com/pricing)
Entry plan | Quote after demo | Not published | Not published | 1-year renewing terms | Stripe by webhook; Chargebee, Recurly, Paddle | | [Affitor](https://affitor.com/pricing)
until a program has made $10,000 through affiliates | $0 | 3.5% of affiliate-driven sales
after the first $10,000 per program | None | None | Stripe with no code; other billing through the API or SDK |
Entry plans as listed on each vendor's pricing page on Oct 12, 2026; the tool name links to it. PartnerStack does not publish prices, fees or caps, so those cells say so. We make Affitor; it sits in the last row of each table for reference, and the section Where Affitor fits covers it. ## Where Dub Partners is stronger - **A published price.** Business is $90 a month and Advanced $300, with a 14-day trial and 10% off yearly. PartnerStack confirms the plan and price during a demo, based on program size, features and support. - **No minimum term.** Dub's pricing page says you can cancel your subscription at any time. PartnerStack's [SaaS agreement](https://www.partnerstack.com/legal/saas-agreement) renews automatically for one-year terms. - **Stripe natively.** Dub has a native Stripe integration and credits sales to Stripe promotion codes. PartnerStack listens to Stripe through a webhook integration. - **Importers.** Dub imports partners from Rewardful, PartnerStack, FirstPromoter, Tolt, Tapfiliate and Lemon Squeezy. PartnerStack's own importer creates or updates records from a CSV file. - **Tax forms on Business.** Dub says it handles W-9, W-8 and 1099 forms. We could not check PartnerStack's tax-form handling. - **Links, analytics and payouts in one product**, since Dub Partners runs on Dub's link platform. The limits to know: Business holds 500 partners and 10 users and covers $2,500 a month in partner payouts, and Dub charges 5% on payouts you fund by ACH and 8% by card (3% and 6% on Enterprise). Its marketplace listing and partner discovery are on Enterprise. ## Where PartnerStack is stronger - **A marketplace on the entry plan.** Launch includes PartnerStack Marketplace access, where active B2B partners can discover your program. Dub's marketplace listing and partner discovery are on Enterprise. - **Unlimited partners and internal users.** Dub Business holds 500 partners and 10 users. - **Built for B2B partners beyond affiliates.** On Launch you pick affiliate link tracking or lead and deal registration, with onboarding and training tools, CRM integrations and an MCP connector. Growth adds a learning management system and MDF management. - **More billing systems.** PartnerStack integrates with Chargebee, Recurly and Paddle next to Stripe. Dub connects Stripe and Shopify and takes other billing through its API. - **One monthly invoice for payouts.** PartnerStack consolidates approved commissions into a single monthly invoice and pays partners for you; they withdraw by direct deposit, PayPal or Stripe. The fee is not stated. The limits to know: the price comes after a demo, the agreement renews for one-year terms, and its own FAQ says most teams are up and running in weeks, depending on program complexity and integrations. ## Partners and payouts How many partners and teammates the entry plan holds, whether the vendor helps you find partners, and who sends the money. Hover a column for what it checks. | Tool / Platform | Partners
No limit on affiliates on the entry plan. | Seats
No limit on team members on the entry plan. | Marketplace
The vendor lists your program in a marketplace or directory affiliates browse. | Finds affiliates
A network, matching or outreach service that recruits partners. | Payouts
The vendor sends money to affiliates for you. | PayPal
Affiliates can be paid by PayPal through the tool. | Tax forms
Collects W-9/W-8 forms or files 1099s. | | --- | --- | --- | --- | --- | --- | --- | --- | | [Dub Partners](https://dub.co/pricing) | Partial
500 on Business | Partial
10 on Business | Partial
Enterprise | Partial
Enterprise | Partial
5% payout fee | Partial
14 countries | Yes
Business plan | | [PartnerStack](https://www.partnerstack.com/pricing) | Yes
all plans | Yes
all plans | Yes
Launch | Yes
Marketplace, Launch | Yes
fee not stated | Yes
direct deposit, PayPal | Not checked | | [Affitor](https://affitor.com/pricing) | Yes
unlimited | Yes
unlimited | Yes
every live program | Yes
team service | Yes
bank or Wise | No
bank or Wise | Yes
W-8BEN, W-8BEN-E or W-9 |
## Tracking and setup Both read sales from Stripe, Dub natively and PartnerStack through a webhook. The differences are coupon tracking, other billing systems and importing. Hover a column for what it checks. | Tool / Platform | Stripe
Reads sales from Stripe natively. | Other billing
Native support for Paddle, Chargebee, Recurly, Braintree or others. | Coupons
Credits a sale to an affiliate by coupon or promo code. | REST API
A public REST API on the entry plan. | MCP
An official MCP server for AI agents. | Importer
Imports affiliates, links or history from another affiliate tool. | | --- | --- | --- | --- | --- | --- | --- | | [Dub Partners](https://dub.co/pricing) | Yes
native | Partial
Shopify; else API | Yes
Stripe promo codes | Yes
Business | Yes
Business | Yes
Rewardful, Tolt +4 | | [PartnerStack](https://www.partnerstack.com/pricing) | Yes
webhook | Yes
Chargebee, Recurly, Paddle | Not checked | Yes
plan not stated | Yes
Launch | Partial
CSV | | [Affitor](https://affitor.com/pricing) | Yes
native, OAuth | Partial
via API/SDK | No
not stated publicly | Yes
every program | Partial
beta | No
partners rejoin |
## Which one should you pick? Choose Dub Partners when you want to launch on a published price, keep the option to leave any month, and have Dub send payouts and handle tax forms; budget $90 a month plus 5% of payouts funded by ACH, and $300 a month on Advanced once payouts pass $2,500 a month. Choose PartnerStack when the partners you need are B2B affiliates, resellers and co-sell partners, you want them to find you in a marketplace from the entry plan, and a demo, a quote and a one-year term fit how you buy software. ## Where Affitor fits Like PartnerStack, Affitor lists your program where affiliates look; like Dub, it publishes its price and has no minimum term. Our marketplace is young and much smaller than PartnerStack's network. Affitor, which we make, has no subscription: $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales, with no cap on affiliate revenue and no limit on partners or seats. Every program is listed on the [Affitor marketplace](https://affitor.com/marketplace), and the Affitor team helps you recruit, onboard and train partners ([affitor.com/join](https://affitor.com/join)). It reads Stripe sales with no code, takes other billing systems through its API or SDK, and lets you run a test sale before launch. The trade-offs are in the tables above: there is no importer, so partners join again through your program page and get new links; payouts go out by bank transfer or Wise after a review, not PayPal; and Affitor does not track coupon codes. Affitor collects a tax form from each partner (W-8BEN, W-8BEN-E or W-9) before the first payout. Details are on the [pricing page](https://affitor.com/pricing). ## FAQ ### How much does PartnerStack cost compared with Dub? PartnerStack does not publish prices: its Launch, Growth and Enterprise plans are priced after a demo, based on program size, features and support, on one-year renewing terms. Dub Partners publishes its prices: Business is $90 a month with up to $2,500 a month in partner payouts and Advanced is $300 with up to $15,000, plus 5% on payouts funded by ACH or 8% by card. Checked October 12, 2026. ### Which one helps you find partners? PartnerStack includes access to the PartnerStack Marketplace on its Launch plan, where active B2B partners can discover your program. Dub Partners lists your program in its marketplace and helps you discover partners on Enterprise, its custom annual plan (as of October 12, 2026). ### Can I move from PartnerStack to Dub? Yes. Dub Partners imports partners from Rewardful, PartnerStack, FirstPromoter, Tolt, Tapfiliate and Lemon Squeezy. PartnerStack's own importer creates or updates records from a CSV file. ### Do Dub and PartnerStack work with Stripe? Both do. Dub Partners has a native Stripe integration and can credit sales to Stripe promotion codes. PartnerStack connects to Stripe through a webhook integration and also integrates with Chargebee, Recurly and Paddle (as of October 12, 2026). ### Is there an option with no monthly fee? Affitor, which we make, has no subscription: it costs nothing until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales, with no cap on affiliate revenue. It lists every program on its marketplace and reads Stripe sales with no code. It has no importer, so partners get new links, and it pays partners by bank transfer or Wise rather than PayPal (as of October 12, 2026). ## More comparisons Every head-to-head and alternatives page is on the [comparison hub](/blog/compare). Related: [PartnerStack vs Rewardful](/blog/partnerstack-vs-rewardful), [PartnerStack alternatives](/blog/partnerstack-alternatives), [Rewardful vs Dub](/blog/rewardful-vs-dub), [Dub vs Tolt](/blog/dub-vs-tolt) and the [19-tool comparison of affiliate software and pricing](/blog/best-affiliate-software-saas). --- id: "blog/dub-vs-tolt" type: "blog" url: "https://affitor.com/blog/dub-vs-tolt" updated: "2026-10-17" --- # Dub vs Tolt: Pricing, Payout Fees and Features Compared (Checked Oct 2026) > Tolt starts at $69 a month for up to $10,000 a month in affiliate revenue, with unlimited affiliates and manual payouts; automatic payouts start on Growth at $99 a month, plus a 2% fee. Dub Partners starts at $90 a month plus a 5% payout fee, and sends payouts and handles tax forms on that plan. Checked on both pricing pages on October 12, 2026. Pick [Tolt](https://tolt.com/pricing) if you bill through Stripe, Paddle or Chargebee and want unlimited affiliates and a lower payout fee: Basic is $69 a month, and automatic payouts start on Growth at $99 with a 2% fee. Pick [Dub Partners](https://dub.co/pricing) if you want payouts and tax forms on the entry plan, links and analytics in the same product, and built-in importers, at $90 a month plus 5% of the payouts you fund by ACH. Both checked on October 12, 2026. | Tool / Platform | Entry price | Fee on top | Revenue cap
The most affiliate revenue, payouts or ARR the entry plan covers before you move up. | Minimum term
Shortest commitment on the entry plan, from the vendor's pricing page or terms. | Billing | | --- | --- | --- | --- | --- | --- | | [Dub Partners](https://dub.co/pricing)
Business, 14-day trial | $90/mo | 5% of payouts funded by ACH
8% if funded by card; 3% and 6% on Enterprise | $2,500/mo in payouts
500 partners on Business | None | Stripe, Shopify; others through the API | | [Tolt](https://tolt.com/pricing)
Basic, 14-day trial, no card | $69/mo | None on Basic
manual payouts; automatic payouts start on Growth at $99/mo, plus 2% | $10,000/mo
affiliate revenue on Basic | Not published | Stripe, Paddle, Chargebee | | [Affitor](https://affitor.com/pricing)
until a program has made $10,000 through affiliates | $0 | 3.5% of affiliate-driven sales
after the first $10,000 per program | None | None | Stripe with no code; other billing through the API or SDK |
Entry plans as listed on each vendor's pricing page on Oct 12, 2026; the tool name links to it. Tolt's cap counts affiliate revenue and Dub's counts the payouts you send partners, so the two caps measure different things. We make Affitor; it sits in the last row of each table for reference, and the section Where Affitor fits covers it. ## Where Dub Partners is stronger - **Payouts and tax forms on the entry plan.** Business sends partner payouts for you, and Dub says it handles W-9, W-8 and 1099 forms. On Tolt, automatic payouts and tax forms start on Growth at $99; Basic payouts are manual. - **More seats.** Business includes 10 users, against 3 team members on Tolt Basic. - **Importers.** Dub imports partners from Rewardful, PartnerStack, FirstPromoter, Tolt, Tapfiliate and Lemon Squeezy. Tolt's page for Rewardful users describes a customer that moved its program to Tolt in one click. - **No minimum term stated.** Dub's pricing page says you can cancel at any time; Tolt's pricing page does not state a minimum term. - **Links, analytics and payouts in one product**, since Dub Partners runs on Dub's link platform. - **A marketplace listing and partner discovery**, on Enterprise. Tolt lists neither in its plan table. The limits to know: Business covers $2,500 a month in partner payouts and holds 500 partners, and Dub charges 5% on payouts you fund by ACH and 8% by card (3% and 6% on Enterprise). When you hit your plan's payout limit you can't send more payouts until the next billing period; Advanced is $300 a month with up to $15,000. ## Where Tolt is stronger - **Lower entry price.** Basic is $69 a month for up to $10,000 a month in affiliate revenue, against $90 a month for Dub's Business plan. Growth is $99 for up to $20,000 and Pro $199 for up to $50,000. - **Lower payout fee.** Automatic payouts carry a 2% processing fee, against 5% by ACH or 8% by card on Dub. - **Unlimited affiliates and referrals on every plan.** Dub Business holds 500 partners. - **Paddle and Chargebee natively**, next to Stripe. Dub connects Stripe and Shopify and takes other billing through its API. - **Payout methods on Growth.** PayPal, Wise, local bank, crypto and wire, plus W-9/W-8 collection and 1099 filing. - **More than one program.** Basic includes 2 programs, Growth 5 and Pro unlimited. - **A trial with no card**, 14 days, and a 30-day refund. The limits to know: Basic is manual payouts, with 3 team members, and the pricing page does not state a minimum term. ## Partners and payouts How many partners and teammates the entry plan holds, whether the vendor helps you find partners, and who sends the money. Hover a column for what it checks. | Tool / Platform | Partners
No limit on affiliates on the entry plan. | Seats
No limit on team members on the entry plan. | Marketplace
The vendor lists your program in a marketplace or directory affiliates browse. | Finds affiliates
A network, matching or outreach service that recruits partners. | Payouts
The vendor sends money to affiliates for you. | PayPal
Affiliates can be paid by PayPal through the tool. | Tax forms
Collects W-9/W-8 forms or files 1099s. | | --- | --- | --- | --- | --- | --- | --- | --- | | [Dub Partners](https://dub.co/pricing) | Partial
500 on Business | Partial
10 on Business | Partial
Enterprise | Partial
Enterprise | Partial
5% payout fee | Partial
14 countries | Yes
Business plan | | [Tolt](https://tolt.com/pricing) | Yes
all plans | Partial
3 on Basic | No
not in plan table | No
not in plan table | Partial
Growth, 2% fee | Yes
auto on Growth | Partial
Growth, $99 | | [Affitor](https://affitor.com/pricing) | Yes
unlimited | Yes
unlimited | Yes
every live program | Yes
team service | Yes
bank or Wise | No
bank or Wise | Yes
W-8BEN, W-8BEN-E or W-9 |
## Tracking and setup Both read sales from Stripe natively, credit sales to coupon codes, and offer a REST API and an MCP server. The differences are other billing systems and importing. Hover a column for what it checks. | Tool / Platform | Stripe
Reads sales from Stripe natively. | Other billing
Native support for Paddle, Chargebee, Recurly, Braintree or others. | Coupons
Credits a sale to an affiliate by coupon or promo code. | REST API
A public REST API on the entry plan. | MCP
An official MCP server for AI agents. | Importer
Imports affiliates, links or history from another affiliate tool. | | --- | --- | --- | --- | --- | --- | --- | | [Dub Partners](https://dub.co/pricing) | Yes
native | Partial
Shopify; else API | Yes
Stripe promo codes | Yes
Business | Yes
Business | Yes
Rewardful, Tolt +4 | | [Tolt](https://tolt.com/pricing) | Yes
native | Yes
Paddle, Chargebee | Yes
Basic | Yes
no plan gate | Yes
v1, live | Yes
Rewardful, claimed | | [Affitor](https://affitor.com/pricing) | Yes
native, OAuth | Partial
via API/SDK | No
not stated publicly | Yes
every program | Partial
beta | No
partners rejoin |
## Which one should you pick? Choose Tolt when you want unlimited affiliates, Paddle or Chargebee natively, and the lower payout fee: $69 a month for up to $10,000 a month in affiliate revenue, then $99 on Growth for automatic payouts and tax forms. Choose Dub Partners when you want payouts and tax forms from the entry plan, more teammates, or you already use Dub for links; budget $90 a month plus 5% of payouts funded by ACH, and $300 a month on Advanced once payouts pass $2,500 a month. Both offer a 14-day trial. ## Where Affitor fits If you would rather not pay a monthly plan before affiliates sell, there is a third shape. Affitor, which we make, has no subscription: $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales, with no cap on affiliate revenue and no limit on partners or seats. Every program is listed on the [Affitor marketplace](https://affitor.com/marketplace), and the Affitor team helps you recruit, onboard and train partners ([affitor.com/join](https://affitor.com/join)). It reads Stripe sales with no code, takes other billing systems through its API or SDK, and lets you run a test sale before launch. The trade-offs are in the tables above: there is no importer, so partners join again through your program page and get new links; payouts go out by bank transfer or Wise after a review, not PayPal; and Affitor does not track coupon codes. Affitor collects a tax form from each partner (W-8BEN, W-8BEN-E or W-9) before the first payout. Details are on the [pricing page](https://affitor.com/pricing). ## FAQ ### How do Tolt and Dub prices compare? On the entry plans, Tolt costs less. Tolt Basic is $69 a month for up to $10,000 a month in affiliate revenue, with manual payouts. Dub Partners Business is $90 a month for up to $2,500 a month in partner payouts, plus 5% on payouts funded by ACH or 8% by card. Tolt's automatic payouts, on Growth at $99 a month, carry a 2% fee. Prices checked October 12, 2026. ### Which one pays affiliates for you? Dub Partners sends payouts on its Business plan. Tolt sends automatic payouts from its Growth plan, by PayPal, Wise, local bank, crypto and wire, with a 2% processing fee; on Basic you pay affiliates yourself (as of October 12, 2026). ### Do Dub and Tolt handle tax forms? Dub says its Business plan handles W-9, W-8 and 1099 forms. Tolt collects W-9 and W-8 forms and files 1099s from its Growth plan at $99 a month (as of October 12, 2026). ### Can I move from Tolt to Dub? Yes. Dub Partners imports partners from Rewardful, PartnerStack, FirstPromoter, Tolt, Tapfiliate and Lemon Squeezy. Moving the other way, Tolt's page for Rewardful users describes a customer that moved its program to Tolt in one click. ### Is there an option with no monthly fee? Affitor, which we make, has no subscription: it costs nothing until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales, with no cap on affiliate revenue. It lists every program on its marketplace and reads Stripe sales with no code. It has no importer, so partners get new links, and it pays partners by bank transfer or Wise rather than PayPal (as of October 12, 2026). ## More comparisons Every head-to-head and alternatives page is on the [comparison hub](/blog/compare). Related: [Tolt vs Rewardful](/blog/tolt-vs-rewardful), [Tolt alternatives](/blog/tolt-alternatives), [Rewardful vs Dub](/blog/rewardful-vs-dub), [Dub vs PartnerStack](/blog/dub-vs-partnerstack) and the [19-tool comparison of affiliate software and pricing](/blog/best-affiliate-software-saas). --- id: "blog/firstpromoter-alternatives" type: "blog" url: "https://affitor.com/blog/firstpromoter-alternatives" updated: "2026-10-17" --- # Best FirstPromoter Alternatives for SaaS in 2026 (5 Tools Compared) > Five honest FirstPromoter alternatives for SaaS: Affitor, Rewardful, Tolt, Dub Partners, and PartnerStack. Pricing checked October 2026, attribution trade-offs, and a straight answer on who should pick what. SaaS teams leave FirstPromoter for three reasons: the lowest entry-plan revenue cap of the flat-fee trackers here ($5,000/month in affiliate revenue before the $49 plan forces an upgrade), features that wait on a higher plan, and cookie-based attribution that loses referrals when the cookie dies before signup. If none of those hurt yet, keep FirstPromoter. Its entry plan already includes APIs and webhooks, recurring and multi-tier commissions, W-9/W-8BEN collection, fraud detection, and five native billing connections (Chargebee, Recurly, and Braintree included) that neither Affitor nor Rewardful matches. Plenty of programs never need to move. This guide compares five alternatives worth shortlisting in 2026: Affitor, Rewardful, Tolt, Dub Partners, and PartnerStack. One disclosure before we start: we build Affitor. It is one of the five tools below, and this post tells you plainly where the others beat it. ## Quick answer: what is the best FirstPromoter alternative for SaaS? For SaaS that wants to pay $0 until affiliates have made a program its first $10,000, Affitor is the best fit. Pick Rewardful if you want more revenue headroom at $49 and unlimited affiliates on the entry plan, Tolt if you want unlimited affiliates on a flat subscription, Dub Partners if developer tooling decides your stack, and PartnerStack if you run a multi-type partner program with an enterprise budget. Stay on FirstPromoter if you bill through a provider like Chargebee: of the tools here, it lists the most native billing connections. | Tool | Best for | From price (checked Oct 2026) | Fees on top | How it tracks | |---|---|---|---|---| | [Affitor](https://affitor.com/pricing) | Paying on results | $0/mo | 3.5% of affiliate-driven sales after the first $10,000 per program | Click cookie (60-day default), then the signup customer key | | [Rewardful](https://www.rewardful.com/pricing) | Simplest Stripe setup, more headroom at $49 | $49/mo | 0% transaction fee; optional Managed Payouts 3% | Cookie, 60-day default, first- or last-touch | | [Tolt](https://tolt.com/pricing) | Unlimited affiliates on a flat fee | $69/mo | 2% on auto payouts | Cookie with a set duration, plus a signup call | | [Dub Partners](https://dub.co/pricing) | Developer-first teams | $90/mo | Payout fee: 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise) | Links with conversion tracking | | [PartnerStack](https://www.partnerstack.com/pricing) | Enterprise multi-type programs | Not published; set during a demo | Not published | Link tracking or lead and deal registration | Every price on this page was checked against each vendor's pricing page in October 2026. Affiliate software pricing moves fast, and PartnerStack does not publish prices, so treat the live pages as the source of truth. ## Why teams outgrow FirstPromoter FirstPromoter's model is a flat subscription with revenue-capped plans. Per [firstpromoter.com/pricing](https://firstpromoter.com/pricing), checked October 2026: Starter is $49/mo for up to $5,000/mo in affiliate revenue, with 3 campaigns and up to 1,000 affiliates. Business is $99/mo for up to $15,000/mo, with unlimited campaigns and affiliates, 2 websites, and a custom dashboard domain. Enterprise starts at $149/mo above that. Team members are unlimited on every plan, there is a 14-day trial with no credit card required, and no transaction fee is listed on the pricing page. The cap is the first thing that bites, and it bites earlier here than anywhere else in the flat-fee group. Rewardful's $49 plan covers $7,500/mo in affiliate revenue; Tolt's $69 plan covers $10,000/mo. FirstPromoter's $49 plan stops at $5,000/mo: a program doing modestly well crosses it within months, and the tool's price doubles not because you used more software but because your affiliates performed. The second issue is what waits on a higher plan. The entry plan has the APIs, webhooks, MCP server (in beta), and the full commission engine. But a second website on its own domain needs Business (2 websites) or Enterprise (3), one-click PayPal payouts and a custom dashboard domain need Business, and managed payouts, where FirstPromoter pays affiliates for you, need [Enterprise 2 and up, for SaaS companies, subject to approval](https://help.firstpromoter.com/en/articles/9998853-how-managed-auto-payouts-work). If you run more than one product, Starter is not an option. The third is attribution. FirstPromoter tracks with a cookie, with first- or last-click credit and a cookie life you set (up to 9,999 days). When the cookie is gone before signup (cleared, blocked, or the buyer switches devices), the referral is gone with it. ## What to evaluate in a replacement Three questions separate the five tools below faster than any feature checklist. **How does it charge?** Flat subscription, percentage of results, or both. Watch for double tolls: some tools charge a subscription and then add a fee on payouts or transactions on top. **What happens when the cookie dies?** Every tool here starts from a partner click. The difference is what carries the referral afterwards: a browser cookie all the way to each sale, or a customer record that the signup ties to the partner, which later payments match against. **Can your coding agent do the integration?** In 2026 a lot of Stripe SaaS integration work is done by AI agents. By October 2026 most tools here have an MCP server of some kind: Dub on Business, a Tolt connection to Claude, FirstPromoter in beta, PartnerStack on Launch, and Affitor in beta, while Rewardful's MCP server covers its developer docs. The question to ask is whether an agent can install tracking and then prove it works with a test sale. ## 1. Affitor: best for paying on results ![Affitor's Partners view: active partners and applications in one table with live stats](/blog/shots/partners-table-live.png) Affitor is our product, so here is the model stated plainly: you pay nothing until your affiliate program pays you. ### Key features Tracking starts like the rest: a partner click sets a first-party cookie, and the partner whose click creates the customer keeps that customer. What carries the referral after that is the signup: you send your own customer key, it rides Stripe Checkout and subscription metadata as `affitor_customer_key`, and later payments are matched to the customer rather than to the cookie. The attribution window is set per program, 60 days by default, and is checked once, at the first attributed payment: the click must be no older than the window at signup (or at that payment, if there was no signup). Renewals of an attributed customer are not re-checked. The chain is documented in [how Affitor tracking fits together](/docs/brand/tracking/tracking-overview). The agent surface is live today: a `skill.md` runbook an agent can follow end to end, the `affitor` CLI, browser and server SDKs plus an MCP server (`@affitor/sdk` and `@affitor/mcp`, both labeled beta), and `npx affitor onboard`, which installs tracking and then fires a test click, lead, and sale through your live integration until it reports `integration_verified`. You (or your agent) get proof the integration works before a real affiliate joins. The full setup path is walked in [How to create a Stripe affiliate program](/blog/stripe-affiliate-program). ![Affitor advertiser dashboard: performance overview tracking revenue, partners, clicks, signups, and paid customers for one program](/docs/brand/dashboard.png) Every live program is listed on the [Affitor marketplace](https://affitor.com/marketplace), and the Affitor team helps you recruit, onboard, and train partners ([affitor.com/join](https://affitor.com/join)). Day-to-day operations stay deliberately small: one partner table holds active partners and applications, and you approve each application by hand or turn on Auto-approve. ### Pricing $0/mo, no setup fee, and nothing per partner or per seat. You pay $0 on the first $10,000 of affiliate revenue per program, then 3.5% of the sales affiliates drove (checked Oct 2026, [affitor.com/pricing](https://affitor.com/pricing)). If your affiliates generate nothing, you pay nothing. There are no tiers and no revenue caps. ### Pros & cons **Pros:** no subscription and no caps, so cost follows results; renewals stay attributed after the cookie is gone; a marketplace listing with recruiting help; an integration an agent can complete and test with a synthetic sale. **Cons:** a percentage fee grows with your affiliate revenue, while a flat subscription stays flat until its cap, so price your own expected volume on both pricing pages before you choose. Affitor reads Stripe natively; on Chargebee or another billing system you wire it up through its API or SDK, while FirstPromoter connects five billing systems natively. Affitor collects each partner's tax form (W-8BEN, W-8BEN-E or W-9) before the first payout, as FirstPromoter does on every plan, and partners withdraw by bank transfer or Wise, where FirstPromoter also pays by PayPal, Stripe, and crypto. **FirstPromoter:** $49 to $149+/mo from day one, cookie attribution with first- or last-click credit. **Affitor:** $0/mo, 3.5% of affiliate-driven sales after the first $10,000 per program, a click cookie and then the signup customer key. ## 2. Rewardful: best for the simplest Stripe setup Rewardful is a common flat-fee pick for Stripe SaaS, and against FirstPromoter specifically it wins on two concrete points: a higher entry-plan cap and unlimited affiliates on every plan. ### Key features Setup is two scripts or a native one-click integration (Rewardful is a Premier Stripe Partner). The transaction fee is 0% on every plan, and every plan includes the REST API, first- or last-touch attribution, coupon code tracking, self-referral fraud detection, PayPal mass payouts, and Wise bulk payouts. ### Pricing Per [rewardful.com/pricing](https://www.rewardful.com/pricing), checked October 2026: Starter is $49/mo for up to $7,500/mo in affiliate-attributed revenue, with 1 campaign and up to 2 team members. Growth is $99/mo for up to $15,000/mo, with unlimited campaigns and team members and a branded affiliate portal. Enterprise starts at $149/mo and covers up to $30,000/mo on its entry tier. Every plan has a 14-day trial, and annual billing gives 12 months for the price of 10. ### Pros & cons **Pros:** $7,500/mo of headroom at $49 where FirstPromoter stops at $5,000; unlimited affiliates on every plan where FirstPromoter's Starter holds 1,000; a stated 0% transaction fee. **Cons:** the plan table lists no multi-tier commissions and no W-9/W-8BEN collection (Rewardful collects tax info through its optional Managed Payouts, at 3%), and Starter allows 1 campaign and 2 team members where FirstPromoter's Starter has 3 campaigns and unlimited team members. Billing connections are Stripe and Paddle Classic: if you bill through Chargebee, Rewardful is not an option. Attribution is cookie-based (first- or last-touch, 60-day default), the same model FirstPromoter uses. For the full head-to-head, see [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter); if you end up shortlisting against Rewardful instead, the [Rewardful alternatives guide](/blog/rewardful-alternatives) covers that direction. **Rewardful:** $49 to $149+/mo, 0% transaction fee, API on every plan, Stripe and Paddle Classic. **Affitor:** $0/mo, 3.5% of affiliate-driven sales after the first $10,000 per program, Stripe-native. ## 3. Tolt: best for unlimited affiliates on a flat fee Tolt is a clean modern product in this peer group, and it removes two FirstPromoter limits at once: the affiliate count and the entry-plan cap. ### Key features Unlimited affiliates and referrals on every plan, where FirstPromoter's Starter caps you at 1,000 affiliates. Payout rails are the broadest here: PayPal, Wise, local bank transfer, crypto, and wire, with auto payouts from the Growth plan up. At $99/mo Tolt gives you $20,000/mo of revenue headroom against FirstPromoter Business's $15,000. Tolt also has a [REST API](https://docs.tolt.com/introduction) and an MCP connection to Claude. ### Pricing Per [tolt.com/pricing](https://tolt.com/pricing), checked October 2026: Basic is $69/mo for up to $10,000/mo in affiliate revenue with 2 programs, 3 team members, and manual payouts. Growth is $99/mo for up to $20,000/mo with 5 programs, auto payouts, and W-9/W-8 collection with 1099 filing. Pro is $199/mo for up to $50,000/mo with unlimited programs. 14-day trial, no credit card required, 30-day refund policy. ### Pros & cons **Pros:** unlimited affiliates everywhere, wide payout rails, and double FirstPromoter's entry-plan revenue cap ($10,000 vs $5,000) for $20 more per month. **Cons:** the nuance sits in the payout fees. Tolt markets "0% commission", and that claim has a footnote: auto payouts carry a 2% processing fee, and the Basic plan avoids the fee because its payouts are manual. Tax-form collection starts on Growth, where FirstPromoter collects forms on every plan, and Basic holds 3 team members where FirstPromoter's are unlimited. Tracking starts from a cookie with a set duration, plus a signup call that ties the click to your customer. **Tolt:** $69 to $199/mo, plus 2% on auto payouts. **Affitor:** $0/mo, one 3.5% fee on affiliate-driven sales after the first $10,000 per program. ## 4. Dub Partners: best for developer-first teams Dub is affiliate infrastructure shaped like developer tooling. ### Key features Dub's pricing page lists a REST API, an MCP server, native SDKs, and real-time event webhooks on every Partners plan, plus tax compliance handled for you, so you do not collect W-9, W-8 or 1099 forms yourself. If you already run Dub for link infrastructure, adding Partners keeps links, analytics, and payouts in one platform. ### Pricing Per [dub.co/pricing](https://dub.co/pricing), checked October 2026: Partners needs a paid plan. Business is $90/mo with partner payouts up to $2,500/mo and up to 500 partners. Advanced is $300/mo with payouts up to $15,000/mo and unlimited partners. Enterprise is custom, billed annually, with unlimited payouts and a marketplace listing. The [payout fee](https://dub.co/help/article/partner-payouts) is 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise). ### Pros & cons **Pros:** API, MCP server, SDKs, and webhooks on the entry plan; tax compliance handled; one platform for links, analytics, and payouts. **Cons:** the toll structure. You pay the subscription and a payout fee of 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise), and the payout caps meter your program's growth by plan: a Business-plan program cannot pay partners more than $2,500 in a month, and lifting that ceiling to $15,000 means the $300/mo Advanced plan. The marketplace listing and partner network are Enterprise features. **Dub Partners:** $90/mo plus a payout fee of 5% if you fund payouts by ACH or 8% by card, capped by plan. **Affitor:** $0/mo plus 3.5% of affiliate-driven sales after the first $10,000 per program, no revenue cap. ## 5. PartnerStack: best for enterprise partner programs PartnerStack is not really a FirstPromoter substitute; it is a different category, priced like one. ### Key features A full partner-relationship-management suite ([pricing page](https://www.partnerstack.com/pricing), checked Oct 2026): PartnerStack Marketplace access on every plan, affiliate link tracking or lead and deal registration on Launch (both on Enterprise), partner payments, an MCP connector, and on Growth a learning management system, partner challenges, and MDF management. If you run affiliates, resellers, and referral partners as one program at scale, it is the serious option on this page. ### Pricing PartnerStack does not publish prices. Per [partnerstack.com/pricing](https://www.partnerstack.com/pricing), checked October 2026, Launch, Growth, and Enterprise all start with a demo, and "Your final plan and pricing are confirmed during your demo." Pricing depends on program size, feature needs, and level of support. Its FAQ says there is no limit on partners or internal users. ### Pros & cons **Pros:** marketplace distribution, multi-type partner motions, and enterprise operations no point tool on this page attempts. **Cons:** the process. You see a price after a demo, and its FAQ says most teams are up and running in weeks. For Stripe, its docs describe a webhook that listens for charge and subscription events; we make no other claims about its attribution. For an early or mid-stage SaaS replacing a $49 tool, this is the wrong aisle; for a partnerships team that has outgrown a pure affiliate motion, it is the right one. If PartnerStack's process is the reason you are here, the dedicated [PartnerStack alternatives guide](/blog/partnerstack-alternatives) goes deeper. **PartnerStack:** priced in a demo, full PRM suite. **Affitor:** self-serve signup, $0/mo, affiliate programs without the PRM layer. ## Which one should you pick? The honest segmentation is by stage, because the pricing models behave differently as affiliate revenue grows. **$0–500K ARR: pick Affitor, or Rewardful if you want a known flat cost.** At this stage your affiliate program earns little or nothing yet, and a $49–$90 subscription is pure downside risk, doubly so on FirstPromoter, whose $5,000/mo cap is the first one you will hit. Affitor costs $0 until a program has made $10,000 through affiliates, so the software decision needs no budget. If you would rather pay a predictable $49/mo, Rewardful gives you more headroom at the same price. **$500K–5M ARR: compare at your own volume.** If affiliate-driven revenue is steady, a capped flat plan is predictable: FirstPromoter Business at $99/mo covers up to $15,000/mo with multi-tier commissions, tax-form collection, and fraud detection, and Tolt's $99 plan covers $20,000/mo with unlimited affiliates. If you bill through Chargebee or another non-Stripe provider, staying on FirstPromoter Business is often the honest answer. If affiliate revenue is still lumpy, Affitor's pay-on-results model keeps quiet months at $0. **$5M+ ARR: think in programs, not trackers.** If you run affiliates plus resellers plus referral partners with a partner manager, PartnerStack's PRM suite is the real option. If it is still a pure affiliate motion, the Enterprise plans of FirstPromoter (from $149/mo) or Rewardful ($149+/mo), or Dub's custom Enterprise with its lower payout fees (3% by ACH, 6% by card), cover the volume. ## Every alternative at a glance :::note All prices checked against each vendor's pricing page in October 2026. PartnerStack does not publish prices. Check the live page before you commit. ::: | Platform | Monthly price | Fees on top | Caps | How it tracks | API and agent surface | |---|---|---|---|---|---| | **[Affitor](https://affitor.com/pricing)** | $0 | 3.5% of affiliate-driven sales after the first $10,000 per program | None | Click cookie (60-day default), then the signup customer key | API, CLI, beta MCP, test sale that returns `integration_verified` | | **[FirstPromoter](https://firstpromoter.com/pricing)** | $49 / $99 / $149+ | None listed | $5K / $15K per mo affiliate revenue | Cookie up to 9,999 days, first- or last-click | API and webhooks on every plan; MCP in beta | | **[Rewardful](https://www.rewardful.com/pricing)** | $49 / $99 / $149+ | 0%; optional Managed Payouts 3% | $7.5K / $15K / $30K (entry Enterprise) per mo affiliate revenue | Cookie, 60-day default, first- or last-touch | REST API on every plan; MCP for its docs | | **[Tolt](https://tolt.com/pricing)** | $69 / $99 / $199 | 2% on auto payouts | $10K / $20K / $50K per mo affiliate revenue | Cookie with a set duration, plus a signup call | REST API; MCP connection to Claude | | **[Dub Partners](https://dub.co/pricing)** | $90 / $300 / custom | Payout fee: 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise) | Payouts $2.5K / $15K per mo | Links with conversion tracking | REST API, MCP server, native SDKs | | **[PartnerStack](https://www.partnerstack.com/pricing)** | Set during a demo | Not published | Not published | Link tracking or lead and deal registration | REST API; MCP connector on Launch | ## FAQ ### What is the best FirstPromoter alternative for SaaS? It depends on why you are leaving. For SaaS that wants no monthly fee, Affitor is the best fit: $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales. Rewardful is the strongest pick when you want more revenue headroom at $49 ($7,500 a month against $5,000), and Tolt when you want unlimited affiliates on a flat subscription. ### How does Affitor's pricing compare with FirstPromoter's? They charge in different shapes. Affitor has no subscription: $0 on the first $10,000 of affiliate revenue per program, then 3.5% of affiliate-driven sales. FirstPromoter charges a monthly plan by affiliate-revenue tier ($49, $99 or from $149) with no transaction fee listed (checked October 2026). A new program pays nothing on Affitor until it has made $10,000 through affiliates; after that, compare both at your own monthly volume. ### Does FirstPromoter charge transaction fees? FirstPromoter's pricing page lists no transaction fee: the subscription ($49, $99 or from $149 a month, checked October 2026) is the price. The trade-offs are revenue-capped plans ($5,000 a month in affiliate revenue on Starter, the lowest cap of the three flat-fee trackers here) and features that arrive on higher plans, such as a second website on Business and managed payouts on Enterprise 2 and up, for SaaS companies, subject to approval. ### Which affiliate software has no monthly fee? In this comparison, Affitor: $0 a month, $0 on the first $10,000 of affiliate revenue per program, then 3.5% of affiliate-driven sales. The others charge a monthly plan: FirstPromoter $49, Rewardful $49, Tolt $69, Dub Partners $90, and PartnerStack prices every plan in a demo. Outside this comparison, PromoteKit has a $0 plan for up to 3 referrals and Endorsely a $0 plan below $1,000 a month in affiliate revenue (checked October 2026). ### How much does affiliate tracking software cost in 2026? Entry prices checked October 2026: FirstPromoter and Rewardful $49/month, Tolt $69/month, Dub Partners $90/month plus a payout fee of 5% if you fund payouts by ACH or 8% by card, PartnerStack priced during a demo, and Affitor $0/month with 3.5% of affiliate-driven sales after the first $10,000 per program. Prices in this category change often, and PartnerStack does not publish prices (checked October 2026). ### Why do SaaS teams leave FirstPromoter? Three common reasons: the $5,000 a month affiliate-revenue cap on the $49 Starter plan, the lowest of the three flat-fee trackers here; features that need a higher plan (a second website and one-click PayPal payouts on Business, managed payouts on Enterprise 2 and up, for SaaS companies, subject to approval); and cookie-based attribution that loses the referral when the cookie is gone before signup. ## What's next The short version: stay on FirstPromoter if its back office (tax forms, fraud detection, multi-tier commissions) or its billing coverage is what you use; few tools under $100 cover that combination. Pick Rewardful for the simplest Stripe setup with more headroom at $49. Pick Tolt for unlimited affiliates and broad payout rails at a flat price. Pick Dub Partners if you already live in Dub's link infrastructure and accept the payout fee. Pick PartnerStack when you are running a multi-type partner program with an enterprise budget. Pick Affitor if you want to pay when your affiliates generate revenue and not before, keep renewals attributed after the cookie is gone, or hand the whole integration to an agent and get back proof it works. If the performance model fits your stage, [create your program](https://affitor.com/welcome). It costs nothing to run until a program has made $10,000 through affiliates, so the way to evaluate Affitor is to launch with it. If you want to see how Affitor tracking works before you decide, [read the tracking docs](/docs/brand/tracking/tracking-overview). The click, signup, and sale chain is documented end to end, including the test that proves your integration is live. ## More comparisons - [Every comparison in one table](/blog/compare) - [The best Rewardful alternatives for SaaS](/blog/rewardful-alternatives) - [PartnerStack alternatives](/blog/partnerstack-alternatives) - [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter) - [Tolt alternatives](/blog/tolt-alternatives) - [Tolt vs Rewardful](/blog/tolt-vs-rewardful) - [PartnerStack vs Rewardful](/blog/partnerstack-vs-rewardful) - [Best affiliate software for SaaS: pricing compared](/blog/best-affiliate-software-saas) --- id: "blog/firstpromoter-vs-dub" type: "blog" url: "https://affitor.com/blog/firstpromoter-vs-dub" updated: "2026-10-17" --- # FirstPromoter vs Dub: Pricing, Fees and Features Compared (Checked Oct 2026) > FirstPromoter starts at $49 a month with no fees listed and native support for five billing systems. Dub Partners starts at $90 a month plus a 5% payout fee, and sends payouts and handles tax forms on that plan. Checked on both pricing pages on October 12, 2026. Pick [FirstPromoter](https://firstpromoter.com/pricing) if you bill through Paddle, Chargebee, Recurly or Braintree as well as Stripe, or want unlimited team members and multi-tier commissions, from $49 a month. Pick [Dub Partners](https://dub.co/pricing) if you want Dub to send partner payouts and handle tax forms on its entry plan, at $90 a month plus 5% of the payouts you fund by ACH. Both checked on October 12, 2026. | Tool / Platform | Entry price | Fee on top | Revenue cap
The most affiliate revenue, payouts or ARR the entry plan covers before you move up. | Minimum term
Shortest commitment on the entry plan, from the vendor's pricing page or terms. | Billing | | --- | --- | --- | --- | --- | --- | | [FirstPromoter](https://firstpromoter.com/pricing)
Starter, 14-day trial, no card | $49/mo | None listed | $5,000/mo
affiliate revenue on Starter | None | Stripe, Paddle, Chargebee, Recurly, Braintree | | [Dub Partners](https://dub.co/pricing)
Business, 14-day trial | $90/mo | 5% of payouts funded by ACH
8% if funded by card; 3% and 6% on Enterprise | $2,500/mo in payouts
500 partners on Business | None | Stripe, Shopify; others through the API | | [Affitor](https://affitor.com/pricing)
until a program has made $10,000 through affiliates | $0 | 3.5% of affiliate-driven sales
after the first $10,000 per program | None | None | Stripe with no code; other billing through the API or SDK |
Entry plans as listed on each vendor's pricing page on Oct 12, 2026; the tool name links to it. FirstPromoter's cap counts affiliate revenue and Dub's counts the payouts you send partners, so the two caps measure different things. We make Affitor; it sits in the last row of each table for reference, and the section Where Affitor fits covers it. ## Where FirstPromoter is stronger - **Lower entry price.** Starter is $49 a month, or $490 a year, against $90 a month for Dub's Business plan. - **No fees listed.** FirstPromoter's pricing page lists no fees on top of the plan. Dub charges 5% on payouts you fund by ACH and 8% by card (3% and 6% on Enterprise). - **Five billing systems.** FirstPromoter works natively with Stripe, Paddle, Chargebee, Recurly and Braintree. Dub connects Stripe and Shopify and takes other billing through its API. - **Unlimited team members on every plan**, against 10 users on Dub Business. Starter holds up to 1,000 affiliates; Dub Business holds 500 partners. - **Commission rules.** Multi-tier commissions up to 3 levels, and API and webhooks on every plan. - **Help moving in.** FirstPromoter's team helps migrate your promoters from another platform, and it offers a historical Stripe import when you migrate. The limits to know: Starter covers up to $5,000 a month in affiliate revenue, with 3 campaigns. Business is $99 for up to $15,000, and it is where the custom dashboard domain and the in-app embedded dashboard start. ## Where Dub Partners is stronger - **Payouts on the entry plan.** Business sends partner payouts for you, with the fee above. FirstPromoter's managed auto payouts need its Enterprise 2 plan or higher; direct PayPal payouts start on Business. - **Tax forms.** Dub says it handles W-9, W-8 and 1099 forms on Business. FirstPromoter collects W-9 and W-8BEN forms in the affiliate portal on every plan, with no 1099 filing listed. - **An MCP server on Business.** FirstPromoter's MCP server is in beta. - **Importers.** Dub imports partners from Rewardful, PartnerStack, FirstPromoter, Tolt, Tapfiliate and Lemon Squeezy. - **Links, analytics and payouts in one product**, since Dub Partners runs on Dub's link platform. - **A marketplace listing and partner discovery**, on Enterprise. FirstPromoter lists neither in its plan table. The limits to know: Business covers $2,500 a month in partner payouts, and when you hit your plan's payout limit you can't send more payouts until the next billing period. Advanced is $300 a month with up to $15,000. ## Partners and payouts How many partners and teammates the entry plan holds, whether the vendor helps you find partners, and who sends the money. Hover a column for what it checks. | Tool / Platform | Partners
No limit on affiliates on the entry plan. | Seats
No limit on team members on the entry plan. | Marketplace
The vendor lists your program in a marketplace or directory affiliates browse. | Finds affiliates
A network, matching or outreach service that recruits partners. | Payouts
The vendor sends money to affiliates for you. | PayPal
Affiliates can be paid by PayPal through the tool. | Tax forms
Collects W-9/W-8 forms or files 1099s. | | --- | --- | --- | --- | --- | --- | --- | --- | | [FirstPromoter](https://firstpromoter.com/pricing) | Partial
1,000 on Starter | Yes
all plans | No
not in plan table | No
not in plan table | Partial
Enterprise 2+ | Yes
direct on Business+ | Yes
collects, no 1099 | | [Dub Partners](https://dub.co/pricing) | Partial
500 on Business | Partial
10 on Business | Partial
Enterprise | Partial
Enterprise | Partial
5% payout fee | Partial
14 countries | Yes
Business plan | | [Affitor](https://affitor.com/pricing) | Yes
unlimited | Yes
unlimited | Yes
every live program | Yes
team service | Yes
bank or Wise | No
bank or Wise | Yes
W-8BEN, W-8BEN-E or W-9 |
## Tracking and setup Both read sales from Stripe natively and credit sales to coupon codes. FirstPromoter adds four more billing systems natively; Dub adds Shopify and its API. Hover a column for what it checks. | Tool / Platform | Stripe
Reads sales from Stripe natively. | Other billing
Native support for Paddle, Chargebee, Recurly, Braintree or others. | Coupons
Credits a sale to an affiliate by coupon or promo code. | REST API
A public REST API on the entry plan. | MCP
An official MCP server for AI agents. | Importer
Imports affiliates, links or history from another affiliate tool. | | --- | --- | --- | --- | --- | --- | --- | | [FirstPromoter](https://firstpromoter.com/pricing) | Yes
native | Yes
+4 billing systems | Yes
all plans | Yes
all plans | Partial
beta | Yes
assisted, 24-48h | | [Dub Partners](https://dub.co/pricing) | Yes
native | Partial
Shopify; else API | Yes
Stripe promo codes | Yes
Business | Yes
Business | Yes
Rewardful, Tolt +4 | | [Affitor](https://affitor.com/pricing) | Yes
native, OAuth | Partial
via API/SDK | No
not stated publicly | Yes
every program | Partial
beta | No
partners rejoin |
## Which one should you pick? Choose FirstPromoter when you bill through more than Stripe, want detailed commission rules, or need many teammates in the account: $49 a month for up to $5,000 a month in affiliate revenue, then $99 for up to $15,000. Choose Dub Partners when you want Dub to send payouts and handle tax forms from the entry plan, or you already use Dub for links; budget $90 a month plus 5% of payouts funded by ACH, and $300 a month on Advanced once payouts pass $2,500 a month. Both offer a 14-day trial, FirstPromoter's with no card, and both let you cancel any time. ## Where Affitor fits If you would rather not pay a monthly plan before affiliates sell, there is a third shape. Affitor, which we make, has no subscription: $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales, with no cap on affiliate revenue and no limit on partners or seats. Every program is listed on the [Affitor marketplace](https://affitor.com/marketplace), and the Affitor team helps you recruit, onboard and train partners ([affitor.com/join](https://affitor.com/join)). It reads Stripe sales with no code, takes other billing systems through its API or SDK, and lets you run a test sale before launch. The trade-offs are in the tables above: there is no importer, so partners join again through your program page and get new links; payouts go out by bank transfer or Wise after a review, not PayPal; and Affitor does not track coupon codes. Affitor collects a tax form from each partner (W-8BEN, W-8BEN-E or W-9) before the first payout. Details are on the [pricing page](https://affitor.com/pricing). ## FAQ ### How do FirstPromoter and Dub prices compare? On the entry plans, FirstPromoter costs less. FirstPromoter Starter is $49 a month with no fees listed on its pricing page and covers up to $5,000 a month in affiliate revenue. Dub Partners Business is $90 a month, covers up to $2,500 a month in partner payouts, and charges 5% on payouts you fund by ACH or 8% by card. Prices checked October 12, 2026. ### Which one works with Paddle or Chargebee? FirstPromoter supports Stripe, Paddle, Chargebee, Recurly and Braintree natively. Dub Partners connects to Stripe and Shopify, and other billing systems send sales through its API (as of October 12, 2026). ### Which one pays affiliates for you? Dub Partners sends partner payouts on its Business plan, with a 5% fee on payouts funded by ACH and 8% by card. FirstPromoter's managed auto payouts need its Enterprise 2 plan or higher, and direct PayPal payouts start on Business (as of October 12, 2026). ### Can I move from FirstPromoter to Dub? Yes. Dub Partners imports partners from Rewardful, PartnerStack, FirstPromoter, Tolt, Tapfiliate and Lemon Squeezy. Moving the other way, FirstPromoter's team helps migrate your promoters from another platform. ### Is there an option with no monthly fee? Affitor, which we make, has no subscription: it costs nothing until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales, with no cap on affiliate revenue. It lists every program on its marketplace and reads Stripe sales with no code. It has no importer, so partners get new links, and it pays partners by bank transfer or Wise rather than PayPal (as of October 12, 2026). ## More comparisons Every head-to-head and alternatives page is on the [comparison hub](/blog/compare). Related: [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter), [FirstPromoter alternatives](/blog/firstpromoter-alternatives), [Rewardful vs Dub](/blog/rewardful-vs-dub), [Dub vs Tolt](/blog/dub-vs-tolt) and the [19-tool comparison of affiliate software and pricing](/blog/best-affiliate-software-saas). --- id: "blog/how-to-start-saas-affiliate-program" type: "blog" url: "https://affitor.com/blog/how-to-start-saas-affiliate-program" updated: "2026-10-18" --- # How to Start an Affiliate Program for Your SaaS (Step-by-Step Guide 2026) > Six steps take you from no program to your first partner payout: commission, software, tracking, recruiting, payout terms, and what to measure, with 2026 benchmarks and pricing checked October 2026. Starting an affiliate program for your SaaS comes down to six decisions: what you pay, which software runs it, how sales get attributed, who you recruit, when money moves, and what you watch in the first ninety days. This guide takes them in order as six steps, with 2026 benchmark numbers where verified data exists, and links to honest comparisons where the right answer depends on your stage. One principle sits under all six. An affiliate program is performance spend: you pay after revenue arrives, not before. That is what makes it attractive next to ads. Every decision below either protects that property or quietly gives it away, so when two options look equal, pick the one that keeps your costs proportional to results. ## Quick answer: how do you start a SaaS affiliate program? Start a SaaS affiliate program in six steps: set a commission in the 20–25% band that stays within 30–40% of your gross margin, pick software priced for your stage (self-serve floors run from $0 at Affitor to $90 a month at Dub Partners as of October 2026; PartnerStack prices in a demo), install tracking that survives cookie loss, hand-recruit your first five to twenty aligned partners, set payout holds that match your refund window, and spend the first ninety days measuring click-to-signup rate per partner rather than revenue. The cheapest way to run the software decision: Affitor charges $0/month until your affiliates generate their first $10,000, so the program costs nothing until it works. | Tool | Best for | From price (checked Oct 2026) | Transaction fee | Attribution | |---|---|---|---|---| | [Affitor](https://affitor.com) | Starting from zero, paying on results | $0/mo | 3.5% on affiliate-driven sales after first $10K | Signup-anchored via Stripe metadata | | [Rewardful](https://www.rewardful.com/pricing) | The known flat-fee default for Stripe | $49/mo | 0% | Cookie, 60-day default | | [FirstPromoter](https://firstpromoter.com/pricing) | Billing beyond Stripe and Paddle | $49/mo | None stated | Cookie, 60-day default | | [Tolt](https://tolt.com/pricing) | Unlimited affiliates on a flat fee | $69/mo | 2% on automated payouts | Cookie, configurable window | | [Dub Partners](https://dub.co/pricing) | Developer-first teams | $90/mo | 5% of payouts by ACH, 8% by card (3% and 6% on Enterprise) | Signup/lead-anchored | | [PartnerStack](https://www.partnerstack.com/pricing) | Enterprise multi-type programs | Not published; priced in a demo | None published | Not publicly documented | Every price on this page was checked against each vendor's live pricing page on October 17, 2026. ## Step 1: Decide what you'll pay ![Partner groups each carry their own commission rate — VIP tiers without spreadsheets](/blog/shots/groups-commission.png) Start from the benchmark, then adjust for your margin. The typical SaaS affiliate commission is 20% of the revenue a partner generates. An analysis of 96 real percentage-based campaigns puts the average at 23.3%, with 20-25% the most common band. Mature programs tend to settle at 15-25%, inside an overall industry range of 5-30%. The commission model matters as much as the rate: | Commission model | How it pays | Best for | |---|---|---| | Recurring percentage | A share of every referred payment, typically for 12+ months | Subscription SaaS — in renewal-paying programs, 70% of commission events are renewals | | One-time bounty | A fixed amount per converted customer | Simple budgeting, high-touch sales-assisted deals | | Hybrid | A recurring share plus a signup bonus | Competing for established affiliates who compare programs on both | Two rules keep the number safe: **Stay within 30-40% of your gross margin.** Commission is a cut of margin, not of revenue. If your gross margin is 80%, a 20% commission consumes a quarter of it, comfortably inside the guidance. At 60% margin, the same 20% commission eats a third of it, which is already inside the 30-40% ceiling. Run this arithmetic before you publish a rate, because raising is easy and cutting is a partner-relations problem. **Prefer recurring commissions over one-time bounties.** In programs that pay on renewals, 70% of all commission events are renewal payments. Most of what a good partner earns arrives after the first sale, and that ongoing stake is exactly what keeps them promoting you next quarter instead of the next tool. If your margin allows it, pay on renewals for at least the first year of each referred subscription. ## Step 2: Choose your software Four criteria separate the tools. Weigh them before you look at a single feature list. **Pricing model.** Every major tool except one charges a monthly subscription before your program has produced anything. As of October 2026 the floors are: Rewardful $49/mo, FirstPromoter $49/mo, Tolt $69/mo, Dub Partners $90/mo, and PartnerStack prices every plan in a demo. Some also charge twice: Dub adds 5% of payouts funded by ACH (8% by card) on Business and Advanced, and Tolt takes a 2% processing fee on automated payouts. Watch revenue caps too. Entry tiers commonly cap the monthly affiliate revenue you can process (FirstPromoter at $5,000/mo, Rewardful at $7,500/mo), which means a program that works forces an upgrade. Prices drift fast, so re-check each vendor's live pricing page before you commit. **Attribution durability.** Ask where attribution actually lives: in a browser cookie that expires, or anchored to something durable like the customer's signup identity. Step 3 explains why this decides whether partners trust your numbers. **Billing fit.** Stripe has no native affiliate feature, so whatever you pick must plug into your billing stack. On Stripe you have the widest menu. Off Stripe, the shortlist narrows quickly: Rewardful covers Stripe and Paddle, Tolt covers Stripe, Paddle, and Chargebee, and FirstPromoter integrates with five billing providers (Stripe, Paddle, Recurly, Chargebee, Braintree). **Agent surface.** In 2026 there is a real chance the "developer" wiring your integration is an AI coding agent. By October 2026 Dub (Business), FirstPromoter (beta, every plan), PartnerStack (Launch) and Tolt ship an MCP server, and Rewardful's MCP server covers its docs. The question is whether an agent can install tracking and prove it with a test sale. APIs exist (Rewardful includes its REST API on every tier; FirstPromoter includes its APIs and webhooks on every plan, including the $49 Starter), but they are built for human developers reading docs. Where Affitor fits, with the obvious disclosure that I build it: Affitor is the performance-priced option. You pay $0 until your program earns its first $10,000 through affiliates, then 3.5% on affiliate-driven sales only. No monthly fee, no setup fee; the 3.5% is the whole cost. It is also the tool built agent-first: an AI coding agent can complete the entire integration from one paste line and prove it worked. And the honest counterpoints: if you want the most recognized brand and a simple flat subscription for a Stripe SaaS, Rewardful is the category default and its 0% transaction fee is genuine. If you run affiliates, resellers, and referral partners at enterprise scale, PartnerStack is a full partner-management suite that Affitor does not try to be. The detailed trade-offs live in dedicated comparisons: [the best affiliate software for SaaS by stage](/blog/best-affiliate-software-saas), [Rewardful alternatives](/blog/rewardful-alternatives), [PartnerStack alternatives](/blog/partnerstack-alternatives), [FirstPromoter alternatives](/blog/firstpromoter-alternatives), [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter), and [Rewardful vs Tolt](/blog/tolt-vs-rewardful). ## Step 3: Set up tracking that survives real customers The whole program rests on one chain: click, signup, sale. A partner sends a visitor, the visitor becomes a signup, the signup becomes a paying customer, and every later invoice traces back to the partner who started it. ```mermaid flowchart LR A[Click] --> B[Signup] B --> C[Sale] C --> D[Commission
on hold] D --> E[Approved] E --> F[Payout] ``` *Every affiliate program runs this loop: a partner's click becomes a signup, the signup becomes attributed sales, and each sale creates a commission that clears a hold period before it is paid out.* Where tools differ is what carries attribution across that chain. Rewardful, FirstPromoter, and Tolt attribute through cookie windows (Rewardful and FirstPromoter default to 60 days; Tolt's window is configurable). Cookies work when the buyer stays in one browser and converts inside the window. They fail when the cookie is cleared, blocked, or the buyer switches from their phone to their work laptop before paying, and the partner silently loses credit. To be fair to the category, Dub Partners anchors attribution to the signup rather than the cookie, the same architectural bet Affitor makes. Affitor's chain works like this: a lightweight browser snippet stores the click in an `affitor_click_id` cookie, your signup handler sends a server-side lead event that binds the click to the customer's identity, and sale events ride Stripe metadata on the Checkout Session. Once the signup is recorded, attribution no longer depends on the cookie at all: the chain runs click to signup identity to Stripe customer, and it survives cookie loss and device switches. You can also prove the whole thing works before a single real customer arrives: ```bash title="terminal" npx affitor onboard ``` The CLI detects your stack, installs click tracking, injects the sale call into your Stripe webhook handler, and then fires a synthetic click, lead, and sale through the live pipeline. When the readiness check returns `integration_verified: true`, tracking is proven end to end. The same capability is exposed to AI agents through an MCP server (5 tools by default, 7 with write tools on; the hosted server has 12) and a public `skill.md` runbook, so "set up tracking" can be a ten-minute delegation to your coding agent instead of a sprint task. Setup details live in the docs: [how the tracking pieces fit together](/docs/brand/tracking/tracking-overview), [payment tracking with Stripe](/docs/brand/tracking/payment-tracking-stripe), and [testing your integration end to end](/docs/brand/tracking/testing-integration). If you are on Stripe, the companion guide [How to create a Stripe affiliate program](/blog/stripe-affiliate-program) walks the whole integration step by step. ## Step 4: Recruit your first partners Software launches nothing. Your first ten partners will be hand-recruited, and that is normal. Five to twenty aligned partners beat a hundred random affiliates, so work the channels in order of warmth: 1. **Your own customers.** They already use the product, believe its pitch, and often have exactly the audience you want. An email to your most engaged accounts announcing the program is the highest-conversion outreach you will ever send. 2. **Creators already covering your category.** Find the people writing comparisons, filming tutorials, and ranking for the searches your buyers make. Personalize the pitch: name the piece of theirs you read and state your commission terms plainly. 3. **Communities where your buyers gather.** Founders' Slacks, subreddits, Discords, newsletters. Contribute first; recruit second. 4. **Partners of adjacent products.** People who already promote tools your customers use know how to sell software like yours. They are the fastest to activate because the workflow is not new to them. 5. **A marketplace listing.** List your program where affiliates already browse. In Affitor, opt your program into the [marketplace](https://affitor.com/marketplace), and partners discover and apply on their own; you approve manually or set auto-accept. See [reviewing partner applications](/docs/brand/quickstart/partner-approval-quality-control). Recruit for fit, not follower count. One partner whose audience actually buys SaaS beats ten whose audiences scroll past, and you will see the difference in your click-to-signup numbers within weeks. ## Step 5: Set payout terms that match your refund policy Money mechanics decide whether the program feels safe to run. Three settings do most of the work: **Hold periods.** Never pay commission on revenue that can still be refunded. Set the hold at least as long as your refund window, plus a buffer for disputes. In Affitor, a commission waits for the program's hold period, which you set, and approves automatically when it ends unless you approve or reject it first; you can also extend the hold on one commission. :::tip Match the hold period to your refund window before launch. It is the one payout setting that is awkward to tighten later, because shortening feels fine to partners and lengthening feels like a rug-pull. ::: **Refund clawbacks.** When a payment is refunded or disputed, the commission should reverse automatically. Affitor does this out of the box, with every state change kept in an audit trail. Whatever tool you choose, confirm this behavior before you buy, because manual clawbacks are the kind of chore that stops happening after month two. **Payout thresholds.** A minimum balance before withdrawal keeps you from processing five-dollar payouts. On Affitor the minimum withdrawal is $20 for every program, and Affitor pays partners through Wise or by bank transfer. The mechanics are documented in [commission approval and cash flow](/docs/brand/quickstart/commission-approval-cash-flow) and [payouts](/docs/brand/quickstart/payouts); rate and hold configuration lives in [define commission](/docs/brand/quickstart/define-commission). ## Step 6: Launch and measure the first ninety days Expect the start to be quiet, and plan around it. A partner recruited today publishes content in a few weeks, that content converts a visitor weeks later, and the resulting commission clears its hold after that. The loop in the diagram above is measured in months the first time through. What matters early is not revenue; it is proof that each stage of the loop works. **Month 1: prove the plumbing and land the first partners.** Verify tracking end to end before announcing anything (a synthetic test chain, or a real test purchase). Get your listing live, approve your first applications, and confirm every accepted partner has their link. The number to watch: how many recruited partners generated at least one click. **Month 2: watch the first commissions move.** Real clicks should be turning into signups, and the first sales into on-hold commissions. Check attribution quality (sales landing on the right partner), confirm refunds reverse commissions, and make sure the hold and approval flow behaves the way you configured it. The number to watch: click-to-signup rate per partner, which tells you whose audience actually matches your product. **Month 3: judge channels, not partners.** Look at which recruiting channel produced the partners who drive revenue, then double down there and stop spending time on the rest. If the data says your rate is wrong, adjust it going forward rather than retroactively; in Affitor, commission policies are versioned and apply from an effective date, so a rate change never rewrites history. Program-level metrics live in [performance tracking](/docs/brand/quickstart/view-performance). ## Key takeaways - A 20–25% recurring commission is the SaaS standard; keep it within 30–40% of your gross margin. - In renewal-paying programs, 70% of commission events are renewals — recurring beats one-time for subscription businesses. - A 60-day cookie window is the category default, and signup-anchored attribution is what survives when the cookie dies. - Software floors run $49–$90/month as of October 2026 (Rewardful to Dub Partners), and PartnerStack prices in a demo; Affitor is the $0/month exception, charging 3.5% only after your first $10,000 in affiliate revenue. - Five to twenty aligned partners beat a hundred random affiliates. - Set the commission hold at least as long as your refund window, and make clawbacks automatic. - Measure the first ninety days by stage — clicks, then click-to-signup rate, then revenue by channel — not by revenue totals. ## FAQ ### How much should a SaaS affiliate program pay? The typical SaaS affiliate commission is 20% of the revenue a partner generates, with 20–25% the most common band; an analysis of 96 real percentage-based campaigns puts the average at 23.3%, inside an overall industry range of 5–30%. Keep the rate within 30–40% of your gross margin and prefer recurring commissions on renewals over one-time bounties. ### How much does affiliate program software cost in 2026? Monthly floors as of October 2026: Rewardful $49, FirstPromoter $49, Tolt $69, Dub Partners $90 (plus 5% of payouts funded by ACH, 8% by card), and PartnerStack prices every plan in a demo. Affitor has no subscription: $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales. ### How long should the affiliate cookie window be? 60 days is the category default — Rewardful and FirstPromoter both ship 60-day cookie windows out of the box. The deeper question is what happens when the cookie dies: signup-anchored attribution (Affitor, and architecturally Dub) survives cleared cookies and device switches, while pure cookie models silently drop the referral. ### How many affiliates do you need to start a SaaS affiliate program? Five to twenty aligned partners beat a hundred random affiliates. Your first ten will be hand-recruited — from your own customers, creators already covering your category, and communities where your buyers gather — and one partner whose audience actually buys SaaS outperforms ten whose audiences scroll past. ### How long until an affiliate program produces revenue? Plan in months, not weeks. A partner recruited today publishes content in a few weeks, that content converts visitors weeks later, and the resulting commission clears its hold period after that. In the first ninety days, measure proof that each stage works — clicks per partner in month one, click-to-signup rate in month two, revenue by recruiting channel in month three — not revenue totals. ### Should commissions be recurring or one-time? Recurring, if your margin allows it. In programs that pay on renewals, 70% of all commission events are renewal payments — most of what a good partner earns arrives after the first sale, and that ongoing stake is exactly what keeps them promoting you next quarter. ## What's next You have the six steps: a rate grounded in the 20-25% benchmark and your margin, software priced the way you want to pay, tracking that survives real customers, a recruiting plan that starts warm, payout terms that match your refund policy, and a ninety-day measurement plan. Two ways to move: - **Start the program.** [Create your Affitor program](https://affitor.com/welcome). It costs $0 until your program earns its first $10,000 through affiliates, so the software decision does not need a budget meeting. - **Go deeper on the mechanics.** The [advertiser quickstart](/docs/brand/quickstart) walks from account creation to a configured program, and the [tracking overview](/docs/brand/tracking/tracking-overview) explains the attribution chain in full. --- id: "blog/partnerstack-alternatives" type: "blog" url: "https://affitor.com/blog/partnerstack-alternatives" updated: "2026-10-17" --- # Best PartnerStack Alternatives in 2026 (5 Tools Compared) > PartnerStack does not publish its prices: every plan is priced during a demo. Here is what its plans include, who should pay for it, and five self-serve alternatives with pricing checked in October 2026. PartnerStack does not publish its prices. Its pricing page lists three plans, Launch, Growth and Enterprise, each with a "Book your demo" button, and says "Your final plan and pricing are confirmed during your demo." If you run a multi-type partner program at scale, that process can be fair. If you are an early-stage SaaS founder who wants an affiliate program running this quarter, it is probably the wrong tool, and this page exists to help you pick the right one. One disclosure before anything else: we build [Affitor](https://affitor.com), one of the alternatives below. To keep this useful anyway, every price on this page comes from the vendor's own pricing page, checked in October 2026, with a link so you can check it yourself. And we start by telling you when PartnerStack is the better choice. ## Quick answer: what is the best PartnerStack alternative? For an early-stage SaaS, Affitor is the best fit: it is self-serve and costs $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales, and its team helps you recruit partners. Rewardful is the flat-fee pick for Stripe SaaS, FirstPromoter connects the most billing systems, Tolt gives you unlimited affiliates on every plan, and Dub Partners suits developer-led teams. Keep PartnerStack on the table if you run affiliates, resellers, and referral partners as one program with a partner manager. | Tool | Best for | From price (checked Oct 2026) | Fees on top | How it tracks | |---|---|---|---|---| | [Affitor](https://affitor.com/pricing) | Starting from zero on Stripe | $0/mo | 3.5% of affiliate-driven sales after the first $10,000 per program | Click cookie (60-day default), then the signup customer key | | [Rewardful](https://www.rewardful.com/pricing) | The known flat-fee default | $49/mo | 0% transaction fee; optional Managed Payouts 3% | Cookie, 60-day default, first- or last-touch | | [FirstPromoter](https://firstpromoter.com/pricing) | Billing beyond Stripe and Paddle | $49/mo | None listed | Cookie life up to 9,999 days, first- or last-click | | [Tolt](https://tolt.com/pricing) | Unlimited affiliates on a flat fee | $69/mo | 2% on auto payouts | Cookie with a set duration, plus a signup call | | [Dub Partners](https://dub.co/pricing) | Developer-led teams | $90/mo | Payout fee: 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise) | Links with conversion tracking | | [PartnerStack](https://www.partnerstack.com/pricing) | Enterprise multi-type programs | Not published; set during a demo | Not published | Link tracking or lead and deal registration | Every price on this page was checked against each vendor's pricing page on October 12 and 13, 2026. ## What PartnerStack actually is Most "PartnerStack alternatives" pages skip this part, and it produces bad decisions. PartnerStack is not an affiliate link tracker with a high price. It is a full partner relationship management (PRM) platform, and the extra money buys a different category of product ([pricing page](https://www.partnerstack.com/pricing), checked Oct 2026): - **A partner marketplace.** Every plan includes PartnerStack Marketplace access, pitched as "Get discovered by active B2B partners." Rewardful, FirstPromoter and Tolt list no marketplace in their plan tables; Dub lists one on Enterprise, and Affitor lists every live program on its marketplace. - **Multi-type partner programs.** Launch includes affiliate link tracking or lead and deal registration (you pick one); Enterprise includes both. Growth adds a learning management system, partner challenges, and MDF (market development funds) management. - **Enterprise operations.** Partner payments, CRM integrations, onboarding and training tools, and on the Enterprise plan a designated customer success manager and custom workflows. If you compare that to a $49 affiliate tracker on price alone, you are comparing categories, not products. The real question is whether you need a PRM at all. ## What it costs **PartnerStack:** per [its pricing page](https://www.partnerstack.com/pricing), checked October 2026, all three plans start with a demo. The page says "Pricing is based on your partner program size, feature needs and level of support." The page lists no trial and no $0 plan, and its FAQ says most teams are up and running "in weeks, depending on program complexity and integrations." What it does state plainly: no limit on partners and no limit on internal users. **The self-serve field:** every alternative below publishes its price and lets you sign up yourself, from $0 a month (Affitor) to $90 a month (Dub Partners) at the entry plan, and you can have a tracked link the same day. Two notes on older comparison articles. First, PartnerStack does not publish prices (checked October 2026), so treat any PartnerStack price you read elsewhere, including on older versions of this page, as stale unless it comes from your own demo. Second, you will find third-party reports claiming PartnerStack takes an extra percentage of partner payouts. Its public pages state no payout fee either way, so we are not repeating them. ## When PartnerStack is the right call Recommending against a product for everyone is a sales pitch, not a comparison. PartnerStack is the right choice when: - You run **more than one partner motion**: affiliates plus referral partners plus resellers, with deal registration feeding a sales team. - You want **marketplace distribution**, recruiting from B2B partners already active on the network instead of building your recruiting pipeline from zero. - You need **program operations at scale**: partner training, MDF budgets, partner payments and CRM sync across a large partner base. - You have (or are hiring) a **partner manager** whose job this platform is. If that describes you, book the demo and negotiate. Nothing below replaces a full PRM, and pretending a $49 tracker covers deal registration would be a strawman. ## What early-stage SaaS needs instead If you were priced out rather than sold short, the checklist flips. Judge alternatives on four things: 1. **Self-serve signup.** You should be live this week, not after a contract cycle. Everything below has self-serve signup; PartnerStack starts with a demo. 2. **Pricing shaped like performance.** Early programs earn $0 in month one. Your cost should scale with affiliate revenue, not start as a fixed commitment before your first partner sale. 3. **Tracking that fits your billing stack.** If you charge customers through Stripe, pick a tool that reads Stripe directly, and check how it credits a payment that lands weeks after the click. 4. **A surface you can verify.** An API at minimum. Ideally a way for you, or an AI agent working for you, to run a test sale end to end before a real dollar moves. **PartnerStack:** demo, plan and price set in the demo, then onboarding that takes weeks. **The five below:** sign up, install, first tracked link the same day. ## 1. Affitor: best for starting from zero on Stripe ![Affitor's Partners view: active partners and applications in one table with live stats](/blog/shots/partners-table-live.png) The performance-priced option: your cost is $0 until the program produces, then a single percentage of what it produces. ### Key features - **Stripe-native tracking that outlives the cookie.** A partner click sets a first-party cookie, and the partner whose click creates the customer keeps that customer. Once the customer signs up, the customer key you send (and `affitor_customer_key` on the Stripe Checkout Session and subscription metadata) carries the attribution to later payments, so renewals do not depend on the cookie. The attribution window is set per program, 60 days by default, and is checked once, at the first attributed payment: the click must be no older than the window at signup (or at that payment, if there was no signup). Renewals of an attributed customer are not re-checked. The details are in [how Affitor tracking fits together](/docs/brand/tracking/tracking-overview). - **Built for agents as well as humans.** `npx affitor onboard` detects your stack, installs tracking, adds the sale call, and then fires a test click, lead, and sale through your live integration until it reports `integration_verified`, so you know attribution works before launch. The MCP server and SDK packages (`@affitor/mcp`, `@affitor/sdk`) are in beta. - **A marketplace and recruiting help.** Every live program gets a listing on the [Affitor marketplace](https://affitor.com/marketplace), and the Affitor team helps you recruit, onboard, and train partners ([affitor.com/join](https://affitor.com/join)). - **Partner operations without a partner manager.** One partner table shows active partners and applications in a single view; approve each application by hand or turn on Auto-approve. ### Pricing $0 per month and no setup fee. You pay $0 on the first $10,000 of affiliate revenue per program, then 3.5% of the sales affiliates drove for you (checked Oct 2026, [affitor.com/pricing](https://affitor.com/pricing)). Details are on the [pricing model page](/docs/getting-started/pricing-performance-model). Against PartnerStack the contrast is the process: **PartnerStack** sets your plan and price in a demo before your first partner sale; **Affitor** charges nothing until affiliates have brought a program $10,000. ### Pros & cons **Pros:** no fixed monthly cost, no revenue cap, no limit on partners or seats, a marketplace listing with recruiting help, and an integration an agent can complete and test. **Cons:** Affitor is an affiliate layer, not a PRM. There is no deal registration, no LMS, no MDF management; if you need those, you are back in PartnerStack territory. It reads Stripe natively; on any other billing system you wire it up through the API or SDK, while FirstPromoter connects five billing systems natively. Partners withdraw by bank transfer or Wise, with no PayPal option. And a percentage fee grows with your affiliate revenue while a flat plan stays flat until its cap, so price your own expected volume on each vendor's page before you choose. **Fits:** Stripe-based SaaS starting an affiliate program from zero, and teams that want an integration an agent can complete and prove. ## 2. Rewardful: best flat-fee default for Stripe SaaS A flat-fee tracker built around Stripe, with a 0% transaction fee and published prices. ### Key features Setup is two scripts or a native one-click integration (Rewardful is a Premier Stripe Partner). Every plan includes the REST API, unlimited affiliates, first- or last-touch attribution, coupon code tracking, and self-referral fraud detection. ### Pricing Per [rewardful.com/pricing](https://www.rewardful.com/pricing), checked October 2026: Starter at $49/mo (up to $7,500/mo in affiliate-attributed revenue, 1 campaign, up to 2 team members), Growth at $99/mo (up to $15,000/mo, unlimited campaigns and team members, branded portal and custom domain), Enterprise at $149+/mo (up to $30,000/mo on the entry Enterprise tier, phone support, one-click PayPal payouts). The transaction fee is 0% on every plan; optional Managed Payouts cost 3% of payouts. Every plan has a 14-day trial, and annual billing gives 12 months for the price of 10. **PartnerStack:** a price set in a demo. **Rewardful:** $588 for a year of Starter month to month, or $490 paid annually. ### Pros & cons **Pros:** published prices, fast setup, the API from the first plan, and a stated 0% transaction fee. **Cons:** its billing connections are Stripe and Paddle Classic; its help center says it does not support Paddle Billing. Attribution is cookie-based (first- or last-touch, with a 60-day default window you can change per campaign), so a referral depends on the cookie surviving until the customer converts. The revenue-capped plans mean success forces upgrades, and you pay $49 from day one whether or not affiliates deliver. If you are weighing it against its closest rival, read [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter); if you are weighing it against everything, read [the best Rewardful alternatives](/blog/rewardful-alternatives). **Fits:** Stripe SaaS that wants the known, simple option and is comfortable with cookie-window attribution. ## 3. FirstPromoter: best for billing beyond Stripe and Paddle The most native billing connections in the set, with a deep back office under $100. ### Key features Native connections to five billing systems (Stripe, Paddle, Chargebee, Recurly, Braintree), recurring and lifetime commissions, multi-tier commissions up to 3 levels, W-9 and W-8BEN collection in the affiliate portal, and fraud detection, all on every plan. Its APIs and webhooks are on every plan too, and its MCP server is in beta. If your billing is not Stripe, this is the strongest flat-fee option here. ### Pricing Per [firstpromoter.com/pricing](https://firstpromoter.com/pricing), checked October 2026: Starter at $49/mo (up to $5,000/mo in affiliate revenue, 3 campaigns, up to 1,000 affiliates), Business at $99/mo (up to $15,000/mo, unlimited campaigns and affiliates, 2 websites, custom dashboard domain), Enterprise from $149/mo (above $15,000/mo, 3 websites). Team members are unlimited on every plan. 14-day trial, no credit card required. **PartnerStack:** a demo before you see a price. **FirstPromoter:** $588 a year at the floor, or $490 paid annually. ### Pros & cons **Pros:** five billing connections, detailed commission rules, and tax-form collection and API access on the entry plan. **Cons:** its $5,000/mo revenue cap on Starter is the lowest of the three flat-fee trackers here, so upgrade pressure hits earliest. Starter cannot run a second website (Business allows 2). Tracking is a cookie with first- or last-click credit and a cookie life you set. Managed payouts, where FirstPromoter pays partners for you, need [Enterprise 2 and up, for SaaS companies, subject to approval](https://help.firstpromoter.com/en/articles/9998853-how-managed-auto-payouts-work). **Fits:** SaaS on Paddle, Chargebee, Recurly, or Braintree, and teams that want detailed commission rules with tax paperwork collected in the portal. ## 4. Tolt: best for unlimited affiliates The modern flat-fee pick that removes affiliate-count limits entirely. ### Key features Unlimited affiliates and referrals on every plan, more revenue headroom at $99 than Rewardful or FirstPromoter ($20,000 cap against $15,000), and wide payout rails: PayPal, Wise, local bank transfer, crypto, and wire, with auto payouts from Growth up. Tolt also has a [REST API](https://docs.tolt.com/introduction) and an MCP connection to Claude. ### Pricing Per [tolt.com/pricing](https://tolt.com/pricing), checked October 2026: Basic at $69/mo (up to $10,000/mo in affiliate revenue, 2 programs, 3 team members, manual payouts), Growth at $99/mo (up to $20,000/mo, 5 programs, auto payouts with a 2% processing fee, W-9/W-8 collection and 1099 filing), Pro at $199/mo (up to $50,000/mo, unlimited programs), Enterprise custom above that. 14-day trial, no credit card required, 30-day refund policy. **PartnerStack:** a price set in a demo. **Tolt:** $828 a year at the floor, monthly terms. ### Pros & cons **Pros:** no affiliate limits anywhere, global payout options, and the most revenue headroom at the $99 price point. **Cons:** the $69 floor is the highest of the flat-fee trio, and the "0% commission" marketing carries a nuance: auto payouts have a 2% processing fee, and the Basic plan avoids it by making every payout manual. Tax-form collection starts on Growth. Its JavaScript stores the partner click with a cookie duration, and a signup call ties that click to your customer. **Fits:** SaaS on Stripe, Paddle, or Chargebee that expects a large affiliate base early and wants global payout options. ## 5. Dub Partners: best for developer-led teams Affiliate infrastructure priced and shaped like developer tooling. ### Key features Dub's pricing page lists a REST API, an MCP server, native SDKs, and real-time event webhooks on every Partners plan, plus tax compliance handled for you, so you do not collect W-9, W-8 or 1099 forms yourself. You also get link infrastructure, analytics, and partner payouts in one platform. ### Pricing Per [dub.co/pricing](https://dub.co/pricing), checked October 2026: Business at $90/mo (up to $2,500/mo in partner payouts, 500 partners, 10 users, 10K new links and 250K tracked events a month), Advanced at $300/mo (up to $15,000/mo in payouts, unlimited partners, 20 users), Enterprise custom on annual billing (unlimited payouts, marketplace listing, SAML/SSO). The [payout fee](https://dub.co/help/article/partner-payouts) is 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise). Partners needs a paid plan; Business and Advanced start with a 14-day trial. **PartnerStack:** one price, set in a demo. **Dub:** two published ones, a subscription plus a payout fee. ### Pros & cons **Pros:** API, MCP server, SDKs, and webhooks on the entry plan; tax compliance handled; links, analytics, and payouts in one product. **Cons:** you pay twice: a $90/mo floor plus a payout fee of 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise). Payout caps meter your growth: $2,500/mo on Business means a successful program hits the ceiling fast, and Business holds 500 partners. The marketplace listing and partner network are Enterprise features. **Fits:** developer-led teams already using Dub for links, with budget for the subscription plus the payout fee. ## Which one should you pick? **$0–500K ARR: Affitor, or Rewardful for a known flat cost.** A demo-priced PRM contract at this stage is a category error. Affitor costs $0 until a program has made $10,000 through affiliates; Rewardful is the familiar $49/mo default if you prefer a fixed bill. **$500K–5M ARR: pick by billing stack and volume.** On Stripe with steady affiliate revenue, put a capped flat plan (Rewardful Growth or Tolt Growth at $99/mo) next to a percentage at your own volume and decide. Off Stripe, FirstPromoter's five billing connections decide it. Developer-led teams already on Dub can justify the subscription plus payout fee for the tooling. **$5M+ ARR with multiple partner motions: PartnerStack.** This is the stage its plans assume: a partner manager on payroll, resellers and referral partners alongside affiliates, and marketplace distribution worth paying for. Book the demo with the checklist from this page in hand. ## Every option at a glance All figures from each vendor's pricing page, checked October 2026. | Platform | Monthly floor | Fees on top | Caps to watch | Self-serve? | |---|---|---|---|---| | [PartnerStack](https://www.partnerstack.com/pricing) | Not published; set during a demo | Not published | No partner or user limit; plan limits not published | No, demo-led | | [Affitor](https://affitor.com/pricing) | $0 | 3.5% of affiliate-driven sales, after the first $10,000 per program | None | Yes | | [Rewardful](https://www.rewardful.com/pricing) | $49 | 0% transaction fee; optional Managed Payouts 3% | $7,500/mo affiliate revenue on Starter | Yes | | [FirstPromoter](https://firstpromoter.com/pricing) | $49 | None listed | $5,000/mo affiliate revenue and 1,000 affiliates on Starter | Yes | | [Tolt](https://tolt.com/pricing) | $69 | 2% on auto payouts (Growth and up) | $10,000/mo on Basic; manual payouts on Basic | Yes | | [Dub Partners](https://dub.co/pricing) | $90 | Payout fee: 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise) | $2,500/mo payouts and 500 partners on Business | Yes | :::note Affiliate software pricing drifts fast, and PartnerStack does not publish prices, so treat every figure here as checked in October 2026 and confirm against the linked pricing pages before you commit. ::: ## FAQ ### How much does PartnerStack cost? PartnerStack does not publish prices. Its pricing page lists three plans (Launch, Growth and Enterprise), each behind a demo, and says your final plan and pricing are confirmed during your demo. The price depends on your partner program size, feature needs and level of support (checked October 2026). ### What is the best PartnerStack alternative for SaaS? It depends on what you need from PartnerStack. For an early-stage SaaS, Affitor is the best fit: self-serve signup, $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales, a marketplace listing, and a team that helps you recruit partners. If you run affiliates, resellers and referral partners with a partner manager, PartnerStack itself may still be the right call. ### Is there a PartnerStack alternative with no monthly fee? Yes. Affitor has no subscription and no setup fee: you pay $0 on the first $10,000 of affiliate revenue per program, then 3.5% of the sales affiliates drove. Rewardful, FirstPromoter, Tolt and Dub Partners charge monthly plans that start between $49 and $90 (checked October 2026). ### Does PartnerStack take a cut of partner payouts? Its pricing page lists no fees at all: every plan is priced during a demo. PartnerStack does pay partners for you: it consolidates approved commissions into a single monthly invoice and distributes the earnings. What that costs is not stated on its public pages (checked October 2026), so ask during the demo. ### Which PartnerStack alternatives are self-serve? All five alternatives on this page (Affitor, Rewardful, FirstPromoter, Tolt and Dub Partners) let you sign up yourself and publish their prices. Rewardful, FirstPromoter, Tolt and Dub Partners start with a 14-day trial, and Affitor charges nothing until a program has made $10,000 through affiliates. PartnerStack starts every plan with a demo. ## What's next If PartnerStack's category is what you need, book their demo with the checklist from this page in hand. If you need an affiliate program without the commitment, [create your program on Affitor](https://affitor.com/welcome): it costs $0 until a program has made $10,000 through affiliates, then 3.5%. Then read [how Affitor tracking fits together](/docs/brand/tracking/tracking-overview) before you install anything, and if you are starting a program from scratch, [the six-step launch guide](/blog/how-to-start-saas-affiliate-program) covers everything beyond the software choice. ## More comparisons - [Every comparison in one table](/blog/compare) - [The best Rewardful alternatives for SaaS](/blog/rewardful-alternatives) - [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter) - [FirstPromoter alternatives](/blog/firstpromoter-alternatives) - [Tolt alternatives](/blog/tolt-alternatives) - [Tolt vs Rewardful](/blog/tolt-vs-rewardful) - [PartnerStack vs Rewardful](/blog/partnerstack-vs-rewardful) - [Best affiliate software for SaaS: pricing compared](/blog/best-affiliate-software-saas) --- id: "blog/partnerstack-vs-rewardful" type: "blog" url: "https://affitor.com/blog/partnerstack-vs-rewardful" updated: "2026-10-17" --- # PartnerStack vs Rewardful: Which Should Your SaaS Pick in 2026? > One prices you in a sales demo, the other starts at $49 a month: they aren't really the same tool. A straight comparison of the enterprise PRM versus the focused affiliate app, with every price checked against both pages in October 2026, plus Affitor, the $0/month option that starts where they both charge. PartnerStack and Rewardful both show up when you search for affiliate software, but putting them side by side is a little like comparing Salesforce to a Stripe payment link: one is a partner-relationship suite priced in a sales demo, the other is a $49-a-month app you set up yourself. This page lays out what each one is, what it costs with the numbers checked in October 2026, and which one fits your stage, plus the option that charges nothing until your program works. :::tip Disclosure: we make [Affitor](https://affitor.com), which competes with both products. Affitor gets one clearly marked section near the end and one column in the summary table. Everything else comes from [PartnerStack's](https://www.partnerstack.com/pricing) and [Rewardful's](https://www.rewardful.com/pricing) own pricing pages and docs, checked in October 2026. Prices drift, and PartnerStack does not publish prices, so check the live pages before you buy. ::: ## Quick answer: PartnerStack or Rewardful? Choose by scope, not by feature list. If you need affiliate and referral tracking for a Stripe SaaS, Rewardful is the correct size: $49/month, set up with two scripts or a one-click integration, REST API on every plan. If you run a multi-type partner program (affiliates plus resellers plus referral partners) at mid-market or enterprise scale, PartnerStack's PRM suite and partner marketplace are built for exactly that, and its Enterprise plan adds a designated customer success manager. The trap is buying PartnerStack's scope before you have the partner motion to fill it. And if you are early enough that even $49/month of fixed cost feels premature, Affitor charges $0 until a program has made $10,000 through affiliates. | Tool | Best for | From price (checked Oct 2026) | Billing model | Setup | |---|---|---|---|---| | [PartnerStack](https://www.partnerstack.com/pricing) | Mid-market/enterprise B2B running many partner types | Not published; set during a demo | Plan priced in a demo | Demo, then onboarding in weeks | | [Rewardful](https://www.rewardful.com/pricing) | Stripe SaaS that just needs affiliates | $49/mo | Subscription, self-serve | Self-serve: two scripts or a one-click integration | | [Affitor](https://affitor.com/pricing) | SaaS that wants to pay when it works | $0/mo, then 3.5% after $10,000 per program | Performance fee, no subscription | Self-serve or agent-installed | ## The real difference: PRM suite vs affiliate app The pricing gap is not a discount or a markup: it reflects two different products. **PartnerStack is a partner-relationship management platform.** Affiliate tracking is one feature inside it: on Launch you pick affiliate link tracking or lead and deal registration, and Enterprise runs both. The rest is the reason it costs what it does: marketplace access pitched as "Get discovered by active B2B partners", partner payments, onboarding and training tools, CRM integrations, and on Growth a learning management system, partner challenges, and market-development-fund (MDF) management. You buy PartnerStack when "affiliates" is one of several partner types you manage, and when partner sourcing itself is a channel you invest in. **Rewardful is a focused affiliate app.** It tracks affiliate and referral conversions for Stripe (and Paddle Classic), lets you pay commissions by PayPal or Wise bulk payouts or through its optional Managed Payouts, and gives each affiliate a dashboard, and it stops there, deliberately. That focus is why it sets up in minutes and costs $49 to start. You buy Rewardful when you want an affiliate program running this week without a sales call. Neither is "better." They answer different questions. The mistake is letting a comparison article flatten them onto one axis. ## Pricing, checked October 2026 **Rewardful** is straightforward and self-serve ([rewardful.com/pricing](https://www.rewardful.com/pricing)): - **Starter, $49/mo:** up to $7,500/mo in affiliate-attributed revenue, 1 campaign, up to 2 team members - **Growth, $99/mo:** up to $15,000/mo, unlimited campaigns and team, branded portal, custom domain - **Enterprise, $149+/mo:** up to $30,000/mo on the entry Enterprise tier, phone support, one-click PayPal payouts - A 0% transaction fee on every plan (optional Managed Payouts cost 3% of payouts), a 14-day trial, 12 months for the price of 10 on annual billing, and its REST API included even on the $49 plan. **PartnerStack** publishes plans but no prices ([partnerstack.com/pricing](https://www.partnerstack.com/pricing)): - **Launch:** affiliate link tracking or lead and deal registration (pick one), marketplace access, an AI and MCP connector, partner payments, onboarding and training tools, CRM integrations - **Growth:** adds advanced integrations, a learning management system, partner challenges and incentives, MDF management, advanced partner segmentation - **Enterprise:** full access to link tracking and lead and deal registration, custom workflows, a designated CSM Every plan starts with a demo: "Your final plan and pricing are confirmed during your demo." The page states no limit on partners or internal users, and its FAQ says most teams are up and running "in weeks." (Third-party reports of a per-commission cut circulate, but PartnerStack does not state one on its pages, so we do not assert it.) The honest read: these two are not competing for the same buyer, and the pricing process says so. One publishes a $49 plan you can start today; the other prices your program in a demo. ## Attribution **Rewardful** uses cookie-based attribution with a [60-day default window](https://help.rewardful.com/en/articles/2155812-how-long-are-referral-cookies-valid) you can change per campaign, and lets you choose first-touch or last-touch credit. It is simple and well understood, and it shares the cookie cohort's blind spot: when a buyer clears cookies, blocks them, or switches devices before converting, the affiliate can silently lose credit. **PartnerStack's** Launch plan offers affiliate link tracking or lead and deal registration, and for Stripe its docs describe a webhook that listens for charge and subscription events. Beyond that we will not describe its attribution model: for an enterprise PRM it is usually part of the implementation conversation with their team rather than a published spec. If attribution durability is a deciding factor, that is worth a direct question to each vendor, and it is the specific gap Affitor is built around, below. ## Where Affitor fits We build [Affitor](https://affitor.com), so read this section knowing that. It is not trying to be PartnerStack's PRM suite, and it undercuts Rewardful's model rather than matching its feature list. - **No subscription.** $0/month, no setup fee, and $0 on the first $10,000 of affiliate revenue per program, then 3.5% of affiliate-driven sales ([affitor.com/pricing](https://affitor.com/pricing), checked Oct 2026). You pay nothing until the program has already paid for itself. - **Attribution that outlives the cookie after signup.** A partner click sets a first-party cookie, and the partner whose click creates the customer keeps that customer; once the customer signs up, the customer key you send rides Stripe metadata as `affitor_customer_key`, so later payments are matched to the customer rather than to the cookie. The attribution window is set per program, 60 days by default, and is checked once, at the first attributed payment: the click must be no older than the window at signup (or at that payment, if there was no signup). Renewals of an attributed customer are not re-checked. Details in [how Affitor tracking fits together](/docs/brand/tracking/tracking-overview). - **A marketplace and recruiting help.** Every live program is listed on the [Affitor marketplace](https://affitor.com/marketplace), and the Affitor team helps you recruit, onboard, and train partners ([affitor.com/join](https://affitor.com/join)). - **One flat partner surface.** Active partners and applications live in a single table; approve each application by hand or turn on Auto-approve. - **Agent-installable and self-verifying.** Affitor ships a CLI and an MCP server (beta): `npx affitor onboard` installs click, lead, and sale tracking and then fires a test click, lead, and sale that reports `integration_verified` before a real partner joins. Affitor is the wrong tool if you need deal registration for resellers or MDF management: that is PartnerStack's territory. It is the right tool if you want an affiliate program that costs nothing until it works, with a marketplace listing and recruiting help, and that an agent can stand up for you. See the [guide to starting a program](/blog/how-to-start-saas-affiliate-program) or [sign up](https://affitor.com/welcome). ## Who should pick which - **Pre-revenue or early SaaS, just need affiliates:** Rewardful at $49/month, or Affitor at $0/month if you would rather not pay a fixed cost before the program earns. - **Growing SaaS on Stripe, affiliates are the whole motion:** Rewardful or Affitor. Decide on subscription-vs-performance pricing and on how each carries a referral after signup. - **Mid-market/enterprise B2B with resellers, referral partners, and affiliates together:** PartnerStack. The PRM scope is the point, and the price buys the marketplace and, on Enterprise, a designated CSM. - **You want an agent to install and verify tracking for you:** Affitor ships that path today with `npx affitor onboard`. ## Verify the numbers yourself Every price on this page was checked against each vendor's pricing page in October 2026: [PartnerStack](https://www.partnerstack.com/pricing) (plans priced during a demo) and [Rewardful](https://www.rewardful.com/pricing) ($49/$99/$149+, 0% transaction fee). PartnerStack does not publish prices, so re-check it before you commit. For every head-to-head we have published, see [the compare hub](/blog/compare). ## FAQ **Is PartnerStack more expensive than Rewardful?** PartnerStack does not publish prices: every plan is priced during a demo, based on your program size, feature needs and level of support (checked October 2026). Rewardful publishes its prices, from $49/month. They price so differently because they are different categories of product: PartnerStack is a partner-relationship management suite, Rewardful a focused affiliate app for Stripe SaaS. **What is the difference between PartnerStack and Rewardful?** PartnerStack is a partner-relationship management (PRM) platform: affiliate link tracking or lead and deal registration, marketplace access and partner payments, plus an LMS and MDF management on Growth and a designated CSM on Enterprise, built for B2B SaaS running many partner types at once. Rewardful does one thing: affiliate and referral tracking for Stripe SaaS, set up with two scripts or a one-click integration. If affiliates are your whole motion, Rewardful is the right size; if you run resellers and referral partners too, PartnerStack is built for that scope. **Does PartnerStack have a trial?** Its pricing page lists no trial (checked October 2026): every plan starts with a demo. Rewardful offers a 14-day trial. Affitor has no subscription to trial: you pay $0 on the first $10,000 of affiliate revenue per program, then 3.5% of affiliate-driven sales. **Which is best for an early-stage SaaS, PartnerStack or Rewardful?** For a pre-revenue or early SaaS, a demo-priced PRM contract is hard to justify. Rewardful at $49/month is a sane starting point, and Affitor costs $0 until a program has made $10,000 through affiliates. PartnerStack earns its price once you run multi-type partner programs at mid-market or enterprise scale. **Is there an alternative to PartnerStack and Rewardful with no subscription?** Affitor: $0/month, $0 on the first $10,000 of affiliate revenue per program, then 3.5% of affiliate-driven sales. Every live program gets a marketplace listing, the Affitor team helps you recruit, onboard and train partners, and an AI agent can install tracking and verify it with a test sale from the command line. ## More comparisons - [Every comparison in one table](/blog/compare) - [The best Rewardful alternatives for SaaS](/blog/rewardful-alternatives) - [PartnerStack alternatives](/blog/partnerstack-alternatives) - [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter) - [FirstPromoter alternatives](/blog/firstpromoter-alternatives) - [Tolt alternatives](/blog/tolt-alternatives) - [Tolt vs Rewardful](/blog/tolt-vs-rewardful) - [Best affiliate software for SaaS: pricing compared](/blog/best-affiliate-software-saas) --- id: "blog/rewardful-alternatives" type: "blog" url: "https://affitor.com/blog/rewardful-alternatives" updated: "2026-10-17" --- # Best Rewardful Alternatives for SaaS in 2026 (5 Tools Compared) > Five honest Rewardful alternatives for SaaS on Stripe: Affitor, FirstPromoter, Tolt, Dub Partners, and PartnerStack. Pricing checked October 2026, attribution trade-offs, and a straight answer on who should pick what. SaaS teams leave Rewardful for three reasons: revenue caps that force plan upgrades as you grow, cookie-based attribution that drops conversions when the cookie is lost, and a narrower feature set than some rivals. If none of those hurt yet, keep Rewardful. Setup is two scripts or a one-click Stripe integration, the transaction fee is 0%, and the REST API is included on every plan, including the $49 one. Plenty of programs never need more. This guide compares five alternatives worth shortlisting in 2026: Affitor, FirstPromoter, Tolt, Dub Partners, and PartnerStack. One disclosure before we start: we build Affitor. It is one of the five tools below, and this post tells you plainly where the others beat it. ## Quick answer: what is the best Rewardful alternative for SaaS? For SaaS that wants to pay $0 until affiliates have made a program its first $10,000, Affitor is the best fit. Pick FirstPromoter if you bill outside Stripe, Tolt if you want unlimited affiliates on a flat subscription, Dub Partners if developer tooling decides your stack, and PartnerStack if you run a multi-type partner program with an enterprise budget. Stay on Rewardful if its revenue caps and cookie attribution do not hurt you yet. | Tool | Best for | From price (checked Oct 2026) | Fees on top | How it tracks | |---|---|---|---|---| | [Affitor](https://affitor.com/pricing) | Paying on results | $0/mo | 3.5% of affiliate-driven sales after the first $10,000 per program | Click cookie (60-day default), then the signup customer key | | [FirstPromoter](https://firstpromoter.com/pricing) | Billing beyond Stripe and Paddle | $49/mo | None listed | Cookie life up to 9,999 days, first- or last-click | | [Tolt](https://tolt.com/pricing) | Unlimited affiliates on a flat fee | $69/mo | 2% on auto payouts | Cookie with a set duration, plus a signup call | | [Dub Partners](https://dub.co/pricing) | Developer-first teams | $90/mo | Payout fee: 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise) | Links with conversion tracking | | [PartnerStack](https://www.partnerstack.com/pricing) | Enterprise multi-type programs | Not published; set during a demo | Not published | Link tracking or lead and deal registration | Every price on this page was checked against each vendor's pricing page in October 2026. Affiliate software pricing moves fast, and PartnerStack does not publish prices, so treat the live pages as the source of truth. ## Why teams outgrow Rewardful Rewardful's model is a flat subscription with revenue-capped plans. Per [rewardful.com/pricing](https://www.rewardful.com/pricing), checked October 2026: Starter is $49/mo for up to $7,500/mo in affiliate-attributed revenue, with 1 campaign and up to 2 team members. Growth is $99/mo for up to $15,000/mo, with unlimited campaigns, a branded affiliate portal, and a custom domain. Enterprise starts at $149/mo and covers up to $30,000/mo on its entry tier. There is no $0 plan; every plan has a 14-day trial. The 0% transaction fee is genuine: the subscription is what you pay Rewardful, and its optional Managed Payouts cost 3% of payouts. The caps are the first thing that bites. A program doing well crosses $7,500/mo in affiliate revenue and the tool's price doubles, not because you used more software but because your affiliates performed. Cross $15,000/mo and it steps again. The second issue is attribution. Rewardful tracks with cookies, with first- or last-touch credit and a [60-day default window](https://help.rewardful.com/en/articles/2155812-how-long-are-referral-cookies-valid) you can change per campaign. When the cookie is gone (cleared, blocked, expired, or the buyer switches devices) before the customer converts, the referral is gone with it, and the affiliate who earned the sale does not get paid. The third is the feature set. Rewardful covers the core well: coupon code tracking, double-sided incentives, and self-referral fraud detection are on every plan. But its plan table lists no multi-tier commissions, which FirstPromoter lists on every plan, and its billing connections are Stripe and Paddle Classic, not Paddle Billing. ## What to evaluate in a replacement Three questions separate the five tools below faster than any feature checklist. **How does it charge?** Flat subscription, percentage of results, or both. Watch for double tolls: some tools charge a subscription and then add a fee on payouts or transactions on top. **What happens when the cookie dies?** Every tool here starts from a partner click. The difference is what carries the referral afterwards: a browser cookie all the way to each sale, or a customer record that the signup ties to the partner, which later payments match against. **Can your coding agent do the integration?** In 2026 a lot of Stripe SaaS integration work is done by AI agents. By October 2026 most tools here have an MCP server of some kind: Dub on Business, a Tolt connection to Claude, FirstPromoter in beta, PartnerStack on Launch, and Affitor in beta, while Rewardful's MCP server covers its developer docs. The question to ask is whether an agent can install tracking and then prove it works with a test sale. ## 1. Affitor: best for paying on results ![Affitor's Partners view: active partners and applications in one table with live stats](/blog/shots/partners-table-live.png) Affitor is our product, so here is the model stated plainly: you pay nothing until your affiliate program pays you. ### Key features Tracking starts like the rest: a partner click sets a first-party cookie, and the partner whose click creates the customer keeps that customer. What carries the referral after that is the signup: you send your own customer key, it rides Stripe Checkout and subscription metadata as `affitor_customer_key`, and later payments are matched to the customer rather than to the cookie. The attribution window is set per program, 60 days by default, and is checked once, at the first attributed payment: the click must be no older than the window at signup (or at that payment, if there was no signup). Renewals of an attributed customer are not re-checked. The chain is documented in [how Affitor tracking fits together](/docs/brand/tracking/tracking-overview). The agent surface is live today: a `skill.md` runbook an agent can follow end to end, the `affitor` CLI, browser and server SDKs plus an MCP server (`@affitor/sdk` and `@affitor/mcp`, both labeled beta), and `npx affitor onboard`, which installs tracking and then fires a test click, lead, and sale through your live integration until it reports `integration_verified`. You (or your agent) get proof the integration works before a real affiliate joins. The full setup path is walked in [How to create a Stripe affiliate program](/blog/stripe-affiliate-program). ![Affitor advertiser dashboard: performance overview tracking revenue, partners, clicks, signups, and paid customers for one program](/docs/brand/dashboard.png) Every live program is listed on the [Affitor marketplace](https://affitor.com/marketplace), and the Affitor team helps you recruit, onboard, and train partners ([affitor.com/join](https://affitor.com/join)). Day-to-day operations stay deliberately small: one partner table holds active partners and applications, and you approve each application by hand or turn on Auto-approve. ### Pricing $0/mo, no setup fee, and nothing per partner or per seat. You pay $0 on the first $10,000 of affiliate revenue per program, then 3.5% of the sales affiliates drove (checked Oct 2026, [affitor.com/pricing](https://affitor.com/pricing)). If your affiliates generate nothing, you pay nothing. There are no tiers and no revenue caps. ### Pros & cons **Pros:** no subscription and no caps, so cost follows results; renewals stay attributed after the cookie is gone; a marketplace listing with recruiting help; an integration an agent can complete and test with a synthetic sale. **Cons:** a percentage fee grows with your affiliate revenue, while a flat subscription stays flat until its cap, so price your own expected volume on both pricing pages before you choose. Affitor reads Stripe natively; on another billing system you wire it up through its API or SDK, while FirstPromoter connects five billing systems natively. Partners withdraw by bank transfer or Wise, where Rewardful offers PayPal mass payouts and Wise bulk payouts on every plan. **Rewardful:** $49 to $149+/mo from day one, 0% transaction fee, cookie attribution. **Affitor:** $0/mo, 3.5% of affiliate-driven sales after the first $10,000 per program, a click cookie and then the signup customer key. ## 2. FirstPromoter: best for billing providers beyond Stripe FirstPromoter is the practical answer when your billing stack rules Rewardful out, and it lists commission and tax features Rewardful's plan table does not. ### Key features Native connections to five billing systems (Stripe, Paddle, Chargebee, Recurly, Braintree), recurring and lifetime commissions, multi-tier commissions up to 3 levels, W-9 and W-8BEN collection in the affiliate portal, fraud detection, and APIs with webhooks, all on every plan. Its MCP server is in beta. A custom dashboard domain arrives on the Business plan. ### Pricing Per [firstpromoter.com/pricing](https://firstpromoter.com/pricing), checked October 2026: Starter is $49/mo for up to $5,000/mo in affiliate revenue, 3 campaigns, and up to 1,000 affiliates. Business is $99/mo for up to $15,000/mo with unlimited campaigns and affiliates and 2 websites. Enterprise starts at $149/mo above that. Team members are unlimited on every plan. 14-day trial, no credit card required. No transaction fee is listed on the pricing page. ### Pros & cons **Pros:** five native billing connections; multi-tier and recurring commission rules; tax-form collection and fraud detection on every plan; 3 campaigns on the entry plan where Rewardful allows 1 (FirstPromoter's campaigns are promoter groups with their own commissions). **Cons:** the $5,000/mo cap on Starter is the lowest of the three flat-fee trackers here, so upgrade pressure arrives earliest. A second website needs Business, one-click PayPal payouts need Business, and managed payouts (FirstPromoter pays partners for you) need [Enterprise 2 and up, for SaaS companies, subject to approval](https://help.firstpromoter.com/en/articles/9998853-how-managed-auto-payouts-work). Tracking is a cookie with first- or last-click credit and a cookie life you set. For the full head-to-head with Rewardful, see [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter). **FirstPromoter:** API and webhooks on every plan, from $49/mo. **Affitor:** API, CLI, and a beta MCP server at $0/mo on every program. ## 3. Tolt: best for unlimited affiliates on a flat fee Tolt is a clean modern product in the Rewardful mold, and it removes the affiliate-count question entirely. ### Key features Unlimited affiliates and referrals on every plan. Payout rails are the broadest here: PayPal, Wise, local bank transfer, crypto, and wire, with auto payouts from the Growth plan up. At $99/mo Tolt gives you more revenue headroom than Rewardful's $99 plan ($20,000 vs $15,000 cap). Tolt also has a [REST API](https://docs.tolt.com/introduction) and an MCP connection to Claude. ### Pricing Per [tolt.com/pricing](https://tolt.com/pricing), checked October 2026: Basic is $69/mo for up to $10,000/mo in affiliate revenue with 2 programs and manual payouts. Growth is $99/mo for up to $20,000/mo with 5 programs, auto payouts, and W-9/W-8 collection with 1099 filing. Pro is $199/mo for up to $50,000/mo with unlimited programs. 14-day trial, no credit card required, 30-day refund policy. ### Pros & cons **Pros:** unlimited affiliates everywhere, wide payout rails, and the most revenue headroom of the flat-fee trio at $99. **Cons:** the nuance sits in the payout fees. Tolt markets "0% commission", and that claim has a footnote: auto payouts carry a 2% processing fee, and the Basic plan avoids the fee because its payouts are manual. Tax-form collection starts on Growth. Tracking starts from a cookie: its JavaScript stores the partner click with a cookie duration, and a signup call ties that click to your customer. **Tolt:** $69 to $199/mo, plus 2% on auto payouts. **Affitor:** $0/mo, one 3.5% fee on affiliate-driven sales after the first $10,000 per program. ## 4. Dub Partners: best for developer-first teams Dub is affiliate infrastructure shaped like developer tooling. ### Key features Dub's pricing page lists a REST API, an MCP server, native SDKs, and real-time event webhooks on every Partners plan, plus tax compliance handled for you, so you do not collect W-9, W-8 or 1099 forms yourself. If you already run Dub for link infrastructure, adding Partners keeps links, analytics, and payouts in one platform. ### Pricing Per [dub.co/pricing](https://dub.co/pricing), checked October 2026: Partners needs a paid plan. Business is $90/mo with partner payouts up to $2,500/mo and up to 500 partners. Advanced is $300/mo with payouts up to $15,000/mo and unlimited partners. Enterprise is custom, billed annually, with unlimited payouts and a marketplace listing. The [payout fee](https://dub.co/help/article/partner-payouts) is 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise). ### Pros & cons **Pros:** API, MCP server, SDKs, and webhooks on the entry plan; tax compliance handled; one platform for links, analytics, and payouts. **Cons:** the toll structure. You pay the subscription and a payout fee of 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise), and the payout caps meter your program's growth by plan: a Business-plan program cannot pay partners more than $2,500 in a month. The marketplace listing and partner network are Enterprise features. **Dub Partners:** $90/mo plus a payout fee of 5% if you fund payouts by ACH or 8% by card, capped by plan. **Affitor:** $0/mo plus 3.5% of affiliate-driven sales after the first $10,000 per program, no revenue cap. ## 5. PartnerStack: best for enterprise partner programs PartnerStack is not really a Rewardful substitute; it is a different category, priced like one. ### Key features A full partner-relationship-management suite ([pricing page](https://www.partnerstack.com/pricing), checked Oct 2026): PartnerStack Marketplace access on every plan, affiliate link tracking or lead and deal registration on Launch (both on Enterprise), partner payments, an MCP connector, and on Growth a learning management system, partner challenges, and MDF management. If you run affiliates, resellers, and referral partners as one program at scale, it is the serious option on this page. ### Pricing PartnerStack does not publish prices. Per [partnerstack.com/pricing](https://www.partnerstack.com/pricing), checked October 2026, Launch, Growth, and Enterprise all start with a demo, and "Your final plan and pricing are confirmed during your demo." Pricing depends on program size, feature needs, and level of support. Its FAQ says there is no limit on partners or internal users. ### Pros & cons **Pros:** marketplace distribution, multi-type partner motions, and enterprise operations no point tool on this page attempts. **Cons:** the process. You see a price after a demo, and its FAQ says most teams are up and running in weeks. For Stripe, its docs describe a webhook that listens for charge and subscription events; we make no other claims about its attribution. For an early or mid-stage SaaS replacing a $49 tool, this is the wrong aisle; for a partnerships team that has outgrown a pure affiliate motion, it is the right one. If PartnerStack's process is the reason you are here, the dedicated [PartnerStack alternatives guide](/blog/partnerstack-alternatives) goes deeper. **PartnerStack:** priced in a demo, full PRM suite. **Affitor:** self-serve signup, $0/mo, affiliate programs without the PRM layer. ## Which one should you pick? The honest segmentation is by stage, because the pricing models behave differently as affiliate revenue grows. **$0–500K ARR: pick Affitor, or Rewardful if you want a known flat cost.** At this stage your affiliate program earns little or nothing yet, and a $49–$90 subscription is pure downside risk. Affitor costs $0 until a program has made $10,000 through affiliates, so the software decision needs no budget. If you would rather pay a predictable $49/mo for a familiar tool, Rewardful is the default. **$500K–5M ARR: compare at your own volume.** If affiliate-driven revenue is steady, a capped flat plan is predictable: Rewardful Growth at $99/mo covers up to $15,000/mo, and Tolt's $99 plan covers $20,000/mo with unlimited affiliates. If you bill through Chargebee, Recurly, or Braintree, FirstPromoter's native connections decide it. If affiliate revenue is still lumpy, Affitor's pay-on-results model keeps quiet months at $0. **$5M+ ARR: think in programs, not trackers.** If you run affiliates plus resellers plus referral partners with a partner manager, PartnerStack's PRM suite is the real option. If it is still a pure affiliate motion, the Enterprise plans of Rewardful ($149+/mo) or FirstPromoter (from $149/mo), or Dub's custom Enterprise with its lower payout fees (3% by ACH, 6% by card), cover the volume. ## Every alternative at a glance :::note All prices checked against each vendor's pricing page in October 2026. PartnerStack does not publish prices. Check the live page before you commit. ::: | Platform | Monthly price | Fees on top | Caps | How it tracks | API and agent surface | |---|---|---|---|---|---| | **[Affitor](https://affitor.com/pricing)** | $0 | 3.5% of affiliate-driven sales after the first $10,000 per program | None | Click cookie (60-day default), then the signup customer key | API, CLI, beta MCP, test sale that returns `integration_verified` | | **[Rewardful](https://www.rewardful.com/pricing)** | $49 / $99 / $149+ | 0%; optional Managed Payouts 3% | $7.5K / $15K / $30K (entry Enterprise) per mo affiliate revenue | Cookie, 60-day default, first- or last-touch | REST API on every plan; MCP for its docs | | **[FirstPromoter](https://firstpromoter.com/pricing)** | $49 / $99 / $149+ | None listed | $5K / $15K per mo affiliate revenue | Cookie up to 9,999 days, first- or last-click | API and webhooks on every plan; MCP in beta | | **[Tolt](https://tolt.com/pricing)** | $69 / $99 / $199 | 2% on auto payouts | $10K / $20K / $50K per mo affiliate revenue | Cookie with a set duration, plus a signup call | REST API; MCP connection to Claude | | **[Dub Partners](https://dub.co/pricing)** | $90 / $300 / custom | Payout fee: 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise) | Payouts $2.5K / $15K per mo | Links with conversion tracking | REST API, MCP server, native SDKs | | **[PartnerStack](https://www.partnerstack.com/pricing)** | Set during a demo | Not published | Not published | Link tracking or lead and deal registration | REST API; MCP connector on Launch | ## FAQ ### What is the best Rewardful alternative for SaaS? It depends on why you are leaving. For SaaS that wants no monthly fee, Affitor is the best fit: $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales. FirstPromoter is the strongest pick when you bill outside Stripe, and Tolt when you want unlimited affiliates and more revenue headroom on a flat subscription. ### How does Affitor's pricing compare with Rewardful's? They charge in different shapes. Affitor has no subscription: $0 on the first $10,000 of affiliate revenue per program, then 3.5% of affiliate-driven sales. Rewardful charges a monthly plan by affiliate-revenue tier ($49, $99 or $149+) with a 0% transaction fee (checked October 2026). A new program pays nothing on Affitor until it has made $10,000 through affiliates; after that, compare both at your own monthly volume. ### Does Rewardful charge transaction fees? No. Rewardful states a 0% transaction fee on affiliate-attributed revenue on every plan ($49, $99 or $149+ a month, checked October 2026). Optional Managed Payouts cost 3% of payouts, and payment-provider fees are separate. The trade-off is revenue-capped plans: $7,500 a month in affiliate revenue on Starter, $15,000 on Growth, and $30,000 on the entry Enterprise tier. ### Which affiliate software has no monthly fee? In this comparison, Affitor: $0 a month, $0 on the first $10,000 of affiliate revenue per program, then 3.5% of affiliate-driven sales. The others charge a monthly plan: Rewardful $49, FirstPromoter $49, Tolt $69, Dub Partners $90, and PartnerStack prices every plan in a demo. Outside this comparison, PromoteKit has a $0 plan for up to 3 referrals and Endorsely a $0 plan below $1,000 a month in affiliate revenue (checked October 2026). ### How much does affiliate tracking software cost in 2026? Entry prices checked October 2026: Rewardful and FirstPromoter $49/month, Tolt $69/month, Dub Partners $90/month plus a payout fee of 5% if you fund payouts by ACH or 8% by card, PartnerStack priced during a demo, and Affitor $0/month with 3.5% of affiliate-driven sales after the first $10,000 per program. Prices in this category change often, and PartnerStack does not publish prices (checked October 2026). ### Why do SaaS teams leave Rewardful? Three common reasons: revenue-capped plans that force upgrades as affiliate sales grow, cookie-based attribution (60-day default window) that loses the referral when the cookie is gone before the customer converts, and a narrower feature set than FirstPromoter, whose plans list multi-tier commissions and five native billing connections. ## What's next The short version: stay on Rewardful if its caps and cookie model do not hurt you yet. Pick FirstPromoter for billing providers beyond Stripe and Paddle or for tax forms. Pick Tolt for unlimited affiliates and broad payout rails at a flat price. Pick Dub Partners if you already live in Dub's link infrastructure and accept the payout fee. Pick PartnerStack when you are running a multi-type partner program with an enterprise budget. Pick Affitor if you want to pay when your affiliates generate revenue and not before, keep renewals attributed after the cookie is gone, or hand the whole integration to an agent and get back proof it works. If the performance model fits your stage, [create your program](https://affitor.com/welcome). It costs nothing to run until a program has made $10,000 through affiliates, so the way to evaluate Affitor is to launch with it. If you want to see how Affitor tracking works before you decide, [read the tracking docs](/docs/brand/tracking/tracking-overview). The click, signup, and sale chain is documented end to end, including the test that proves your integration is live. ## More comparisons - [Every comparison in one table](/blog/compare) - [PartnerStack alternatives](/blog/partnerstack-alternatives) - [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter) - [FirstPromoter alternatives](/blog/firstpromoter-alternatives) - [Tolt alternatives](/blog/tolt-alternatives) - [Tolt vs Rewardful](/blog/tolt-vs-rewardful) - [PartnerStack vs Rewardful](/blog/partnerstack-vs-rewardful) - [Best affiliate software for SaaS: pricing compared](/blog/best-affiliate-software-saas) --- id: "blog/rewardful-vs-dub" type: "blog" url: "https://affitor.com/blog/rewardful-vs-dub" updated: "2026-10-17" --- # Rewardful vs Dub: Pricing, Fees and Features Compared (Checked Oct 2026) > Rewardful starts at $49 a month with a 0% transaction fee and unlimited affiliates. Dub Partners starts at $90 a month plus a 5% payout fee, and sends payouts and handles tax forms on that plan. Prices, limits and features checked on both pricing pages on October 12, 2026. Pick [Rewardful](https://www.rewardful.com/pricing) if you sell through Stripe or Paddle Classic and want a flat $49 a month with a 0% transaction fee and unlimited affiliates. Pick [Dub Partners](https://dub.co/pricing) if you want Dub to send partner payouts and handle tax forms on its entry plan, with links and analytics in the same product, at $90 a month plus 5% of the payouts you fund by ACH. Both checked on October 12, 2026. | Tool / Platform | Entry price | Fee on top | Revenue cap
The most affiliate revenue, payouts or ARR the entry plan covers before you move up. | Minimum term
Shortest commitment on the entry plan, from the vendor's pricing page or terms. | Billing | | --- | --- | --- | --- | --- | --- | | [Rewardful](https://www.rewardful.com/pricing)
Starter, 14-day trial | $49/mo | 0%
3% if Rewardful runs payouts | $7,500/mo
affiliate revenue on Starter | None | Stripe, Paddle Classic | | [Dub Partners](https://dub.co/pricing)
Business, 14-day trial | $90/mo | 5% of payouts funded by ACH
8% if funded by card; 3% and 6% on Enterprise | $2,500/mo in payouts
500 partners on Business | None | Stripe, Shopify; others through the API | | [Affitor](https://affitor.com/pricing)
until a program has made $10,000 through affiliates | $0 | 3.5% of affiliate-driven sales
after the first $10,000 per program | None | None | Stripe with no code; other billing through the API or SDK |
Entry plans as listed on each vendor's pricing page on Oct 12, 2026; the tool name links to it. Rewardful's cap counts affiliate revenue and Dub's counts the payouts you send partners, so the two caps measure different things. We make Affitor; it sits in the last row of each table for reference, and the section Where Affitor fits covers it. ## Where Rewardful is stronger - **Lower entry price.** Starter is $49 a month, or $490 a year, against $90 a month for Dub's Business plan. - **No fee by default.** Rewardful states a 0% transaction fee; its optional Managed Payouts cost 3%. Dub charges 5% on payouts you fund by ACH and 8% by card (3% and 6% on Enterprise). - **Unlimited affiliates on every plan.** Dub's Business plan holds 500 partners. - **Paddle Classic next to Stripe.** Rewardful is a Premier Stripe Partner with two-way Stripe sync. - **PayPal mass payouts.** Dub offers PayPal payouts in 14 countries. The limits to know: Starter covers up to $7,500 a month in affiliate revenue, with 1 campaign and 2 team members. Growth is $99 for up to $15,000, and it is where the branded portal, custom domain and private campaigns start. ## Where Dub Partners is stronger - **Payouts and tax forms on the entry plan.** Business sends partner payouts for you, with the fee above, and Dub says it handles W-9, W-8 and 1099 forms. On Rewardful, payouts and tax info go through Managed Payouts at 3%. - **An MCP server on Business**, next to the REST API. Rewardful has a REST API on every plan; its MCP server covers its developer docs. - **Importers.** Dub imports partners from Rewardful, PartnerStack, FirstPromoter, Tolt, Tapfiliate and Lemon Squeezy. Rewardful's support team imports affiliate accounts from a file you send. - **More seats.** Business includes 10 users, against 2 team members on Rewardful Starter. - **Links, analytics and payouts in one product**, since Dub Partners runs on Dub's link platform. - **A marketplace listing and partner discovery**, on Enterprise. Rewardful lists neither in its plan table. The limits to know: Business covers $2,500 a month in partner payouts, and when you hit your plan's payout limit you can't send more payouts until the next billing period. Advanced is $300 a month with up to $15,000. ## Partners and payouts How many partners and teammates the entry plan holds, whether the vendor helps you find partners, and who sends the money. Hover a column for what it checks. | Tool / Platform | Partners
No limit on affiliates on the entry plan. | Seats
No limit on team members on the entry plan. | Marketplace
The vendor lists your program in a marketplace or directory affiliates browse. | Finds affiliates
A network, matching or outreach service that recruits partners. | Payouts
The vendor sends money to affiliates for you. | PayPal
Affiliates can be paid by PayPal through the tool. | Tax forms
Collects W-9/W-8 forms or files 1099s. | | --- | --- | --- | --- | --- | --- | --- | --- | | [Rewardful](https://www.rewardful.com/pricing) | Yes
all plans | Partial
2 on Starter | No
not in plan table | No
not in plan table | Partial
3% fee | Yes
mass payouts | Partial
Managed Payouts, 3% | | [Dub Partners](https://dub.co/pricing) | Partial
500 on Business | Partial
10 on Business | Partial
Enterprise | Partial
Enterprise | Partial
5% payout fee | Partial
14 countries | Yes
Business plan | | [Affitor](https://affitor.com/pricing) | Yes
unlimited | Yes
unlimited | Yes
every live program | Yes
team service | Yes
bank or Wise | No
bank or Wise | Yes
W-8BEN, W-8BEN-E or W-9 |
## Tracking and setup Both read sales from Stripe natively and credit sales to coupon codes: Rewardful on every plan, Dub through Stripe promotion codes. The differences are other billing systems, the MCP server and how you bring partners from the tool you use today. Hover a column for what it checks. | Tool / Platform | Stripe
Reads sales from Stripe natively. | Other billing
Native support for Paddle, Chargebee, Recurly, Braintree or others. | Coupons
Credits a sale to an affiliate by coupon or promo code. | REST API
A public REST API on the entry plan. | MCP
An official MCP server for AI agents. | Importer
Imports affiliates, links or history from another affiliate tool. | | --- | --- | --- | --- | --- | --- | --- | | [Rewardful](https://www.rewardful.com/pricing) | Yes
native, Premier Partner | Yes
Paddle Classic | Yes
all plans | Yes
all plans | No
docs-search MCP | Partial
CSV via support | | [Dub Partners](https://dub.co/pricing) | Yes
native | Partial
Shopify; else API | Yes
Stripe promo codes | Yes
Business | Yes
Business | Yes
Rewardful, Tolt +4 | | [Affitor](https://affitor.com/pricing) | Yes
native, OAuth | Partial
via API/SDK | No
not stated publicly | Yes
every program | Partial
beta | No
partners rejoin |
## Which one should you pick? Choose Rewardful when your affiliates are already lined up, you bill through Stripe or Paddle Classic, and you want a known bill: $49 a month for up to $7,500 a month in affiliate revenue, then $99 for up to $15,000. Choose Dub Partners when you want Dub to send payouts and handle tax forms, you already use Dub for links, or you are moving from one of the tools it imports from; budget $90 a month plus 5% of payouts funded by ACH, and $300 a month on Advanced once payouts pass $2,500 a month. Both offer a 14-day trial and let you cancel any time. ## Where Affitor fits If neither monthly bill fits a program that has not earned yet, there is a third shape. Affitor, which we make, has no subscription: $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales, with no cap on affiliate revenue and no limit on partners or seats. Every program is listed on the [Affitor marketplace](https://affitor.com/marketplace), and the Affitor team helps you recruit, onboard and train partners ([affitor.com/join](https://affitor.com/join)). It reads Stripe sales with no code, takes other billing systems through its API or SDK, and lets you run a test sale before launch. The trade-offs are in the tables above: there is no importer, so partners join again through your program page and get new links; payouts go out by bank transfer or Wise after a review, not PayPal; and Affitor does not track coupon codes. Affitor collects a tax form from each partner (W-8BEN, W-8BEN-E or W-9) before the first payout. Details are on the [pricing page](https://affitor.com/pricing). ## FAQ ### How do Rewardful and Dub prices compare? On the entry plans, Rewardful costs less. Rewardful Starter is $49 a month with a 0% transaction fee and covers up to $7,500 a month in affiliate revenue. Dub Partners Business is $90 a month, covers up to $2,500 a month in partner payouts, and charges 5% on payouts you fund by ACH or 8% by card. Rewardful's optional Managed Payouts cost 3%. Prices checked October 12, 2026. ### Can I move from Rewardful to Dub? Yes. Dub Partners imports partners from Rewardful, PartnerStack, FirstPromoter, Tolt, Tapfiliate and Lemon Squeezy. Moving the other way, Rewardful's support team imports affiliate accounts from a file you send them. ### Does Dub Partners handle tax forms? Yes. Dub says its Business plan handles tax compliance, so you don't send W-9, 1099 or W-8 forms yourself. On Rewardful, tax info is collected through Managed Payouts, which cost 3% (as of October 12, 2026). ### Which one has an MCP server? Dub Partners lists a REST API and an MCP server on its Business plan. Rewardful has a REST API on every plan, and its MCP server covers its developer docs (as of October 12, 2026). ### Is there an option with no monthly fee? Affitor, which we make, has no subscription: it costs nothing until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales, with no cap on affiliate revenue. It lists every program on its marketplace and reads Stripe sales with no code. It has no importer, so partners get new links, and it pays partners by bank transfer or Wise rather than PayPal (as of October 12, 2026). ## More comparisons Every head-to-head and alternatives page is on the [comparison hub](/blog/compare). Related: [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter), [Tolt vs Rewardful](/blog/tolt-vs-rewardful), [Rewardful alternatives](/blog/rewardful-alternatives), [FirstPromoter vs Dub](/blog/firstpromoter-vs-dub) and the [19-tool comparison of affiliate software and pricing](/blog/best-affiliate-software-saas). --- id: "blog/rewardful-vs-firstpromoter" type: "blog" url: "https://affitor.com/blog/rewardful-vs-firstpromoter" updated: "2026-10-17" --- # Rewardful vs FirstPromoter: Which Is Best for SaaS in 2026? > Same $49 floor, different ceilings: revenue caps, plan limits, and billing coverage decide this one. Every number checked against both pricing pages in October 2026, plus Affitor, the $0/month option neither compare page mentions. Rewardful and FirstPromoter both charge $49 a month to start, both track affiliates with cookies and let you pick first- or last-touch credit, and both publish their own comparison pages for this exact search, each with an obvious favorite. This page is the version you would send a friend: the checked numbers, the trade-offs each vendor's page leaves out, a verdict per criterion, and the one option neither of them mentions. :::tip Disclosure: we make [Affitor](https://affitor.com), which competes with both products. Affitor gets one clearly marked section near the end of this page and one column in the summary table. Everything else comes from [Rewardful's](https://www.rewardful.com/pricing) and [FirstPromoter's](https://firstpromoter.com/pricing) own pricing pages and help centers, checked in October 2026. Prices drift, so check the live pages before you buy. ::: ## Quick answer: Rewardful or FirstPromoter? Rewardful is the better pick for most Stripe SaaS in 2026: it states a 0% transaction fee plainly, gives 50% more affiliate-revenue headroom at the entry price, and has no affiliate limit on any plan. Pick FirstPromoter if you bill through Chargebee, Recurly, or Braintree, or if you want multi-tier commissions and tax-form collection on every plan. Both include an API on the $49 plan, and attribution is a tie. If you want to skip the subscription entirely, Affitor charges $0 until a program has made $10,000 through affiliates. | Tool | Best for | From price (checked Oct 2026) | Fees on top | Attribution | |---|---|---|---|---| | [Rewardful](https://www.rewardful.com/pricing) | Stripe SaaS wanting more headroom at $49 | $49/mo | 0% transaction fee; optional Managed Payouts 3% | Cookie, 60-day default, first- or last-touch | | [FirstPromoter](https://firstpromoter.com/pricing) | Billing beyond Stripe and Paddle; tax forms | $49/mo | None listed | Cookie life up to 9,999 days, first- or last-click | | [Affitor](https://affitor.com/pricing) | Paying on results | $0/mo | 3.5% after the first $10,000 of affiliate revenue per program | Click cookie (60-day default), then the signup customer key | Every number on this page was checked against each vendor's pricing page in October 2026. ## Rewardful vs FirstPromoter pricing: same floor, different ceilings Both ladders look identical from a distance: $49, then $99, then $149 and up. The differences live in what each rung caps and what it unlocks. Both vendors meter you by monthly *affiliate revenue*, meaning the revenue your affiliates generate, not your total revenue. **Rewardful** prices like this ([rewardful.com/pricing](https://www.rewardful.com/pricing), checked Oct 2026): - Starter, $49/mo: up to $7,500/mo in affiliate-attributed revenue, 1 campaign, up to 2 team members - Growth, $99/mo: up to $15,000/mo, unlimited campaigns and team members, branded affiliate portal, custom domain - Enterprise, $149+/mo: up to $30,000/mo on the entry Enterprise tier, phone support, one-click PayPal payouts Rewardful states a 0% transaction fee on every plan, plainly, on the pricing page; its optional Managed Payouts cost 3% of payouts. There is a 14-day trial, and annual billing gives 12 months for the price of 10, so Growth runs $990 a year paid annually instead of $1,188 paid month to month. There is no $0 plan. **FirstPromoter** uses the same three rungs with different limits ([firstpromoter.com/pricing](https://firstpromoter.com/pricing), checked Oct 2026): - Starter, $49/mo: up to $5,000/mo in affiliate revenue, 3 campaigns, up to 1,000 affiliates - Business, $99/mo: up to $15,000/mo, unlimited campaigns and affiliates, 2 websites, custom dashboard domain, one-click PayPal payouts - Enterprise, from $149/mo: above $15,000/mo, 3 websites, white-labeling Managed auto payouts, where FirstPromoter pays affiliates for you, need [Enterprise 2 and up, for SaaS companies, subject to approval](https://help.firstpromoter.com/en/articles/9998853-how-managed-auto-payouts-work). The trial is 14 days with no credit card required, there is no $0 plan, and team members are unlimited on every plan. FirstPromoter's pricing page lists no transaction fee; Rewardful's states one. (Rewardful's page does not say whether its trial needs a card, which is why we make that claim for FirstPromoter alone.) Look past the headline price and the entry plans ration different things. Rewardful's Starter allows 1 campaign and up to 2 team members but gives you more revenue headroom and unlimited affiliates. FirstPromoter's Starter allows 3 campaigns (promoter groups with their own commission terms), unlimited team members, and up to 1,000 affiliates, but caps revenue lower and cannot run a second website. Which constraint bites first depends on whether your bottleneck is people, programs, or sales volume. Two honest observations. First, FirstPromoter's $5,000/mo entry cap is the lowest in its peer group, so upgrade pressure arrives earliest: if your affiliates drive $6,000 in sales next month, you are over FirstPromoter's Starter cap and shopping for the $99 plan, while on Rewardful you are still $1,500 under the limit. Second, both ladders meter success. The better your program performs, the sooner you pay more, whether or not your margins moved. **Verdict: Rewardful leads on pricing.** 50% more affiliate-revenue headroom at the same $49, unlimited affiliates, and a transaction-fee policy stated in writing. ## Attribution: two cookie models, one blind spot This criterion is closer to a tie than either vendor's marketing suggests. **Rewardful** attribution is cookie-based with a [60-day default window](https://help.rewardful.com/en/articles/2155812-how-long-are-referral-cookies-valid) you can change per campaign, and you can choose first-touch or last-touch credit. That choice matters more than it sounds: first-touch pays the affiliate whose link the buyer clicked first, which protects reviewers and content sites; last-touch pays the most recent click, which tends to favor whoever the buyer touched on the way to checkout. **FirstPromoter** is also cookie-based, with first-click or last-click credit and a cookie life you can set up to 9,999 days. A 60-day window is generous: a click today still credits the affiliate if the customer converts within two months. For the common case, one browser, one device, a conversion inside the window, both systems work. The shared weakness is that cookie-based attribution breaks on cookie loss, and the failure is silent. The buyer switches devices, clears cookies, or converts after the window closes; the affiliate loses credit, and no dashboard shows you the miss. Neither vendor is worse than the other here. It is the same model with the same blind spot, so do not let either compare page convince you tracking is the reason to switch between these two. **Verdict: a tie.** The same cookie model with the same silent failure mode; tracking is not the reason to pick either. ## API and integrations: an API on both, broader billing on one **Rewardful** includes its REST API on every plan, including the $49 Starter. Its billing connections are Stripe (it is a Premier Stripe Partner) and Paddle Classic; its help center says it does not support Paddle Billing. Setup is two scripts or a one-click integration. **FirstPromoter** connects natively to five billing systems (Stripe, Paddle, Chargebee, Recurly, Braintree) and lists its Admin, Affiliate and Tracking APIs and webhooks on every plan, including the $49 Starter. The July 2026 version of this page said its API started at $99; FirstPromoter's pricing page in October 2026 shows it on every plan. That leaves one clean decision rule: if you bill through a provider Rewardful does not support, Rewardful is off the table and FirstPromoter is not. Billing fit overrides every other criterion on this page, because a tracker that cannot see your invoices tracks nothing. Worth knowing if you automate with AI agents: FirstPromoter lists an MCP server in beta on every plan, while Rewardful's MCP server covers its developer documentation. **Verdict: FirstPromoter leads on integrations.** Both ship an API at $49, and FirstPromoter adds three more native billing connections and an MCP server in beta. If you bill through Stripe, this criterion is close to a tie. ## Payouts and tax: two different back offices **FirstPromoter** has the deeper commission and tax engine. Recurring, lifetime, and multi-tier commissions (up to 3 levels), W-9 and W-8BEN collection in the affiliate portal, fraud detection, and mass payouts by PayPal, Wise, Stripe, crypto, or bank transfer are on every plan. One-click direct PayPal payouts arrive on Business, and managed auto payouts, where FirstPromoter pays affiliates for you, need Enterprise 2 and up, for SaaS companies, subject to approval. **Rewardful** keeps this surface smaller but makes hands-off payouts available earlier. PayPal mass payouts and Wise bulk payouts are on every plan, and optional Managed Payouts, where Rewardful collects tax info, distributes funds, and handles compliance, are available on every plan for a 3% processing fee. One-click PayPal payouts are on Enterprise. For a program with more than a handful of affiliates, the tax-form question is not cosmetic: someone has to collect the paperwork before payouts go out, and doing it in a spreadsheet is exactly the kind of chore that stops happening by month three. One caution while you research: FirstPromoter's own compare page knocks Rewardful on features. Those claims come from a competitor's marketing page, so weigh them accordingly, and apply the same skepticism to the Affitor section below. **Verdict: a split.** FirstPromoter leads on tax paperwork and commission rules, with forms collected on every plan at no extra fee; Rewardful leads on hands-off payouts, with Managed Payouts on every plan at 3%. ## Who should pick which **Pick Rewardful if** you bill through Stripe, want more headroom at $49 and no affiliate limit, and value a transaction fee that is stated as 0% rather than left unsaid. Its Starter cap gives you 50% more affiliate-revenue headroom than FirstPromoter's at the same price, and Managed Payouts let it pay affiliates for you on any plan. **Pick FirstPromoter if** you bill through Chargebee or another provider beyond Rewardful's Stripe and Paddle Classic, want multi-tier or detailed commission rules, or want W-9 and W-8BEN forms collected inside the product instead of in a spreadsheet. It also gives you 3 campaigns and unlimited team members at $49. Expect to outgrow the $5,000/mo Starter cap first. Neither choice is a mistake at this price. Both are mature products aimed squarely at subscription SaaS, and for many teams the deciding factor is simply which billing provider they already use. If you are also weighing the rest of the field, [the best Rewardful alternatives for SaaS](/blog/rewardful-alternatives) compares five tools side by side, and [the compare hub](/blog/compare) lists every head-to-head we have published. ## The option neither compare page mentions ![Affitor's Partners view: every partner and application in one table with live stats](/blog/shots/partners-table-live.png) Rewardful's comparison article and FirstPromoter's compare pages measure the two against each other and a few look-alikes. Neither mentions Affitor, so here is that section, written with the same rules as everything above. **Affitor** drops the subscription entirely. It costs $0/mo with no setup fee: you pay $0 on the first $10,000 of affiliate revenue per program, then 3.5% of the sales affiliates drove ([affitor.com/pricing](https://affitor.com/pricing), checked Oct 2026). There is no tier ladder to outgrow because there are no tiers, and no revenue cap that turns your affiliates' good month into your upgrade email. Attribution works differently after signup. Tracking starts with a first-party click cookie, and the partner whose click creates the customer keeps that customer. The customer key you send at signup then rides the Stripe Checkout Session and subscription metadata as `affitor_customer_key`, so later payments are matched to the customer rather than to the cookie. The attribution window is set per program, 60 days by default, and is checked once, at the first attributed payment: the click must be no older than the window at signup (or at that payment, if there was no signup). Renewals of an attributed customer are not re-checked. The chain is documented in [how Affitor tracking fits together](/docs/brand/tracking/tracking-overview). And the integration is agent-verifiable, shipped and live today: a `skill.md` runbook an AI agent can follow end to end, an `affitor` CLI whose `onboard` command fires a test click, lead, and sale and reports `integration_verified`, and an MCP server in beta. The full Stripe wiring is walked step by step in [How to create a Stripe affiliate program](/blog/stripe-affiliate-program). Program operations follow the same keep-it-small idea: one partner table holds active partners and applications, and you approve each application by hand or turn on Auto-approve. Every live program is listed on the [Affitor marketplace](https://affitor.com/marketplace), and the Affitor team helps you recruit, onboard, and train partners ([affitor.com/join](https://affitor.com/join)). Now the trade-offs, because this page promised them: - **Affitor reads Stripe natively.** On Chargebee or another billing system you wire it up through its API or SDK, while FirstPromoter connects five billing systems natively. - **Percentage fees grow with volume.** A flat subscription stays flat until its cap; a percentage grows with your affiliate revenue. Paying $0 until the program works suits a new program that might earn nothing; for a large, predictable program, price your own volume on each pricing page before choosing. - **Payouts by bank or Wise, with a tax form.** Affitor partners withdraw by bank transfer or Wise, and Affitor collects a tax form (W-8BEN, W-8BEN-E or W-9) from each partner before the first payout; both tools above pay by PayPal too, and FirstPromoter collects W-9 and W-8BEN forms. ## Every number at a glance | | Rewardful | FirstPromoter | Affitor | |---|---|---|---| | Monthly price | $49 / $99 / $149+ | $49 / $99 / from $149 | $0 | | Platform fee | 0% transaction fee on every plan; optional Managed Payouts 3% | None listed on the pricing page | 3.5% of affiliate-driven sales after the first $10,000 per program | | Cap on the $49 plan | $7,500/mo affiliate revenue | $5,000/mo affiliate revenue | No tiers | | Affiliates and team on the $49 plan | Unlimited affiliates, up to 2 team members | Up to 1,000 affiliates, unlimited team members | Unlimited partners and seats | | API access | Every plan, including $49 | Every plan, including $49 | Included, with CLI and agent runbook | | Billing connections | Stripe, Paddle Classic | Stripe, Paddle, Chargebee, Recurly, Braintree | Stripe natively; others through the API or SDK | | Attribution | Cookie, 60-day default, first- or last-touch | Cookie life up to 9,999 days, first- or last-click | Click cookie (60-day default), then the signup customer key | | Payouts and tax | PayPal and Wise bulk payouts on every plan; Managed Payouts (3%) collect tax info | Mass payouts and W-9/W-8BEN collection on every plan; managed payouts on Enterprise 2 and up, for SaaS companies, subject to approval | Bank transfer or Wise; W-8BEN, W-8BEN-E or W-9 before the first payout | | Trial | 14-day trial | 14 days, no credit card | $0 until the first $10,000 of affiliate revenue per program | | Agent integration | MCP server for its developer docs | MCP server in beta | `skill.md` runbook, beta MCP server, test sale returning `integration_verified` | | Stronger on | Entry-plan headroom, managed payouts on every plan | Billing coverage, commission rules, tax forms | A different model: no subscription | All Rewardful and FirstPromoter figures were checked against their pricing pages in October 2026. Pricing in this category moves fast, so treat any comparison page older than a few months, including this one, as a starting point rather than a quote. ## FAQ ### Is Rewardful cheaper than FirstPromoter? They cost the same on paper: both start at $49/month and step to $99 and $149+ (checked October 2026). Rewardful gives you more revenue headroom on the entry plan, $7,500/month in affiliate revenue against FirstPromoter's $5,000/month, and unlimited affiliates where FirstPromoter's Starter holds 1,000. FirstPromoter gives you unlimited team members and 3 campaigns at $49, where Rewardful allows 2 team members and 1 campaign. ### Does FirstPromoter charge transaction fees? FirstPromoter's pricing page lists no transaction fee (checked October 2026). Rewardful states a 0% transaction fee on every plan explicitly, and charges 3% of payouts if you use its optional Managed Payouts. Neither page shows a per-transaction charge on top of the subscription. ### Which is better for a Stripe SaaS, Rewardful or FirstPromoter? Rewardful is the better pick for most SaaS that bill through Stripe alone: a 0% transaction fee stated in writing, 50% more affiliate-revenue headroom at the entry price, and unlimited affiliates on every plan. FirstPromoter wins when you bill through Chargebee, Recurly, or Braintree, or want multi-tier commissions and tax-form collection on every plan. ### Does FirstPromoter have an API on the $49 plan? Yes. FirstPromoter's pricing page lists its Admin, Affiliate and Tracking APIs and webhooks on every plan, including the $49 Starter, plus an MCP server in beta (checked October 2026). Rewardful also includes its REST API on every plan. The July 2026 version of this page said FirstPromoter kept its API for the $99 plan; that is not what its pricing page shows in October 2026. ### Is there an alternative to both Rewardful and FirstPromoter? Affitor drops the subscription both of them charge: $0 on the first $10,000 of affiliate revenue per program, then 3.5% of affiliate-driven sales. Tracking starts with a click cookie, then the customer key you send at signup carries attribution to later payments, so renewals do not depend on the cookie. ### How do Rewardful and FirstPromoter track referrals? Both use cookie-based attribution with first- or last-touch credit. Rewardful's default cookie window is 60 days and can be changed per campaign; FirstPromoter lets you set a cookie life of up to 9,999 days. Both share the same blind spot: when the cookie is cleared, blocked, or the buyer switches devices before converting, the affiliate silently loses credit. ## What's next If you are choosing between the two names in the title, take both 14-day trials, wire up one real affiliate link in each, and see which dashboard your team actually opens in week two. The caps, the plan limits, and your billing provider will make the decision for you faster than any comparison page. If the $0-until-it-works model fits where your program is today, [create your program on Affitor](https://affitor.com/welcome) or [read how the performance pricing model works](/docs/getting-started/pricing-performance-model). ## More comparisons - [Every comparison in one table](/blog/compare) - [The best Rewardful alternatives for SaaS](/blog/rewardful-alternatives) - [PartnerStack alternatives](/blog/partnerstack-alternatives) - [FirstPromoter alternatives](/blog/firstpromoter-alternatives) - [Tolt alternatives](/blog/tolt-alternatives) - [Tolt vs Rewardful](/blog/tolt-vs-rewardful) - [PartnerStack vs Rewardful](/blog/partnerstack-vs-rewardful) - [Best affiliate software for SaaS: pricing compared](/blog/best-affiliate-software-saas) --- id: "blog/stripe-affiliate-program" type: "blog" url: "https://affitor.com/blog/stripe-affiliate-program" updated: "2026-10-12" --- # Best Affiliate Tracking Software for Stripe in 2026 (8 Tools Compared) > Eight Stripe affiliate tracking tools compared on what they read from Stripe, price, fees, revenue caps and the catch, with every price checked on October 12, 2026. Then a four-step Affitor setup that ends with a test click, signup and sale. The best affiliate tracking software for Stripe depends on how you want to pay. As of October 12, 2026, Affitor is $0 until a program earns $10,000 through affiliates, then 3.5% of affiliate-driven sales; PromoteKit is $29 a month up to $10,000 a month in affiliate revenue; Rewardful is $49 a month up to $7,500. Stripe has no affiliate feature of its own: no referral links, no partner accounts, no commission ledger. Every tool below adds that layer on top of your Stripe account, and they differ on three things: what they read from Stripe, how they charge you, and where the price jumps. Disclosure: we build Affitor, one of the eight tools on this page. Every price comes from the vendor's own pricing page, and every Stripe permission from the vendor's Stripe App Marketplace listing, all checked on October 12, 2026; sources are listed under the table. Each tool gets a Catch, ours included. ## Stripe affiliate tracking software compared (October 2026) Sorted by entry price. Each tool name links to its pricing page. "Read and write" means the app can also change those objects in your Stripe account, usually to add referral details to metadata or to create a partner's promo code. | Tool | What it reads from Stripe | Price (checked Oct 12, 2026) | Fee on top | Revenue cap | Catch | |---|---|---|---|---|---| | [Affitor](https://affitor.com/pricing) | Completed Checkout Sessions, paid invoices, refunds and disputes, through Stripe Connect | $0 until a program earns $10,000 through affiliates | 3.5% of affiliate-driven sales after the first $10,000 | None | No importer, so partners get new links. Payouts go by bank or Wise, not PayPal | | [PromoteKit](https://www.promotekit.com/pricing) | Checkout Sessions, customers, invoices, subscriptions and promo codes (read and write); charges and refunds (read) | $0 for your first 3 referrals, then $29/mo on Pro | None on sales; if PromoteKit sends payouts, 5% when you fund them by bank (ACH) or 8% by card, added on top of the payout total | $10,000/mo on Pro | Requires Stripe; above $10,000/mo in affiliate revenue it's a quote | | [Endorsely](https://endorsely.com/pricing) | Charges, refunds, Checkout Sessions, customers, invoices and subscriptions (read); coupons and promo codes (read and write) | $0 up to $1,000/mo in affiliate revenue, then $39/mo on Pro | None stated | $1,000/mo on Starter, $5,000/mo on Pro | Tracking needs a paid plan once affiliate revenue passes $1,000 in a month; payouts are a PayPal bulk file you send yourself | | [Rewardful](https://www.rewardful.com/pricing) | Charges, refunds, customers, invoices, subscriptions, coupons and promo codes (read and write); Checkout Sessions and events (read) | $49/mo on Starter | 0%; 3% if Rewardful runs payouts | $7,500/mo on Starter | Growth is $99 for up to $15,000/mo; outside Stripe it supports Paddle Classic | | [FirstPromoter](https://firstpromoter.com/pricing) | Charges, refunds, Checkout Sessions, disputes, invoices and subscriptions (read); customers, coupons and promo codes (read and write) | $49/mo on Starter | None listed | $5,000/mo on Starter | Starter allows up to 1,000 affiliates; managed payouts need Enterprise 2 or higher | | [Partnero](https://www.partnero.com/pricing) | Charges, refunds, Checkout Sessions, disputes, invoices and payment intents (read); customers, subscriptions, coupons and promo codes (read and write) | $59/mo, or $49/mo billed annually | 7% if Partnero runs payouts | None | Starter is 1 program and 1 team member | | [Tolt](https://tolt.com/pricing) | Charges, refunds, Checkout Sessions, customers, invoices, subscriptions and products (read); coupons and promo codes (read and write) | $69/mo on Basic | 2% on automatic payouts (Growth and up) | $10,000/mo on Basic | Basic is manual payouts | | [Trackdesk](https://trackdesk.com/pricing) | Customers and events (read access) | $299/mo billed yearly, or $399 month to month, on Business | None listed | None listed; 5 seats and 10 active offers on Business | No current plan below $299/mo; the trial is a 14-day assisted trial | Sources, checked Oct 12, 2026. Stripe App Marketplace listings: [PromoteKit](https://marketplace.stripe.com/apps/promotekit), [Endorsely](https://marketplace.stripe.com/apps/endorsely), [Rewardful](https://marketplace.stripe.com/apps/rewardful-affiliate-software), [FirstPromoter](https://marketplace.stripe.com/apps/firstpromoter), [Partnero](https://marketplace.stripe.com/apps/partnero), [Tolt](https://marketplace.stripe.com/apps/tolt), [Trackdesk](https://marketplace.stripe.com/apps/trackdesk). Payout fees and limits: [PromoteKit payout fees](https://www.promotekit.com/docs/payouts/stripe-payouts#fees), [FirstPromoter managed payouts](https://help.firstpromoter.com/en/articles/9998853-how-managed-auto-payouts-work), [Partnero managed payouts](https://help.partnero.com/article/292-intermediary-payouts). Affitor: [our Stripe tracking docs](https://affitor.com/docs/brand/tracking/payment-tracking-stripe) and how our Stripe Connect integration handles events. :::caution Prices and plan limits change often in this category. Everything in this table was checked on October 12, 2026. Open the linked pricing page before you commit. ::: ## How these tools connect to Stripe There are two ways an affiliate tool gets your Stripe data, and it is worth knowing which one you are approving. **A Stripe App.** PromoteKit, Endorsely, Rewardful, FirstPromoter, Partnero, Tolt and Trackdesk install from the Stripe App Marketplace. Before you install, Stripe shows the exact objects the app can read or change, and the table above summarizes those lists. Most of them ask for write access to coupons and promotion codes so they can create a partner's discount code in Stripe for you. Trackdesk asks for the least: read access to customers and events. [Rewardful's help center](https://help.rewardful.com/en/articles/2213091-how-does-rewardful-use-my-stripe-account) describes how it uses its access: it reads the `referral` attribute in customer metadata, paid invoices and refunds, and adds affiliate and commission details back to that metadata. **An OAuth connection.** Affitor connects through Stripe Connect OAuth, using Stripe's standard read_write scope. From the connected account it handles completed Checkout Sessions, paid invoices for subscription renewals, refunds (the commission is reversed) and disputes. With Affitor you keep charging customers in your own Stripe account; Affitor never becomes the merchant of record. If some revenue does not go through Stripe Checkout, Affitor also takes sales from your server with `POST /api/v1/track/sale`, which works with any payment provider. The [payment tracking docs](https://affitor.com/docs/brand/tracking/payment-tracking-stripe) cover both paths. ## Which one fits your Stripe setup Prices below are as of October 12, 2026. - **No affiliate revenue yet.** Affitor, Endorsely and PromoteKit let you start without a subscription. The bill starts at different points: Affitor after a program has earned $10,000 through affiliates in total, Endorsely in any month affiliate revenue passes $1,000, PromoteKit after the third referral. - **A low fixed bill on Stripe.** PromoteKit Pro is $29 a month for up to $10,000 a month in affiliate revenue. - **A Premier Stripe Partner.** Rewardful is $49 a month, with a 0% transaction fee and its data visible inside your Stripe dashboard. More options in [the best Rewardful alternatives](/blog/rewardful-alternatives). - **Billing outside Stripe too.** FirstPromoter supports Stripe, Paddle, Chargebee, Recurly and Braintree from $49 a month. The head-to-head is in [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter). - **A price that does not grow with revenue.** Partnero is $59 a month with no revenue cap; it prices by programs and seats. - **Payouts and tax forms on a flat plan.** Tolt Growth at $99 a month adds automatic payouts (with a 2% processing fee), W-9/W-8 collection and 1099 filing. - **High traffic.** Trackdesk lists clicks and conversions as uncapped on every plan, from $299 a month billed yearly. ### What Affitor costs Affitor has no subscription. A program pays nothing until it has made $10,000 through affiliates; after that, 3.5% of affiliate-driven sales is the whole price, and partner payouts by bank or Wise carry no extra fee for you. Affitor's billing view showing the $0 platform fee until the first $10,000 in affiliate revenue ## How to set up Stripe affiliate tracking on Affitor Four steps, and the last one tests the chain before a partner sends real traffic. Affitor attributes each customer to the partner whose click first brought them in, within the attribution window you set. ## Step 1: Create your program and set the commission Create a program at [affitor.com/welcome](https://affitor.com/welcome), or from your project root: ```bash npx affitor login npx affitor init --no-wizard ``` `init` creates the program and writes its API key to `.affitor/.env`, which it adds to `.gitignore`. The `--no-wizard` flag keeps it from editing your project; you add the tracker by hand in Step 3. Then open the program in the dashboard and set the commission on its Default partner group: that is the rate partners are paid on every sale, and the test in Step 4 needs it. The [CLI commands reference](https://affitor.com/docs/brand/cli/commands) lists every flag. ## Step 2: Connect Stripe In your program's settings, click **Connect Stripe** and approve the Stripe Connect authorization. From then on Affitor receives your checkout, invoice, refund and dispute events. Affitor matches each sale to a partner using the click ID, the email captured at signup, the Stripe customer ID or your own customer key, whichever it finds. To make the match reliable, pass your user ID and program ID as metadata on the Checkout Session: ```js title="server/create-checkout.js" // clickId comes from the affitor_click_id cookie. // customer_key is your internal user ID: send the SAME value you send at signup. const session = await stripe.checkout.sessions.create({ line_items: [{ price: 'price_xxx', quantity: 1 }], mode: 'subscription', success_url: 'https://yoursite.com/success', cancel_url: 'https://yoursite.com/cancel', metadata: { affitor_click_id: clickId, affitor_customer_key: currentUser.id, program_id: 'YOUR_PROGRAM_ID', }, // Repeat the values here so renewal invoices stay attributed. subscription_data: { metadata: { affitor_click_id: clickId, affitor_customer_key: currentUser.id, program_id: 'YOUR_PROGRAM_ID', }, }, }); ``` Prefer not to connect Stripe? Report each sale from your own Stripe webhook handler with `POST /api/v1/track/sale` instead, as the [payment tracking docs](https://affitor.com/docs/brand/tracking/payment-tracking-stripe) show. Use one path, not both. ## Step 3: Add click and signup tracking Add the tracker to every page where partner traffic can land. It reads the `?aff=` parameter and stores the click in a first-party cookie: ```html ``` When a signup succeeds, tell Affitor who signed up, using the same customer key you put in the Stripe metadata: ```js window.affitor.signup(currentUser.id, currentUser.email); ``` Add both by hand. Replace `YOUR_PROGRAM_ID` with your real program ID, which the dashboard shows (and `.affitor/config.json` holds if you used `init`). The [tracking overview](https://affitor.com/docs/brand/tracking/tracking-overview) explains how the pieces fit. ## Step 4: Run a test click, signup and sale Run the test from your project root. It uses the API key from `.affitor/.env`, or pass one with `--api-key`. The `--json` flag keeps it from editing any of your files: ```bash npx affitor onboard --json ``` It fires a synthetic click, signup and sale through Affitor's attribution pipeline, then polls the program's readiness and prints a summary: ```json title="npx affitor onboard --api-key aff_xxx --json" { "program_id": "430", "steps": [ { "step": "detect", "status": "ok", "detail": "framework=next-app, provider=stripe" }, { "step": "browser_tracking", "status": "skipped", "detail": "json mode" }, { "step": "server_sale", "status": "manual", "detail": "json mode (no auto-edit)" }, { "step": "env_key", "status": "manual", "detail": ".env: json mode (no auto-edit)" } ], "integration_verified": true } ``` `integration_verified: true` means the program passed its readiness checks: profile, commission, tracking, and a live event. A real click or sale on the program can also satisfy those checks, so `true` on its own does not prove the test sale was attributed. Check the test chain directly in the readiness response. The CLI reads the key from `.affitor/.env` on its own, but your shell does not, so load it first (if you created the program in the dashboard or passed `--api-key`, set `AFFITOR_API_KEY` to that program API key instead): ```bash export AFFITOR_API_KEY="$(grep '^AFFITOR_API_KEY=' .affitor/.env | cut -d= -f2-)" curl -s https://api.affitor.com/api/v1/programs/me/readiness \ -H "Authorization: Bearer $AFFITOR_API_KEY" ``` `gates.live.test_chain.sale` should read `"attributed"`. If the summary says `false`, `blocker` and `next_action` name the first check to fix. Fix it and run the test again until the sale step reads attributed. The test rows are flagged as tests: no partner earns from them, they create no platform fee, and they stay out of your revenue numbers. You can run the test 10 times per program per hour. The synthetic chain runs inside Affitor. It does not go through your site's signup call or Stripe's webhook delivery to your account, so it cannot prove those two pieces work. The Affitor program dashboard once tracking is live, with revenue, partners and an action queue When the test sale reads attributed, click **Go live** on your program's Share Program page. The program becomes active and gets its marketplace listing. Before partners promote at scale, have one partner send a real click and make one real purchase through their link, then check that the sale and its commission show up in your dashboard. The [CLI quickstart](https://affitor.com/docs/brand/cli/quickstart) covers the same commands. ## FAQ ### What is the best affiliate tracking software for Stripe? It depends on how you want to pay. As of October 12, 2026: Affitor is $0 until a program earns $10,000 through affiliates, then 3.5% of affiliate-driven sales; PromoteKit is $29 a month for up to $10,000 a month in affiliate revenue; Rewardful, a Premier Stripe Partner, is $49 a month for up to $7,500; FirstPromoter, also $49 a month, adds Paddle, Chargebee, Recurly and Braintree. ### Does Stripe have a built-in affiliate program? No. Stripe has no native affiliate feature: no referral links, no partner accounts, no commission calculation and no affiliate dashboard. Affiliate tracking for Stripe is a separate tool that connects to your Stripe account, through a Stripe App or an OAuth connection, and reads your payments from there. ### How much does Stripe affiliate software cost? Entry prices checked on October 12, 2026: Affitor $0 until a program earns $10,000 through affiliates, then 3.5% of affiliate-driven sales; PromoteKit $29 a month after your first 3 referrals; Endorsely $0 while affiliate revenue stays under $1,000 a month, then $39 a month; Rewardful and FirstPromoter $49 a month; Partnero $59 a month; Tolt $69 a month; Trackdesk $299 a month billed yearly. Check each vendor's pricing page before you commit. ### Which Stripe affiliate tools can you start without paying? As of October 12, 2026, three of the eight tools compared here have a no-cost start: Affitor charges nothing until a program earns $10,000 through affiliates (all-time, per program), Endorsely charges nothing while affiliate revenue stays under $1,000 a month, and PromoteKit covers your first 3 referrals. Rewardful, FirstPromoter, Tolt and Trackdesk offer 14-day trials, and Partnero offers 30 days. ### How do I test Stripe affiliate tracking before launch? On Affitor, run npx affitor onboard --json from your project root. It fires a synthetic click, signup and sale through Affitor's attribution pipeline without editing your files. Then read the program's readiness and check that gates.live.test_chain.sale says attributed, because integration_verified: true can also come from real traffic. The test does not go through your own signup call or Stripe's webhook delivery, so make one real purchase through a partner link before partners promote at scale. Test rows are flagged as tests, and you can run the test 10 times per program per hour. ### Can affiliate tracking work without cookies? Partly. Coupon and promo-code tracking needs no cookie, and PromoteKit, Endorsely, Rewardful, FirstPromoter, Tolt, Partnero and Trackdesk offer it; Affitor does not, as of October 12, 2026. Affitor shortens the time the cookie matters instead: it ties the click to the person at signup, so a cookie cleared after signup does not lose the sale. ## What's next [Create your program on Affitor](https://affitor.com/welcome). It costs $0 until a program earns $10,000 through affiliates, then 3.5% of affiliate-driven sales. If you are still deciding on commission rates, hold periods and how to recruit your first partners, [how to start a SaaS affiliate program](/blog/how-to-start-saas-affiliate-program) covers everything beyond the software. ## More comparisons - [Best affiliate software for SaaS: pricing compared](/blog/best-affiliate-software-saas) - [The best Rewardful alternatives](/blog/rewardful-alternatives) - [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter) - [FirstPromoter alternatives](/blog/firstpromoter-alternatives) - [Tolt alternatives](/blog/tolt-alternatives) - [PartnerStack alternatives](/blog/partnerstack-alternatives) --- id: "blog/tolt-alternatives" type: "blog" url: "https://affitor.com/blog/tolt-alternatives" updated: "2026-10-17" --- # Best Tolt Alternatives for SaaS in 2026 (5 Tools Compared) > Five honest Tolt alternatives for SaaS: Affitor, Rewardful, FirstPromoter, Dub Partners, and PartnerStack. Pricing checked October 2026, the 2% payout-fee nuance, attribution trade-offs, and a straight answer on who should pick what. SaaS teams leave Tolt for three reasons: revenue caps that step the price up as affiliates perform, a payout model where automation costs an extra 2% and the entry plan pays partners manually, and tighter limits on the lower plans. If none of those hurt yet, keep Tolt. It is a clean modern product in its lane, with unlimited affiliates and referrals on every plan, global payout rails (PayPal, Wise, local bank, crypto, wire), a REST API and an MCP connection to Claude, and more revenue headroom at $99 than Rewardful or FirstPromoter offer at the same price. Plenty of programs never need more. This guide compares five alternatives worth shortlisting in 2026: Affitor, Rewardful, FirstPromoter, Dub Partners, and PartnerStack. One disclosure before we start: we build Affitor. It is one of the five tools below, and this post tells you plainly where the others beat it. ## Quick answer: what is the best Tolt alternative for SaaS? For SaaS that wants to pay $0 until affiliates have made a program its first $10,000, Affitor is the best fit. Pick Rewardful if you want a familiar flat-fee tool that costs $20 less at entry, FirstPromoter if you bill through providers beyond Stripe and Paddle, Dub Partners if developer tooling decides your stack, and PartnerStack if you run a multi-type partner program with an enterprise budget. Stay on Tolt if unlimited affiliates on a flat subscription is exactly what you need and its caps and payout fees do not hurt you yet. | Tool | Best for | From price (checked Oct 2026) | Fees on top | How it tracks | |---|---|---|---|---| | [Affitor](https://affitor.com/pricing) | Paying on results | $0/mo | 3.5% of affiliate-driven sales after the first $10,000 per program | Click cookie (60-day default), then the signup customer key | | [Rewardful](https://www.rewardful.com/pricing) | Simplest flat-fee setup on Stripe | $49/mo | 0% transaction fee; optional Managed Payouts 3% | Cookie, 60-day default, first- or last-touch | | [FirstPromoter](https://firstpromoter.com/pricing) | Billing beyond Stripe and Paddle | $49/mo | None listed | Cookie life up to 9,999 days, first- or last-click | | [Dub Partners](https://dub.co/pricing) | Developer-first teams | $90/mo | Payout fee: 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise) | Links with conversion tracking | | [PartnerStack](https://www.partnerstack.com/pricing) | Enterprise multi-type programs | Not published; set during a demo | Not published | Link tracking or lead and deal registration | Every price on this page was checked against each vendor's pricing page in October 2026. Affiliate software pricing moves fast, and PartnerStack does not publish prices, so treat the live pages as the source of truth. ## Why teams outgrow Tolt Tolt's model is a flat subscription with revenue-capped plans. Per [tolt.com/pricing](https://tolt.com/pricing), checked October 2026: | Plan | Price (checked Oct 2026) | Affiliate revenue cap | Programs | Payouts | |---|---|---|---|---| | Basic | $69/mo | $10,000/mo | 2 | Manual | | Growth | $99/mo | $20,000/mo | 5 | Automated, 2% processing fee | | Pro | $199/mo | $50,000/mo | Unlimited | Automated, 2% processing fee | | Enterprise | Custom | $50,001+/mo | Unlimited | Automated, 2% processing fee | There is no $0 plan; there is a 14-day trial with no credit card required and a 30-day refund policy. Three things push growing programs off this ladder. The first is the caps. A program doing well crosses $10,000/mo in affiliate revenue and the price steps to $99, crosses $20,000/mo and it steps to $199, not because you used more software, but because your affiliates performed. The second is the payout nuance. Tolt markets "0% commission", and that claim has a footnote: auto payouts carry a 2% processing fee, and the Basic plan avoids the fee because its payouts are manual. At $69/mo, you are the payout automation. To pay partners automatically you need the $99 plan, and you hand back 2% of every payout on top of the subscription. The third is the lower plans' limits. Basic holds 2 programs and 3 team members, W-9/W-8 collection and 1099 filing start on Growth, and unlimited programs and team members need Pro at $199/mo. Programmatic teams are covered: Tolt has a [REST API](https://docs.tolt.com/introduction) and an MCP connection to Claude. Its JavaScript stores the partner click with a cookie duration, and a signup call ties that click to your customer. ## What to evaluate in a replacement Three questions separate the five tools below faster than any feature checklist. **How does it charge, and how many times?** Flat subscription, percentage of results, or both. Tolt itself is a subscription plus 2% on auto payouts; some replacements charge once, some also charge twice. Watch for the double toll before comparing headline prices. **What happens when the cookie dies?** Every tool here starts from a partner click. The difference is what carries the referral afterwards: a browser cookie all the way to each sale, or a customer record that the signup ties to the partner, which later payments match against. **Can your coding agent do the integration?** In 2026 a lot of Stripe SaaS integration work is done by AI agents. By October 2026 most tools here have an MCP server of some kind: Dub on Business, a Tolt connection to Claude, FirstPromoter in beta, PartnerStack on Launch, and Affitor in beta, while Rewardful's MCP server covers its developer docs. The question to ask is whether an agent can install tracking and then prove it works with a test sale. ## 1. Affitor: best for paying on results ![Affitor's Partners view: active partners and applications in one table with live stats](/blog/shots/partners-table-live.png) Affitor is our product, so here is the model stated plainly: you pay nothing until your affiliate program pays you. ### Key features Tracking starts like the rest: a partner click sets a first-party cookie, and the partner whose click creates the customer keeps that customer. What carries the referral after that is the signup: you send your own customer key, it rides Stripe Checkout and subscription metadata as `affitor_customer_key`, and later payments are matched to the customer rather than to the cookie. The attribution window is set per program, 60 days by default, and is checked once, at the first attributed payment: the click must be no older than the window at signup (or at that payment, if there was no signup). Renewals of an attributed customer are not re-checked. The chain is documented in [how Affitor tracking fits together](/docs/brand/tracking/tracking-overview). The agent surface is live today: a `skill.md` runbook an agent can follow end to end, the `affitor` CLI, browser and server SDKs plus an MCP server (`@affitor/sdk` and `@affitor/mcp`, both labeled beta), and `npx affitor onboard`, which installs tracking and then fires a test click, lead, and sale through your live integration until it reports `integration_verified`. You (or your agent) get proof the integration works before a real affiliate joins. The full setup path is walked in [How to create a Stripe affiliate program](/blog/stripe-affiliate-program). Every live program is listed on the [Affitor marketplace](https://affitor.com/marketplace), and the Affitor team helps you recruit, onboard, and train partners ([affitor.com/join](https://affitor.com/join)). ### Pricing ![Affitor's Billing view: platform fee meter showing $0 accrued until the first $10,000 of affiliate revenue, then 3.5%](/blog/shots/billing-fee.png) $0/mo, no setup fee, and nothing per partner or per seat. You pay $0 on the first $10,000 of affiliate revenue per program, then 3.5% of the sales affiliates drove (checked Oct 2026, [affitor.com/pricing](https://affitor.com/pricing)). If your affiliates generate nothing, you pay nothing. There are no tiers and no revenue caps. ### Pros & cons **Pros:** no subscription and no caps, so cost follows results; renewals stay attributed after the cookie is gone; a marketplace listing with recruiting help; an integration an agent can complete and test with a synthetic sale. **Cons:** a percentage fee grows with your affiliate revenue, while a flat subscription stays flat until its cap, so price your own expected volume on both pricing pages before you choose. Affitor reads Stripe natively; on another billing system you wire it up through its API or SDK, while FirstPromoter connects five billing systems natively. And Tolt's payout rails (PayPal, Wise, local bank, crypto, wire) are broader: Affitor partners withdraw by bank transfer or Wise. **Tolt:** $69 to $199/mo from day one, plus 2% on auto payouts. **Affitor:** $0/mo, 3.5% of affiliate-driven sales after the first $10,000 per program, a click cookie and then the signup customer key. ## 2. Rewardful: best for the simplest flat-fee setup on Stripe Tolt is often described as the modern Rewardful alternative, so it is fair to point back the other way: Rewardful remains a default flat-fee pick for a Stripe SaaS, and it is $20/mo less at entry. ### Key features Setup is two scripts or a native one-click integration (Rewardful is a Premier Stripe Partner). The 0% transaction fee is genuine; optional Managed Payouts cost 3% of payouts. Every plan includes the REST API, first- or last-touch attribution, coupon code tracking, PayPal mass payouts, and Wise bulk payouts. ### Pricing Per [rewardful.com/pricing](https://www.rewardful.com/pricing), checked October 2026: Starter is $49/mo for up to $7,500/mo in affiliate-attributed revenue, with 1 campaign and up to 2 team members. Growth is $99/mo for up to $15,000/mo, with unlimited campaigns and a branded affiliate portal. Enterprise starts at $149/mo and covers up to $30,000/mo on its entry tier, with phone support and one-click PayPal payouts. Every plan has a 14-day trial, and annual billing gives 12 months for the price of 10. ### Pros & cons **Pros:** the lowest entry price of the flat-fee trio ($49 against Tolt's $69), a 0% transaction fee, the REST API on every plan, and bulk payouts by PayPal or Wise without moving up a plan. **Cons:** the caps are tighter than Tolt's: $7,500/mo on Starter vs Tolt's $10,000, and $15,000/mo at the $99 plan vs Tolt's $20,000. Starter allows 1 campaign and 2 team members where Tolt Basic allows 2 programs and 3 team members. Attribution is cookie-based (first- or last-touch, with a 60-day default window you can change per campaign). If Rewardful is your leading candidate, the dedicated [Rewardful alternatives guide](/blog/rewardful-alternatives) runs this comparison from the other direction. **Rewardful:** $49 to $149+/mo, 0% transaction fee, cookie attribution, API on every plan. **Affitor:** $0/mo, 3.5% of affiliate-driven sales after the first $10,000 per program, a click cookie and then the signup customer key. ## 3. FirstPromoter: best for billing providers beyond Stripe and Paddle FirstPromoter is the practical answer when your billing stack rules Tolt out: its pricing page lists native connections to five billing providers, Stripe, Paddle, Chargebee, Recurly, and Braintree. ### Key features Recurring and lifetime commissions, multi-tier commissions up to 3 levels, W-9 and W-8BEN collection in the affiliate portal, fraud detection, and APIs with webhooks, all on every plan, plus an MCP server in beta. A custom dashboard domain arrives on the Business plan. If you bill through Recurly or Braintree, FirstPromoter is often the shortest path to a working program. ### Pricing Per [firstpromoter.com/pricing](https://firstpromoter.com/pricing), checked October 2026: Starter is $49/mo for up to $5,000/mo in affiliate revenue, 3 campaigns, and up to 1,000 affiliates. Business is $99/mo for up to $15,000/mo with unlimited campaigns and affiliates and 2 websites. Enterprise starts at $149/mo. Team members are unlimited on every plan. 14-day trial, no credit card required. No transaction fee is listed on the pricing page. ### Pros & cons **Pros:** detailed commission rules, tax-form collection and fraud detection on every plan, and the widest native billing coverage in the sub-$100 set. **Cons:** the $5,000/mo cap on Starter is the lowest in this peer group, half of Tolt Basic's headroom, so upgrade pressure arrives earliest here. A second website needs Business, and managed payouts (FirstPromoter pays partners for you) need [Enterprise 2 and up, for SaaS companies, subject to approval](https://help.firstpromoter.com/en/articles/9998853-how-managed-auto-payouts-work). Tracking is a cookie with first- or last-click credit and a cookie life you set. For a head-to-head with Rewardful, see [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter). **FirstPromoter:** $49 to $149+/mo, API and webhooks on every plan, five billing connections. **Affitor:** API, CLI, and a beta MCP server at $0/mo on every program. ## 4. Dub Partners: best for developer-first teams If developer tooling is what you want more of, Dub is affiliate infrastructure shaped like developer tooling. ### Key features Dub's pricing page lists a REST API, an MCP server, native SDKs, and real-time event webhooks on every Partners plan, plus tax compliance handled for you, so you do not collect W-9, W-8 or 1099 forms yourself. If you already run Dub for link infrastructure, adding Partners keeps links, analytics, and payouts in one platform. ### Pricing Per [dub.co/pricing](https://dub.co/pricing), checked October 2026: Partners needs a paid plan. Business is $90/mo with partner payouts up to $2,500/mo and up to 500 partners. Advanced is $300/mo with payouts up to $15,000/mo and unlimited partners. Enterprise is custom, billed annually, with unlimited payouts and a marketplace listing. The [payout fee](https://dub.co/help/article/partner-payouts) is 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise). ### Pros & cons **Pros:** API, MCP server, SDKs, and webhooks on the entry plan; tax compliance handled; one platform for links, analytics, and payouts. **Cons:** the toll structure is heavier than the one you are leaving. Tolt charges a subscription plus 2% on auto payouts; Dub charges a bigger subscription plus a payout fee of 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise), and the payout caps meter your program's growth by plan: a Business-plan program cannot pay partners more than $2,500 in a month. The marketplace listing and partner network are Enterprise features. **Dub Partners:** $90/mo plus a payout fee of 5% if you fund payouts by ACH or 8% by card, capped by plan. **Affitor:** $0/mo plus 3.5% of affiliate-driven sales after the first $10,000 per program, no revenue cap. ## 5. PartnerStack: best for enterprise partner programs PartnerStack is not really a Tolt substitute; it is a different category, priced like one. ### Key features A full partner-relationship-management suite ([pricing page](https://www.partnerstack.com/pricing), checked Oct 2026): PartnerStack Marketplace access on every plan, affiliate link tracking or lead and deal registration on Launch (both on Enterprise), partner payments, an MCP connector, and on Growth a learning management system, partner challenges, and MDF management. If you run affiliates, resellers, and referral partners as one program at scale, it is the serious option on this page. ### Pricing PartnerStack does not publish prices. Per [partnerstack.com/pricing](https://www.partnerstack.com/pricing), checked October 2026, Launch, Growth, and Enterprise all start with a demo, and "Your final plan and pricing are confirmed during your demo." Pricing depends on program size, feature needs, and level of support. Its FAQ says there is no limit on partners or internal users. ### Pros & cons **Pros:** marketplace distribution, multi-type partner motions, and enterprise operations no point tool on this page attempts. **Cons:** the process. You see a price after a demo, and its FAQ says most teams are up and running in weeks. For Stripe, its docs describe a webhook that listens for charge and subscription events; we make no other claims about its attribution. For a team replacing a $69 tool, this is the wrong aisle; for a partnerships team that has outgrown a pure affiliate motion, it is the right one. If PartnerStack's process is the reason you are here, the dedicated [PartnerStack alternatives guide](/blog/partnerstack-alternatives) goes deeper. **PartnerStack:** priced in a demo, full PRM suite. **Affitor:** self-serve signup, $0/mo, affiliate programs without the PRM layer. ## Which one should you pick? The honest segmentation is by stage, because the pricing models behave differently as affiliate revenue grows. **$0–500K ARR: pick Affitor, or Rewardful if you want a known flat cost.** At this stage your affiliate program earns little or nothing yet, and a $49–$90 subscription is pure downside risk, Tolt's $69/mo doubly so, since its entry plan has you run payouts by hand anyway. Affitor costs $0 until a program has made $10,000 through affiliates, so the software decision needs no budget. If you would rather pay a predictable flat fee for a familiar tool, Rewardful's $49 Starter is $20/mo less than Tolt Basic. **$500K–5M ARR: compare at your own volume.** At steady volume Tolt's $99 Growth plan is a strong value, with a $20,000/mo cap above Rewardful's and FirstPromoter's $15,000 at the same price; include the 2% auto-payout fee when you compare. If you bill through Recurly, Chargebee, or Braintree, FirstPromoter's Business plan at $99/mo is the short list. If affiliate revenue is still lumpy, Affitor's pay-on-results model keeps quiet months at $0. **$5M+ ARR: think in programs, not trackers.** If you run affiliates plus resellers plus referral partners with a partner manager, PartnerStack's PRM suite is the real option. If it is still a pure affiliate motion, Tolt's Pro plan ($199/mo up to $50,000/mo) and the Enterprise plans of Rewardful ($149+/mo) or FirstPromoter (from $149/mo), or Dub's custom Enterprise with its lower payout fees (3% by ACH, 6% by card), cover the volume. ## Every alternative at a glance :::note All prices checked against each vendor's pricing page in October 2026. PartnerStack does not publish prices. Check the live page before you commit. ::: | Platform | Monthly price | Fees on top | Caps | How it tracks | API and agent surface | |---|---|---|---|---|---| | **[Affitor](https://affitor.com/pricing)** | $0 | 3.5% of affiliate-driven sales after the first $10,000 per program | None | Click cookie (60-day default), then the signup customer key | API, CLI, beta MCP, test sale that returns `integration_verified` | | **[Tolt](https://tolt.com/pricing)** | $69 / $99 / $199 | 2% on auto payouts (Basic: manual payouts) | $10K / $20K / $50K per mo affiliate revenue | Cookie with a set duration, plus a signup call | REST API; MCP connection to Claude | | **[Rewardful](https://www.rewardful.com/pricing)** | $49 / $99 / $149+ | 0%; optional Managed Payouts 3% | $7.5K / $15K / $30K (entry Enterprise) per mo affiliate revenue | Cookie, 60-day default, first- or last-touch | REST API on every plan; MCP for its docs | | **[FirstPromoter](https://firstpromoter.com/pricing)** | $49 / $99 / $149+ | None listed | $5K / $15K per mo affiliate revenue | Cookie up to 9,999 days, first- or last-click | API and webhooks on every plan; MCP in beta | | **[Dub Partners](https://dub.co/pricing)** | $90 / $300 / custom | Payout fee: 5% if you fund payouts by ACH, 8% by card (3% and 6% on Enterprise) | Payouts $2.5K / $15K per mo | Links with conversion tracking | REST API, MCP server, native SDKs | | **[PartnerStack](https://www.partnerstack.com/pricing)** | Set during a demo | Not published | Not published | Link tracking or lead and deal registration | REST API; MCP connector on Launch | ## FAQ ### What is the best Tolt alternative for SaaS? It depends on why you are leaving. For SaaS that wants no monthly fee, Affitor is the best fit: $0 until a program has made $10,000 through affiliates, then 3.5% of affiliate-driven sales. Rewardful is the strongest pick if you want a familiar flat-fee tool that costs $20 less at entry, and FirstPromoter when you bill through providers beyond Stripe and Paddle. ### Does Tolt charge transaction fees? Tolt markets 0% commission, with one nuance: auto payouts carry a 2% processing fee, and the $69/month Basic plan avoids that fee because its payouts are manual (per tolt.com/pricing, checked October 2026). The subscription itself runs $69, $99, or $199 per month, with each plan capped by monthly affiliate revenue. ### How does Affitor's pricing compare with Tolt's? They charge in different shapes. Affitor has no subscription: $0 on the first $10,000 of affiliate revenue per program, then 3.5% of affiliate-driven sales. Tolt charges a monthly plan by affiliate-revenue tier ($69, $99 or $199) plus 2% on auto payouts (checked October 2026). A new program pays nothing on Affitor until it has made $10,000 through affiliates; after that, compare both at your own monthly volume, including Tolt's payout fee. ### Which affiliate software has no monthly fee? In this comparison, Affitor: $0 a month, $0 on the first $10,000 of affiliate revenue per program, then 3.5% of affiliate-driven sales. The others charge a monthly plan: Rewardful $49, FirstPromoter $49, Tolt $69, Dub Partners $90, and PartnerStack prices every plan in a demo. Outside this comparison, PromoteKit has a $0 plan for up to 3 referrals and Endorsely a $0 plan below $1,000 a month in affiliate revenue (checked October 2026). ### How much does affiliate tracking software cost in 2026? Entry prices checked October 2026: Rewardful and FirstPromoter $49/month, Tolt $69/month, Dub Partners $90/month plus a payout fee of 5% if you fund payouts by ACH or 8% by card, PartnerStack priced during a demo, and Affitor $0/month with 3.5% of affiliate-driven sales after the first $10,000 per program. Prices in this category change often, and PartnerStack does not publish prices (checked October 2026). ### Why do SaaS teams leave Tolt? Three common reasons: revenue-capped plans ($10,000, $20,000, and $50,000 per month) that step the price up as affiliate sales grow; a payout model where auto payouts cost a 2% processing fee and the entry plan pays partners manually; and tighter limits on the lower plans, such as 3 team members and 2 programs on Basic and tax forms from Growth. ## What's next The short version: stay on Tolt if unlimited affiliates on a clean flat-fee product is exactly what you need and the caps and the 2% payout fee do not hurt you yet. Pick Rewardful for a familiar flat-fee setup that costs $20 less at entry, with an API on every plan. Pick FirstPromoter for billing providers beyond Stripe and Paddle or for tax forms on every plan. Pick Dub Partners if you want serious developer tooling and accept the payout fee. Pick PartnerStack when you are running a multi-type partner program with an enterprise budget. Pick Affitor if you want to pay when your affiliates generate revenue and not before, keep renewals attributed after the cookie is gone, or hand the whole integration to an agent and get back proof it works. If the performance model fits your stage, [create your program](https://affitor.com/welcome). It costs nothing to run until a program has made $10,000 through affiliates, so the way to evaluate Affitor is to launch with it. If you want to see how Affitor tracking works before you decide, [read the tracking docs](/docs/brand/tracking/tracking-overview). The click, signup, and sale chain is documented end to end, including the test that proves your integration is live. ## More comparisons - [Every comparison in one table](/blog/compare) - [The best Rewardful alternatives for SaaS](/blog/rewardful-alternatives) - [PartnerStack alternatives](/blog/partnerstack-alternatives) - [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter) - [FirstPromoter alternatives](/blog/firstpromoter-alternatives) - [Tolt vs Rewardful](/blog/tolt-vs-rewardful) - [PartnerStack vs Rewardful](/blog/partnerstack-vs-rewardful) - [Best affiliate software for SaaS: pricing compared](/blog/best-affiliate-software-saas) --- id: "blog/tolt-vs-rewardful" type: "blog" url: "https://affitor.com/blog/tolt-vs-rewardful" updated: "2026-10-13" --- # Tolt vs Rewardful: Which Is Best for SaaS in 2026? > Rewardful starts $20 lower; Tolt gives a third more headroom at $99 and automates global payouts. Both publish an API. Every number checked against both pricing pages in October 2026, plus Affitor, the $0/month option neither compare page mentions. Tolt markets itself as the modern alternative to Rewardful, and Rewardful is the name every Tolt shopper is measuring against, so this is the most natural head-to-head in the category. Both are flat-subscription affiliate trackers built for Stripe SaaS, both start tracking from a cookie, and they sit $20 apart on the entry plan. This page is the version you would send a friend: the checked numbers, the trade-offs each vendor's marketing leaves out, a verdict per criterion, and the one option neither of them mentions. :::tip Disclosure: we make [Affitor](https://affitor.com), which competes with both products. Affitor gets one clearly marked section near the end of this page and one column in the summary table. Everything else comes from [Tolt's](https://tolt.com/pricing) and [Rewardful's](https://www.rewardful.com/pricing) own pricing pages, docs, and help centers, checked in October 2026. Prices drift, so check the live pages before you buy. ::: ## Quick answer: Tolt or Rewardful? Rewardful is the better pick for most Stripe SaaS starting an affiliate program in 2026: it costs $20 less at entry, states a 0% transaction fee, and lets you hand payouts to it on any plan through Managed Payouts. Pick Tolt when payouts and program count decide it: auto payouts to PayPal, Wise, local bank, crypto, or wire from the $99 plan, 2 programs on the entry plan, and a third more revenue headroom at $99. Both publish an API. If you want to skip the subscription entirely, Affitor charges $0 until a program has made $10,000 through affiliates. | Tool | Best for | From price (checked Oct 2026) | Fees on top | Attribution | |---|---|---|---|---| | [Tolt](https://tolt.com/pricing) | Global payout rails and more programs per plan | $69/mo | 0% commission marketed; 2% fee on auto payouts | Cookie with a set duration, plus a signup call | | [Rewardful](https://www.rewardful.com/pricing) | Stripe SaaS wanting the lower entry price | $49/mo | 0% transaction fee; optional Managed Payouts 3% | Cookie, 60-day default, first- or last-touch | | [Affitor](https://affitor.com/pricing) | Paying on results | $0/mo | 3.5% after the first $10,000 of affiliate revenue per program | Click cookie (60-day default), then the signup customer key | Every number on this page was checked against each vendor's pricing page in October 2026. ## Tolt vs Rewardful pricing: $20 apart at the door, different math at $99 Both products sell a flat monthly subscription metered by *affiliate revenue*: the revenue your affiliates generate each month, not your total revenue. The ladders look similar from a distance; the differences live in the caps and the fine print. **Tolt** prices like this (per [tolt.com/pricing](https://tolt.com/pricing), checked October 2026): | Plan | Price | Affiliate revenue cap | Programs | Payouts | |---|---|---|---|---| | Basic | $69/mo | $10,000/mo | 2 | Manual | | Growth | $99/mo | $20,000/mo | 5 | Automated, 2% processing fee | | Pro | $199/mo | $50,000/mo | Unlimited | Automated, 2% processing fee | | Enterprise | Custom | $50,001+/mo | Unlimited | Automated, 2% processing fee | Affiliates and referrals are unlimited on every plan. The trial is 14 days with no credit card required, and there is a 30-day refund policy. There is no $0 plan. **Rewardful** uses the familiar three rungs (per [rewardful.com/pricing](https://www.rewardful.com/pricing), checked October 2026): | Plan | Price | Affiliate revenue cap | Notable limits and unlocks | |---|---|---|---| | Starter | $49/mo | $7,500/mo | 1 campaign, up to 2 team members | | Growth | $99/mo | $15,000/mo | Unlimited campaigns and team, branded portal, custom domain | | Enterprise | $149+/mo | Up to $30,000/mo on the entry tier | Phone support, one-click PayPal payouts | Rewardful states a 0% transaction fee on every plan, plainly, on the pricing page. Affiliates are unlimited on every plan. There is a 14-day trial (the page does not say whether a card is required, so we will not claim it either way), annual billing gives 12 months for the price of 10, and there is no $0 plan. The REST API is included on every plan. Now the head-to-head math. On the entry rung, Rewardful is $20 less in absolute terms; Tolt answers with a higher revenue cap ($10,000/mo against $7,500/mo) and 2 programs and 3 team members where Rewardful's Starter allows 1 campaign and 2 team members. At the $99 rung, the value flips direction: Tolt's Growth caps at $20,000/mo where Rewardful's caps at $15,000/mo, a third more headroom for the same money. Then there is the fee print. Both say 0%, and both charge if you want the tool to pay partners for you. Tolt's auto payouts carry a 2% processing fee and start on Growth; Basic payouts are manual. Rewardful's optional Managed Payouts carry a 3% processing fee and are available on every plan. Without them, you send the money yourself: Rewardful lists PayPal mass payouts and Wise bulk payouts on every plan, and Tolt's FAQ says you can pay affiliates with PayPal or Wise. And note that both ladders meter success: the better your affiliates perform, the sooner you cross a cap and get the upgrade email, whether or not your margins moved. If you want the cost picture across the whole category, [the affiliate software pricing comparison](/blog/best-affiliate-software-saas) lays out the plans side by side. **Verdict: Rewardful leads on pricing, narrowly.** A $20-lower floor and 12 months for the price of 10 on annual billing. But if you expect to live at the $99 plan, Tolt's extra $5,000/month of headroom is the better buy, and its payout automation costs 2% against Rewardful's 3%. ## Attribution: both start from a cookie This criterion is closer to a tie than either vendor's positioning suggests. **Rewardful** uses a cookie with a [60-day default window](https://help.rewardful.com/en/articles/2155812-how-long-are-referral-cookies-valid) you can change per campaign, and lets you choose first-touch or last-touch credit. That choice matters more than it sounds: first-touch pays the affiliate whose link the buyer clicked first, which protects reviewers and content sites; last-touch pays the most recent click, which favors whoever touched the buyer on the way to checkout. **Tolt** also starts from a cookie. Per its [JavaScript docs](https://docs.tolt.com/javascript/overview), a visit through a partner link stores the click with a cookie duration, and a `signup` call turns that click into a lead tied to your customer's email or ID. For the common case, one browser, one device, a conversion inside the window, both systems work fine. The shared weakness is that the cookie step breaks on cookie loss, and the failure is silent. The buyer switches from laptop to phone, clears cookies, runs a blocker, or converts after the window closes; the affiliate loses credit, and no dashboard shows you the miss. Neither vendor is worse than the other here on the public record, so do not let a compare page convince you tracking is the reason to switch between these two. **Verdict: a tie.** Both start from a cookie with the same silent failure mode; attribution is not the reason to pick either. ## API and integrations: both ship an API **Rewardful** includes its REST API on every plan, including the $49 Starter. It is a Premier Stripe Partner, setup is two scripts or a one-click integration, and its billing connections are Stripe and Paddle Classic; its help center says it does not support Paddle Billing. **Tolt** documents a [REST API](https://docs.tolt.com/introduction) for partners, customers, links, clicks, commissions, and transactions, plus webhooks. It integrates with Stripe, Paddle (its help center covers both [Paddle Billing](https://help.tolt.com/en/articles/8455444-how-to-set-up-paddle-billing-with-tolt) and Paddle Classic), and Chargebee. The July 2026 version of this page said no API was surfaced on Tolt's pricing page; Tolt's docs show one. Worth knowing if you automate with AI agents: Tolt has an [MCP connection to Claude](https://help.tolt.com/en/articles/14321072-integrate-tolt-mcp-with-claude), while Rewardful's MCP server covers its developer documentation. **Verdict: Tolt leads narrowly on integrations.** Both publish an API; Tolt adds Chargebee and Paddle Billing and a live MCP connection for agents. If you bill through Stripe, this criterion is close to a tie. ## Payouts and program limits: global rails vs managed payouts **Tolt** pays affiliates through PayPal, Wise, local bank transfer, crypto, or wire, with auto payouts from the $99 Growth plan up (that automation is where the 2% processing fee applies). Growth also collects W-9/W-8 forms and files 1099s. Affiliates and referrals are unlimited on every plan, and the ladder scales from 2 programs on Basic to 5 on Growth to unlimited on Pro, which also adds a dedicated Slack channel. **Rewardful** keeps this surface smaller but opens it earlier. PayPal mass payouts and Wise bulk payouts are on every plan, and optional Managed Payouts, where Rewardful collects tax info, distributes funds, and handles compliance, are available on every plan at 3%. One-click PayPal payouts are on Enterprise. On the program side, Starter allows 1 campaign and up to 2 team members at $49. For a program with more than a handful of affiliates, payout mechanics are not cosmetic. Someone has to send the money every month, and doing it by hand across PayPal and bank transfers is exactly the kind of chore that stops happening by month three. If your partners are international, Tolt's auto payouts cover local bank, crypto, and wire as well as PayPal and Wise. **Verdict: Tolt leads on payouts and program limits.** Five payout rails with automation from $99 at 2%, tax forms and 1099 filing from Growth, and more programs per plan. Rewardful's Managed Payouts are the simpler hands-off option on its $49 plan, at 3%. ## When to choose Tolt over Rewardful - **Your affiliates are global and you refuse to run payouts by hand.** Auto payouts to PayPal, Wise, local bank, crypto, or wire from $99/mo, at 2%, is the clearest payout advantage Tolt has. - **You expect to live at the $99 plan.** $20,000/mo of affiliate-revenue headroom against Rewardful's $15,000/mo means your affiliates can grow a third further before the next upgrade email. - **You want more than one program on the entry plan.** Tolt Basic allows 2 programs and 3 team members, against Rewardful Starter's 1 campaign and 2 team members. - **You want an exit ramp.** A 14-day no-card trial plus a 30-day refund is the friendlier try-it policy of the two; Rewardful's page offers 14 days and stays silent on the card. If Tolt is winning this comparison for you but you still want to see the field, [the best Tolt alternatives for SaaS](/blog/tolt-alternatives) compares five tools against it. ## When to choose Rewardful over Tolt - **You want the lower flat price with an API.** $49/mo with the REST API included is the lower entry point of the two. - **You want the tool to pay affiliates for you on the entry plan.** Rewardful's Managed Payouts are available on every plan (3%), where Tolt's auto payouts start at $99. - **You bill through Stripe and want a Premier Stripe Partner integration.** Setup is two scripts or a one-click integration. - **You plan to pay annually.** 12 months for the price of 10 takes Growth from $1,188 to $990 a year; Tolt's pricing page shows monthly prices. If Rewardful is winning but you want to stress-test it, [the best Rewardful alternatives for SaaS](/blog/rewardful-alternatives) puts it against its strongest challengers, and [the compare hub](/blog/compare) lists every head-to-head we have published. ## The option neither compare page mentions ![Affitor's Partners view: every partner and application in one table with live stats](/blog/shots/partners-table-live.png) Tolt positions itself against Rewardful, and Rewardful is the incumbent everyone measures against, but neither vendor's marketing mentions Affitor, so here is that section, written under the same rules as everything above. **Affitor** drops the subscription entirely. It costs $0/mo with no setup fee: you pay $0 on the first $10,000 of affiliate revenue per program, then 3.5% of the sales affiliates drove ([affitor.com/pricing](https://affitor.com/pricing), checked Oct 2026). There is no tier ladder to outgrow because there are no tiers, and no revenue cap that turns your affiliates' good month into your upgrade email. Attribution works differently after signup. Tracking starts with a first-party click cookie, and the partner whose click creates the customer keeps that customer. The customer key you send at signup then rides the Stripe Checkout Session and subscription metadata as `affitor_customer_key`, so later payments are matched to the customer rather than to the cookie. The attribution window is set per program, 60 days by default, and is checked once, at the first attributed payment: the click must be no older than the window at signup (or at that payment, if there was no signup). Renewals of an attributed customer are not re-checked. The chain is documented in [how Affitor tracking fits together](/docs/brand/tracking/tracking-overview). And the integration is agent-verifiable, shipped and live today: a `skill.md` runbook an AI agent can follow end to end, an `affitor` CLI whose `onboard` command fires a test click, lead, and sale and reports `integration_verified`, and an MCP server in beta. The full Stripe wiring is walked step by step in [How to create a Stripe affiliate program](/blog/stripe-affiliate-program). Every live program is listed on the [Affitor marketplace](https://affitor.com/marketplace), and the Affitor team helps you recruit, onboard, and train partners ([affitor.com/join](https://affitor.com/join)). Now the trade-offs, because this page promised them: - **Affitor reads Stripe natively.** If you bill through Paddle, both tools above connect to it natively; Affitor takes it through its API or SDK. - **Percentage fees grow with volume.** A flat subscription stays flat until its cap; a percentage grows with your affiliate revenue. Paying $0 until the program works suits a new program that might earn nothing; for a large, predictable program, price your own volume on each pricing page before choosing. - **Payouts by bank or Wise.** Affitor partners withdraw by bank transfer or Wise; Tolt's auto payouts also cover PayPal, local bank, crypto, and wire. ## Every number at a glance | | Tolt | Rewardful | Affitor | |---|---|---|---| | Monthly price | $69 / $99 / $199 / custom | $49 / $99 / $149+ | $0 | | Platform fee | 0% commission marketed; 2% processing fee on auto payouts | 0% transaction fee; optional Managed Payouts 3% | 3.5% of affiliate-driven sales after the first $10,000 per program | | Cap on the entry plan | $10,000/mo affiliate revenue | $7,500/mo affiliate revenue | No tiers | | Affiliates and team on the entry plan | Unlimited affiliates, 2 programs, 3 team members | Unlimited affiliates, 1 campaign, up to 2 team members | Unlimited partners and seats | | API access | REST API; MCP connection to Claude | REST API on every plan; MCP for its docs | API, CLI, and agent runbook; beta MCP | | Billing connections | Stripe, Paddle, Chargebee | Stripe, Paddle Classic | Stripe natively; others through the API or SDK | | Attribution | Cookie with a set duration, plus a signup call | Cookie, 60-day default, first- or last-touch | Click cookie (60-day default), then the signup customer key | | Payouts | Manual on Basic; auto payouts to PayPal, Wise, local bank, crypto, wire from $99 (2%) | PayPal and Wise bulk payouts on every plan; Managed Payouts (3%); one-click PayPal on Enterprise | Bank transfer or Wise | | Trial | 14 days, no credit card; 30-day refund | 14-day trial | $0 until the first $10,000 of affiliate revenue per program | | Stronger on | Payout rails, headroom at $99, programs per plan | Entry price, managed payouts on every plan | A different model: no subscription | All Tolt and Rewardful figures were checked against their pricing pages in October 2026. Pricing in this category moves fast, so treat any comparison older than a few months, including this one, as a starting point rather than a quote. ## FAQ ### Is Tolt cheaper than Rewardful? Not on the entry plan: Tolt starts at $69/month against Rewardful's $49/month (checked October 2026). At the $99 plan the math flips: Tolt caps you at $20,000/month in affiliate revenue where Rewardful caps at $15,000/month, so Tolt gives a third more headroom for the same price. If you want the tool to pay affiliates for you, Tolt's auto payouts cost 2% and Rewardful's Managed Payouts cost 3%. ### Does Tolt charge transaction fees? Tolt markets 0% commission, with one nuance: auto payouts carry a 2% processing fee, and the $69/month Basic plan avoids that fee because its payouts are manual (per tolt.com/pricing, checked October 2026). Rewardful states a 0% transaction fee on every plan; its optional Managed Payouts cost 3% of payouts. ### Which is better for a Stripe SaaS, Tolt or Rewardful? Rewardful is the better pick for most Stripe SaaS starting an affiliate program: it costs $20 less at entry, states a 0% transaction fee, and offers Managed Payouts on every plan. Tolt wins once payouts and program count decide it: auto payouts to PayPal, Wise, local bank, crypto, or wire from $99, 2 programs on the entry plan, and more revenue headroom at $99. ### Does Tolt have an API? Yes. Tolt documents a REST API for managing your partnership program at docs.tolt.com, and an MCP connection that links Tolt to Claude (checked October 2026). Rewardful includes its REST API on every plan, and its MCP server covers its developer docs. The July 2026 version of this page said Tolt surfaced no API; Tolt's own docs show one. ### Is there an alternative to both Tolt and Rewardful? Affitor drops the subscription both of them charge: $0 on the first $10,000 of affiliate revenue per program, then 3.5% of affiliate-driven sales. Tracking starts with a click cookie, then the customer key you send at signup carries attribution to later payments, so renewals do not depend on the cookie. ### How do Tolt and Rewardful track referrals? Both start from a cookie. Rewardful's default cookie window is 60 days, changeable per campaign, with first- or last-touch credit. Tolt's JavaScript stores the partner click with a cookie duration and offers a signup call that turns the click into a lead tied to your customer's email or ID. Any cookie-based step shares the same blind spot: when the cookie is cleared, blocked, or the buyer switches devices before it is used, the affiliate can silently lose credit. ## What's next If you are choosing between the two names in the title, take both 14-day trials, wire up one real affiliate link in each, and watch two things: which dashboard your team actually opens in week two, and how each handles your first real payout run. The payout rails, the program limits, and the $99-plan caps will make the decision faster than any comparison page. If the $0-until-it-works model fits where your program is today, [create your program on Affitor](https://affitor.com/welcome) or [read how the performance pricing model works](/docs/getting-started/pricing-performance-model). ## More comparisons - [Every comparison in one table](/blog/compare) - [The best Rewardful alternatives for SaaS](/blog/rewardful-alternatives) - [PartnerStack alternatives](/blog/partnerstack-alternatives) - [Rewardful vs FirstPromoter](/blog/rewardful-vs-firstpromoter) - [FirstPromoter alternatives](/blog/firstpromoter-alternatives) - [Tolt alternatives](/blog/tolt-alternatives) - [PartnerStack vs Rewardful](/blog/partnerstack-vs-rewardful) - [Best affiliate software for SaaS: pricing compared](/blog/best-affiliate-software-saas) --- id: "blog/what-affitor-means" type: "blog" url: "https://affitor.com/blog/what-affitor-means" updated: "2026-07-05" --- # What Affitor means > Affitor is affiliate + -tor: an AI-native affiliate platform for SaaS that costs $0 until your first $10,000 in affiliate revenue, then 3.5%, and verifies its own integration. The story behind the name and the bet the company is built on. {/* DRAFT: naming narrative proposed by content team, Son must confirm before publish */} {/* Publish gates (CONTENT-MAP V2): - BLOCKED on Open Question 1 (name origin). No source file explains the name (FACTS-wishes 1). The etymology below is a PROPOSED reading, not a verified fact. Son must confirm or replace it before this ships. - The pricing-philosophy language echoes the 2026-06-09 manifesto draft, which was written "for owner review" and has not been verified as shipped copy. Son's confirmation of this post covers that reuse. */} Affitor is not a dictionary word, and until now we never wrote down what it means, so this post is the answer: where the name points, the pain that produced the product, and the one bet the whole company is built on. ## The name Affitor is affiliate, compressed, plus the suffix -tor. English borrows -tor from Latin to name a thing by what it does: an actor acts, a creator creates, a competitor competes. An affitor, if the dictionary had needed the word, would be the thing that does the affiliate work. That is the job description in one word. Most affiliate software is a ledger you operate: you configure it, you reconcile it, you chase it. The name describes software that acts instead. It sets the program up, tracks the sale, and proves the tracking worked, so you do not have to. There is a second resonance in the ending. The suffix -tor is also how attributor ends, and attribution is the question this entire category lives or dies on: who sent the customer, and can you prove it. The name points at that job too. ## Built from over a decade of affiliate pain I have worked in affiliate for over a decade, on the affiliate side, long before I built software for it. Affitor did not start as a market analysis. I said it plainly in June 2025: Affitor is a product I built myself, and it came from my own pain doing affiliate work. The pain is specific. When I measured it in April 2026, setting up an affiliate program from scratch took about 60 minutes and 11 manual steps. Every step assumed a human with patience: paste this snippet, configure that webhook, hope the test sale shows up. We collapsed that into three commands and about five minutes, and we put the whole setup flow into the terminal, where the work actually happens. The product exists because the founder was the user first. That is also why the rest of this post is short on adjectives. When you have lived the problem, you describe it instead of decorating it. ## What it stands for Three commitments, and each one is checkable. **Pay for outcomes, not access.** Most affiliate tools charge a subscription from day one, before a partner has sent you anything. We did not want to build that. Affitor costs $0 until your program earns its first $10,000 through affiliates, then 3.5%, and the fee applies only to the sales affiliates drove for you. We make money when affiliates make you money. That is the whole arrangement. **Be the layer an agent reaches for.** Affitor is an AI-native affiliate marketing platform for SaaS companies, and the one bet behind it is this: be the affiliate layer an AI agent reaches for by default, installs, and can prove works. Agents do not forgive a broken quickstart the way humans do. An agent that fails its first integration never defaults to you again, so the integration has to verify itself, end to end. **Label everything honestly.** What is shipped, we call shipped. What is a draft, we call a draft, including in the next section. A platform whose pitch is verifiability cannot afford unverifiable marketing. ## Where it's going Two directions, one shipped and one that is explicitly not. **Open program data: shipped.** When [OpenAffiliate](https://openaffiliate.dev) launched on April 18, 2026, free and open source with 450 affiliate programs, and roughly 750 within two days, I gave the rationale plainly: affiliate data should be public infrastructure, not the proprietary database of any single network. Like npm for packages, OpenAffiliate for affiliate programs. **Verifiable attribution: vision.** VSAL, the Verifiable Signup Attribution Log, is a draft specification, not a product. The design goal is that VSAL replaces trust with proof: every touchpoint becomes a signed claim, and the winner is picked by a public deterministic function instead of by whoever runs the log. Nothing there is shipped, and we will keep saying so until it is. The full argument lives in [the agent commerce post](/blog/agent-commerce-attribution-layer). In November 2025 I wrote about a dream: seeing Vietnamese builders ship products that do not have to be modest in any market. Affitor is the path I chose. When I say the name, that is what it means. ## What's next If the arrangement sounds fair, [create your program on Affitor](https://affitor.com). It stays free until your affiliates have earned you real money. If you want the mechanics first, [read the docs](https://affitor.com/docs), or point your coding agent at [skill.md](https://affitor.com/docs/skill.md) and let it verify the integration itself. --- id: "changelog" type: "changelog" url: "https://affitor.com/changelog" updated: "2026-11-09" --- # Affitor Changelog > New features, improvements and fixes in Affitor. ## Entries - 2026-11-09 · digest · brands, partners, developers · tracking, dashboard · [Planned integrations and One-click Stripe Payment Links](https://affitor.com/changelog/improvements-2026-11-09): Integrations lists planned integrations and marks Stripe Payment Links One-click; a missing page outside Docs, Blog and Changelog has one button. - 2026-11-08 · digest · brands, partners, developers · dashboard, marketplace, mcp · [Link preview images, four more AI agents, and a withdrawal check](https://affitor.com/changelog/improvements-2026-11-08): Shared links show preview images, Integrations adds Grok, Muse Code, Hermes Agent and OpenClaw, and a repeat withdrawal within five minutes is refused. - 2026-11-07 · digest · brands, partners, developers · dashboard, marketplace, mcp, tracking · [Members land on their program, Grok steps, and Markdown pages](https://affitor.com/changelog/improvements-2026-11-07): Team members land on their program after sign-in, Connect an AI tool has Grok steps, six more pages answer in Markdown, and deleting an API key no longer fails. - 2026-11-06 · digest · partners, brands, developers · dashboard, mcp · [A Claude Code plugin, Join or Create on consent, and payout skip](https://affitor.com/changelog/improvements-2026-11-06): A Claude Code plugin and Gemini CLI extension, Add to Claude and VS Code links, Join or Create on AI app consent, and a payout skip per account. - 2026-11-05 · digest · brands, partners · dashboard · [Chat for two-sided accounts, kept rows, and bulk Reject fixes](https://affitor.com/changelog/improvements-2026-11-05): Chat keeps brand and partner sides apart, Partners, Groups and Commissions keep their rows on revisit, and bulk Reject acts only on pending selections. - 2026-11-05 · feature · brands, developers · tracking, api · [Send sales in other currencies, with commissions before tax](https://affitor.com/changelog/multi-currency-sales): Sales in other currencies are converted to USD when recorded, and commissions and platform fees use the price after discounts and before tax. - 2026-11-03 · feature · brands, partners, developers · mcp, dashboard · [Connect an AI tool to several programs at once](https://affitor.com/changelog/mcp-multiple-programs): Pick up to 50 programs, or all current and future ones, when an AI tool connects over MCP, and see each connection's programs in AI agents. - 2026-11-02 · digest · brands, partners, developers · dashboard, mcp · [Send feedback, complete analytics, and one Affitor mark](https://affitor.com/changelog/improvements-2026-11-02): Send feedback from the account menu, analytics without a Building history wait, Last 30 days with today, one Affitor mark, and Grok connections. - 2026-11-01 · digest · partners, brands, developers · dashboard, tracking, api · [Program logos in one frame, and numeric IDs on tracking](https://affitor.com/changelog/improvements-2026-11-01): Referral and invite pages show program logos whole in one framed tile, and lead and refund tracking accept whole-number IDs. - 2026-10-27 · feature · brands, developers · dashboard, api · [Give each API key Full access or Tracking only](https://affitor.com/changelog/api-key-permissions): Set Full access or Tracking only on each program API key, rename it or change its permission, and disable or enable it without a new key. - 2026-10-27 · digest · brands, partners · dashboard · [Website logos at signup, public names, and composer focus](https://affitor.com/changelog/improvements-2026-10-27): New programs pick up the website's logo, partners show by public name in Chat and Sources, Viewers read Chat only, and the composer keeps focus. - 2026-10-26 · digest · brands, partners · dashboard · [Chat at its own address, your name in menus, and customer keys](https://affitor.com/changelog/improvements-2026-10-26): Chat moves to its own address, menus show your name, and sales and commissions fall back to your customer key when no email is recorded. - 2026-10-26 · feature · partners · dashboard · [Track all your programs from the Programs page](https://affitor.com/changelog/partner-programs-analytics): Programs adds up clicks, leads, sales and earnings across every program you joined, and each program opens on the same date range with its top links. - 2026-10-25 · feature · brands · dashboard · [Track your program on the new Dashboard](https://affitor.com/changelog/brand-dashboard): The brand Dashboard shows clicks, leads, sales and revenue against the period before, with Latest sales, Top partners and Needs you below. - 2026-10-25 · digest · brands, partners, developers · dashboard, marketplace, api, mcp · [An API keys table, Billing by program, and 30-day MCP connections](https://affitor.com/changelog/improvements-2026-10-25): An API keys table, product rates on the marketplace, Billing for one program at a time, and MCP connections that last up to 30 days. - 2026-10-24 · digest · partners · dashboard · [Partner totals no longer count test events](https://affitor.com/changelog/improvements-2026-10-24): Partner totals and charts no longer count test events, and older leads count again. - 2026-10-23 · digest · brands, partners, developers · dashboard, marketplace, tracking, api · [A new Members table, Commissions totals, and Review application](https://affitor.com/changelog/improvements-2026-10-23): A new Members table, a money summary on Commissions, Review application from notifications, and archived programs closed to new links. - 2026-10-21 · digest · brands, partners · dashboard, marketplace · [An Approval card, Join right away, and browser translation](https://affitor.com/changelog/improvements-2026-10-21): An Approval card in Program settings, Join right away on auto-approve programs, commissions from exact cents and the $50 Refer reward timing. - 2026-10-20 · digest · brands, partners, developers · dashboard, marketplace, api, mcp · [Commission terms for Owners and Admins, and pages for AI agents](https://affitor.com/changelog/improvements-2026-10-20): Only Owners and Admins change commission terms, marketplace pages state the combined $20 minimum, and affitor.com answers AI agents. - 2026-10-19 · digest · brands, partners, developers · dashboard, tracking, api · [Auto-approval for new programs and AI tracking setup](https://affitor.com/changelog/improvements-2026-10-19): New programs start on automatic approval, Tracking opens on With AI, a daily check records missed Stripe sales, and the Tracking API spec is public. - 2026-10-19 · feature · brands, partners · dashboard, tracking · [Choose which pages partners can link to](https://affitor.com/changelog/partner-page-links): Brands set allowed destinations and a per-partner link limit in Program settings › Partner links; partners link to an allowed page, then copy the link or download its QR code. - 2026-10-19 · feature · brands, partners · dashboard · [Sign in or sign up with a code from your email](https://affitor.com/changelog/sign-in-with-email-code): Enter your email on the sign-in or sign-up page and Affitor emails you a six-digit code that signs you in or creates your account. - 2026-10-19 · feature · brands, partners · dashboard · [Bring your team into partner chats](https://affitor.com/changelog/team-in-partner-chat): Owners, and Admins by default, now read and reply in every partner chat; choose which other roles join under Chat access on Members. - 2026-10-18 · feature · brands · dashboard · [Set up your program in one full-screen flow](https://affitor.com/changelog/brand-onboarding-flow): Creating a program opens five full-screen steps, from Business to Go live, with Save and exit on every step. - 2026-10-18 · digest · brands, partners, developers · dashboard, marketplace, api, cli, sdk, mcp · [Improvements and fixes, Oct 12–18](https://affitor.com/changelog/improvements-2026-10-18): Simpler username rules, website suggestions for your Business details, faster partner pages, and fixes to renewals, phones and sign-up. - 2026-10-18 · feature · brands, partners, developers · mcp · [Integrations and AI agents pages](https://affitor.com/changelog/integrations-and-agents): Two new public pages show what Affitor connects to, Integrations with a guide for each and AI agents for connecting your AI app over MCP. - 2026-10-18 · feature · partners, brands · marketplace, dashboard · [A new Refer Program page, with milestones tied to paid invoices](https://affitor.com/changelog/refer-program-page): The Refer Program page shows an example of what a referral can earn, and the $50 and $350 milestones now follow paid invoices, checked in a review. - 2026-10-17 · feature · brands, partners · dashboard · [See your first results as they happen](https://affitor.com/changelog/first-results): Brands track their first partner, traffic, sale and payout on Get started; partners track their first click, commission and payout on Programs; sign-up asks brand or partner first. - 2026-10-17 · feature · brands, partners, developers · [A Help Center and use cases in the docs](https://affitor.com/changelog/help-center-use-cases): The docs now open by job for brands or partners, with a searchable Help Center, three end-to-end use cases and a guide to connect a new Stripe account. - 2026-10-17 · feature · brands, partners · dashboard · [One navigation for brands and partners](https://affitor.com/changelog/navigation-v2): Brands and partners share one left rail, with Chat in it, your account and inbox at the bottom, and a program menu that remembers your last program. - 2026-10-17 · feature · partners · dashboard · [Get paid through Wise or a bank transfer](https://affitor.com/changelog/partner-payouts-wise): Partners finish a short payout setup, with a legal name, a Wise or bank account and a tax form, then withdraw any amount from $20. - 2026-10-17 · feature · partners, brands · marketplace · [Find verified programs on the marketplace](https://affitor.com/changelog/verified-programs): A blue check marks programs Affitor has verified, and the Verified only filter shows just those on the marketplace. - 2026-10-17 · feature · brands, partners · dashboard · [Your account, one page for both sides](https://affitor.com/changelog/your-account): Your profile, sign-in and payout settings now live on one Your account page, opened from the account menu at the bottom of the rail. - 2026-10-16 · feature · brands, partners, developers · mcp · [Connect Claude, ChatGPT and Cursor to Affitor](https://affitor.com/changelog/hosted-mcp-server): The hosted Affitor MCP server at mcp.affitor.com lets AI apps read your program or partner data after you sign in. No API key, read-only. - 2026-10-15 · feature · brands · dashboard · [Going live now needs a payment source](https://affitor.com/changelog/go-live-needs-payments): A program can go live once it has a business, a commission and a way to count sales. A logo is no longer required. - 2026-10-15 · feature · brands · dashboard · [Set up a program in five steps](https://affitor.com/changelog/guided-program-setup): A new program now walks you through Business, Commission, Tracking, Payments and Go live, with a live preview of your program card. - 2026-10-15 · feature · partners, brands · marketplace · [Marketplace cards show who joined, with new sort and filters](https://affitor.com/changelog/marketplace-partners-joined): Each program card shows how many partners joined, with the initials of its top partners, and the marketplace has a Sort menu and a Filter menu. - 2026-10-15 · feature · brands, partners · dashboard · [Referral links open an invite page](https://affitor.com/changelog/referral-invite-page): When someone opens your Refer a brand link, they see who invited them and how Affitor pricing works before they sign up. - 2026-10-14 · feature · partners, brands · marketplace · [A new marketplace to find your next program](https://affitor.com/changelog/marketplace-redesign): The marketplace is now a grid of program cards you can search, filter by commission type and sort, and every program page shows its terms at a glance. - 2026-10-14 · feature · brands, partners, developers · tracking · [Partner sales from Stripe Payment Links, Buy Buttons and Pricing Tables](https://affitor.com/changelog/stripe-payment-links-attribution): If you sell with Stripe's no-code checkouts, partner sales are now credited automatically. Nothing to change in your checkout. - 2026-10-13 · feature · brands · dashboard · [Billing that shows what you owe and what is next](https://affitor.com/changelog/billing-invoices-redesign): The Billing page now shows what is due, what this week's invoice will be and where you stand against the free tier, and each invoice breaks down by partner. - 2026-10-12 · breaking · developers · mcp · [MCP server records sales only when you allow it](https://affitor.com/changelog/mcp-write-tools-off): From @affitor/mcp 0.2.1, the tools that record sales and refunds are off by default. Agents that record sales need AFFITOR_MCP_WRITE=1. - 2026-10-11 · digest · brands, partners · dashboard · [Improvements and fixes, Oct 5–11](https://affitor.com/changelog/improvements-2026-10-11): One-click commission approval, clearer refund notifications, and notification links that open the right page. - 2026-10-08 · feature · partners, brands · dashboard · [Partners withdraw commissions once the brand has paid](https://affitor.com/changelog/withdraw-paid-commissions): Commissions approved from Oct 9 become withdrawable when the brand pays its invoice. Partners see what is waiting, and brands no longer mark commissions as paid. - 2026-10-04 · digest · brands, partners, developers · dashboard, marketplace, tracking, cli · [Improvements and fixes, Sep 28–Oct 4](https://affitor.com/changelog/improvements-2026-10-04): A changelog for you and your agents, clearer answers from the tracking API, and fixes for Google sign-in and CLI-created programs. - 2026-10-02 · feature · partners · dashboard · [See what you owe after a refund](https://affitor.com/changelog/balance-owed-after-refund): When a customer refund reverses a commission you already withdrew, your payout page shows the balance owed, and it is recovered from your next commissions. - 2026-09-30 · breaking · developers, brands · tracking, api · [Send leads from your server to count them](https://affitor.com/changelog/browser-leads-server-side): A signup sent only from the browser is now recorded as provisional on older programs too. Send the lead from your server with your program API key so it counts. - 2026-09-30 · feature · brands · dashboard · [Test sales are never invoiced](https://affitor.com/changelog/test-sales-never-invoiced): Sales from your own tests are labeled and never billed. An invoice made only of test sales is voided automatically, and it no longer keeps your program paused. - 2026-09-27 · digest · brands, partners, developers · dashboard, marketplace, api · [Improvements and fixes, Sep 21–27](https://affitor.com/changelog/improvements-2026-09-27): Commission notifications that point to the exact commission, a featured carousel on the marketplace, and access fixes for workspace members. - 2026-09-24 · feature · brands, partners · dashboard, tracking · [Partners get their link the moment you approve them](https://affitor.com/changelog/partner-links-on-approval): Approving a partner now creates their referral link right away, every referral code has one owner, and links can use your own /r/ short link. - 2026-09-20 · breaking · brands, developers · api, cli, dashboard · [Know when your API key must be replaced](https://affitor.com/changelog/api-key-rotation): If Affitor flags your program's API key for replacement, your dashboard, every API response and the CLI now tell you. After the deadline the old key is refused. - 2026-09-20 · digest · brands, partners, developers · dashboard, marketplace, tracking, api · [Improvements and fixes, Sep 14–20](https://affitor.com/changelog/improvements-2026-09-20): Password reset pages, notifications that open the right place, faster pages, and fixes across commissions, chat and tracking. - 2026-09-13 · digest · developers, brands, partners · api, marketplace · [Improvements and fixes, Sep 1–13](https://affitor.com/changelog/improvements-2026-09-13): A cleaner docs feed for AI assistants, and tighter access to program and marketplace data. - 2026-08-22 · digest · brands · dashboard · [Improvements and fixes, August 2026](https://affitor.com/changelog/improvements-2026-08): New brands can create their first program right after sign-up again. - 2026-07-06 · digest · brands, partners, developers · dashboard, api · [Improvements and fixes, July 2026](https://affitor.com/changelog/improvements-2026-07): Every docs page as Markdown for AI assistants, an About page, and an end-to-end guide. - 2026-07-05 · feature · brands · [Read honest affiliate-software comparisons on the new Affitor blog](https://affitor.com/changelog/blog-launch): Twelve posts comparing the tools you're actually evaluating, with every price dated "as of" and competitor strengths conceded up front, plus .md twins and llms.txt so your AI assistant reads the same facts you do. - 2026-07-04 · feature · brands · dashboard · [Invite partners with the email already written](https://affitor.com/changelog/invite-partners): Recruit affiliates by email, CSV, or from your other programs, and send an invitation generated from your program's real terms instead of writing one from scratch. - 2026-06-27 · feature · brands · dashboard · [Go live when you are ready](https://affitor.com/changelog/go-live-button): A single Go Live button publishes your program as soon as your business profile and commission are set, and the Quick start checklist shows what is really set up. - 2026-06-27 · digest · brands, partners, developers · dashboard, marketplace, tracking, api, sdk · [Improvements and fixes, June 2026](https://affitor.com/changelog/improvements-2026-06): Shorter app addresses, a calmer design, apply first and sign up after, per-program billing and notifications, refunds through the API, and the end of list.affitor.com. - 2026-06-12 · feature · partners · marketplace, dashboard · [Earn by referring brands to Affitor](https://affitor.com/changelog/refer-program): Partners promote Affitor itself through the Refer Program and earn rewards and a share of the platform fee from the brands they bring. - 2026-06-10 · feature · developers, partners · api, sdk · [A full API reference and integration guides](https://affitor.com/changelog/docs-api-reference): The docs gain an API Reference, an SDK reference, an agent integration guide, integration guides and a machine-readable OpenAPI spec. - 2026-06-08 · pricing · brands · dashboard · [Free up to $10,000 in affiliate revenue, then 3.5%](https://affitor.com/changelog/pricing-2026): Each program runs free until it has driven $10,000 in affiliate revenue; after that Affitor charges a 3.5% platform fee on affiliate sales. - 2026-06-07 · feature · partners, brands · marketplace · [The marketplace is open to everyone](https://affitor.com/changelog/public-marketplace): Browse every live program without an account, open its page, and apply, or go straight to your dashboard if you already joined. - 2026-05-25 · feature · developers · cli, sdk · [Sign in from the CLI, and init wires tracking into Next.js](https://affitor.com/changelog/affitor-init-wizard): The CLI signs you in through the browser, and init detects Next.js, installs the SDK and adds the tracking code, asking before each install and showing a diff before it edits your layout. - 2026-05-23 · digest · brands, partners · dashboard · [Improvements and fixes, May 2026](https://affitor.com/changelog/improvements-2026-05): Redesigned account and invoice emails, a faster brand dashboard, and partner earnings that say what they are. - 2026-04-25 · feature · brands, partners, developers · [Faster, less noisy docs search](https://affitor.com/changelog/faster-docs-search): Search now matches page titles only, so you no longer wade through paragraph snippets to find what you need. - 2026-04-25 · digest · brands, partners, developers · dashboard, marketplace, cli · [Improvements and fixes, April 2026](https://affitor.com/changelog/improvements-2026-04): Replies in messages, new program defaults, CLI pages in the docs, and a profile that saves without signing you out. - 2026-04-25 · feature · brands, partners · dashboard, marketplace, tracking · [Programs go live once setup is complete](https://affitor.com/changelog/programs-go-live-automatically): A program went live by itself once its tracking worked end to end and appeared in the marketplace without waiting for a review. Since June 2026 you publish it with a Go Live button. - 2026-04-24 · feature · partners · marketplace · [A marketplace of programs for partners](https://affitor.com/changelog/partner-marketplace-2026): Partners browse programs inside Affitor, search them with typo-tolerant search, and sort by commission. - 2026-04-20 · feature · partners · [Content Lab writes affiliate posts in one click](https://affitor.com/changelog/content-lab-launch): Pick a program, get a publish-ready affiliate post in one click, free for 30 posts a day. - 2026-04-10 · feature · developers, brands · cli · [Create an affiliate program from your terminal](https://affitor.com/changelog/affitor-cli): Run npx affitor init to create an affiliate program and get its tracking script and API key, then check it and send test events from your terminal. - 2026-04-08 · feature · brands · dashboard · [Billing and invoices in your dashboard](https://affitor.com/changelog/billing-and-invoices-2026): Brands get a Billing area with every invoice, its status, and an invoice detail page. - 2026-04-03 · feature · partners · dashboard · [Partner profile and security settings](https://affitor.com/changelog/partner-profile-settings): Partners can now update their profile, avatar, payout details and password, and request a withdrawal, without contacting support. - 2026-03-31 · digest · brands, partners, developers · dashboard, tracking, api · [Improvements and fixes, March 2026](https://affitor.com/changelog/improvements-2026-03): Partner withdrawals and transaction history, team members, a hold period and cookie window per program, a redesigned brand dashboard, and a new logo. - 2026-03-28 · feature · developers · cli · [47 agent skills for affiliate workflows](https://affitor.com/changelog/affiliate-skills-v2): Run common affiliate workflows, from researching programs and drafting content to analyzing traffic, directly from your AI assistant. - 2026-03-17 · feature · developers, brands · tracking, sdk, api · [Rebuilt tracking and SDK 2.0](https://affitor.com/changelog/tracking-v2): Partner links use ?aff=, clicks, leads and sales are recorded as separate events tied by a click ID, and the SDK adds signup(). - 2026-03-15 · feature · partners, developers · marketplace, api, mcp · [list.affitor.com, a community list of programs and agent skills](https://affitor.com/changelog/list-affitor-community): Browse and star affiliate programs and agent skills on a community site, and let an AI assistant search them through an API key or a Claude connector. - 2026-02-28 · digest · brands, partners, developers · dashboard, marketplace, tracking, sdk · [Improvements and fixes, February 2026](https://affitor.com/changelog/improvements-2026-02): A redesigned homepage, the tracker on npm, sales credited even without a cookie, partial refunds, private customer emails, and timestamps in the transcript tool. - 2026-02-27 · feature · brands · dashboard · [Partner groups with their own commissions](https://affitor.com/changelog/partner-groups): Organize partners into groups and give each group its own commission rate and duration. - 2026-02-24 · feature · brands · dashboard · [Approve, reject and mark commissions as paid](https://affitor.com/changelog/commission-review): Review partner commissions in the dashboard, approve or reject them with a reason, act on many at once, and mark approved ones as paid. - 2026-02-22 · feature · developers · api, tracking · [Send leads from your server with an API token](https://affitor.com/changelog/server-side-leads-2026-02): Create an API token in the dashboard and record leads from your backend, with a test mode to try the call first. - 2026-01-28 · digest · brands, partners · dashboard · [Improvements and fixes, January 2026](https://affitor.com/changelog/improvements-2026-01): Each program page shows only its own commissions and customers, the Setting tab has your tracking snippet ready to copy, and the chart has a Share button for your program link. - 2026-01-25 · feature · developers, brands · tracking, api · [A public documentation site](https://affitor.com/changelog/docs-site-launch): A public docs site explains how tracking works, how to onboard as a brand, how to set up Stripe and how cookies are handled. - 2026-01-23 · feature · partners · dashboard · [Edit referral links and get a QR code for each](https://affitor.com/changelog/referral-link-qr): Change a referral link's short name and destination page after you create it, then download or copy its QR code. - 2025-12-30 · digest · brands, partners · dashboard, tracking · [Improvements and fixes, December 2025](https://affitor.com/changelog/improvements-2025-12): A redesigned program page, search and sort on partner lists, and test events kept out of your numbers. - 2025-12-11 · feature · brands · dashboard, tracking · [A Getting Started checklist for new brands](https://affitor.com/changelog/getting-started-checklist): New brands see what is left to set up, and clear guidance when the tracking code is not installed yet. - 2025-12-11 · feature · partners · dashboard · [Refer brands and earn](https://affitor.com/changelog/refer-a-brand-2025): Partners get a personal referral link to invite brands to Affitor, and earn $50 when a referred brand sets up its program and $150 when that brand reaches $1,000 in sales. - 2025-11-20 · digest · brands, partners · dashboard · [Improvements and fixes, November 2025](https://affitor.com/changelog/improvements-2025-11): A program switcher for brands, auto-accept per program, early access sign-up, and no double commission on a first subscription invoice. - 2025-11-19 · feature · brands, partners · dashboard · [Message your brands and partners in Affitor](https://affitor.com/changelog/brand-partner-messages): Brands and partners talk in Affitor, with conversations, contacts and messages that arrive live. - 2025-10-29 · digest · brands, partners · dashboard, marketplace, tracking · [Improvements and fixes, October 2025](https://affitor.com/changelog/improvements-2025-10): A public application form for brands, a customer status filter for brands, and commissions on every subscription renewal. - 2025-10-29 · feature · brands, partners · dashboard, tracking · [Connect Stripe and see every commission](https://affitor.com/changelog/stripe-connect-commissions): Brands connect their Stripe account so checkout sales are matched to partners, and a new Commissions screen lists each program's commissions with filters. - 2025-09-29 · feature · brands, partners · dashboard, marketplace, tracking · [Run your own affiliate program on Affitor](https://affitor.com/changelog/affiliate-programs-for-brands): Brands create affiliate programs, partners apply and get tracked links, and clicks, sign-ups and checkout sales are attributed to the partner who sent them. - 2025-08-29 · digest · partners · marketplace, dashboard · [Improvements and fixes, August 2025](https://affitor.com/changelog/improvements-2025-08): Browse affiliate programs by category with counts, sorting and page numbers, faster category pages, and no more NaN referral balances. - 2025-07-31 · digest · partners · dashboard, tracking · [Improvements and fixes, July 2025](https://affitor.com/changelog/improvements-2025-07): Short referral links, community sign-in with your Affitor account, and redesigned program pages. - 2025-07-26 · feature · partners · dashboard, tracking · [Join the Affitor referral program](https://affitor.com/changelog/referral-program-2025): Get referral links for Affitor and follow your visitors, leads, conversions and commissions in one dashboard. - 2025-07-23 · feature · partners · dashboard, tracking · [Publish pages with your referral links built in](https://affitor.com/changelog/pages-with-referral-links): Write a page in a rich-text editor, add images and links, and give each page its own referral link. - 2025-06-20 · digest · partners · dashboard · [Improvements and fixes, June 2025](https://affitor.com/changelog/improvements-2025-06): A redesigned script assistant chat box, and Show more works again on video lists. - 2025-05-29 · digest · partners · dashboard · [Improvements and fixes, May 2025](https://affitor.com/changelog/improvements-2025-05): A Top Ads page with transcripts, Google sign-in that works from in-app browsers, and no more duplicate ads. - 2025-05-18 · pricing · partners · dashboard · [Paid plans for more research](https://affitor.com/changelog/paid-plans-2025): Monthly, quarterly and yearly plans, paid by card through Stripe, with coupons and cancel anytime. - 2025-04-30 · digest · partners, brands · marketplace · [Improvements and fixes, April 2025](https://affitor.com/changelog/improvements-2025-04): Google sign-in, filters you can share, traffic by country, the value of a conversion on every program, and a form to submit a program. - 2025-04-14 · feature · partners · dashboard · [Write video scripts with an AI assistant](https://affitor.com/changelog/ai-script-assistant): Turn the transcript of a popular video about a program into a script for your own video. - 2025-03-23 · feature · partners · marketplace · [Find affiliate programs in one searchable table](https://affitor.com/changelog/program-directory-launch): Affitor starts as a directory of affiliate programs for creators and marketers, with search, sorting and a page for every program. --- id: "changelog/improvements-2026-11-09" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-11-09" updated: "2026-11-09" --- # Planned integrations and One-click Stripe Payment Links > Integrations lists planned integrations and marks Stripe Payment Links One-click; a missing page outside Docs, Blog and Changelog has one button. ### New - **Integrations** has a **Planned** section under **All**: Dodo Payments, Paddle, Vercel, Stripe App and Webhooks. ### Improved - **Stripe Payment Links** on **Integrations** is marked **One-click**: one approval on Stripe's page, with no key and no webhook. - The guide links on the Clerk, Supabase and NextAuth integration pages open the signup step of the Next.js guide. - A missing page outside Docs, Blog and the Changelog shows **Page not found** and one button: **Go to Dashboard** when signed in, **Go to Marketplace** when not. - The homepage steps and FAQ describe revenue share on sales only; the FAQ lists one-time, recurring for a set number of months, or lifetime. - The footer on the homepage, Pricing, Docs, Blog and the Changelog links to Affitor on GitHub. ### Fixed - Partners who open a link to **Integrations** in their dashboard while signed out see it right after signing in, without reloading. - Editing a group that still pays per click or per lead keeps those terms unless you pick new ones. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - Saying a Planned integration works today: the section lists names only, with no date. - Saying Planned integrations appear in integrations.md or llms.txt: they stay out, so an AI agent never reads them as live. - Saying Stripe Payment Links tracking is new: only its label changed. - Saying the Clerk, Supabase Auth or NextAuth guides are new pages: the links now open the signup step of the Next.js guide. - Saying Stripe Payment Links need nothing on your site: the Affitor tracker on your page adds the click. - Saying the Page not found screen has a Go Back button or a large 404: it has one button and three links. - Saying groups that pay per click or per lead were converted or stop paying: their terms stay as they are. ### Media - Image (Payments on the Integrations page: Stripe, Stripe Payment Links with a One-click tag, and Polar, each with its logo): light https://affitor.com/docs/changelog/improvements-2026-11-09/payments-light.png, dark https://affitor.com/docs/changelog/improvements-2026-11-09/payments-dark.png, raw https://affitor.com/docs/changelog/improvements-2026-11-09/payments-raw.png --- id: "changelog/improvements-2026-11-08" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-11-08" updated: "2026-11-08" --- # Link preview images, four more AI agents, and a withdrawal check > Shared links show preview images, Integrations adds Grok, Muse Code, Hermes Agent and OpenClaw, and a repeat withdrawal within five minutes is refused. ### New - Links you share from Affitor now show a preview image made for that page or program. ### Improved - The **Integrations** page lists Grok, Muse Code, Hermes Agent and OpenClaw with the other AI agents. - Each AI tool card on **Integrations** opens that tool's own steps in Connect your AI tool. - The **Build on the Affitor API** tile is now **Server API**, under Frameworks and auth: track clicks, signups and sales from your backend. ### Fixed - In **Connect an AI tool**, the partner steps now also say to pick your programs, then click **Allow**. - Category pages that answer in Markdown, such as `/ai-video.md`, now list each program's monthly traffic. - Requesting the same amount to the same payout account again within five minutes, while the first is pending or approved, is refused with a note pointing to **Payouts**. - On Stripe Connect programs, a sale partly refunded before its numbers were counted now adds its net to program revenue and counts as a conversion, instead of staying at zero. - Chat app previews of a referral short link on affitor.com no longer add to its visitor count. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - Saying Grok or Muse Code connect in one click: Grok is a custom connector added at grok.com/connectors, Muse Code is set up from the terminal. - Saying the Server API is new: it is the same API; only the tile's name, place and line changed. - Saying category pages in Markdown showed traffic before: the values were left out since those pages first answered in Markdown. - Saying partners can now choose programs: the consent screen already offered it; only the written steps changed. - Saying AI tools can now write or change programs: connections still only read. - Saying every shared link shows a custom image: a page that cannot be drawn falls back to the default Affitor card. - Saying Hermes Agent or OpenClaw connect in one click: their cards open written steps. - Saying duplicate withdrawals are impossible: a different amount, or the same request after five minutes, still creates a second pending request. - Saying partners can cancel a payout: they cannot. - Saying a full refund before processing counts revenue: it stays at zero. - Saying the refund fix applies to older sales: it applies going forward only. - Saying every real visit now counts once: this change only stops previews from counting. - Saying bots can never count: a direct request to the redirect endpoint still counts. - Saying every early-refunded sale is recovered: one whose refund record is missing or disputed stays held. ### Media None. --- id: "changelog/improvements-2026-11-07" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-11-07" updated: "2026-11-07" --- # Members land on their program, Grok steps, and Markdown pages > Team members land on their program after sign-in, Connect an AI tool has Grok steps, six more pages answer in Markdown, and deleting an API key no longer fails. ### Improved - In **Connect an AI tool**, the **Other** tab now has steps for Grok: add Affitor as a custom connector at grok.com/connectors, then sign in. - In **Connect an AI tool**, the **Other** tab now has steps for Muse Code: add Affitor to `~/.config/muse/settings.json`, then run `muse mcp login affitor` in your terminal. - AI tools can read `/agents`, `/switch`, `/privacy`, `/terms`, `/legal/refer-program` and `/legal/subprocessors` as Markdown: add `.md` to the address or send `Accept: text/markdown`. - AI tools can read category pages such as `/ai-video` as Markdown, with the first 50 programs the page lists: add `.md` to the address or send `Accept: text/markdown`. - The **Commission Type** menu in a commission policy now offers CPS One-time, CPS Recurring and CPS Lifetime only. - Policies that already use CPC or CPL are not changed. ### Fixed - In **Connect an AI tool**, the brand steps for Claude, ChatGPT, Grok and Muse Code now say to pick your programs, then click **Allow**. - The AI agents page at `/agents` lists all 13 tools, including `list_programs`, and says a brand connection reads the programs you choose when you connect. - Team members with no brand or partner account of their own now land on their team's program after signing in, instead of **How will you use Affitor?** - If your brand has no program yet, opening **Groups**, **Commissions** or another dashboard section takes you to creating your first program. - A saved **Dashboard** link for a program you can't open now takes you to a program you can, or to setting one up if you have none. - In Program settings, **Business** drafts the About text once per program in your browser, so reloading the page no longer asks for a new draft. - Screen readers now announce when the totals on **Commissions** are updating. - Program pages in the marketplace no longer show the program name, facts and **Apply to promote** button stacked in one spot for a moment while loading. - Deleting an API key no longer fails. After you type the key's name to confirm, the key is deleted. - Affitor now accepts the sign-in from Town and from Perplexity Enterprise, so they can finish connecting when you add Affitor's MCP server. - If the database can't confirm a save, commission status changes, invoice settlement, payouts marked as sent and disputes now return an error and notify no one, instead of reporting success. - For an inactive referral link, the hint from `POST /api/v1/track/click` now says the link or its program is not active, instead of saying the partner or brand turned it off. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - Saying Town or Perplexity Enterprise were tested end to end: Affitor now accepts their sign-in, and nobody has connected one yet. - Saying saves used to fail often or that money was lost: this only matters when the database fails at the moment of saving. - Saying an error means nothing was saved: the save may have happened when only its confirmation was lost; retrying is safe. - Saying partner withdrawal requests changed: they did not. - Saying Grok has a one-click install: it is a custom connector added at grok.com/connectors. - Saying anything about old directory pages or OpenAffiliate redirects. - Saying Cancel on the AI app consent screen changed. - Saying team members get a brand account or new permissions: they land on a program they already belong to. - Saying Muse Code connects in one click: you add Affitor to its settings file, then sign in from the terminal. - Saying the Markdown answer lists every program in a category: it lists the first page the category table shows. - Saying every category address answers in Markdown: a category whose address a short link already uses redirects to that link. - Saying Affitor pays per click or per lead, or that CPC or CPL policies stop working, stop paying or are converted: commissions come from sales, and this update only changes what the menu offers. - Saying settings pages load faster: no measured number yet. - Saying AI tools can now write or change programs: connections still only read. - Saying brands can now pick several programs when an AI tool connects: that has worked since November 3; this update only changes the instructions and the AI agents page. ### Media None. --- id: "changelog/improvements-2026-11-06" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-11-06" updated: "2026-11-06" --- # A Claude Code plugin, Join or Create on consent, and payout skip > A Claude Code plugin and Gemini CLI extension, Add to Claude and VS Code links, Join or Create on AI app consent, and a payout skip per account. ### Improved - Add Affitor to Claude or VS Code in one click from Connect an AI tool, which now has a VS Code tab. Manual setup steps stay as a fallback. - When your account has nothing to connect yet, the AI app consent screen offers Join as partner or Create program, then takes you back to approve. ### Fixed - Skip for now on payout setup applies only to the account you are signed in with. Another account on the same browser keeps its own Finish setup. ### For developers - Install the [Affitor plugin](https://github.com/Affitor/claude-plugins) in Claude Code, or the extension in Gemini CLI, and sign in with your Affitor account. Access is read-only and needs no API key. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - Saying the plugin or extension is listed in a plugin directory, gallery or marketplace. - Saying AI apps can create links, send test sales or change data: access is read-only. - Saying the dashboard now opens your first active program instead of an archived one. - Saying Add to Claude or Add to VS Code connects without signing in: you still sign in to Affitor. ### Media - Image (The Connect an AI tool sheet open on the Claude tab, with an Add to Claude button and the manual steps): light https://affitor.com/docs/changelog/improvements-2026-11-06/connect-claude-light.png, dark https://affitor.com/docs/changelog/improvements-2026-11-06/connect-claude-dark.png - Image (The consent page with Nothing to connect yet and two choices, Join as partner and Create program): light https://affitor.com/docs/changelog/improvements-2026-11-06/consent-empty-light.png, dark https://affitor.com/docs/changelog/improvements-2026-11-06/consent-empty-dark.png, raw https://affitor.com/docs/changelog/improvements-2026-11-06/consent-empty-raw.png --- id: "changelog/improvements-2026-11-05" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-11-05" updated: "2026-11-05" --- # Chat for two-sided accounts, kept rows, and bulk Reject fixes > Chat keeps brand and partner sides apart, Partners, Groups and Commissions keep their rows on revisit, and bulk Reject acts only on pending selections. ### Improved - If you are on a brand team and also a partner, Chat keeps each side's conversations, people, replies and uploads apart when you switch sides. - Partners and Groups show the rows you last saw right away when you come back, then refresh them in place. - Commissions refreshes its list and totals when you come back and after every action. Totals turn gray while they update. ### Fixed - Bulk Reject on Commissions sends only the rows selected in the current list, and cancels if any of them stopped being pending. - When the list fails to load, Commissions shows the error alert alone, without an empty "No commissions found" table. - Switching programs on Groups clears the open group, so its details never show the previous program's partners. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - Sales in other currencies, tax or refunds: they have their own entry for Nov 5. - Onboarding or signup changes: they are not part of this entry. - A page speed or download size figure. ### Media - Image (Commissions refreshing: Revenue, Commission and To pay shown in gray while the new totals load): light https://affitor.com/docs/changelog/improvements-2026-11-05/commissions-light.png, dark https://affitor.com/docs/changelog/improvements-2026-11-05/commissions-dark.png, raw https://affitor.com/docs/changelog/improvements-2026-11-05/commissions-raw.png --- id: "changelog/multi-currency-sales" type: "changelog" url: "https://affitor.com/changelog/multi-currency-sales" updated: "2026-11-05" --- # Send sales in other currencies, with commissions before tax > Sales in other currencies are converted to USD when recorded, and commissions and platform fees use the price after discounts and before tax. **Action required.** Developers: If you report refunds through the API, send `refund_amount_cents` in the sale's own currency and minor unit, or leave it out to refund the whole sale. A value of 0 is no longer accepted for sales from November 5. Send sales in other currencies, and send the tax inside each sale. Starting Thursday, November 5, 2026 (16:00 UTC), we handle tax and currency differently in commissions and platform fees on new sales. Until now, a sale sent through the API was commissioned on the amount as sent: amounts were not converted between currencies, and `tax_cents` was accepted but not used. Now the currency and the tax both count. ## How it works - Commissions and platform fees are calculated on the price your customer paid after discounts and before tax, whenever your payment provider or your API call gives us the tax amount. - Sales in other currencies are converted to USD at the latest daily exchange rate when the sale is recorded, and we keep the original amount next to it. - Commissions already recorded do not change. ## Send the tax with each sale If your amount includes tax, add the tax in the `tax_cents` field of `POST /api/v1/track/sale`, in the same unit as `amount_cents`. Set `currency` to the sale's own currency: ```json tab="Request body" { "transaction_id": "txn_abc123", "customer_key": "usr_9876", "amount_cents": 490000, "tax_cents": 40000, "currency": "VND" } ``` Despite its name, `amount_cents` uses the currency's minor unit, not always hundredths: USD 49.00 is `4900`, VND 490,000 is `490000`, and BHD 1.234 is `1234`. A currency we do not support returns `422 unsupported_currency` and creates no sale. ## What to do If you report refunds, send `refund_amount_cents` in the sale's own currency and minor unit, or leave it out to refund the whole sale. A value of 0 is no longer accepted for sales from November 5: `0`, a negative number or a non-integer returns `400 invalid_request`. Refunds of earlier sales work as before. ```bash tab="cURL" curl -X POST https://api.affitor.com/api/v1/track/refund \ -H "Authorization: Bearer YOUR_PROGRAM_API_KEY" \ -H "Content-Type: application/json" \ -d '{"transaction_id":"txn_abc123","refund_amount_cents":10000,"refund_id":"re_123"}' ``` ## Conclusion From November 5, tax and currency count in commissions and platform fees on new sales. [Learn more in Track Sale](https://affitor.com/docs/api-reference/track-sale) and [Track Refund](https://affitor.com/docs/api-reference/track-refund), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - Starting Thursday, November 5, 2026 (16:00 UTC), Affitor handles tax and currency differently in commissions and platform fees on new sales. - Commissions and platform fees are calculated on the price the customer paid after discounts and before tax, whenever the payment provider or the API call gives Affitor the tax amount. - Sales in other currencies are converted to USD at the latest daily exchange rate when the sale is recorded, and Affitor keeps the original amount next to it. - Commissions already recorded do not change. - API sales go to POST https://api.affitor.com/api/v1/track/sale. If the amount includes tax, send the tax in tax_cents, in the same unit as amount_cents. Reference: https://affitor.com/docs/api-reference/track-sale - amount_cents and tax_cents use the currency's minor unit, not always hundredths: USD 49.00 is 4900, VND 490,000 is 490000, BHD 1.234 is 1234. - For sales recorded from November 5, 2026 (16:00 UTC), refund_amount_cents on POST /api/v1/track/refund is in the sale's own currency and minor unit, tax included. Leaving it out refunds the whole sale. 0, a negative number or a non-integer returns 400 invalid_request. Reference: https://affitor.com/docs/api-reference/track-refund - Refunds of sales recorded before November 5, 2026 (16:00 UTC) work as before. - A currency code Affitor does not support returns 422 unsupported_currency and creates no sale, commission or fee. ### Avoid - A change to the platform fee rate or to pricing plans (only the amount the fee is calculated on changed) - Saying every currency in the world is accepted (codes without a numeric minor unit and ten listed codes are not) - Saying commissions or fees already recorded were recalculated - Saying the dashboard shows the original currency or amount (it is kept on the sale record, not shown) - Promising every non-USD sale is priced at once (a sale with no usable daily rate is kept with no commission, see Track Sale) - Naming the exchange rate providers - Converting amount_cents or refund_amount_cents to USD or subtracting tax before sending them - Saying a refund amount of 0 now refunds the whole sale on new sales (it returns 400; leave the field out instead) ### CTA [Read Track Sale](https://affitor.com/docs/api-reference/track-sale) ### Media None. --- id: "changelog/mcp-multiple-programs" type: "changelog" url: "https://affitor.com/changelog/mcp-multiple-programs" updated: "2026-11-03" --- # Connect an AI tool to several programs at once > Pick up to 50 programs, or all current and future ones, when an AI tool connects over MCP, and see each connection's programs in AI agents. Connect Claude, ChatGPT, Cursor or another AI tool to several of your programs in one step, or to all of them, including programs you join later. Until this week, a brand connection reached one program: the consent screen asked you to pick a single **Program**, so each program needed its own connection, and a partner connection always covered every program you had joined. Now you choose the programs on the same screen, and one connection reads all of them. ## How it works - **Pick programs**: tick up to 50 programs, or choose **All current and future programs**. - **Read-only**: a connection reads your data and changes nothing. - **One list to manage**: **AI agents** shows which programs each connection reaches. ## Choose programs when you connect When your AI tool asks to connect, Affitor shows the account you are signed in with, then **Access** and **Programs**. Open **Read account data**, always on, to see the four kinds of data the tool can read. Under **Programs**, tick the programs you want, each shown with your role, or choose **All current and future programs** so programs you join later are included without reconnecting. With a long list, **Search programs** narrows it. If you are on a brand team and also a partner, switch between **As a brand** and **As a partner**. Then click **Allow**. ## See and remove access in Settings Brands open **AI agents** under **Developers** in Program settings. **Connections** lists each AI tool with **Connected by**, **Added**, **Last used** and **Access**, and shows the programs it reaches under its name. Partners find their list under **Integrations** in the account menu. **Disconnect** your own connection to end its access to every program in it. Removing a teammate's connection from a program ends its access to that program only; its other programs keep their access. ## Conclusion One connection now reaches the programs you choose. [Learn more in AI agents](https://affitor.com/brand/settings/ai-agents), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - When an AI tool such as Claude, ChatGPT or Cursor connects to Affitor over MCP, the consent page shows the signed-in account, then Access and Programs, then Cancel and Allow. - Under Programs, a person ticks up to 50 programs or chooses All current and future programs. All also covers programs they join later, without reconnecting. - Each program in the list shows the person's role, such as Owner. With more than six programs, Search programs narrows the list. - Someone who is on a brand team and is also a partner switches between As a brand and As a partner on the consent page. - Access shows Read account data, always on (label since 06/11; it read Read-only on 03/11). A brand connection reads programs and settings, partners and applications, clicks and leads, and commissions and billing. A partner connection reads programs joined, links and clicks, commissions and earnings, and payouts. - Brands manage connections at https://affitor.com/brand/settings/ai-agents (program menu, Program settings, Developers, AI agents). Connections lists Client, Connected by, Added, Last used and Access, with the programs each connection reaches under the client name. - Partners manage their connections from the account menu, under Integrations. - Disconnect ends a connection's access to every program in it. Removing a teammate's connection from a program ends its access to that program only. ### UI labels - `Access` - `Read account data` - `Always on` - `Programs` - `All current and future programs` - `Search programs` - `Select up to 50, or choose All` - `As a brand` - `As a partner` - `Switch` - `Remove access any time in Settings.` - `Cancel` - `Allow` - `AI agents` - `Affitor MCP` - `Server URL` - `Connections` - `Client` - `Connected by` - `Added` - `Last used` - `Disconnect` - `Remove` - `Integrations` ### Avoid - Write actions or changes made through an AI tool (connections are read-only) - Going live, creating programs or changing settings from an AI tool - Editing which programs an existing connection reaches (there is no edit control) - More than 50 hand-picked programs in one connection (beyond 50, choose All) - Tabs such as Agents, Activity or Explore on the AI agents page, or a permission dropdown - New ways for AI tools to register with Affitor - An API key for the hosted MCP server (it uses sign-in) - Saying a program owner, or any one role, decides who can remove a teammate's connection ### CTA [Open AI agents](https://affitor.com/brand/settings/ai-agents) ### Media - Image (Consent screen: Claude wants to access Affitor, with read-only access and All current and future programs selected): light https://affitor.com/docs/changelog/mcp-multiple-programs/consent-light.png, dark https://affitor.com/docs/changelog/mcp-multiple-programs/consent-dark.png, raw https://affitor.com/docs/changelog/mcp-multiple-programs/consent-raw.png - Image (AI agents in Program settings with two connections, one listing its programs and one with All current and future programs): light https://affitor.com/docs/changelog/mcp-multiple-programs/connections-light.png, dark https://affitor.com/docs/changelog/mcp-multiple-programs/connections-dark.png, raw https://affitor.com/docs/changelog/mcp-multiple-programs/connections-raw.png --- id: "changelog/improvements-2026-11-02" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-11-02" updated: "2026-11-02" --- # Send feedback, complete analytics, and one Affitor mark > Send feedback from the account menu, analytics without a Building history wait, Last 30 days with today, one Affitor mark, and Grok connections. ### New - Send feedback from the account menu: pick a topic (Idea, Bug, Question or Other), write a note, and optionally rate how Affitor feels. The team reads every message. ### Improved - Dashboard analytics no longer stop at "Building history for this range": cards and charts load your numbers for every range in the date picker. - Last 30 days now includes today: it covers the past 29 days plus today so far. - The browser tab icon, the AI app consent page and the icon MCP clients display all use the blue Affitor mark from the site header. ### For developers - You can add Affitor to Grok on grok.com as a custom connector with `https://mcp.affitor.com/mcp`, then sign in and approve it on Affitor. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - Saying custom date ranges changed: the date picker already limited them to about 30 days. - Saying the API-key Analytics API changed: these changes are on the brand and partner dashboards. - Saying Grok tools were tried in a Grok chat: only connecting and approving was checked. - Any listing in Claude's or another app's connector directory. ### Media - Image (Send feedback from the account menu with a topic, a message box and four faces to rate): light https://affitor.com/docs/changelog/improvements-2026-11-02/feedback-light.png, dark https://affitor.com/docs/changelog/improvements-2026-11-02/feedback-dark.png, raw https://affitor.com/docs/changelog/improvements-2026-11-02/feedback-raw.png --- id: "changelog/improvements-2026-11-01" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-11-01" updated: "2026-11-01" --- # Program logos in one frame, and numeric IDs on tracking > Referral and invite pages show program logos whole in one framed tile, and lead and refund tracking accept whole-number IDs. ### Improved - On Referrals, referred brands and invite pages, program logos use the uploaded logo, or else the website logo, shown whole in a white framed tile. ### For developers - `POST /api/v1/track/lead` accepts a positive whole number as `customer_key`, and `POST /api/v1/track/refund` accepts one as `transaction_id` or `refund_id`, treated like the same value sent as a string. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - Saying every program now shows a logo: without an uploaded or validated website logo, Referrals shows an initial tile and invite pages show none. - Saying whole-number IDs work on every tracking endpoint: only customer_key on lead, and transaction_id and refund_id on refund. - Any Stripe Connect attribution or security change from this release. ### Media - Image (Referrals with program logos framed in white tiles next to a program without a logo shown by its initial): light https://affitor.com/docs/changelog/improvements-2026-11-01/logos-light.png, dark https://affitor.com/docs/changelog/improvements-2026-11-01/logos-dark.png, raw https://affitor.com/docs/changelog/improvements-2026-11-01/logos-raw.png --- id: "changelog/api-key-permissions" type: "changelog" url: "https://affitor.com/changelog/api-key-permissions" updated: "2026-10-27" --- # Give each API key Full access or Tracking only > Set Full access or Tracking only on each program API key, rename it or change its permission, and disable or enable it without a new key. Give each program API key its own permission, **Full access** or **Tracking only**, and turn a key off and on again without replacing it, in [API keys](https://affitor.com/brand/settings/api-keys). Until this week, the API keys table showed Name, Created and Last used, a new key asked only for a name, and each key offered Rotate and Expire. Now every key has a permission you can change, and you can disable a key instead of expiring it. ## How it works - **Two permissions**: **Full access** sends tracking events and reads your stats. **Tracking only** can send clicks, signups, sales and refunds. - **Edit any time**: rename a key or change its permission. The key itself stays the same. - **Disable and enable**: stop a key's calls, then turn it back on later. ## Create a key with a permission Click **Create key**, enter a name and pick **Full access** or **Tracking only**. Full access is selected by default. Your new key appears once in **Copy your key**, so copy it before you click **Done**. Use Tracking only for a server that only reports events. If that key asks for your stats, the request is refused. ## Manage a key from its menu The table shows **Name**, **Key**, **Permission**, **Last used** and **Created** for each live key. From the row menu: - **View details**: the masked key, permission, last use and status. - **Edit key**: a new name or permission, applied from the next call. - **Disable key** or **Enable key**: a disabled key is marked **Disabled**, and its calls are refused until you enable it. - **Rotate key**: a new key with the same name and permission. The old key stops right away. ## Where to find it Open the program menu, choose **Program settings**, then **Developers** › **API keys**. Owners and Admins of the program see this table. ## Conclusion Each key now does only what you allow. [Learn more in API keys](https://affitor.com/brand/settings/api-keys), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - Owners and Admins manage program API keys at https://affitor.com/brand/settings/api-keys (program menu, Program settings, Developers, API keys). - The API keys table shows Name, Key (masked), Permission, Last used and Created. On phones it shows Name, Permission and the menu, with the masked key under the name. - Create key asks for a Name (up to 80 characters) and a Permission: Full access (selected by default) or Tracking only. - Full access sends tracking events and reads stats. Tracking only can send clicks, signups, sales and refunds, and is refused when it asks for stats. - A new or rotated key is shown once, in Copy your key, with Copy and Done. - Each row's menu includes View details, Edit key, Rotate key, and Disable key or Enable key. - Edit key changes the name or the permission. Changes apply to the next call, and the key itself stays the same. - A disabled key shows Disabled next to its name and its calls are refused until it is enabled again. - Rotate key issues a new key with the same name and permission and stops the old key right away. - View details shows Key, Permission, Last used and Status (Active or Disabled), and who created the key when known. ### UI labels - `API keys` - `Create key` - `Name` - `Permission` - `Full access` - `Tracking only` - `Send tracking events and read your stats.` - `Can only send clicks, signups, sales, refunds and chargebacks.` - `Key` - `Last used` - `Created` - `View details` - `Edit key` - `Rotate key` - `Disable key` - `Enable key` - `Disabled` - `Active` - `Status` - `Copy your key` - `Copy` - `Done` - `Save` - `Cancel` ### Avoid - Deleting a key, or saying Delete key works - Expiring a key from this table (Expire is replaced by Disable and Enable) - Test keys or test mode keys in this table (it lists live keys only) - Members or Viewers managing keys (Owners and Admins only) - Seeing a key again after Copy your key closes - Permissions beyond Full access and Tracking only, or per-endpoint scopes - Saying a disabled key is deleted or replaced ### CTA [Open API keys](https://affitor.com/brand/settings/api-keys) ### Media - Image (Create key with a name filled in and Full access or Tracking only to pick): light https://affitor.com/docs/changelog/api-key-permissions/create-key-light.png, dark https://affitor.com/docs/changelog/api-key-permissions/create-key-dark.png, raw https://affitor.com/docs/changelog/api-key-permissions/create-key-raw.png - Image (API keys with a Full access key, a Tracking only key and a Disabled key, each with its masked key and Permission): light https://affitor.com/docs/changelog/api-key-permissions/api-keys-light.png, dark https://affitor.com/docs/changelog/api-key-permissions/api-keys-dark.png, raw https://affitor.com/docs/changelog/api-key-permissions/api-keys-raw.png --- id: "changelog/improvements-2026-10-27" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-10-27" updated: "2026-10-27" --- # Website logos at signup, public names, and composer focus > New programs pick up the website's logo, partners show by public name in Chat and Sources, Viewers read Chat only, and the composer keeps focus. ### Improved - Continue on the first step of `/brand/new` now brings in your website's logo as the program logo when a large enough icon exists. A logo you already have stays. - Chat shows a partner's public name, or a dash when none is set, instead of an email prefix or a word like Partner. - The Sources report labels partners by their public name, or a dash when none is set, instead of an account username or a partner ID. - Viewers on a brand team can read Chat but not send: the composer, Reply and New message are hidden, also when they open a link directly. - After you send a message, the message box keeps your cursor so you can type the next one. - When you approve or reject an application outside the Inbox, its notification shows Resolved right away instead of still offering Review application. ### Fixed - You can attach images and PDFs again in existing Chat conversations. The first message in a new conversation stays text only. - Your Profile and a program's Customers tab show a dash instead of N/A for missing dates and names. A canceled plan is labeled in gray instead of red. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - API key permissions (Full access, Tracking only, disable, rotate): they have their own entry for Oct 27. - Saying the logo import replaces a logo you uploaded, or runs on Save and exit. - Naming a minimum icon size for the logo import. - Saying Payouts showed N/A before. - Saying the first message in a new conversation can carry an attachment. - A pending chat requests list (no screen shows it). ### Media - Image (The Inbox, opened over Commissions, with a new application waiting for review above an approved one marked Resolved): light https://affitor.com/docs/changelog/improvements-2026-10-27/inbox-light.png, dark https://affitor.com/docs/changelog/improvements-2026-10-27/inbox-dark.png, raw https://affitor.com/docs/changelog/improvements-2026-10-27/inbox-raw.png --- id: "changelog/improvements-2026-10-26" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-10-26" updated: "2026-10-26" --- # Chat at its own address, your name in menus, and customer keys > Chat moves to its own address, menus show your name, and sales and commissions fall back to your customer key when no email is recorded. ### Improved - Chat now lives at `/brand/chat` and `/partner/chat`. Old Messages links, notification links and sign-in return links open Chat. - Latest sales and brand commission screens fall back to your own customer key when a sale has no email, instead of Unknown customer or a numbered placeholder. - Your name now shows in the sidebar, the account menu and Profile, instead of Brand, Partner or user@example.com. Without a name, a readable form of your email shows. - Brand commission screens show the partner's public name, or their contact email, instead of N/A when no name is set. - Chat shows each program by its name. Payout rows show the program instead of Unknown program, and payments without a program show their type, such as Commissions. ### Fixed - The new message list in partner Chat only offers programs you can message. A link to one you can't message says so. - On phones, Profile opened from the site menu no longer closes when the menu drawer closes. Commission lists say 1 result instead of 1 results. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - Totals across all programs on the partner Programs page: it has its own entry for Oct 26. - Saying Chat or commission screens used to show numeric program or customer ids as names. - Saying partners see a customer's full email (partners see a masked email). - Saying an AI app can choose only one program, or can change data. ### Media - Image (Brand Chat with the signed-in name, Robin Hale, in the sidebar footer): light https://affitor.com/docs/changelog/improvements-2026-10-26/chat-light.png, dark https://affitor.com/docs/changelog/improvements-2026-10-26/chat-dark.png, raw https://affitor.com/docs/changelog/improvements-2026-10-26/chat-raw.png --- id: "changelog/partner-programs-analytics" type: "changelog" url: "https://affitor.com/changelog/partner-programs-analytics" updated: "2026-10-26" --- # Track all your programs from the Programs page > Programs adds up clicks, leads, sales and earnings across every program you joined, and each program opens on the same date range with its top links. Open [Programs](https://affitor.com/partner) to see clicks, leads, sales and earnings across every program you joined, for the date range you pick. Until today, Programs listed your programs in a table with Clicks, Signups, Paid Signups, Revenue and Total Commission, and no totals for all of them. A program's Overview showed five numbers for 7d, 30d, 90d or All. Now one card at the top of Programs adds up every program, and each program opens on the same date range. ## How it works - **One totals card**: Clicks, Leads, Sales and Earnings across all your programs, each against the period before. - **One header**: on wider screens, Find programs, All programs and the date range sit next to the title. - **Program pages**: the same four totals for one program, your top links and What you earn. ## See all your programs at once At the top of Programs, one card shows **Clicks**, **Leads**, **Sales** and **Earnings** for every program you joined, each with its change against the previous period. Click a total to put it on the chart, where the period before is a dashed line. Below the card, **Your programs** lists each program with its clicks and earnings. ## Pick a program and a date range Choose **Today**, **Yesterday**, **Last 7 days** or **Last 30 days**, or pick **Start** and **End** days on the calendar. With nothing saved, Programs opens on Last 30 days. On a phone, the pickers sit under the title. Choose a program in **All programs**, or click one in Your programs, to open its page with the same date range. ## Open a program A program's **Overview** shows the same four totals and chart for that program alone. Below them, **Links** lists up to four of your links with their clicks, and **What you earn** shows the program's commission terms. ## Where to find it **Programs** is in the left rail at [affitor.com/partner](https://affitor.com/partner). Old links to `/partner/analytics` open Programs. ## Conclusion Your totals for every program and each program's numbers now share one page and one date range. [Learn more on Programs](https://affitor.com/partner), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - Partners open Programs at https://affitor.com/partner, from Programs in the left rail. - With at least one program, Programs shows from top to bottom: the header, the Finish setup or Start earning card when it applies, one card with four totals (Clicks, Leads, Sales, Earnings) above one chart, then Your programs. - The totals add up every program the partner joined. Each total shows its change against the previous period, or New when the previous period had none. Clicking a total puts it on the chart, which draws the period before as a dashed line. - On screens 761 px and wider, the header is one row: Programs on the left, then Find programs, All programs and the date range on the right. On phones, the program and date pickers sit under the title. - The date range offers Today, Yesterday, Last 7 days and Last 30 days, plus Start and End days on a calendar. With nothing saved, it opens on Last 30 days. - Choosing a program in All programs, or clicking a program in Your programs, opens that program's page with the same date range. - A program's Overview tab shows the same four totals and chart for that program, a Links card with up to four of the partner's links and their clicks, and What you earn with the program's commission terms. - Old links to https://affitor.com/partner/analytics open Programs. ### UI labels - `Programs` - `Find programs` - `All programs` - `Last 30 days` - `Today` - `Yesterday` - `Last 7 days` - `Start` - `End` - `Date range` - `Clicks` - `Leads` - `Sales` - `Earnings` - `New` - `Your programs` - `Overview` - `Links` - `Customers` - `Commissions` - `What you earn` - `Copy link` - `No clicks in this period` ### Avoid - Revenue as a partner total (partners see Earnings) - Signups, Paid signups or Total Commission as the new labels (those were the old ones) - Other date choices such as 7d, 30d, 90d, All, Last 90 days or All time - A separate partner Analytics page or a Dashboard item in the partner rail - Saying Find programs shows in the header on phones - Saying the totals card shows for a partner who has no programs yet - Saying Earnings counts only paid commission - A custom range of a specific length - Real-time or live numbers ### CTA [Open Programs](https://affitor.com/partner) ### Media - Image (Programs with Find programs, All programs and Last 30 days in one row, four totals (Clicks, Leads, Sales, Earnings) above one chart, and Your programs below): light https://affitor.com/docs/changelog/partner-programs-analytics/programs-light.png, dark https://affitor.com/docs/changelog/partner-programs-analytics/programs-dark.png, raw https://affitor.com/docs/changelog/partner-programs-analytics/programs-raw.png --- id: "changelog/brand-dashboard" type: "changelog" url: "https://affitor.com/changelog/brand-dashboard" updated: "2026-10-25" --- # Track your program on the new Dashboard > The brand Dashboard shows clicks, leads, sales and revenue against the period before, with Latest sales, Top partners and Needs you below. Open [your Dashboard](https://affitor.com/brand) to see clicks, leads, sales and revenue for the date range you pick, each against the period before it. Until today, the Dashboard showed Performance Overview: five totals, one chart with no comparison line, a choice of the last 7, 30 or 90 days or All time, and an Action Center for pending applications. Now every total is compared with the period before, and your latest sales, top partners and what needs you sit below. ## How it works - **Four totals**: Clicks, Leads, Sales and Revenue, each with its change against the previous period. - **One chart**: the total you pick, with the previous period as a dashed line. - **Three lists**: Latest sales, Top partners, and Needs you when something waits on you. ## Pick a total and a date range Click **Clicks**, **Leads**, **Sales** or **Revenue** to put it on the chart. Above it, choose **Today**, **Yesterday**, **Last 7 days** or **Last 30 days**, or pick **Start** and **End** days on the calendar. The chart draws your range as a solid line and the period before it as a lighter dashed line. Hover a point to compare the two. The Dashboard remembers your total and range in this browser. ## See sales, partners and what needs you **Latest sales** lists your most recent sales with their amounts. **Top partners** lists the partners who brought in the most revenue in your range. Rows open Commissions or Partners, and **View all** opens the full page. **Needs you** lists what waits on you: applications to review, and open invoices, shown as **Pay partners by** a date with the amount. With nothing waiting, it stays hidden. ## Cards keep their size The totals, the chart and both lists keep the same size while they load, when they are empty and when they have data. Empty lists say so, such as **No sales yet**, and a list or the chart that cannot load offers **Try again**. ## Where to find it **Dashboard** is in the left rail at [affitor.com/brand](https://affitor.com/brand) and shows the program you have open. ## Conclusion Your totals, the period before and what needs you now sit on one page. [Learn more on your Dashboard](https://affitor.com/brand), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - Brands open the Dashboard at https://affitor.com/brand, from Dashboard in the left rail. It shows the program you have open. - From top to bottom: the date range, four totals (Clicks, Leads, Sales, Revenue) above one chart, then Latest sales and Top partners (side by side on wider screens, stacked on phones), then Needs you. - Each total shows its change against the previous period, or New when the previous period had none. Clicking a total puts it on the chart. - The chart draws the selected range as a solid blue line and the period just before it as a lighter dashed line. Hovering a point shows its value and the matching value from the period before. - The date range offers Today, Yesterday, Last 7 days and Last 30 days, plus Start and End days on a calendar. With nothing saved, it opens on Last 30 days. Days are UTC days. - The Dashboard remembers the selected total and date range in the same browser. - Latest sales lists up to four of the most recent sales with their amounts and opens Commissions. Top partners lists up to four partners with the most revenue in the selected range and opens Partners. Each list has View all. - Needs you lists what waits on the brand: the number of applications to review, and each open invoice as Pay partners by a date, with its amount. Rows open Partners or Commissions. With nothing waiting, Needs you is hidden. - The totals, the chart and both lists keep the same size while they load, when they are empty and when they have data. Empty lists read No sales yet or No revenue in this period; a list, the chart or Needs you that cannot load offers Try again, and a total that cannot load reads Not available. ### UI labels - `Dashboard` - `Clicks` - `Leads` - `Sales` - `Revenue` - `New` - `Today` - `Yesterday` - `Last 7 days` - `Last 30 days` - `Start` - `End` - `Date range` - `Latest sales` - `Top partners` - `View all` - `Needs you` - `Pay partners by` - `No sales yet` - `No revenue in this period` - `Try again` ### Avoid - A Next row, next step or Next card on the Dashboard (there is none) - A Dashboard for partners (this one is for brands only) - Other date presets such as This month, Last 90 days, This year or All time (the picker has Today, Yesterday, Last 7 days and Last 30 days) - Custom ranges that reach back more than 60 days - Saying Latest sales or Needs you follow the date range (they always show the latest items) - A switch to hide the comparison (it is always on) - Full customer emails or names in Latest sales (rows show a masked email, the brand's own customer ID, or Customer) - Real-time or live numbers ### CTA [Open your Dashboard](https://affitor.com/brand) ### Media - Banner: light https://affitor.com/docs/changelog/brand-dashboard/banner-light.png, dark https://affitor.com/docs/changelog/brand-dashboard/banner-dark.png - Image (The Dashboard with Last 30 days selected, four totals with their change, and Revenue on the chart as a solid line over a dashed line for the previous period): light https://affitor.com/docs/changelog/brand-dashboard/dashboard-light.png, dark https://affitor.com/docs/changelog/brand-dashboard/dashboard-dark.png, raw https://affitor.com/docs/changelog/brand-dashboard/dashboard-raw.png - Image (Latest sales and Top partners, each with View all, and Needs you below with applications to review and Pay partners by a date with the amount): light https://affitor.com/docs/changelog/brand-dashboard/lists-light.png, dark https://affitor.com/docs/changelog/brand-dashboard/lists-dark.png, raw https://affitor.com/docs/changelog/brand-dashboard/lists-raw.png --- id: "changelog/improvements-2026-10-25" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-10-25" updated: "2026-10-25" --- # An API keys table, Billing by program, and 30-day MCP connections > An API keys table, product rates on the marketplace, Billing for one program at a time, and MCP connections that last up to 30 days. ### Improved - Owners and Admins manage API keys in one table in Program settings › API keys: create named live keys shown once, see last use, and rotate or expire each key. - A program's marketplace FAQ can now list each product rule's commission rate. Owners and Admins give custom products a public name in Program settings › Commission › Product rules. - Billing lists only the selected program. To see another program's invoices, switch programs from the program menu. - When a partner has no public name, Partners shows their contact email instead of their account username. - On a phone, Program settings has one top bar with the menu and search, instead of a second menu bar and a back row on each page. ### Fixed - An overdue invoice pauses only a live program. Draft and archived programs keep their status, so paying the invoice no longer makes them live. - On a phone, partner Integrations shows connected AI apps as a stacked list instead of a wide table, with a larger Remove button. ### For developers - AI apps connected over MCP stay connected for up to 30 days instead of asking you to approve them again about every hour. - MCP tools no longer send a partner's email address as their name, and every field in a tool's output has a description. - MCP list tools accept any positive `limit` and return up to 50 items, with `next_cursor` for the rest, instead of an input error. - The `hint` on `api_key_rotation_required` warnings and errors now says to rotate the key you use in Program settings › Developers › API keys. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - API key permissions, Full access or Tracking only, test keys, or renaming, disabling or deleting a key. - Saying every marketplace program shows per-product rates, or that brands create product rules or rename Stripe products there. - The new brand Dashboard: it has its own entry for Oct 25. ### Media - Image (API keys with three named live keys, each with its masked key and Last used, and a menu open with Rotate and Expire): light https://affitor.com/docs/changelog/improvements-2026-10-25/api-keys-light.png, dark https://affitor.com/docs/changelog/improvements-2026-10-25/api-keys-dark.png, raw https://affitor.com/docs/changelog/improvements-2026-10-25/api-keys-raw.png --- id: "changelog/improvements-2026-10-24" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-10-24" updated: "2026-10-24" --- # Partner totals no longer count test events > Partner totals and charts no longer count test events, and older leads count again. ### Fixed - Partner program totals and charts no longer count test events, and older leads that were left out are now counted. --- id: "changelog/improvements-2026-10-23" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-10-23" updated: "2026-10-23" --- # A new Members table, Commissions totals, and Review application > A new Members table, a money summary on Commissions, Review application from notifications, and archived programs closed to new links. ### Improved - Members shows Name, Permission level and Status, with a Permission level dropdown per member you can change. Make owner lets an Owner add a co-owner and stay an owner. - Commissions shows Revenue, Commission and To pay for the selected date range. Status and search filter only the table below. - A notification for an application waiting on you has a Review application button that opens Partners › Applied, where you approve or decline. Partners has one Share program button. - On your own program's marketplace page, Your program opens that program's Dashboard. - When a program is archived, its partners can't create links or change destinations, its page offers a way back to Programs, and its links stop recording clicks. ### Fixed - The Applied tab count on Partners updates right after you approve or decline an application. ### For developers - Tracking a click on an archived program's link with `POST /api/v1/track/click` returns `410` with error code `link_disabled`. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - Describing what the brand Dashboard contains when Your program opens it. - Claims about paused programs, or saying brands can archive or unarchive a program. ### Media - Image (Members with each person's name, email and Permission level: Owner for you, and a Permission level dropdown on the Admin and Member rows): light https://affitor.com/docs/changelog/improvements-2026-10-23/members-light.png, dark https://affitor.com/docs/changelog/improvements-2026-10-23/members-dark.png, raw https://affitor.com/docs/changelog/improvements-2026-10-23/members-raw.png --- id: "changelog/improvements-2026-10-21" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-10-21" updated: "2026-10-21" --- # An Approval card, Join right away, and browser translation > An Approval card in Program settings, Join right away on auto-approve programs, commissions from exact cents and the $50 Refer reward timing. ### Improved - Program settings › Status has an Approval card: choose Auto-approve or Manual review and save it on its own. - On a program's marketplace page, the line under Apply to promote says Join right away when the program approves partners automatically. - Partners can hide the Finish setup card on Programs. - The $50 Refer a brand reward comes after the referred brand pays its first invoice with partner commissions over $0, even when Affitor's fee is $0. - Green success toasts now use Affitor blue. - You can translate Affitor pages with your browser's built-in translation, which the site used to turn off, and pages keep working while translated. ### Fixed - Percentage commissions on programs without product rules are priced from the sale's exact cents, so a half-cent result always rounds up. Commissions already recorded are unchanged. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - Calling the Approval card's page anything but Program settings › Status (its menu item reads Go live until the program is live). ### Media - Image (Program settings › Status with the Program status card and, below it, the Approval card: Auto-approve selected, Manual review, and the card's own Save): light https://affitor.com/docs/changelog/improvements-2026-10-21/approval-light.png, dark https://affitor.com/docs/changelog/improvements-2026-10-21/approval-dark.png, raw https://affitor.com/docs/changelog/improvements-2026-10-21/approval-raw.png --- id: "changelog/improvements-2026-10-20" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-10-20" updated: "2026-10-20" --- # Commission terms for Owners and Admins, and pages for AI agents > Only Owners and Admins change commission terms, marketplace pages state the combined $20 minimum, and affitor.com answers AI agents. ### Improved - Only Owners and Admins can change a program's commission type, rate and duration. Members see the current terms instead of the controls. - Marketplace program pages say the $20 minimum payout is combined across all your programs, and no longer label the attribution window as first click. ### Fixed - On a phone, the Partners page title and its buttons no longer overlap. ### For developers - Rate-limited Tracking API routes also send the standard `RateLimit-Policy` and `RateLimit` headers, next to `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. - [Test mode](https://affitor.com/docs/api-reference/test-mode) in the API reference shows how to send test clicks, leads and sales with `"test_mode": true` in `additional_data`. - affitor.com answers `Accept: text/markdown` on the homepage, pricing, about and integrations pages, and serves `/pricing.md`, `/about.md`, `/auth.md` and `/integrations.md` to AI agents. - affitor.com publishes `/.well-known/` discovery files for AI agents, including an MCP server card at `/.well-known/mcp/server-card.json`, and registers read-only WebMCP tools in browsers that support them. - The MCP Registry entry `com.affitor/mcp` shows the Affitor icon. --- id: "changelog/improvements-2026-10-19" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-10-19" updated: "2026-10-19" --- # Auto-approval for new programs and AI tracking setup > New programs start on automatic approval, Tracking opens on With AI, a daily check records missed Stripe sales, and the Tracking API spec is public. ### Improved - New programs start with automatic partner approval. Existing programs keep their current setting. - Tracking setup opens on With AI: pick Claude Code, Cursor, Codex, ChatGPT or Other, then copy a ready prompt with your Program ID. - A daily check now records partner-referred sales from your connected Stripe account that never reached Affitor in the last 7 days, unless refunded or disputed. - Affitor emails show X and LinkedIn links in the footer. ### For developers - A `409` from `POST /api/v1/track/sale` returns your program's earlier sale id in `error.details.sale_id`, or `null` when another program used that `transaction_id`. - The Tracking API spec is at `affitor.com/openapi.json` and `affitor.com/docs/openapi.json`. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Avoid - Saying the Tracking prompt differs per AI tool, or that it runs a setup command for each tool. - Saying sales the daily Stripe check records include refunded or disputed ones, or sales no partner referred. - Chat, partner page links and email code sign-in: they have their own entries for Oct 19. ### Media - Image (Install tracking on With AI: Claude Code, Cursor, Codex, ChatGPT and Other above a prompt with Program ID 71 and a Copy prompt button): light https://affitor.com/docs/changelog/improvements-2026-10-19/tracking-light.png, dark https://affitor.com/docs/changelog/improvements-2026-10-19/tracking-dark.png, raw https://affitor.com/docs/changelog/improvements-2026-10-19/tracking-raw.png --- id: "changelog/partner-page-links" type: "changelog" url: "https://affitor.com/changelog/partner-page-links" updated: "2026-10-19" --- # Choose which pages partners can link to > Brands set allowed destinations and a per-partner link limit in Program settings › Partner links; partners link to an allowed page, then copy the link or download its QR code. Choose which pages partners can link to, and how many links each can create, in **Program settings › Partner links** at [affitor.com/brand/settings/partner-links](https://affitor.com/brand/settings/partner-links). Until today, a partner could point a link at any page on your program's website, with no limit, and Program settings had no page for it. Now you set the allowed destinations and a limit per partner, and partners choose from your list when they create a link. ## How it works - **Allowed destinations**: up to 20, each an HTTPS domain open to **Any page on this domain** or **One specific page**. - **A limit per partner**: 1 to 100 additional links. The default program link doesn't count. - **Page links**: partners link to an allowed page, then copy it or download its QR code. ## Set your allowed destinations In **Partner links**, under **Allowed destinations**, click **Add domain**, enter an **HTTPS domain** such as `https://example.com`, and pick **Pages**. For **One specific page**, enter the **Allowed page**, for example `/pricing`. Check **I manage this domain and will ensure tracking is installed**, click **Add domain**, then **Save changes**. ## Set how many links each partner can create Under **Additional links**, keep **Allow partners to create links to your pages** on and set **Additional links per partner**. Until you save this page, your program keeps the earlier rule: any page on your website, no limit. Owners, Admins and Members can save; Viewers can only view. ## Create a link to a page Partners open a program, go to **Links** and click **Create link**. Add a **Private label**, keep or change the **Link key**, pick a **Domain** and enter a **Page path**. When the brand allows one specific page, the path is already filled in. The saved link is the page with your key added, for example `https://example.com/pricing?via=k7Qm2xa` (some programs use `?aff=`). Copy it from the list, or open its QR code and click **Download PNG**. Each link now also shows **Earnings**: what it has earned, with any pending amount below it. ## Where to change it later Change destinations or the limit on **Partner links** any time. Turning additional links off, or lowering the limit, stops new links and keeps the ones partners already share. ## Conclusion Partners now send people to the right page, within the rules you set. [Learn more about partner links](https://affitor.com/docs/brand/partner-links), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - Brands set where partner links can go in Program settings › Partner links, at https://affitor.com/brand/settings/partner-links. The item sits right after Tracking. - Allowed destinations holds up to 20 rules. Each rule is an HTTPS domain set to Any page on this domain or One specific page, which takes an Allowed page path such as /pricing. - Each domain needs the box I manage this domain and will ensure tracking is installed. It is an acknowledgement only; it does not install or check tracking. - Additional links per partner is a whole number from 1 to 100. The partner's default program link does not count toward it. - A program that has never saved Partner links keeps the earlier rule: partners can link to any page on its website, with no limit. The page shows its controls as a draft until the brand saves. - Turning off Allow partners to create links to your pages, or lowering the limit, stops new links and keeps the links partners already have. - Owners, Admins and Members can save Partner links. Viewers can open it but not save. - Partners open a program, go to the Links tab and click Create link. The form asks for a Private label, a Link key, a Domain and a Page path. With One specific page, the path is filled in and locked. - A page link is the page URL with the partner's link key as a query parameter, for example https://example.com/pricing?via=k7Qm2xa. Programs created before October 16, 2026, and programs set to aff, use ?aff= instead. - Each saved link has a Copy button and a QR button. The QR opens Link QR code with Download PNG. - Above the list, partners see how many additional links they have, for example 2 / 10 additional links. At the limit, Create link is turned off. - Each link shows Earnings: the commission earned on that link, with any pending amount below it. - Docs: https://affitor.com/docs/brand/partner-links ### UI labels - `Program settings` - `Partner links` - `Additional links` - `Allow partners to create links to your pages` - `Additional links per partner` - `Allowed destinations` - `Add domain` - `Add link domain` - `HTTPS domain` - `Pages` - `Any page on this domain` - `One specific page` - `Allowed page` - `Save changes` - `Partner link settings saved.` - `Links` - `Create link` - `Private label` - `Link key` - `Domain` - `Page path` - `Query link preview` - `Earnings` - `Link QR code` - `Download PNG` ### Avoid - Saying partners get short /r// links. Page links are query links; the short form is only a preview marked not ready, whatever Preferred format says - Saying the domain checkbox installs, verifies or tests tracking - Saying an allowed domain also covers its subdomains or another port - Saying the limit counts the default program link, or that lowering it deletes links - Saying partners can change a link key after creating it - Saying Viewers can save Partner links - Presenting the October 23 fixes as part of this release: a full URL pasted after the prefilled slash in Page path, the link settings loading message, archived programs ### CTA [Open Partner links](https://affitor.com/brand/settings/partner-links) ### Media - Banner: light https://affitor.com/docs/changelog/partner-page-links/banner-light.png, dark https://affitor.com/docs/changelog/partner-page-links/banner-dark.png - Image (Allowed destinations with https://blog.example.com on Any page on this domain and https://example.com on One specific page, Allowed page /pricing): light https://affitor.com/docs/changelog/partner-page-links/destinations-light.png, dark https://affitor.com/docs/changelog/partner-page-links/destinations-dark.png, raw https://affitor.com/docs/changelog/partner-page-links/destinations-raw.png - Image (The partner's Create link form with Domain https://example.com · /pricing and Page path /pricing filled in and locked, above the query link preview https://example.com/pricing?via=k7Qm2xa): light https://affitor.com/docs/changelog/partner-page-links/create-link-light.png, dark https://affitor.com/docs/changelog/partner-page-links/create-link-dark.png, raw https://affitor.com/docs/changelog/partner-page-links/create-link-raw.png --- id: "changelog/sign-in-with-email-code" type: "changelog" url: "https://affitor.com/changelog/sign-in-with-email-code" updated: "2026-10-19" --- # Sign in or sign up with a code from your email > Enter your email on the sign-in or sign-up page and Affitor emails you a six-digit code that signs you in or creates your account. Sign in to Affitor, or create your account, with a six-digit code sent to your email at [affitor.com/login](https://affitor.com/login). Until this week, using your email meant a password: you typed one to sign in, and to sign up you chose one, typed it twice and then clicked a verification link. Now your email gets a code instead. Google sign-in and sign-up work as before. ## How it works - **Enter your email**: click **Email me a code** to sign in, or **Create account** to sign up. - **Enter the code**: type or paste the six digits, and they submit themselves. - **One code at a time**: a code works once, for 10 minutes, and a new one replaces it. ## Sign in On [the sign-in page](https://affitor.com/login), enter your email and click **Email me a code**. **Check your email** shows where the code went. Type or paste the code from the email titled "Your Affitor sign-in code", and you are signed in. There is no button to press. ## Sign up On [the sign-up page](https://affitor.com/signup), pick **I'm a brand** or **I'm a partner**, enter your email and click **Create account**. Enter the code and your account is ready, with no password to choose and no verification link to open. The code works the same on both pages: if an account already uses that email, it signs you in; if none does, it creates one. ## If the code does not work - **That code is wrong or has expired.** means the code was mistyped or is more than 10 minutes old. After five wrong tries, a code stops working. - **Resend code** appears a minute after each send. After a wrong code, it reads **Send a new code**. - **Use a different email** takes you back to the first step. ## Prefer a password? On the sign-in page, **Use password** opens the email and password form, and **Email me a code instead** brings the code back. ## Conclusion Signing in or up with your email now starts with a code; on the sign-in page, **Use password** still opens the password form. [Learn more on the sign-in page](https://affitor.com/login), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - Affitor's sign-in page is https://affitor.com/login. Enter an email and click Email me a code; Affitor emails a six-digit code in an email titled Your Affitor sign-in code. - On https://affitor.com/signup, pick I'm a brand or I'm a partner, enter an email and click Create account; the same kind of code is sent. - The next screen, Check your email, shows six boxes. Typing or pasting the six digits signs you in; there is no submit button. - If an account already uses that email, the code signs in to it. If none does, the code creates the account, with no password and no verification link. - A code works once, for 10 minutes. A new code replaces the previous one, and five wrong tries end a code. - Resend code appears one minute after a send, and reads Send a new code after a wrong code. Use a different email returns to the first step. - Use password on the sign-in page opens the email and password form; Email me a code instead returns to the code. Google sign-in and sign-up are unchanged. ### UI labels - `Sign in to your account` - `Sign in with Google` - `Email` - `Email me a code` - `Use password` - `Email me a code instead` - `Create your account` - `I'm a brand` - `I'm a partner` - `Sign up with Google` - `Create account` - `Check your email` - `Sent to` - `Resend code` - `Send a new code` - `Use a different email` - `That code is wrong or has expired.` - `Too many attempts. Wait a minute and try again.` ### Avoid - Saying passwords are removed or stop working (Use password keeps the password form) - A code length other than six digits, or an expiry other than 10 minutes - A Verify, Submit or Continue button on the code step (the code submits itself) - Saying sign-up with email asks for a password, a name or a verification link - A Use password link on the sign-up page (it is only on sign-in) - A sign-in link in the email (the email holds a code, not a magic link) - Applying to a program from the marketplace with a code (not part of this entry) - How many codes you can ask for in an hour, rate limits, or how codes are stored ### CTA [Sign in to your account](https://affitor.com/login) ### Media - Banner: light https://affitor.com/docs/changelog/sign-in-with-email-code/banner-light.png, dark https://affitor.com/docs/changelog/sign-in-with-email-code/banner-dark.png - Image (The Sign in to your account page with an email entered above the Email me a code button, and Use password below it): light https://affitor.com/docs/changelog/sign-in-with-email-code/login-light.png, dark https://affitor.com/docs/changelog/sign-in-with-email-code/login-dark.png, raw https://affitor.com/docs/changelog/sign-in-with-email-code/login-raw.png --- id: "changelog/team-in-partner-chat" type: "changelog" url: "https://affitor.com/changelog/team-in-partner-chat" updated: "2026-10-19" --- # Bring your team into partner chats > Owners, and Admins by default, now read and reply in every partner chat; choose which other roles join under Chat access on Members. Bring your team into every chat with your partners, and choose which roles join, in [Chat](https://affitor.com/brand/chat). Until this week, Chat belonged to the account that created the brand: invited team members, owners included, had no Chat in their menu. Now Owners are always in your partner chats, Admins join by default, and you decide whether Members and Viewers join too. ## How it works - **Set once per program**: **Chat access** on **Members** applies to every partner chat of the program. - **By role**: Owners always, Admins by default, Members and Viewers when you tick them. Viewers read only. - **Names, not emails**: your side sees who wrote each message and their role. ## Choose who joins Open **Members** from the program menu and find **Chat access**. **Owners** are ticked and marked **Always**. Tick **Admins**, **Members** or **Viewers**, then click **Save**. Only an Owner or Admin can change it. Everyone you let in gets **Chat** in their menu and every partner conversation of that program. Each message shows who on your team wrote it and their role, and your own messages sit on the right. ## Find and follow chats The **All** menu above the inbox switches to **Unread**. Search looks through partner and program names under **Conversations**, and message text under **Messages**. A message result opens the chat at that message, with **Jump to latest** to return. **In this conversation** lists your team in the chat with their roles. Its **Mute** and **Mark as unread** change only your own inbox. Partners get the same inbox, search, **Mute** and **Mark as unread** at [affitor.com/partner/chat](https://affitor.com/partner/chat). Since October 20, each side of Chat lists only its own conversations, every message from your team sits on the right in your view, and partners see your brand's name instead of who on your team wrote. Since October 25, conversation details open in a centered window, or a sheet on phones. ## Change it later Change who joins any time under **Chat access**. Unticking a role takes its members out of that program's partner chats. ## Conclusion Your partner chats now include the people who run the program with you. [Learn more by opening Chat](https://affitor.com/brand/chat), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - Brand team members take part in partner chats on Affitor. Brands open Chat at https://affitor.com/brand/chat and partners at https://affitor.com/partner/chat. - Owners are always in every partner chat of their program. Admins join by default. Members and Viewers join when an Owner or Admin ticks them. Viewers can read but not reply. - Who joins is set per program in the Chat access card on Members (opened from the program menu). One Save applies to every partner chat of that program. Only Owners and Admins can change it. - Chat shows names, never email addresses. On the brand side each message shows who wrote it and their role. Since October 20, 2026, partners see the brand's name on every message from the brand's team; on October 19 they saw each writer's name and role. - Since October 20, 2026, each side of Chat lists only its own conversations (on October 19 one inbox held both sides). Brand mode shows the partner chats of the program selected in the program menu; partner mode shows the chats where you are the partner. - Search finds conversations by partner or program name and messages by their text, only in chats you can read. - In this conversation lists, on the brand side, your team in the chat with their roles. On both sides it has Mute and Mark as unread, which change only your own inbox. Since October 25, 2026, it opens as a centered dialog, or a sheet on phones (on October 19 it was a side panel). ### UI labels - `Chat` - `Members` - `Chat access` - `Which roles are in every chat with your partners.` - `Owners` - `Always` - `Admins` - `Members` - `Viewers` - `Read only` - `Save` - `Applies to every partner chat at once.` - `Only an Owner or Admin can change this.` - `All` - `Unread` - `Search chats` - `Conversations` - `Messages` - `Jump to latest` - `In this conversation` - `Your team` - `Mute` - `Mark as unread` ### Avoid - Linking /brand/messages or /partner/messages. Chat moved to /brand/chat and /partner/chat on 26/10/2026; the old paths only redirect. - Saying partners see which team member wrote a message (they see the brand's name). - Saying Chat shows anyone's email address. - Saying you can attach files or images in Chat (the chat has no attach button). - Adding or removing one person from one chat (access goes by role, for every partner chat of the program). - Saying Viewers can reply. - A Direct filter with chats in it (Direct is empty; partner chats are under Groups). - A Who joins line or a Change link in the conversation details (removed on 25/10/2026). - One inbox that mixes brand and partner chats (that was launch day only; each side now lists its own). - Saying Chat access is set per partner, per person or once for the whole account (it is per program). ### CTA [Open Chat](https://affitor.com/brand/chat) ### Media - Banner: light https://affitor.com/docs/changelog/team-in-partner-chat/banner-light.png, dark https://affitor.com/docs/changelog/team-in-partner-chat/banner-dark.png - Image (The Chat access card on Members: Owners ticked and marked Always, Admins ticked, Members and Viewers (Read only) unticked, and Save): light https://affitor.com/docs/changelog/team-in-partner-chat/chat-access-light.png, dark https://affitor.com/docs/changelog/team-in-partner-chat/chat-access-dark.png, raw https://affitor.com/docs/changelog/team-in-partner-chat/chat-access-raw.png - Image (A partner chat on the brand side: Maya Codes · Partner on the left, Linh Tran · Admin and You · Owner on the right): light https://affitor.com/docs/changelog/team-in-partner-chat/thread-light.png, dark https://affitor.com/docs/changelog/team-in-partner-chat/thread-dark.png, raw https://affitor.com/docs/changelog/team-in-partner-chat/thread-raw.png --- id: "changelog/brand-onboarding-flow" type: "changelog" url: "https://affitor.com/changelog/brand-onboarding-flow" updated: "2026-10-18" --- # Set up your program in one full-screen flow > Creating a program opens five full-screen steps, from Business to Go live, with Save and exit on every step. Set up a new program in one full-screen flow, one step at a time, at [affitor.com/brand/new](https://affitor.com/brand/new). Until today, creating a program started on a separate form that also asked for a program handle, and the setup steps after it sat next to a step list and, on a wide screen, a preview of what partners see, with a Skip for now button on Tracking and Payments. Now every step is one screen in the same flow. ## How it works - **Five steps**: Business, Commission, Tracking, Payments and Go live, each with **Step n of 5** and a progress bar. - **Two fields to start**: Business asks only for a business name and a website. - **Leave any time**: **Save and exit** is on every step. ## Start with your business Enter your business name and website, then click **Continue**. Affitor creates the program and opens Commission for it. If you already run a program, Business starts with its name and website; change them for the new one. ## Keep going, or come back later Commission, Tracking and Payments each have **Back** and **Continue**. On Tracking and Payments, **Continue** works while Affitor is still checking; the step is not marked done until the check passes. Go live still checks that everything is in place before your program goes live. **Save and exit** saves your progress and opens the program's dashboard. On Business, it creates the program from the two fields; with both fields empty, it leaves without creating one. ## Where to change it later Once a program is live, it has no setup: each step is its page in Program settings, and old setup links open that page. ## Conclusion Setting up a program is now one guided flow from Business to Go live. [Learn more by creating a program](https://affitor.com/brand/new), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - Creating a program on Affitor opens a full-screen setup at https://affitor.com/brand/new with five steps in this order: Business, Commission, Tracking, Payments, Go live. - Each step shows Step n of 5, a progress bar and a Save and exit button. - Business asks for two things: a business name and a website. Continue creates the program and opens Commission. - Tracking and Payments have one Continue button that works while the check is still pending; it does not mark the step done. - A program that is already live has no setup; its setup links open the matching Program settings page. ### UI labels - `Step 1 of 5` - `Your business` - `Business name` - `Website` - `Continue` - `Save and exit` - `Back` - `Commission` - `Install tracking` - `Payments` - `Go live` - `Create a program` ### Avoid - Saying setup copies settings, a logo or partners from another program - Saying Continue on Tracking or Payments marks them done or skips the Go live checks - A setup time such as five minutes - A Skip button (there is none) ### CTA [Create a program](https://affitor.com/brand/new) ### Media - Banner: light https://affitor.com/docs/changelog/brand-onboarding-flow/banner-light.png, dark https://affitor.com/docs/changelog/brand-onboarding-flow/banner-dark.png - Image (Step 1 of 5, Your business, with Business name, Website and Continue): light https://affitor.com/docs/changelog/brand-onboarding-flow/business-light.png, dark https://affitor.com/docs/changelog/brand-onboarding-flow/business-dark.png, raw https://affitor.com/docs/changelog/brand-onboarding-flow/business-raw.png --- id: "changelog/improvements-2026-10-18" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-10-18" updated: "2026-10-18" --- # Improvements and fixes, Oct 12–18 > Simpler username rules, website suggestions for your Business details, faster partner pages, and fixes to renewals, phones and sign-up. ### Improved - Usernames are 3 to 30 lowercase letters, numbers and hyphens. Change yours once every 14 days; a name you give up is held for you for 14 days. - In Program settings › Business, saving your website suggests a logo, tagline and About for you to review. Nothing is saved until you save each card. - Partner pages you opened before show at once and refresh in the background, and moving between them keeps the sidebar in place. - Every page that shows your attribution window shows the one tracking applies. - The Payments page says why connecting Stripe failed, inside the Stripe card. - Old directory links (`/list/`) open the program on the Affitor marketplace, or the marketplace when it is not listed. - The tracking and CLI quickstarts in the docs have an **Agent prompt** tab you can copy into your coding agent. - [changelog.json](https://affitor.com/changelog.json) and [context.md](https://affitor.com/changelog/context.md) give AI tools every changelog entry and the facts to reuse. - The Customers page is retired. Commissions names the customer on each row, shows a count for each status in use, and old Customers links open it. - Invoice emails drop the invoice number from the subject and show the amount due large at the top of the invoice details. - Confirm and reset emails no longer show a long link under the button. - Invite a brand by email from Refer a brand: add up to five addresses, preview the message, and Affitor sends your link. - Program settings › Business shows your Program ID with a Copy button. It is the ID the tracking script, the API and AI agents use. - Program settings › Payments shows two cards, Stripe and Server API, each with its own status. Either one counts for Payments when you go live. - Team members with the Member role no longer see Invite member, Resend invite or Regenerate on the API keys page. Owners keep them. - On the API keys page, a new key comes with a **Copy key** button, Regenerate confirms in a dialog that names the key it stops, and an expired key tells Owners to update `AFFITOR_API_KEY`. - [affitor.com/switch](https://affitor.com/switch) shows how to move from another affiliate tool: connect payments, then test tracking. - Finished steps on Get started and most success tags use Affitor blue instead of green. - On Account › Payouts, the Get ready to be paid list no longer repeats the Add payout method button. The Legal name and Payout method rows jump to their cards on the page. - Marketplace programs without an uploaded logo can show their website's icon instead of initials. An uploaded logo always wins. ### Fixed - A refund or chargeback on a subscription renewal now reaches the commission for that renewal. - Withdraw and the invoice details form fit a phone screen. - On an iPhone, the profile row at the bottom of the rail stays on screen, and tapping a field no longer zooms the page. - A team invite still works when the person signs up with email, and they are not asked to pick brand or partner. - Signing up with email keeps the name you typed. - A renamed Refer a brand link still credits the brands who sign up through it. - Program pages show their whole About, with no Read more. - The invoice number in the How to pay part of invoice emails stays on one line on a phone. - Paying an Affitor invoice by card stays in the invoice currency, with no conversion to a local currency at checkout. - In Partner › Programs, a program's dashboard shows the same logo as your Programs list instead of an initial, and Copy buttons line up for short and long links. ### For developers - New programs use `?via=` in partner links instead of `?aff=`. Older programs keep `?aff=`, and tracking reads both. - `affitor` 0.4.5: `affitor agent setup` configures Claude Code or Cursor for your project, with a dry run and backups first, and prints the command for Codex. - `affitor doctor` checks that your agent config and key are set, without starting an agent or calling the API. - `affitor onboard` leaves your Stripe webhook alone when Stripe is connected in Affitor, so sales are not counted twice. - `@affitor/sdk` 2.1.3 marks its React entry `"use client"`, so it imports cleanly in the Next.js App Router. - `affitor status` and `affitor test` run with an API key alone, with no project config. - Stripe invoices now record their sale from `invoice.paid` as well as `invoice.payment_succeeded`, once per invoice. An invoice already refunded, even partly, when Affitor records it adds no sale. - A Stripe invoice paid with several payments, or by a payment that also pays other invoices, does not record a sale on its own. - `POST /api/v1/track/refund` with an empty Bearer token returns 401 `Empty Bearer token`. - `affitor` 0.4.6: `affitor agent setup --program-id ` gives each coding agent its own restricted key, separate from your live key. Run `affitor login` first; only program Owners can create keys. - MCP tools describe every input: what it means, where it comes from and what leaving it out does. `list_my_payouts` says bank or Wise. - `@affitor/recipes` 0.1.1: the Stripe sale and renewal snippets skip a checkout with no Affitor customer key instead of failing the webhook. --- id: "changelog/integrations-and-agents" type: "changelog" url: "https://affitor.com/changelog/integrations-and-agents" updated: "2026-10-18" --- # Integrations and AI agents pages > Two new public pages show what Affitor connects to, Integrations with a guide for each and AI agents for connecting your AI app over MCP. See what Affitor connects to on two new pages: [Integrations](https://affitor.com/integrations) and [AI agents](https://affitor.com/agents). Until this week, this lived only in the docs. Now each has a page you can share, linked from Product in the site header and from the footer. ## How it works - **One list**: payments, frameworks and auth, AI agents and payouts, filtered by category. - **A page per guide**: eight integrations have a page that says what they do and sets them up in three steps. - **AI agents**: the server address, what your agent can read, and the app you use. ## Browse integrations Open **Integrations** from Product in the site header. Filter by Payments, Frameworks and auth, AI agents or Payouts; each tile opens its page or its guide in the docs. ## Open an integration A page such as [Stripe](https://affitor.com/integrations/stripe) says what the integration does, sets it up in three steps, and links the full guide with **Read the guide**. Stripe also has **Connect Stripe**, which opens your program's Payments settings after you sign in. ## Connect your AI app [AI agents](https://affitor.com/agents) shows the server address to copy, what your agent can read for brands and for partners, and how to add it to Claude, ChatGPT, Cursor or your coding agent. You sign in with your Affitor account, and the connection is read-only. ## Conclusion Everything Affitor connects to now has one place to start. [Learn more about the Affitor MCP server](https://affitor.com/docs/api-reference/mcp), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - https://affitor.com/integrations lists what Affitor connects to, by category (Payments, Frameworks and auth, AI agents, Payouts). - Eight integrations have their own page (Stripe, Polar, Next.js and its Clerk, Supabase and NextAuth variants, Node.js and Express, Fastify); the other tiles open their guide in the docs. - https://affitor.com/agents shows the read-only MCP server at https://mcp.affitor.com/mcp, what an agent can read for brands and for partners, and how to add it to an AI app after signing in with an Affitor account. - Both pages are linked from Product in the site header and from the footer. ### UI labels - `Integrations` - `Connect Affitor to the tools you use` - `Read the guide` - `Connect Stripe` - `AI agents` - `Ask your AI app about your program` - `Copy` - `Connect an AI tool` - `What your agent can do` - `Choose your app` ### Avoid - Every integration having its own page (8 of 18 do; Wise has no page) - An agent that can change data, record sales or move money (the server is read-only) - An agent connection that is set up or verified by these pages on its own ### CTA [See integrations](https://affitor.com/integrations) ### Media - Banner: light https://affitor.com/docs/changelog/integrations-and-agents/banner-light.png, dark https://affitor.com/docs/changelog/integrations-and-agents/banner-dark.png - Image (The Integrations page with its heading, the featured tiles, the category filter and the first row of payment integrations): light https://affitor.com/docs/changelog/integrations-and-agents/integrations-light.png, dark https://affitor.com/docs/changelog/integrations-and-agents/integrations-dark.png, raw https://affitor.com/docs/changelog/integrations-and-agents/integrations-raw.png - Image (The Stripe integration page with Connect Stripe and Read the guide, what it does, and the three steps to connect): light https://affitor.com/docs/changelog/integrations-and-agents/stripe-light.png, dark https://affitor.com/docs/changelog/integrations-and-agents/stripe-dark.png, raw https://affitor.com/docs/changelog/integrations-and-agents/stripe-raw.png - Image (The AI agents page with the server address and a Copy button, and what an agent can do for brands and for partners): light https://affitor.com/docs/changelog/integrations-and-agents/agents-light.png, dark https://affitor.com/docs/changelog/integrations-and-agents/agents-dark.png, raw https://affitor.com/docs/changelog/integrations-and-agents/agents-raw.png --- id: "changelog/refer-program-page" type: "changelog" url: "https://affitor.com/changelog/refer-program-page" updated: "2026-10-18" --- # A new Refer Program page, with milestones tied to paid invoices > The Refer Program page shows an example of what a referral can earn, and the $50 and $350 milestones now follow paid invoices, checked in a review. See what a referral can earn and get your link on the new [Refer Program page](https://affitor.com/marketplace/referral-program). Until today, the page listed the three rewards, a link and the terms. The $50 came when a referred brand's program went live, the $350 at $10,000 in tracked sales, and both reached your balance when their hold ended. Now the page shows a worked example, and the terms tie both milestones to paid invoices: each one is reviewed against those payments before it reaches your balance. ## How it works - **Example**: set how many brands you bring and their monthly partner sales to see the three rewards add up. - **Paid milestones**: $50 after the brand pays its first fee invoice; $350 at $10k in paid sales, with paid Affitor invoices and paid partners. - **Reviewed release**: after the 30-day hold, the $50 and $350 are reviewed one by one. The 15% releases on its own. ## See what a referral could earn The **Example** card starts at 3 brands and $25k in partner sales a month. Change either one and each reward line updates. Below it, the page explains how it works, why to refer, who it is for, and answers common questions. ## Get your link Click **Get your link**. Signed in, it opens **Referrals**; otherwise you sign up first. Referrals shows your link with **Copy** and **Invite via email**, the same three rewards, and a note that the milestones are approved after the hold. ## Where to read the rules The [Refer Program terms](https://affitor.com/legal/refer-program) are the rules. **Refer a partner** shows **Soon** until its terms are published. ## Conclusion The Refer Program page now shows what a referral can earn, and its milestones are reviewed against paid invoices before release. [Learn more about referral rewards](https://affitor.com/docs/partners/referral-rewards), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - The Affitor Refer Program page is https://affitor.com/marketplace/referral-program. Get your link opens Referrals when you are signed in, or sign-up when you are not. - The page has an Example card: pick Brands you bring and Partner sales per brand, a month ($5k, $25k or $50k) to see what the three rewards could add up to. - The rewards for referring a brand are $50 after the brand pays its first fee invoice, $350 at $10k in paid sales with paid Affitor invoices and paid partners, and 15% of its Affitor fees for 12 months. - Each reward is held for 30 days. The $50 and $350 are then reviewed one by one before they reach your balance; the 15% releases on its own after its hold. - Refer a partner shows Soon. It has no published terms yet. ### UI labels - `Affitor Refer Program` - `Get your link` - `Refer a brand` - `Refer a partner` - `Soon` - `Example` - `Brands you bring` - `Partner sales per brand, a month` - `How it works` - `Why refer` - `Who it is for` - `Questions` - `Referrals` - `Your link` - `Copy` - `Invite via email` - `M1 and M2 require admin approval after the hold.` - `Program terms` ### Avoid - Presenting the Example total as a promise or an average; it is an example the reader sets - Saying the $50 comes when a brand goes live (that was the earlier wording) - Saying the review or the paid-invoice check is automatic - Amounts or terms for referring partners - Partner or program counts shown on the page (they change) ### CTA [Get your link](https://affitor.com/marketplace/referral-program) ### Media - Banner: light https://affitor.com/docs/changelog/refer-program-page/banner-light.png, dark https://affitor.com/docs/changelog/refer-program-page/banner-dark.png - Image (The Refer Program page with the Example card set to 3 brands and $25k in partner sales a month): light https://affitor.com/docs/changelog/refer-program-page/example-light.png, dark https://affitor.com/docs/changelog/refer-program-page/example-dark.png, raw https://affitor.com/docs/changelog/refer-program-page/example-raw.png - Image (Referrals with the three reward lines, the approval note and your link with Copy): light https://affitor.com/docs/changelog/refer-program-page/link-light.png, dark https://affitor.com/docs/changelog/refer-program-page/link-dark.png, raw https://affitor.com/docs/changelog/refer-program-page/link-raw.png --- id: "changelog/first-results" type: "changelog" url: "https://affitor.com/changelog/first-results" updated: "2026-10-17" --- # See your first results as they happen > Brands track their first partner, traffic, sale and payout on Get started; partners track their first click, commission and payout on Programs; sign-up asks brand or partner first. See your first results as they happen: brands on [Get started](https://affitor.com/brand/get-started), partners on [Programs](https://affitor.com/partner). Until this week, setup progress showed up in several places, and nothing told you when your program or your link first worked. Now each side has one card that marks its first results, with one next step. ## How it works - **Pick your side first**: sign-up asks brand or partner before the form. - **Brands**: four first results on Get started, once the program is live. - **Partners**: three first results on Programs, each with its date. ## Pick your side [Sign-up](https://affitor.com/signup) asks **I'm a brand** or **I'm a partner** before the form, and the next screen has your answer already picked. ## First results, for brands Once your program is live, **First results** on Get started tracks four steps: **Your first partner joined**, **A partner sent you traffic**, **Your first sale from a partner** and **You paid your first partner**. The next step to reach shows what to do, with a button such as **Share program** or **Go to commissions**. Before your program is live, the card says these start once it is. ## Start earning, for partners Once your partner setup is done, **Start earning** at the top of Programs tracks three steps: **Someone clicked your link**, **You earned your first commission** and **You got paid**, each with the date it happened. If money is waiting and you have no payout method, the card asks you to add one. Use **Hide this list** when you no longer need it. ## Conclusion Brands and partners now see the moment their program or their link starts to work. [Learn more about getting started](https://affitor.com/docs/brand/quickstart), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - Brands see a First results card on the Get started page of their program, with four steps (first partner joined, first traffic from a partner, first sale from a partner, first partner paid). The next step to reach has one button (for example Review applications, Share program or Go to commissions), except the first sale, which has none. - Once partner setup is done, partners see a Start earning card at the top of their Programs page (https://affitor.com/partner) with three steps (first click on their link, first commission, first payout). - The sign-up page (https://affitor.com/signup) asks "I'm a brand" or "I'm a partner" before the form. ### UI labels - `First results` - `Your first partner joined` - `A partner sent you traffic` - `Your first sale from a partner` - `You paid your first partner` - `Share program` - `Go to commissions` - `Start earning` - `Someone clicked your link` - `You earned your first commission` - `You got paid` - `Hide this list` - `I'm a brand` - `I'm a partner` ### Avoid - First results on the Dashboard page (it is on Get started) - Emails sent when a step is reached (none are sent yet) - Signing in with an email code (not live) - A promise that a program will reach every step ### CTA [Create your account](https://affitor.com/signup) ### Media - Banner: light https://affitor.com/docs/changelog/first-results/banner-light.png, dark https://affitor.com/docs/changelog/first-results/banner-dark.png - Image (The sign-up choice with two cards: I'm a brand and I'm a partner): light https://affitor.com/docs/changelog/first-results/signup-light.png, dark https://affitor.com/docs/changelog/first-results/signup-dark.png, raw https://affitor.com/docs/changelog/first-results/signup-raw.png - Image (The First results card on a brand's Get started page, with the first partner joined and Share program as the next step): light https://affitor.com/docs/changelog/first-results/brand-light.png, dark https://affitor.com/docs/changelog/first-results/brand-dark.png, raw https://affitor.com/docs/changelog/first-results/brand-raw.png - Image (The Start earning card on a partner's Programs page, with the first click reached and the first commission as the next step): light https://affitor.com/docs/changelog/first-results/partner-light.png, dark https://affitor.com/docs/changelog/first-results/partner-dark.png, raw https://affitor.com/docs/changelog/first-results/partner-raw.png --- id: "changelog/help-center-use-cases" type: "changelog" url: "https://affitor.com/changelog/help-center-use-cases" updated: "2026-10-17" --- # A Help Center and use cases in the docs > The docs now open by job for brands or partners, with a searchable Help Center, three end-to-end use cases and a guide to connect a new Stripe account. Find what you need in the [docs](https://affitor.com/docs) by the job you want done. Until this week, the docs opened by section, such as Quickstart, Tracking and Billing. Now they open by job, with a Help Center and use cases. ## How it works - **By job**: choose **Brands** or **Partners**, and pages are grouped by task. - **Help Center**: search the common questions in one place. - **Use cases**: a whole setup, with each guide in order. ## Choose Brands or Partners The switch at the top of the docs shows the pages for your side, grouped by the job you want done. ## Search the Help Center The [Help Center](https://affitor.com/docs/help) searches the common questions, by category. If you are still stuck, it links to support. ## Follow a use case [Use cases](https://affitor.com/docs/use-cases) walk through a whole setup, from a partner's link to a commission: selling on Stripe, any payment provider, and subscriptions. A new guide, [Connect a new Stripe account](https://affitor.com/docs/brand/tracking/connect-stripe-account), covers creating the account and connecting it in Program settings › Payments. ## Copy a page for your AI Every guide and reference page has **Copy for LLM** and **View as Markdown** in its header, so you can hand a page to your coding agent as it is. ## Conclusion The docs now start from what you want to do. [Learn more in the Help Center](https://affitor.com/docs/help), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - The Affitor docs (https://affitor.com/docs) have a Brands and Partners switch, with pages grouped by the job you want done. - The Help Center at https://affitor.com/docs/help searches common questions. - Use cases at https://affitor.com/docs/use-cases cover selling on Stripe, any payment provider and subscriptions, each showing the flow and linking the guides in order. - Each guide and reference page has Copy for LLM and View as Markdown in its header. ### UI labels - `Help center` - `Use cases` - `Brands` - `Partners` - `Copy for LLM` - `View as Markdown` - `Connect a new Stripe account` ### Avoid - More use cases coming (not announced) - Pages that moved or links that changed (no URL changed) ### CTA [Open the Help Center](https://affitor.com/docs/help) ### Media - Banner: light https://affitor.com/docs/changelog/help-center-use-cases/banner-light.png, dark https://affitor.com/docs/changelog/help-center-use-cases/banner-dark.png - Image (The Affitor docs home with a Brands and Partners switch above the guides): light https://affitor.com/docs/changelog/help-center-use-cases/nav-light.png, dark https://affitor.com/docs/changelog/help-center-use-cases/nav-dark.png, raw https://affitor.com/docs/changelog/help-center-use-cases/nav-raw.png - Image (The Help center page with a search box, category filters and cards for short answers): light https://affitor.com/docs/changelog/help-center-use-cases/help-light.png, dark https://affitor.com/docs/changelog/help-center-use-cases/help-dark.png, raw https://affitor.com/docs/changelog/help-center-use-cases/help-raw.png - Image (The Use cases page with three cards, each showing its flow from a partner link to a commission): light https://affitor.com/docs/changelog/help-center-use-cases/use-cases-light.png, dark https://affitor.com/docs/changelog/help-center-use-cases/use-cases-dark.png, raw https://affitor.com/docs/changelog/help-center-use-cases/use-cases-raw.png --- id: "changelog/navigation-v2" type: "changelog" url: "https://affitor.com/changelog/navigation-v2" updated: "2026-10-17" --- # One navigation for brands and partners > Brands and partners share one left rail, with Chat in it, your account and inbox at the bottom, and a program menu that remembers your last program. Find everything in one left rail, on both the brand and the partner side of [your dashboard](https://affitor.com/brand). Until this week, Messages, the bell and your avatar sat in the top bar, and the partner side had a layout of its own. Now both sides share one rail, with everything you use in reach. ## How it works - **One rail**: the pages you use every day, with **Chat** among them. - **You at the bottom**: your name opens the account menu, and the bell beside it opens your inbox. - **Your last program**: brands switch programs from the top of the rail, and it opens the one they used last. ## The rail **Chat** is now a rail item, next to the pages you use every day. Your name sits at the bottom of the rail: click it for your account menu and [Your account](https://affitor.com/account). ## Your inbox The bell beside your name opens your **Inbox** right above it. Click an event to open it, or use **Mark all as read**. ## Switch programs The program menu at the top of the rail lists your programs, with search and **Create program**. The next time you sign in on the same browser, it opens the last program you used. **Program settings** and **Billing**, and **Members** if you manage the team, open the settings rail, grouped by Program, Team, Billing and Developers. ## Your link on Programs The partner side has the same layout. On **Programs**, a **Link** column shows your link for each program, with a copy button. Programs that have not approved you yet say **After approval**. ## Conclusion Brands and partners now move through Affitor the same way. [Learn more about the dashboard](https://affitor.com/docs/partners/dashboard), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - Brands and partners use the same left rail in the Affitor dashboard (https://affitor.com/brand and https://affitor.com/partner). - Chat is an item in the rail. The profile row at the bottom of the rail opens the account menu, and the bell next to it opens the Inbox. - Brands switch programs from the program menu at the top of the rail. It opens the last program used in that browser. - On the partner Programs page, a Link column shows the partner's link for each program, with a copy button. ### UI labels - `Chat` - `Inbox` - `Mark all as read` - `Create program` - `Program settings` - `Members` - `Billing` - `Programs` - `Link` - `After approval` ### Avoid - Messages, the bell or the avatar in the top bar (they moved into the rail) - An Archive tab in the inbox (not built) - The last program following you across devices (it is remembered per browser) - Listing every rail item by name (the brand rail is still changing) ### CTA [Open your dashboard](https://affitor.com/brand) ### Media - Banner: light https://affitor.com/docs/changelog/navigation-v2/banner-light.png, dark https://affitor.com/docs/changelog/navigation-v2/banner-dark.png - Image (The brand left rail beside the Dashboard, from the program switcher at the top to Chat and the profile row with the bell at the bottom): light https://affitor.com/docs/changelog/navigation-v2/rail-light.png, dark https://affitor.com/docs/changelog/navigation-v2/rail-dark.png, raw https://affitor.com/docs/changelog/navigation-v2/rail-raw.png - Image (The Inbox open above the profile row, with Mark all as read): light https://affitor.com/docs/changelog/navigation-v2/inbox-light.png, dark https://affitor.com/docs/changelog/navigation-v2/inbox-dark.png, raw https://affitor.com/docs/changelog/navigation-v2/inbox-raw.png - Image (The program menu open at the top of the rail, with Program settings, Members and Billing): light https://affitor.com/docs/changelog/navigation-v2/program-menu-light.png, dark https://affitor.com/docs/changelog/navigation-v2/program-menu-dark.png, raw https://affitor.com/docs/changelog/navigation-v2/program-menu-raw.png - Image (A partner's Programs table with a Link column and After approval for a pending program): light https://affitor.com/docs/changelog/navigation-v2/partner-link-light.png, dark https://affitor.com/docs/changelog/navigation-v2/partner-link-dark.png, raw https://affitor.com/docs/changelog/navigation-v2/partner-link-raw.png --- id: "changelog/partner-payouts-wise" type: "changelog" url: "https://affitor.com/changelog/partner-payouts-wise" updated: "2026-10-17" --- # Get paid through Wise or a bank transfer > Partners finish a short payout setup, with a legal name, a Wise or bank account and a tax form, then withdraw any amount from $20. Get paid through Wise or a bank transfer, from one short setup in [Your account › Payouts](https://affitor.com/account/payouts). Until this week, partners could withdraw without a legal name or a tax form on file. Now you finish three steps once, and then you can withdraw any amount from $20. ## How it works - **Set up once**: a legal name, a payout method and a tax form, all in one card. - **Wise or bank**: Affitor sends your money through Wise, to a Wise account or to a bank account in your name. - **From $20**: once the card says **Ready**, withdraw any amount from $20. ## Open Payouts Open [Your account › Payouts](https://affitor.com/account/payouts). The **Get ready to be paid** card lists what is still missing. ## Add your legal name and payout method Add your **legal name** as on your bank account and ID. It goes on your tax form and payout records. Then choose **Add payout method**: a Wise account, or a bank account in your legal name. ## Fill in your tax form Say whether you are a US citizen or US tax resident. If you are not, sign a W-8BEN as a person or a W-8BEN-E as a business, right in the app. If you are, declare a W-9, and our accountant emails it to you to sign. Affitor never asks for your SSN or EIN, and brands never see your tax form. ## Withdraw When all three steps are done, the card shows **Ready**. Withdraw from your payout page as before. If a step is still missing, the page says **Finish payout setup first** and takes you there with **Go to Payouts**. ## Manage your details Change your payout method or legal name in Payouts at any time; a new legal name needs a new tax form. A W-8BEN or W-8BEN-E stays valid until December 31 of the third year after you sign it, and then the card asks you to sign again. PayPal is no longer offered. A PayPal method you saved before stays visible so you can remove it. ## Conclusion Partners now get paid through Wise or a bank transfer, from one setup they do once. [Learn more about payouts](https://affitor.com/docs/partners/payouts), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - Affitor pays partners through Wise or a bank transfer. PayPal is no longer offered. - Before a withdrawal, a partner finishes "Get ready to be paid" at https://affitor.com/account/payouts (Your account › Payouts) with a legal name, a payout method and a tax form. - The tax form is a W-8BEN (a person) or W-8BEN-E (a business) signed in the app, or a W-9 declaration for US persons, which Affitor's accountant then emails to sign. Affitor never asks for an SSN or EIN. - The minimum withdrawal is $20. Brands never see a partner's tax form. ### UI labels - `Get ready to be paid` - `Add legal name` - `Add payout method` - `Fill in` - `Sign W-8BEN` - `Sign W-8BEN-E` - `Declare W-9` - `Ready` - `Finish payout setup first` - `Go to Payouts` ### Avoid - How fast a payout arrives, what it costs, or which countries are supported (none of these is set by this change) - PayPal as a payout method - A reminder before a tax form expires (no reminder is sent) - Brands seeing or collecting the tax form ### CTA [Set up payouts](https://affitor.com/account/payouts) ### Media - Banner: light https://affitor.com/docs/changelog/partner-payouts-wise/banner-light.png, dark https://affitor.com/docs/changelog/partner-payouts-wise/banner-dark.png - Image (The Get ready to be paid card with three rows: legal name, payout method and tax form): light https://affitor.com/docs/changelog/partner-payouts-wise/setup-light.png, dark https://affitor.com/docs/changelog/partner-payouts-wise/setup-dark.png, raw https://affitor.com/docs/changelog/partner-payouts-wise/setup-raw.png - Image (The Add payout method dialog with recipient country, currency and Wise as the type): light https://affitor.com/docs/changelog/partner-payouts-wise/method-light.png, dark https://affitor.com/docs/changelog/partner-payouts-wise/method-dark.png, raw https://affitor.com/docs/changelog/partner-payouts-wise/method-raw.png - Image (The tax form panel answered No, with A person · W-8BEN picked: country of tax residence, date of birth, permanent address and an optional foreign tax number): light https://affitor.com/docs/changelog/partner-payouts-wise/tax-form-light.png, dark https://affitor.com/docs/changelog/partner-payouts-wise/tax-form-dark.png, raw https://affitor.com/docs/changelog/partner-payouts-wise/tax-form-raw.png - Image (The Withdraw page with the available amount, the $20 minimum and a prompt to finish payout setup): light https://affitor.com/docs/changelog/partner-payouts-wise/withdraw-light.png, dark https://affitor.com/docs/changelog/partner-payouts-wise/withdraw-dark.png, raw https://affitor.com/docs/changelog/partner-payouts-wise/withdraw-raw.png --- id: "changelog/verified-programs" type: "changelog" url: "https://affitor.com/changelog/verified-programs" updated: "2026-10-17" --- # Find verified programs on the marketplace > A blue check marks programs Affitor has verified, and the Verified only filter shows just those on the marketplace. Find programs Affitor has verified on the [marketplace](https://affitor.com/marketplace?verified=true). Until this week, every listed program looked the same. Now a blue check after a program's name means Affitor checked its tracking, payments and invoices. ## How it works - **Automatic**: Affitor checks every listed program; nobody applies. - **Rechecked**: a program keeps its check while its tracking, payments and invoices stay in order. - **Not a review**: the check is about how the program runs on Affitor, not about the product. ## Show verified programs only Open **Filter** and choose **Verified only**. The list and Featured narrow to verified programs. The **Verified** chip shows the filter is on; **Clear** removes it. ## See what the check means Hover or tap a check to see what Affitor checked. ## For brands There is nothing to apply for. Run your tracking, payments and invoices through Affitor, and your program keeps its check. ## Conclusion Partners can now pick programs whose tracking, payments and invoices Affitor has checked. [Learn more about finding programs](https://affitor.com/docs/partners/quickstart/find-and-join-programs), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - On the Affitor marketplace (https://affitor.com/marketplace), a blue check after a program's name means Affitor checked its tracking, payments and invoices. - The Filter menu has Verified only; the link is https://affitor.com/marketplace?verified=true. - Verification is automatic and rechecked; a program cannot apply for it. It is not a review of the product. ### UI labels - `Verified` - `Verified only` - `Filter` - `Verified by Affitor` - `Clear` - `Affitor checked their tracking, payments and invoices.` ### Avoid - Naming the payment provider behind the check - Calling it a product review or a guarantee - A count of verified programs (it changes as programs are rechecked) - Brands applying for the badge ### CTA [Browse verified programs](https://affitor.com/marketplace?verified=true) ### Media - Banner: light https://affitor.com/docs/changelog/verified-programs/banner-light.png, dark https://affitor.com/docs/changelog/verified-programs/banner-dark.png - Image (The marketplace filtered to verified programs, with the Verified chip): light https://affitor.com/docs/changelog/verified-programs/filter-light.png, dark https://affitor.com/docs/changelog/verified-programs/filter-dark.png, raw https://affitor.com/docs/changelog/verified-programs/filter-raw.png - Image (A program card with the blue check and its explanation): light https://affitor.com/docs/changelog/verified-programs/check-light.png, dark https://affitor.com/docs/changelog/verified-programs/check-dark.png, raw https://affitor.com/docs/changelog/verified-programs/check-raw.png --- id: "changelog/your-account" type: "changelog" url: "https://affitor.com/changelog/your-account" updated: "2026-10-17" --- # Your account, one page for both sides > Your profile, sign-in and payout settings now live on one Your account page, opened from the account menu at the bottom of the rail. Open [Your account](https://affitor.com/account) for everything about you, on either side of Affitor. Until this week, your profile and payout settings lived on separate pages for brands and partners. Now there is one page for the person, with three parts: **Profile**, **Login and security** and **Payouts**. ## How it works - **One menu**: click your name at the bottom of the rail. - **One page**: the gear in that menu opens Your account, whichever side you are on. - **Old links still work**: earlier profile links open Your account. ## Open the account menu Click your name at the bottom of the left rail. The menu switches you between the brand and partner sides, and has **Home page**, **Docs** and **Log out**. The gear opens **Your account**. ## Profile Your name, email, username and country sit in one card. Click your avatar to pick a photo, then drag and zoom it in **Adjust your avatar** before you save. ## Login and security Change your password here, and use **Sign out other devices** to end every other browser, phone and CLI session. This device stays signed in. ## Payouts Partners get ready to be paid here: a legal name, a payout method and a tax form. See [Get paid through Wise or a bank transfer](https://affitor.com/changelog/partner-payouts-wise). ## Back to your side **Back** at the top of Your account returns you to the side you came from. **Home page** in the menu opens the Affitor home page, and when you are signed in, opening affitor.com takes you back to the side you used last. ## Conclusion Your account is now one page, a click or two from anywhere in the dashboard. [Learn more about account settings](https://affitor.com/docs/partners/account-settings), and write to support@affitor.com with any question. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - Your account is one page for brands and partners at https://affitor.com/account, with Profile, Login and security, and Payouts. - Clicking the profile row at the bottom of the left rail opens the account menu. The gear in that menu opens Your account. - The account menu also switches between the brand and partner sides, and has Home page, Docs and Log out. - Old profile links (for example /partner/profile) now open Your account. ### UI labels - `Your account` - `Profile` - `Login and security` - `Payouts` - `Back` - `Switch to partner` - `Switch to brand` - `Home page` - `Docs` - `Log out` - `Adjust your avatar` ### Avoid - The ⋯ menu as the way to Your account (the whole profile row opens the menu; Your account is the gear) - Notification settings on Your account (there are none) - Separate profile pages for the brand and partner sides ### CTA [Open Your account](https://affitor.com/account) ### Media - Banner: light https://affitor.com/docs/changelog/your-account/banner-light.png, dark https://affitor.com/docs/changelog/your-account/banner-dark.png - Image (The account menu open from the profile row, with a gear for Your account, Switch to partner, Refer a brand, Home page, Docs and Log out): light https://affitor.com/docs/changelog/your-account/menu-light.png, dark https://affitor.com/docs/changelog/your-account/menu-dark.png, raw https://affitor.com/docs/changelog/your-account/menu-raw.png - Image (Your account on the Profile tab, with the avatar and the name, email, username and country fields): light https://affitor.com/docs/changelog/your-account/profile-light.png, dark https://affitor.com/docs/changelog/your-account/profile-dark.png, raw https://affitor.com/docs/changelog/your-account/profile-raw.png --- id: "changelog/hosted-mcp-server" type: "changelog" url: "https://affitor.com/changelog/hosted-mcp-server" updated: "2026-10-16" --- # Connect Claude, ChatGPT and Cursor to Affitor > The hosted Affitor MCP server at mcp.affitor.com lets AI apps read your program or partner data after you sign in. No API key, read-only. You can now connect Claude, ChatGPT, Cursor, VS Code, Perplexity, Claude Code, Codex and other AI apps to Affitor with one URL, `https://mcp.affitor.com/mcp`, and ask about your program in plain words. You sign in with your Affitor account; there is no API key to copy. ## Add it to your AI app ```bash tab="Claude Code" claude mcp add --transport http affitor https://mcp.affitor.com/mcp ``` ```bash tab="Codex" codex mcp add affitor --url https://mcp.affitor.com/mcp ``` ```json tab="MCP config" { "mcpServers": { "affitor": { "url": "https://mcp.affitor.com/mcp" } } } ``` In Claude, add it as a custom connector; in ChatGPT, as a custom MCP server, with the same URL. Your browser opens affitor.com, where a brand picks one program and a partner connects their partner account. Then click **Allow**. ## What the app can read - **Brands:** the program and its tracker snippet, partners, applications, commissions, a commission summary and billing. - **Partners:** your programs, links, earnings, commissions and payouts. Bank and PayPal details are never included. The connection is read-only: it cannot change data or move money. Remove it any time, in **All settings** › **Developers** › **AI agents** for brands or **Settings** › **Integrations** for partners, and it stops working at once. ```text tab="Agent prompt" Use the Affitor tools. Who are my top partners by earned commission in the last 30 days? ``` The older `@affitor/mcp` stdio server, which tracks events with a program API key, is unchanged. See [Affitor MCP server](https://affitor.com/docs/api-reference/mcp) for every client, the tool list and the limits. [Learn more about the Affitor MCP server](https://affitor.com/docs/api-reference/mcp) --- id: "changelog/go-live-needs-payments" type: "changelog" url: "https://affitor.com/changelog/go-live-needs-payments" updated: "2026-10-15" --- # Going live now needs a payment source > A program can go live once it has a business, a commission and a way to count sales. A logo is no longer required. A program now goes live only once Affitor has a way to count its sales. ## What Go live checks - **Business:** a name and a website. - **Commission:** what partners earn on a sale. - **Payments:** Stripe connected, or one sale sent from your server. A test sale counts. Click tracking shows its state on the same page but does not block Go live. A logo is no longer required. ## If something is missing The Go live button stays off and each missing row links to the step that fixes it. --- id: "changelog/guided-program-setup" type: "changelog" url: "https://affitor.com/changelog/guided-program-setup" updated: "2026-10-15" --- # Set up a program in five steps > A new program now walks you through Business, Commission, Tracking, Payments and Go live, with a live preview of your program card. After you sign up, one screen asks how you will use Affitor: run a program or join programs. Your answer is saved on your account. ## Five steps, in order A new program continues straight into setup: **Business**, **Commission**, **Tracking**, **Payments** and **Go live**. The list on the left checks off each step as the server confirms it, and shows what you saved, like your website or your rate. ## Live preview A card on the right previews your program name, website and commission terms, and updates as you type. ## Saved as you go **Business** and **Commission** save when you press **Continue**, and **Payments** saves as soon as you choose how sales are counted. **Save and exit** takes you to your program's settings. --- id: "changelog/marketplace-partners-joined" type: "changelog" url: "https://affitor.com/changelog/marketplace-partners-joined" updated: "2026-10-15" --- # Marketplace cards show who joined, with new sort and filters > Each program card shows how many partners joined, with the initials of its top partners, and the marketplace has a Sort menu and a Filter menu. Each program card on the marketplace now tells you how active the program is before you open it. ## Partners joined The footer of a card shows how many partners joined, with the initials of the program's top partners. A program nobody has joined yet says **New program**. Only initials are shown, never names or photos. ## Sort and filter - **Sort:** Newest, Highest commission, Most partners or Longest cookie. - **Filter:** pick one or more commission types and categories, and a cookie window. Each choice shows as a chip you can remove, with **Clear** to start over. - On a phone, Filter opens a sheet whose button shows how many programs match. ## One action per card The right side of a card says **Apply**, shows your status if you already applied or joined, or says **Your program** on a program you run. --- id: "changelog/referral-invite-page" type: "changelog" url: "https://affitor.com/changelog/referral-invite-page" updated: "2026-10-15" --- # Referral links open an invite page > When someone opens your Refer a brand link, they see who invited them and how Affitor pricing works before they sign up. Your Refer a brand link now opens a page made for the person you invited. ## Who invited them The page shows your name as the person who invited them, and the pricing up front: free until partners drive $10,000, then 3.5%. If a link is no longer active, the page says so and they can still create an account. ## Your link on the sign-in page If you have opened your link in **Refer a brand** on this browser before, the sign-in page shows it again with **Copy**, so it is one click away the next time you sign in. ## Context for AI Shared context for every entry (brand, facts, what never to say): https://affitor.com/changelog/context.md ### Facts - The link is affitor.com/r/; the username is chosen in Account › Profile. - Opening it shows the Affitor home page with an invite hero at the top. The hero has a chip " invited you", or "You were invited to Affitor" when no name is known. - Under the title "Grow revenue through partners at any scale", the hero says "Free until partners drive $10,000, then 3.5%." That is this entry's pricing line. - In the hero, the visitor types a work email and clicks "Get started" to sign up. - Under the form, the hero keeps the home page's three small stats ("<1hr" Setup time, "Real-time" Tracking, "Performance-based" You earn first, then pay). They are not part of this entry; do not repeat them. - If the link is no longer active, the hero says so, and the visitor can still create an account. - If Affitor cannot look the link up at that moment, the ordinary home hero shows (chip "AI-Native Affiliate Network", button "Launch your program free"), with no invite chip. - The nav bar above the hero and the sections below it (how it works, pricing, FAQ) are the normal home page. Nothing there is specific to the invite. - On the sign-in page, someone who opened their Refer a brand link on this browser sees it again with "Copy". ### UI labels - ` invited you` - `You were invited to Affitor` - `This invite link isn’t active. You can still create an account.` - `Grow revenue through partners at any scale` - `Work email` - `Get started` - `Refer a brand` - `Copy` ### Avoid - affitor.com/invite/ (the link is affitor.com/r/) - As the invite hero's content (valid and inactive links): the subtitle 'Launch your affiliate program in under an hour.', the buttons 'Launch your program free' or 'Launch demo', or 'Create free account' / 'Already have an account? Log in'. The invite hero's action is 'Work email' + 'Get started'. - Home-page lines presented as the invite's message: 'Pay only for results' (pricing section below the hero), 'under an hour' or '<1hr' (ordinary hero subtitle, the stats row, how it works) ### CTA [How referral rewards work](https://affitor.com/docs/partners/referral-rewards) ### Media - Banner: light https://affitor.com/docs/changelog/referral-invite-page/banner-light.png, dark https://affitor.com/docs/changelog/referral-invite-page/banner-dark.png --- id: "changelog/marketplace-redesign" type: "changelog" url: "https://affitor.com/changelog/marketplace-redesign" updated: "2026-10-14" --- # A new marketplace to find your next program > The marketplace is now a grid of program cards you can search, filter by commission type and sort, and every program page shows its terms at a glance. The marketplace now shows every program as a card with the numbers that matter: the commission and how long it pays, the cookie length, and how soon you get paid. ## Find the right program faster Search by name or description, filter by Recurring, One-time or Per action, pick a category, and sort the list. Each filter shows how many programs it holds. Every filter lives in the URL, so you can share a view. Programs listed in the last two weeks carry a **New** pill. When you are signed in, programs you have joined or applied to say **Joined** or **Applied**. On the full list, the Affitor Refer Program sits first, so you can always earn by introducing a brand to Affitor. ## Terms at a glance Each program page opens with four numbers: commission, cookie length, when you get paid, and the minimum payout. Below them are the brand's About section when it has one, an FAQ and similar programs in the same category. Applying takes one optional field. --- id: "changelog/stripe-payment-links-attribution" type: "changelog" url: "https://affitor.com/changelog/stripe-payment-links-attribution" updated: "2026-10-14" --- # Partner sales from Stripe Payment Links, Buy Buttons and Pricing Tables > If you sell with Stripe's no-code checkouts, partner sales are now credited automatically. Nothing to change in your checkout. If you sell through a Stripe Payment Link, a Buy Button or a Pricing Table, Affitor now credits the sale to the partner who sent the customer. You do not need to change your checkout or add a parameter. ## How it works When a visitor arrives from a partner link, the Affitor tracker already on your page passes that click to Stripe. It adds a `client_reference_id` to every `buy.stripe.com` link and to every `` and `` on the page, including ones that load later. Stripe returns it with the completed checkout, and Affitor credits the partner. ```text tab="Payment Link" https://buy.stripe.com/…?client_reference_id=aff_ ``` ```html tab="Buy Button" ``` ```html tab="Pricing Table" ``` It works for one-time payments, subscriptions, the first invoice and renewals. ## What you need - Stripe connected to Affitor. - The hosted tracker on the page that holds the checkout. ## Good to know - **First click wins.** If the buyer is already a customer of another partner, they stay with that partner. - A `client_reference_id` you set yourself is kept, unless it starts with `aff_`. - Visitors who have not given tracking consent, when you use consent mode, are not passed to Stripe. - If you record clicks yourself and set `data-affitor-clicks="off"` on the tracker, it does not add the value. --- id: "changelog/billing-invoices-redesign" type: "changelog" url: "https://affitor.com/changelog/billing-invoices-redesign" updated: "2026-10-13" --- # Billing that shows what you owe and what is next > The Billing page now shows what is due, what this week's invoice will be and where you stand against the free tier, and each invoice breaks down by partner. Your Billing page now answers three questions at a glance: what is due, what this week's invoice will look like, and where you are against the $10,000 free tier. ## Due, this week, platform fee Three cards sit at the top of Billing. **Due** shows the amount and the date it is due. **This week** previews the next weekly invoice before it is issued. **Platform fee** shows your progress toward the free tier. If a program is paused for an unpaid invoice, Billing says so and tells you which invoice resumes it. ## Every invoice, easy to find Filter invoices by status, page through older ones, download a PDF or copy an invoice number from the row menu. ## A clearer invoice page Each invoice shows commissions, the platform fee and the total, a **By partner** table that adds up to the total, and bank transfer details with copy buttons. Workspace members can download the PDF too. --- id: "changelog/mcp-write-tools-off" type: "changelog" url: "https://affitor.com/changelog/mcp-write-tools-off" updated: "2026-10-12" --- # MCP server records sales only when you allow it > From @affitor/mcp 0.2.1, the tools that record sales and refunds are off by default. Agents that record sales need AFFITOR_MCP_WRITE=1. **Action required.** Developers: If an agent records sales or refunds through the Affitor MCP server, add AFFITOR_MCP_WRITE=1 to the server's env. The Affitor MCP server now keeps money tools off by default. An agent that is only exploring its tools can no longer create a sale or reverse one by accident. ## What changes With `@affitor/mcp` 0.2.1, an agent sees five tools by default: readiness, lead, click, integration plan and verification. `affitor_track_sale` and `affitor_track_refund` appear only when you turn them on. Every tool now also says whether it reads, writes or cannot be undone, so your agent client can ask before it runs one. ## What to do If your agent records sales or refunds, turn the tools on in the server's config: ```json tab="MCP config" { "mcpServers": { "affitor": { "command": "npx", "args": ["-y", "@affitor/mcp"], "env": { "AFFITOR_API_KEY": "your_program_key", "AFFITOR_MCP_WRITE": "1" } } } } ``` Agents that only read or track leads and clicks need no change. While you try it out, pass `testMode` on a sale: it records a test sale with no commission. See [Legacy local server](https://affitor.com/docs/api-reference/mcp#legacy-local-server) for the setup. --- id: "changelog/improvements-2026-10-11" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-10-11" updated: "2026-10-11" --- # Improvements and fixes, Oct 5–11 > One-click commission approval, clearer refund notifications, and notification links that open the right page. ### Improved - Approving a commission takes one click. - A refund notification now says what happened to your balance. If the commission was still pending, it says the commission was canceled and your balance did not change. ### Fixed - Notification and reminder links open the right page instead of a "page not found". --- id: "changelog/withdraw-paid-commissions" type: "changelog" url: "https://affitor.com/changelog/withdraw-paid-commissions" updated: "2026-10-08" --- # Partners withdraw commissions once the brand has paid > Commissions approved from Oct 9 become withdrawable when the brand pays its invoice. Partners see what is waiting, and brands no longer mark commissions as paid. Starting with commissions approved on Oct 9, a partner can withdraw a commission once the brand has paid the invoice that includes it. Commissions approved before that date are not affected. ## For partners Your payout page shows a new line under **Ready to withdraw**: **Awaiting brand payment**. It shows the total of approved commissions you can withdraw as soon as the brand pays its weekly invoice. When the brand pays, that amount moves into your available balance on its own, and you withdraw it as usual. Your approved commissions still count toward your earnings right away. Only the timing of the withdrawal changes. ## For brands You no longer mark commissions as paid. Paying your weekly invoice is what releases your partners' commissions, so the **Mark as Paid** action is gone from the Commissions page. If you want your partners paid sooner, pay the invoice as soon as it arrives. Billing shows what is due and when. --- id: "changelog/improvements-2026-10-04" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-10-04" updated: "2026-10-04" --- # Improvements and fixes, Sep 28–Oct 4 > A changelog for you and your agents, clearer answers from the tracking API, and fixes for Google sign-in and CLI-created programs. ### New - A changelog page, with a Markdown version for AI agents. ### Improved - Tracking a click on a disabled referral link answers `410 link_disabled`, so you can tell it apart from an error. - Marketplace pages carry correct structured data for search engines. ### Fixed - If you signed up with Google, you can set a first password through the emailed link. - Partners auto-accepted into a program now get the approval notification. - Programs created from the CLI pay the commission they were created with. ### Security - We tightened sign-in, password reset and withdrawals. --- id: "changelog/balance-owed-after-refund" type: "changelog" url: "https://affitor.com/changelog/balance-owed-after-refund" updated: "2026-10-02" --- # See what you owe after a refund > When a customer refund reverses a commission you already withdrew, your payout page shows the balance owed, and it is recovered from your next commissions. Sometimes a customer asks for a refund after you have already withdrawn the commission for that sale. Until now, that amount quietly disappeared from your history. Now your payout page shows it. ## Balance owed Under **Ready to withdraw**, a **Balance owed** line shows the total. It is recovered from your next commissions, and the line goes away once it is paid down. ## How it is recovered New commissions pay the balance down first. You can withdraw again once your available balance is above zero. If a customer is refunded again later for a larger amount, the rest of that commission is reversed the same way. If a refund leaves your balance too low to cover a withdrawal you requested but have not received, that withdrawal is reduced or canceled to match. Most partners will never see this line. It appears only after a refund on money you had already withdrawn. --- id: "changelog/browser-leads-server-side" type: "changelog" url: "https://affitor.com/changelog/browser-leads-server-side" updated: "2026-09-30" --- # Send leads from your server to count them > A signup sent only from the browser is now recorded as provisional on older programs too. Send the lead from your server with your program API key so it counts. **Action required.** Developers: If you send signups only from the browser, also send them from your server with your program API key and the visitor's click ID. Leads sent only from the browser are now recorded as provisional on every program unless it explicitly allows browser leads. New programs already worked this way. Older programs that never chose a policy now do too. ## What changes A provisional lead does not credit a partner on its own. It settles when your server sends the lead with your program API key, or when that customer's first payment arrives through your connected Stripe account. ## What to do When a customer signs up, send the lead from your server. Forward the visitor's `affitor_click_id` cookie as `click_id`, so the lead is tied to the partner's click: ```bash tab="cURL" curl -X POST https://api.affitor.com/api/v1/track/lead \ -H "Authorization: Bearer YOUR_PROGRAM_API_KEY" \ -H "Content-Type: application/json" \ -d '{"click_id":"","customer_key":"usr_abc123","email":"jane@example.com"}' ``` ```js tab="Node.js" await fetch('https://api.affitor.com/api/v1/track/lead', { method: 'POST', headers: { Authorization: `Bearer ${process.env.AFFITOR_API_TOKEN}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ click_id: req.cookies.affitor_click_id, customer_key: newUser.id, email: newUser.email, }), }); ``` If you take payments through Stripe Checkout on a connected account, the first payment settles the lead for you. ## How to tell The browser call answers with `"provisional": true`. In the dashboard, your partners' signups stay flat while clicks keep rising. See [Lead tracking](https://affitor.com/docs/brand/tracking/lead-tracking-signup) for the full setup. --- id: "changelog/test-sales-never-invoiced" type: "changelog" url: "https://affitor.com/changelog/test-sales-never-invoiced" updated: "2026-09-30" --- # Test sales are never invoiced > Sales from your own tests are labeled and never billed. An invoice made only of test sales is voided automatically, and it no longer keeps your program paused. Testing your integration should never cost you anything. Sales from your Stripe test mode, your integration check or your own partner link are now marked as test data and left out of your weekly invoice. ## Voided, not pending If an unpaid invoice contains only test sales, Affitor voids it automatically. Billing shows it as **Voided** instead of Pending, with no Pay button. If that invoice had paused your program and nothing else is open or overdue, the program resumes on its own. ## Labeled, not hidden Test data stays visible, so your totals match what you see: - **Test** marks your own integration tests. They are never billed and never paid out. - **Team** marks someone on your team. Their sales wait for you to approve them as real or reject them as a test order. --- id: "changelog/improvements-2026-09-27" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-09-27" updated: "2026-09-27" --- # Improvements and fixes, Sep 21–27 > Commission notifications that point to the exact commission, a featured carousel on the marketplace, and access fixes for workspace members. ### Improved - Commission notifications name the program and open the exact commission. - The marketplace shows featured programs in a carousel. - The old CLI endpoint for connecting Stripe now answers `410 Gone`. Connect Stripe from the dashboard instead. ### Fixed - Workspace members can see the partner applications of the programs they work on. - Pages opt out of browser auto-translate, so program terms stay exactly as the brand wrote them. - Screenshots in the docs load again. ### Security - Suspending an account now blocks every way to sign in, and API responses and error messages carry only what the caller needs. --- id: "changelog/partner-links-on-approval" type: "changelog" url: "https://affitor.com/changelog/partner-links-on-approval" updated: "2026-09-24" --- # Partners get their link the moment you approve them > Approving a partner now creates their referral link right away, every referral code has one owner, and links can use your own /r/ short link. When you approve a partner, or your program accepts them automatically, Affitor now creates their referral link right away. It is waiting on their program page, ready to copy. ## A link that is ready to share The link points to your program's website with the partner's own code, for example `yourbrand.com/?aff=k7Qm2xa`. Your program needs a website set; if it has none, the link is created once you add one. Every code belongs to exactly one partner. A code a partner picks must be unique across Affitor, so nobody can use someone else's. ## Use your own /r/ short link If you would rather share short links on your own domain, add a redirect from `/r/` to `/?aff=` on your site: ```text tab="Redirect" yourbrand.com/r/k7Qm2xa → 301 → yourbrand.com/?aff=k7Qm2xa ``` Then open **Settings**, **Click Tracking**, and press **Check /r/** on the **Short link /r/** card. Once the check passes, new links to your homepage use `yourbrand.com/r/`. Links to other pages keep `?aff=`. If your redirect drops `?aff=`, the check tells you. --- id: "changelog/api-key-rotation" type: "changelog" url: "https://affitor.com/changelog/api-key-rotation" updated: "2026-09-20" --- # Know when your API key must be replaced > If Affitor flags your program's API key for replacement, your dashboard, every API response and the CLI now tell you. After the deadline the old key is refused. **Action required.** Brands: If your dashboard shows an API key notice, regenerate the key in Settings > API Key and update it on your server. Sometimes a key has to be replaced, for example when it has been exposed outside your control. Until now there was no visible signal. Now there are three, and they all point to the same fix. Keys that are not flagged are not affected. ## In the dashboard A banner appears at the top of every brand page for that program, with a **Replace key** button. It opens **Settings**, **API Key**, where **Regenerate** creates a new key and clears the notice. ## In API responses Until the deadline, every response made with the flagged key carries standard headers, and JSON object responses also carry a warning: ```http tab="Headers" Deprecation: @ Sunset: Link: ; rel="deprecation" ``` ```json tab="Body" "warnings": [{ "code": "api_key_rotation_required", "rotate_by": "" }] ``` After the deadline, requests with the old key get `401` with `error.code` set to `api_key_rotation_required`. ## In the CLI From `affitor` 0.4.2 (on npm since Oct 12), the CLI prints a one-line warning while the key still works, and points a retired key to the API Key page instead of suggesting `affitor init`. See [Errors: api_key_rotation_required](https://affitor.com/docs/api-reference/errors#api_key_rotation_required) to handle it in code. --- id: "changelog/improvements-2026-09-20" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-09-20" updated: "2026-09-20" --- # Improvements and fixes, Sep 14–20 > Password reset pages, notifications that open the right place, faster pages, and fixes across commissions, chat and tracking. ### New - **Forgot your password?** The sign-in page now has forgot-password and reset-password pages, so you can get back into your account on your own. ### Improved - Clicking a notification opens the page it is about. - Emails from Affitor now come from Affitor, with a plain-text version and a reply-to address. - Program descriptions are drafted from the brand's website, with a fallback when the site cannot be read. - Sign-in, marketplace and dashboard pages load faster and shift less while they load. - Marketplace program pages include the commission in the page itself, and every live program is in the sitemap, so search engines and AI assistants can read your terms. - `llms.txt` and the Markdown version of each public page are generated correctly for agents. - The public marketplace API returns each program's `documentId` and default commission policy. - The homepage links to the Marketplace from the top bar and the footer. ### Fixed - Brands no longer see Approve and Decline on notifications for partners who already joined. - One-time programs show an average sale value without "/month". - Partners see only the commission terms that are active right now. - A completed payout amount can no longer change after it is paid. - Message drafts are kept, and a chat message that failed to send is recovered. - Click tracking matches a partner's `?aff=` code to the right partner. - No hold-extension notification for a commission worth $0. - Featured programs stay featured. - The brand profile explains why it could not load instead of redirecting you away. - The homepage pricing states the $10,000 free tier. ### Security - We tightened how chat attachments, account balances and public marketplace data are handled. --- id: "changelog/improvements-2026-09-13" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-09-13" updated: "2026-09-13" --- # Improvements and fixes, Sep 1–13 > A cleaner docs feed for AI assistants, and tighter access to program and marketplace data. ### Improved - The docs feed for AI assistants is rebuilt: a compact `llms.txt` on every build, a full `llms-full.txt`, a sitemap that lists the Markdown pages, and page details at the top of every `.md` page. ### Security - We tightened access to program details and public marketplace data. --- id: "changelog/improvements-2026-08" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-08" updated: "2026-08-22" --- # Improvements and fixes, August 2026 > New brands can create their first program right after sign-up again. ### Fixed - New brands can create their first program right after sign-up again. If creating a program fails, the error says why. --- id: "changelog/improvements-2026-07" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-07" updated: "2026-07-06" --- # Improvements and fixes, July 2026 > Every docs page as Markdown for AI assistants, an About page, and an end-to-end guide. ### New - **Docs for AI assistants.** Every docs page is available as Markdown at its URL plus `.md`. - An About page with the Affitor story, and an "Ask AI about Affitor" row in the footer that opens your assistant with a ready question. - A How to Use Affitor walkthrough in the docs, and real product screenshots across the brand guides. --- id: "changelog/blog-launch" type: "changelog" url: "https://affitor.com/changelog/blog-launch" updated: "2026-07-05" --- # Read honest affiliate-software comparisons on the new Affitor blog > Twelve posts comparing the tools you're actually evaluating, with every price dated "as of" and competitor strengths conceded up front, plus .md twins and llms.txt so your AI assistant reads the same facts you do. ![Cover of the launch post comparing seven affiliate software tools for SaaS](/blog/covers/best-affiliate-software-saas.png) The [Affitor blog](/blog) is live with 12 posts: comparisons of Rewardful, FirstPromoter, Tolt, PartnerStack, Dub Partners, and more, plus guides on starting and pricing a SaaS affiliate program. - **Honest comparisons.** Every price is verified and labeled "as of July 5, 2026," and every post concedes where a competitor is the better pick before positioning Affitor. - **Built for AI readers.** Each post ships a markdown twin at its URL + `.md`, and the site publishes `llms.txt`, so the assistant researching tools on your behalf gets the same facts. Start with [Best Affiliate Software for SaaS](/blog/best-affiliate-software-saas) → --- id: "changelog/invite-partners" type: "changelog" url: "https://affitor.com/changelog/invite-partners" updated: "2026-07-04" --- # Invite partners with the email already written > Recruit affiliates by email, CSV, or from your other programs, and send an invitation generated from your program's real terms instead of writing one from scratch. ![Invite partners with a pre-written, terms-based email](/docs/changelog/invite-partners/invite-compose.png) You can now invite partners into your program directly: type emails, import a CSV, or pick people already performing in your other Affitor programs. When you get to the email, it's **already written from your program's real terms**: commission model, attribution window, payout threshold. Edit it freely, check the live preview, and send. Invited partners skip the application queue: they're active the moment they accept, tracking link in hand. The Partners page now shows everyone (active partners, applications, pending invites, rejections) in one table with status badges, and you can resend or cancel any pending invite right from the row. --- id: "changelog/go-live-button" type: "changelog" url: "https://affitor.com/changelog/go-live-button" updated: "2026-06-27" --- # Go live when you are ready > A single Go Live button publishes your program as soon as your business profile and commission are set, and the Quick start checklist shows what is really set up. Your program goes live when you say so. A single **Go Live** button on the Share Program step replaces automatic publishing, and it needs only your business profile and commission. Since October 2026, a program paused for an overdue invoice goes live again only after the invoice is paid. The Quick start checklist in the top bar now reflects what is really set up: business profile, commission, tracking, a verified first real event, and going live. [Read the quickstart](/docs/getting-started/quickstart) --- id: "changelog/improvements-2026-06" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-06" updated: "2026-06-27" --- # Improvements and fixes, June 2026 > Shorter app addresses, a calmer design, apply first and sign up after, per-program billing and notifications, refunds through the API, and the end of list.affitor.com. ### New - Record refunds through the tracking API, so the matching commission is reversed. - Record sales from your server without connecting Stripe. - Each program connects its own Stripe account. - Notifications and billing are scoped per program for brands with several programs. - A quick start popover in the top bar, and Billing as its own tab. - A program handle field in program settings and in first-program setup. - Withdraw an application from your Programs list. ### Improved - App addresses are shorter (`/brand/...`, `/partner/...`), and the dashboard says "brand" instead of "advertiser". - Settings, forms, charts, status pills and alerts share one calmer design. - Apply to a program first and sign up after: your application continues once you are in. - The attribution window is one setting, and it is applied when sales settle. Chargebacks reverse commissions. - Approving or rejecting a commission updates the row at once. - The partner table sorts by most clicks first and remembers your sort. - The SDK is published as `@affitor/sdk`, and the docs use it everywhere. - **list.affitor.com is retired** and now opens the marketplace. - Programs without a logo get a default gradient logo, and SVG logos upload. - PayPal is no longer a withdrawal method. ### Fixed - Logging out clears your session completely. - Program pages no longer show default commission numbers that the brand never set. - The tracking setup wizard shows the right snippet and refund guidance. - Test events stay out of brand metrics. - Partner chat no longer shows a message twice. ### Security - We tightened access between accounts so one brand cannot read another's data. --- id: "changelog/refer-program" type: "changelog" url: "https://affitor.com/changelog/refer-program" updated: "2026-06-12" --- # Earn by referring brands to Affitor > Partners promote Affitor itself through the Refer Program and earn rewards and a share of the platform fee from the brands they bring. Affitor has its own affiliate program. Find the **Refer Program** in the marketplace, read the official terms, and share your link. You earn $50 when a brand you referred goes live, $350 when its program reaches $10,000 in tracked sales, and 15% of the platform fee it pays for 12 months. [Read the Refer Program terms](https://affitor.com/legal/refer-program) --- id: "changelog/docs-api-reference" type: "changelog" url: "https://affitor.com/changelog/docs-api-reference" updated: "2026-06-10" --- # A full API reference and integration guides > The docs gain an API Reference, an SDK reference, an agent integration guide, integration guides and a machine-readable OpenAPI spec. The docs are rebuilt for developers. A new **API Reference** tab covers every tracking endpoint, with pages on attribution and errors. Alongside it: - an SDK reference and six integration guides (Next.js on its own or with Clerk, NextAuth or Supabase, Express, and Stripe); - an integration guide for AI agents, and `llms.txt` for assistants that read the docs; - a **For Partners** section; - a machine-readable OpenAPI spec. [Open the API Reference](/docs/api-reference/overview) --- id: "changelog/pricing-2026" type: "changelog" url: "https://affitor.com/changelog/pricing-2026" updated: "2026-06-08" --- # Free up to $10,000 in affiliate revenue, then 3.5% > Each program runs free until it has driven $10,000 in affiliate revenue; after that Affitor charges a 3.5% platform fee on affiliate sales. Pricing is one simple rule. Every program is free until its affiliate sales pass $10,000 in total. Beyond that, the platform fee is 3.5% of each affiliate sale: a $100 sale costs $3.50. Partner commissions are paid as you set them; the fee is separate. [See pricing](https://affitor.com/pricing) or read [how the fee works](/docs/getting-started/pricing-performance-model). --- id: "changelog/public-marketplace" type: "changelog" url: "https://affitor.com/changelog/public-marketplace" updated: "2026-06-07" --- # The marketplace is open to everyone > Browse every live program without an account, open its page, and apply, or go straight to your dashboard if you already joined. Anyone can now browse the Affitor Marketplace without logging in. Each program has a public page with its terms and an **Apply** button, or **View dashboard** if you have already joined. The old directory pages (lists, categories, top videos, top ads and product pages) now open the marketplace. The marketplace has been redesigned since. [Browse the marketplace](https://affitor.com/marketplace) --- id: "changelog/affitor-init-wizard" type: "changelog" url: "https://affitor.com/changelog/affitor-init-wizard" updated: "2026-05-25" --- # Sign in from the CLI, and init wires tracking into Next.js > The CLI signs you in through the browser, and init detects Next.js, installs the SDK and adds the tracking code, asking before each install and showing a diff before it edits your layout. The CLI now signs you in through your browser, so programs you create belong to your dashboard account. `programs` lists them and `whoami` shows who is signed in. ```bash npx affitor login npx affitor init ``` In a Next.js project, `init` detects the framework, installs the SDK and adds the tracking code. It asks before installing anything and shows a diff of the change to your app layout before applying it. A server-side Node SDK ships alongside it, so you can record sales from your backend. Since June 2026 the SDK is published as `@affitor/sdk`. --- id: "changelog/improvements-2026-05" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-05" updated: "2026-05-23" --- # Improvements and fixes, May 2026 > Redesigned account and invoice emails, a faster brand dashboard, and partner earnings that say what they are. ### Improved - Verification, team invite, new invoice and past-due emails share one redesigned layout. We rebuilt our emails again in September 2026. - The brand dashboard opens faster: its performance chart now loads after the page appears. ### Fixed - Customer details show one row per real sale. - The Total Commissions card is now Pending Earnings, because that is what it counts. - A program overview shows the offer from its commission policy. ### Security - We tightened access to admin payout and settings routes. --- id: "changelog/faster-docs-search" type: "changelog" url: "https://affitor.com/changelog/faster-docs-search" updated: "2026-04-25" --- # Faster, less noisy docs search > Search now matches page titles only, so you no longer wade through paragraph snippets to find what you need. Docs search now matches page titles only, instead of a wall of half-matched sentences. Press `⌘K`, start typing, and you'll see a clean list of pages. This is how docs search should feel: you type a topic, you get the page. We rebuilt the search index and re-skinned the results so the page you want is always the first thing you see. Try `tracking`, `commission`, or `payout` and you should land on the right page in one keystroke. [Start from the docs home →](/docs) --- id: "changelog/improvements-2026-04" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-04" updated: "2026-04-25" --- # Improvements and fixes, April 2026 > Replies in messages, new program defaults, CLI pages in the docs, and a profile that saves without signing you out. ### New - Partners get a referral link the first time they open a program. - Reply to a specific message in a conversation. - The docs have CLI pages. - The docs have a changelog and a billing overdue policy. ### Improved - The program switcher moved into the brand header. - A program page shows Joined or Applied, so you cannot apply twice. - Public program pages show the program's commission to visitors who are not signed in. - New programs start from a recurring commission for 18 months and a 90-day cookie. - Confirmations for rejecting, deleting and removing use a calmer outlined button, and deleting a partner group no longer shows an alarm box. ### Fixed - Saving your profile no longer signs you out. - Google sign-in lets you pick the account you want. --- id: "changelog/programs-go-live-automatically" type: "changelog" url: "https://affitor.com/changelog/programs-go-live-automatically" updated: "2026-04-25" --- # Programs go live once setup is complete > A program went live by itself once its tracking worked end to end and appeared in the marketplace without waiting for a review. Since June 2026 you publish it with a Go Live button. You no longer wait for us to publish your program. Once setup is complete (tracking script installed, leads tracked, Stripe connected and a first real sale recorded), the program goes live by itself and shows in the marketplace for partners to find. In June 2026 this became an explicit Go Live button, so you choose the moment. --- id: "changelog/partner-marketplace-2026" type: "changelog" url: "https://affitor.com/changelog/partner-marketplace-2026" updated: "2026-04-24" --- # A marketplace of programs for partners > Partners browse programs inside Affitor, search them with typo-tolerant search, and sort by commission. Partners can find their next program without leaving Affitor. The marketplace lists live programs with search that forgives typos, filters for programs you have joined, applied to, or not yet joined, a commission type filter, and sorting by commission. The marketplace has been redesigned since; [browse it today](https://affitor.com/marketplace). --- id: "changelog/content-lab-launch" type: "changelog" url: "https://affitor.com/changelog/content-lab-launch" updated: "2026-04-20" --- # Content Lab writes affiliate posts in one click > Pick a program, get a publish-ready affiliate post in one click, free for 30 posts a day. Content Lab is now live on [openaffiliate.dev/content-lab](https://openaffiliate.dev/content-lab). Pick any of the affiliate programs in the OpenAffiliate registry (around 750, mostly SaaS and AI) and get a publish-ready post in one click. No prompt engineering, no blank page: the draft is ready to edit and ship. It's free at 30 generations a day, and the whole tool is open source at [github.com/Affitor/content-lab](https://github.com/Affitor/content-lab). [Generate your first post →](https://openaffiliate.dev/content-lab) --- id: "changelog/affitor-cli" type: "changelog" url: "https://affitor.com/changelog/affitor-cli" updated: "2026-04-10" --- # Create an affiliate program from your terminal > Run npx affitor init to create an affiliate program and get its tracking script and API key, then check it and send test events from your terminal. The first version of the Affitor CLI is on npm. Create an affiliate program from your terminal and get its tracking script and API key. ```bash npx affitor init ``` - `status` shows your program's health and recent events, and `test` sends a test click, lead or sale. Programs created this way were not yet linked to a dashboard account. Browser sign-in, `programs` and `whoami` arrived in May. [Read the CLI guide](/docs/brand/cli/quickstart) --- id: "changelog/billing-and-invoices-2026" type: "changelog" url: "https://affitor.com/changelog/billing-and-invoices-2026" updated: "2026-04-08" --- # Billing and invoices in your dashboard > Brands get a Billing area with every invoice, its status, and an invoice detail page. Brands have a **Billing** area. It lists your invoices with a status badge on each, and opens a detail page for any of them. Billing was redesigned in October 2026 to show what you owe and what is next. --- id: "changelog/partner-profile-settings" type: "changelog" url: "https://affitor.com/changelog/partner-profile-settings" updated: "2026-04-03" --- # Partner profile and security settings > Partners can now update their profile, avatar, payout details and password, and request a withdrawal, without contacting support. Partners get a proper Settings page. **Account** holds your name, country, website, social handles and avatar. **Payout** holds where you get paid. **Privacy & Security** is where you change your password. Payout details cover bank transfer, Wise and PayPal, and you can request a withdrawal from the Payout page. Your avatar shows up across the dashboard as soon as you upload it. If you've been emailing support to update partner details, that's no longer needed. [Log in and open Settings to update your profile →](https://affitor.com/welcome) --- id: "changelog/improvements-2026-03" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-03" updated: "2026-03-31" --- # Improvements and fixes, March 2026 > Partner withdrawals and transaction history, team members, a hold period and cookie window per program, a redesigned brand dashboard, and a new logo. ### New - **Payouts.** Partners see a transaction history with a status timeline and can request a withdrawal of their approved balance. Since October 2026, a commission can be withdrawn once the brand has paid the invoice that covers it. - **Team members.** Invite teammates to your workspace and manage them. - Set a hold period and a cookie window per program. Partners see both on the program. - A full customer refund now marks the commission reversed, and a partial refund marks it refunded. Commission filters and counts include reversed. - Change your password from your profile, and show or hide your password while signing in. - The tracker shares attribution across your subdomains. ### Improved - Move partners between groups in bulk, and share your program link from the Partners page. - The brand dashboard is redesigned: trend cards, a new chart, an Action Center and a Getting Started checklist. - A commission shows its fee and revenue breakdown. - The docs have a 3-step integration guide and a guide to testing your integration. - A new Affitor logo across the site and the docs. - Customer tables can be sorted and filtered by status. - Search tolerates typos on the partner customer list and marketplace, brand messages, and partner groups. - Partner program pages work on phones, and link destinations are checked before saving. - Server-side lead examples on the setup page use the `/api/v1/track/lead` path. ### Security - Sign-in sessions are kept in secure cookies. --- id: "changelog/affiliate-skills-v2" type: "changelog" url: "https://affitor.com/changelog/affiliate-skills-v2" updated: "2026-03-28" --- # 47 agent skills for affiliate workflows > Run common affiliate workflows, from researching programs and drafting content to analyzing traffic, directly from your AI assistant. If you use Claude Code or another agent framework, the [affiliate-skills](https://github.com/Affitor/affiliate-skills) library now ships 47 ready-to-use skills across eight stages of affiliate work, research through analytics. One command installs the whole set: ```bash npx skills add Affitor/affiliate-skills ``` A few you might reach for first: `affiliate-program-search` queries the open program directory, `commission-calculator` scores what a program actually pays, and `competitor-spy` and `trending-content-scout` cover research. The library is open source and works with any AI that reads text: Claude Code, Cursor, Windsurf, ChatGPT, or Gemini CLI. *(Update, July 2026: the registry now counts 52 skills.)* [Browse the full skills library →](https://github.com/Affitor/affiliate-skills) --- id: "changelog/tracking-v2" type: "changelog" url: "https://affitor.com/changelog/tracking-v2" updated: "2026-03-17" --- # Rebuilt tracking and SDK 2.0 > Partner links use ?aff=, clicks, leads and sales are recorded as separate events tied by a click ID, and the SDK adds signup(). Tracking is rebuilt from the ground up. Partner links now carry `?aff=` instead of `?ref=`. Clicks, leads and sales are recorded as separate events, tied together by a `click_id`, so a sale can be traced back to the click that started it. SDK 2.0 adds `signup(userId, email)`, which returns a promise you can await, and replaces `trackLead()`, which stays as a deprecated alias. ```js await affitor.signup(user.id, user.email); ``` The setup page now has a live check that ticks off each step, from script loaded to payment tracked, as your test events arrive. [Read how attribution works](/docs/api-reference/attribution) --- id: "changelog/list-affitor-community" type: "changelog" url: "https://affitor.com/changelog/list-affitor-community" updated: "2026-03-15" --- # list.affitor.com, a community list of programs and agent skills > Browse and star affiliate programs and agent skills on a community site, and let an AI assistant search them through an API key or a Claude connector. We opened list.affitor.com, a community site for affiliate programs and agent skills. You could browse, search and star what you liked, and developers could read the same list with an API key or connect it to Claude so an assistant searched programs for them. list.affitor.com was retired in June 2026 and now opens the [Affitor Marketplace](https://affitor.com/marketplace). --- id: "changelog/improvements-2026-02" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-02" updated: "2026-02-28" --- # Improvements and fixes, February 2026 > A redesigned homepage, the tracker on npm, sales credited even without a cookie, partial refunds, private customer emails, and timestamps in the transcript tool. ### New - The tracker is on npm as `@affitor/tracker` (since replaced by `@affitor/sdk`), and calls made before it loads are queued instead of lost. - When the browser cookie is missing, a sale can still be credited to the right partner by matching the customer's user ID or email. - Terms of Service and Privacy Policy pages. ### Improved - **A redesigned homepage**, with how it works, the features, a dashboard preview, pricing and an FAQ. - The free YouTube transcript tool was rebuilt, and transcripts now show timestamps. - Partial refunds are tracked and reduce the commission in proportion to the amount refunded. - Customer emails are masked in the brand's customer list. - On each program page, the Balance card shows your actual balance, and commission totals include approved commissions. - The Setting tab shows whether each tracking step has received events. - Program pages in the directory can be read by search engines, with sharing previews. These pages now open the marketplace. - A simpler 404 page with Go back and Go home buttons. - Pages load faster. - The docs have a sitemap and `llms.txt`. ### Fixed - Logging out returns you to the homepage. - The Categories page and the Show more button on the program list work again (both have since moved to the marketplace). --- id: "changelog/partner-groups" type: "changelog" url: "https://affitor.com/changelog/partner-groups" updated: "2026-02-27" --- # Partner groups with their own commissions > Organize partners into groups and give each group its own commission rate and duration. Not every partner earns the same. Put partners into groups and give each group its own commission rate and duration. New programs start with a default group. --- id: "changelog/commission-review" type: "changelog" url: "https://affitor.com/changelog/commission-review" updated: "2026-02-24" --- # Approve, reject and mark commissions as paid > Review partner commissions in the dashboard, approve or reject them with a reason, act on many at once, and mark approved ones as paid. Brands can now review partner commissions in the dashboard before they are paid. Approve a commission, or reject it with a reason. Select many commissions to act on them at once, then mark approved commissions as paid. We later removed Mark as Paid: partners can withdraw a commission once the brand has paid the invoice that covers it. --- id: "changelog/server-side-leads-2026-02" type: "changelog" url: "https://affitor.com/changelog/server-side-leads-2026-02" updated: "2026-02-22" --- # Send leads from your server with an API token > Create an API token in the dashboard and record leads from your backend, with a test mode to try the call first. Create an API token in your dashboard, then send leads from your own server, with the customer code the browser tracker sets. Test mode lets you try the call before it counts, and you can regenerate the token at any time. [Read the lead API reference](/docs/api-reference/track-lead) --- id: "changelog/improvements-2026-01" type: "changelog" url: "https://affitor.com/changelog/improvements-2026-01" updated: "2026-01-28" --- # Improvements and fixes, January 2026 > Each program page shows only its own commissions and customers, the Setting tab has your tracking snippet ready to copy, and the chart has a Share button for your program link. ### Improved - On each program's page, partners in several programs now see only that program's commissions and customers. - The Setting tab walks you through setup: copy your tracking snippet, which already includes your Program ID, then share your program link. - The performance chart has a Share button that copies your program link. - In the Partners list, each partner's revenue is now the total of all their conversions. ### Fixed - A brand owner can no longer apply to their own program. --- id: "changelog/docs-site-launch" type: "changelog" url: "https://affitor.com/changelog/docs-site-launch" updated: "2026-01-25" --- # A public documentation site > A public docs site explains how tracking works, how to onboard as a brand, how to set up Stripe and how cookies are handled. We launched a public docs site, linked from the dashboard. It covers a quickstart, how tracking works, brand onboarding, Stripe setup and cookie rules. [Open the docs](/docs) --- id: "changelog/referral-link-qr" type: "changelog" url: "https://affitor.com/changelog/referral-link-qr" updated: "2026-01-23" --- # Edit referral links and get a QR code for each > Change a referral link's short name and destination page after you create it, then download or copy its QR code. Edit any referral link to change its short name (we check it is free) and the page it sends visitors to. Every link has a QR code you can download or copy, for slides, print and video. --- id: "changelog/improvements-2025-12" type: "changelog" url: "https://affitor.com/changelog/improvements-2025-12" updated: "2025-12-30" --- # Improvements and fixes, December 2025 > A redesigned program page, search and sort on partner lists, and test events kept out of your numbers. ### New - One account can switch between brand and partner roles. ### Improved - **The public program page is redesigned.** In program settings, you can save a draft of your changes in this browser and preview your logo before saving. - Partner and application lists have search, sorting and page numbers. - Test events no longer count in your performance numbers. - Disconnecting Stripe takes effect right away. - Clearer labels for paid sign-ups and for commissions waiting for payout. --- id: "changelog/getting-started-checklist" type: "changelog" url: "https://affitor.com/changelog/getting-started-checklist" updated: "2025-12-11" --- # A Getting Started checklist for new brands > New brands see what is left to set up, and clear guidance when the tracking code is not installed yet. New brands get a **Getting Started** checklist with the steps left: your program, commission tiers, the tracking code and your first partner. Until the tracking code is on your site, the dashboard says so and takes you to where to add it, instead of showing empty charts. --- id: "changelog/refer-a-brand-2025" type: "changelog" url: "https://affitor.com/changelog/refer-a-brand-2025" updated: "2025-12-11" --- # Refer brands and earn > Partners get a personal referral link to invite brands to Affitor, and earn $50 when a referred brand sets up its program and $150 when that brand reaches $1,000 in sales. Know a brand that should run its affiliate program on Affitor? Copy your personal referral link from your partner dashboard. You earn $50 when a brand you referred sets up its program, and $150 when that brand reaches $1,000 in sales. This became the Affitor Refer Program in June 2026. --- id: "changelog/improvements-2025-11" type: "changelog" url: "https://affitor.com/changelog/improvements-2025-11" updated: "2025-11-20" --- # Improvements and fixes, November 2025 > A program switcher for brands, auto-accept per program, early access sign-up, and no double commission on a first subscription invoice. ### New - Brands with several programs switch between them from a program selector. A brand with no program yet is taken to create one. - Auto-accept for partner applications is set per program. - An early access sign-up on a refreshed landing page with an FAQ. That landing page has since been replaced. ### Fixed - The first invoice of a subscription no longer pays the commission twice. --- id: "changelog/brand-partner-messages" type: "changelog" url: "https://affitor.com/changelog/brand-partner-messages" updated: "2025-11-19" --- # Message your brands and partners in Affitor > Brands and partners talk in Affitor, with conversations, contacts and messages that arrive live. Brands and partners can now talk without leaving Affitor. Start a conversation from your contacts, and new messages arrive live, without reloading the page. --- id: "changelog/improvements-2025-10" type: "changelog" url: "https://affitor.com/changelog/improvements-2025-10" updated: "2025-10-29" --- # Improvements and fixes, October 2025 > A public application form for brands, a customer status filter for brands, and commissions on every subscription renewal. ### New - A public application form for brands that want to run an affiliate program on Affitor. - Brands can filter the customers their partners referred by status: lead, conversion or click. - Commissions are now created on each subscription renewal, not only on the first payment. ### Fixed - The revenue chart no longer breaks when there is no revenue yet. --- id: "changelog/stripe-connect-commissions" type: "changelog" url: "https://affitor.com/changelog/stripe-connect-commissions" updated: "2025-10-29" --- # Connect Stripe and see every commission > Brands connect their Stripe account so checkout sales are matched to partners, and a new Commissions screen lists each program's commissions with filters. Brands have been able to connect their Stripe account since October 13. Now, when a referred customer pays through the Affitor checkout on your connected account, the sale is matched to the partner who referred them and the commission is created for you. We later retired that checkout. The new **Commissions** screen lists each program's commissions with filters. Partners see the commissions they earned in each program they joined. --- id: "changelog/affiliate-programs-for-brands" type: "changelog" url: "https://affitor.com/changelog/affiliate-programs-for-brands" updated: "2025-09-29" --- # Run your own affiliate program on Affitor > Brands create affiliate programs, partners apply and get tracked links, and clicks, sign-ups and checkout sales are attributed to the partner who sent them. We now run affiliate programs. Brands set up a program, partners join it, and we track what each partner brings in. - **For brands:** sign up as a brand with your company email, create programs with your logo, set commission tiers with a percentage rate that can step up with the number of referrals, and auto-accept partner applications. Your dashboard sums up your programs, partners and sales. - **For partners:** apply to a program, get a tracked referral link with a name you choose, and see the customers you referred. - **Tracking:** add the tracking script to your site to record clicks and sign-ups. Commissions were created when buyers paid through an Affitor checkout link, which we later retired. Applying twice to the same program is blocked. --- id: "changelog/improvements-2025-08" type: "changelog" url: "https://affitor.com/changelog/improvements-2025-08" updated: "2025-08-29" --- # Improvements and fixes, August 2025 > Browse affiliate programs by category with counts, sorting and page numbers, faster category pages, and no more NaN referral balances. ### New - **Browse by category.** Category pages list their programs with counts, sorting and page numbers. ### Improved - Category pages load faster. ### Fixed - Referral balances and earnings no longer show `NaN`. Category pages became part of the Affitor Marketplace in June 2026. --- id: "changelog/improvements-2025-07" type: "changelog" url: "https://affitor.com/changelog/improvements-2025-07" updated: "2025-07-31" --- # Improvements and fixes, July 2025 > Short referral links, community sign-in with your Affitor account, and redesigned program pages. ### New - Referral links get a short link you can share. - Sign in to the Affitor community forum with your Affitor account. The forum has since closed. - Free accounts see their daily allowance on the profile page. - In the script assistant, save your own prompts and reuse them. ### Improved - Program pages are redesigned, and the program list gets a new filter bar with country and launch year filters. - The plans page opens on yearly billing. ### Fixed - Sorting by recurring commission works correctly. The program list became the Affitor Marketplace in June 2026, and the script assistant is no longer part of Affitor. --- id: "changelog/referral-program-2025" type: "changelog" url: "https://affitor.com/changelog/referral-program-2025" updated: "2025-07-26" --- # Join the Affitor referral program > Get referral links for Affitor and follow your visitors, leads, conversions and commissions in one dashboard. Partners can now earn by sharing Affitor. A short onboarding sets you up as a referrer, and you create your own referral links to Affitor's pages. The referral dashboard shows how they perform. - Visitors, leads and conversions at a glance, with a performance chart. - An activity feed of what happened with your links. - A list of the commissions you earned. --- id: "changelog/pages-with-referral-links" type: "changelog" url: "https://affitor.com/changelog/pages-with-referral-links" updated: "2025-07-23" --- # Publish pages with your referral links built in > Write a page in a rich-text editor, add images and links, and give each page its own referral link. Write a review or a guide in the new page editor and add images and links. If you are in the Affitor referral program, each page you publish gets its own referral link, and the referral dashboard shows its visitors, leads and conversions. - A list of your pages, to edit or delete any of them. --- id: "changelog/improvements-2025-06" type: "changelog" url: "https://affitor.com/changelog/improvements-2025-06" updated: "2025-06-20" --- # Improvements and fixes, June 2025 > A redesigned script assistant chat box, and Show more works again on video lists. ### Improved - The script assistant's chat box is redesigned. ### Fixed - The Show more button on video lists works again. The script assistant and these video lists are no longer part of Affitor. --- id: "changelog/improvements-2025-05" type: "changelog" url: "https://affitor.com/changelog/improvements-2025-05" updated: "2025-05-29" --- # Improvements and fixes, May 2025 > A Top Ads page with transcripts, Google sign-in that works from in-app browsers, and no more duplicate ads. ### New - **Top Ads.** See ads running for affiliate offers, read their transcripts, and send one to the script assistant. ### Improved - Google sign-in now works from links opened inside apps such as Facebook, Instagram and X: we open the page in your regular browser, and Safari is no longer blocked. - Lists show a loading outline instead of a blank page. ### Fixed - The same ad no longer appears twice in Top Ads. Top Ads and the script assistant are no longer part of Affitor. --- id: "changelog/paid-plans-2025" type: "changelog" url: "https://affitor.com/changelog/paid-plans-2025" updated: "2025-05-18" --- # Paid plans for more research > Monthly, quarterly and yearly plans, paid by card through Stripe, with coupons and cancel anytime. We opened a public pricing page. You could compare plans side by side, choose monthly, quarterly or yearly billing, and pay by card through Stripe, with coupon codes at checkout and cancel anytime. Your profile page showed your plan and how much of your allowance you had used. That pricing page was replaced by program pricing in June 2026; the plans are still available from the Upgrade page in your profile. Running an affiliate program on Affitor is priced separately: each program is free until it earns its first $10,000 in affiliate revenue, then 3.5% of each sale. [See program pricing](https://affitor.com/pricing) --- id: "changelog/improvements-2025-04" type: "changelog" url: "https://affitor.com/changelog/improvements-2025-04" updated: "2025-04-30" --- # Improvements and fixes, April 2025 > Google sign-in, filters you can share, traffic by country, the value of a conversion on every program, and a form to submit a program. ### New - Sign in with your Google account. - **Filter programs** by industry, commission rate, one-time or lifetime commission, and payment method. Filters are saved in the page link, and one button clears them. - Pick which table columns you see; Affitor remembers your choice. - Program pages show traffic by country. - Each program shows the average value of a conversion and its recurring commission. - Ask for a short AI summary of any program from its page. - Anyone could submit a program to be listed. ### Improved - Right-click a program to open it in a new tab. These features were part of the program directory, which became the Affitor Marketplace in June 2026; the submit form and the AI summary are gone. --- id: "changelog/ai-script-assistant" type: "changelog" url: "https://affitor.com/changelog/ai-script-assistant" updated: "2025-04-14" --- # Write video scripts with an AI assistant > Turn the transcript of a popular video about a program into a script for your own video. Sign in, pick a YouTube or TikTok video about a program on its page, and the assistant turns its transcript into a script for your own video. Ask for changes in the chat until it sounds like you. The script assistant is no longer part of Affitor. --- id: "changelog/program-directory-launch" type: "changelog" url: "https://affitor.com/changelog/program-directory-launch" updated: "2025-03-23" --- # Find affiliate programs in one searchable table > Affitor starts as a directory of affiliate programs for creators and marketers, with search, sorting and a page for every program. Affitor starts here: one place to find affiliate programs worth promoting. Search by name, sort by commission or monthly traffic, filter by category and tag, and open a page for each program with its commission details. - Program pages show popular YouTube and TikTok videos about the program, its estimated monthly web traffic and its top search keywords. - Works on phones, with search and navigation sized for small screens. - Light and dark theme. Affitor now uses a light theme only. The directory became the Affitor Marketplace in June 2026. [Browse the marketplace](https://affitor.com/marketplace)