Partner onboarding
Support partner sign-ups and a partner portal.
Give referral partnerships a clear structure
Run referral programs with tracked links, commission rules, partner payouts, and fraud checks.
Each domain runs a program with a currency, cookie window, hold period, minimum payout, first or last click and versioned terms. Commission rules pay a percentage or a fixed amount per product, per category or on everything, with volume tiers and recurring commission for subscriptions. Partners apply at partner.<domain>/join and, once approved, get a code and a link at /r/<code> that sets a first-party cookie and redirects, with an optional coupon code. Conversions arrive through POST /api/v1/conversions or a thank-you page snippet, idempotent by order id, and refunds reverse commission; self-referrals, bursts from one address and browser-only reports are held for review. The ledger moves commission from pending to approved after the hold (by cron) to paid in payout batches with UPI or bank details, a CSV export and the UTR. Partners sign in to /portal with an emailed one-time code to see their stats, links, coupon, sales, payouts and creatives. Claude drafts program terms, outreach emails and performance summaries. affiliates.appneural.com holds every domain; partner.<domain> holds one domain's program.
What Affiliates does for you.
Support partner sign-ups and a partner portal.
Use tracked links and conversion fraud checks.
Work with commission rules and partner payouts.
A suggested path for Affiliates. What you can do depends on your access in the app.
Review the domain and commission rules.
Check the partner sign-up and portal experience.
Inspect tracked conversions and payout context.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain runs a program with a currency, cookie window, hold period, minimum payout, first or last click and versioned terms. Commission rules pay a percentage or a fixed amount per product, per category or on everything, with volume tiers and recurring commission for subscriptions. Partners apply at partner.<domain>/join and, once approved, get a code and a link at /r/<code> that sets a first-party cookie and redirects, with an optional coupon code. Conversions arrive through POST /api/v1/conversions or a thank-you page snippet, idempotent by order id, and refunds reverse commission; self-referrals, bursts from one address and browser-only reports are held for review. The ledger moves commission from pending to approved after the hold (by cron) to paid in payout batches with UPI or bank details, a CSV export and the UTR. Partners sign in to /portal with an emailed one-time code to see their stats, links, coupon, sales, payouts and creatives. Claude drafts program terms, outreach emails and performance summaries. affiliates.appneural.com holds every domain; partner.<domain> holds one domain's program.
Taking the money belongs to Payments; coupon codes belong to Coupons; paid creator campaigns belong to Influencers.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
affiliates.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.