# 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. You can update your email later in account settings. ### 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? Platform fees accrue per attributed sale and are billed through **monthly invoices**. You can download each invoice as a PDF and pay it with Stripe Checkout from your Billing tab. If an invoice goes unpaid, your program can be paused — see the [overdue policy](/brand/billing/overdue-policy). ### Does Affitor collect money from my customers? No. Affitor is **not** the merchant of record. You continue charging customers through your own Stripe or payment setup. --- ## 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 already use Stripe Checkout and can attach Affitor metadata, you can integrate without replacing your existing payment stack. ### 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 - a last-click, last-partner-wins attribution model - a 60-day default attribution window, configurable per program The full model is documented in the [attribution reference](/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? With Stripe integration, Affitor attributes the sale from metadata and webhook events. For subscriptions, renewals also require `subscription_data.metadata` to be populated. --- ## Commissions & Payouts ### Who pays the partner? Affitor handles partner commissions and payouts after attributed conversions move through the commission lifecycle. Partners request withdrawals through Affitor's payout workflow — bank transfer, PayPal, Stripe, or Wise — once their approved balance passes the program's payout threshold. ### What happens after a sale is attributed? At a high level: 1. sale is recorded 2. commission is created 3. commission moves through review / hold operations 4. payout workflow continues in Affitor ### What happens if there is a refund? Refunds are reconciled through Affitor's commission and payout workflow. The exact outcome depends on where the commission is in the lifecycle when the refund happens. --- ## Support & Troubleshooting ### What is the fastest way to self-serve an integration? Follow the manual docs flow in order: 1. [Install Tracking](/brand/tracking/quickstart-integration) 2. [Lead Tracking](/brand/tracking/lead-tracking-signup) 3. [Payment Tracking](/brand/tracking/payment-tracking-stripe) 4. [Testing Integration](/brand/tracking/testing-integration) If your team prefers terminal-based setup, the [Affitor CLI](/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