A referral program looks unprofessional when affiliates land on a generic dashboard with unfamiliar branding. A white label affiliate portal fixes that problem without forcing your team to build tracking, commission logic, and reporting from scratch.
Rewardful gives SaaS teams a hosted affiliate portal they can brand, place on a custom domain, and connect to Stripe. Your job is to set the rules, test the path, and give affiliates a clear operating system.
What a White Label Affiliate Portal Means on Rewardful
White label does not mean you receive Rewardful’s source code or a fully custom affiliate application. It means affiliates see a portal that looks like part of your company.
On Rewardful’s Growth plan, you can use a custom domain, add your logo and favicon, set brand colors, and remove Rewardful branding. Review Rewardful’s affiliate portal branding controls before you choose the plan.
What affiliates see
Affiliates use the hosted portal to join your program, access referral links, review clicks and conversions, check commissions, and add payout details.
You control the program from the merchant dashboard. Affiliates do not need access to your Stripe account, customer records, or internal revenue reports.
A branded portal should include:
- Your logo, colors, and favicon.
- A custom domain such as
affiliates.yourcompany.com. - Program terms, commission rules, and payout timing.
- Links to brand assets, swipe copy, product screenshots, and approved claims.
- A support contact and a simple explanation of what happens when a commission is reversed.
What Rewardful does not replace
Rewardful does not replace your public website, support desk, email platform, legal review, or finance process.
It also does not provide a fully custom affiliate-facing interface where you control every screen and workflow. You are branding Rewardful’s hosted experience, not deploying your own affiliate software.
Use custom portal text, linked files, and the HTML head field to improve the experience. For a fully bespoke partner application, you need a custom build around Rewardful’s tracking and data layer.
Set the Program Rules Before You Configure Anything
A portal with vague commission rules creates support tickets and payout disputes. Write the rules before you invite your first partner.
Start with one campaign. A simple structure is easier to test and easier for affiliates to explain.
Choose a commission model that finance can support
Rewardful supports fixed or percentage commissions. You can also set one-time or recurring rewards and limit recurring commissions to a defined number of invoices.
A common SaaS offer is 20% recurring commission for the first 12 paid invoices. Another is a fixed $100 payment after a new customer completes their first paid month.
Do not publish “20% recurring” unless you define the details. State whether the rate applies to gross revenue, collected revenue, or revenue after discounts and refunds. State the maximum invoice count.
Your terms should also state:
- The cookie window and which campaign it applies to.
- Whether coupon attribution can earn a commission without a tracked link click.
- Which traffic sources are allowed.
- Whether self-referrals, brand bidding, coupon sites, or paid social are restricted.
- When a commission becomes due and when it can reverse.
A created commission is not the same as a payable commission. Refunds, failed payments, disputes, and plan changes can change the final amount.
Rewardful says commissions become due after 30 days by default, unless you configure another period, and only after the affiliate reaches your minimum payout amount. Read its commission and payout overview before you set a payment schedule.
Build terms affiliates can price into their work
Affiliates need operating rules, not marketing language. Put the terms in the signup flow and link them inside the portal.
Use plain statements. “Commissions are calculated on collected subscription revenue.” “Refunded invoices reverse unpaid commissions.” “Paid commissions are recovered through future offsets where permitted.”
Have legal or tax counsel review your agreement. Your business remains responsible for affiliate disclosures, privacy notices, payment records, tax forms, and local contractor rules.
Configure Your Rewardful Account and Stripe Tracking
Connect your payment processor first. For most SaaS teams, that means Stripe.
Rewardful needs the correct checkout and conversion setup to connect a referred visitor with a paid customer. If the checkout path is wrong, a polished portal will not fix attribution.
Install tracking on every relevant domain
Add the Rewardful tracking script where visitors first arrive. Then check each place a customer can enter the purchase path.
That usually includes your marketing site, pricing pages, app subdomain, checkout domain, and any separate signup flow. If the buyer moves across domains or subdomains, configure cross-domain tracking with the required domain settings.
Rewardful’s documentation also covers custom Stripe integration methods for setups that do not fit a standard client-side checkout.
Set the cookie duration at campaign level. Rewardful’s documented default is 60 days, but your program may need a shorter or longer window. Match the window to your buying cycle.
Add coupon attribution for hard-to-track channels
Links work well in blogs, newsletters, YouTube descriptions, and review sites. They work less well in podcasts, live events, printed material, and private social groups.
Create affiliate coupons for those channels. Coupon tracking can assign credit at checkout even when the visitor did not arrive through a tracked referral cookie.
Do not treat coupon tracking as a reason to ignore link testing. You still need to know whether the coupon belongs to the correct affiliate and campaign.
Brand the Affiliate Experience Without Confusing Users
The best white label affiliate portal feels like a natural extension of your product. It uses your domain, follows your visual system, and answers common questions before affiliates submit a ticket.
Start with the URL. A subdomain such as partners.yourcompany.com or affiliates.yourcompany.com is clear and easy to share.
Point a custom domain to Rewardful
Create the required CNAME record and point it to domains.rewardful.com. Then verify the DNS record and contact Rewardful support to complete the switch.
Rewardful documents the full custom affiliate dashboard domain process. Its guidance says activation can take about 24 hours after the DNS record is ready.
Do not change this late in launch week. Rewardful does not redirect the old portal subdomain after you switch. Old signup links, affiliate instructions, and saved bookmarks need manual updates.
Add useful text, links, and assets
Give affiliates the material they need to sell accurately. Add a short welcome message, FAQ entries, a product positioning guide, logo files, screenshots, and approved copy.
Rewardful supports custom portal text, FAQs, and asset links. Keep the portal focused. Ten useful assets beat a library nobody can search.
You can also add custom code to the portal head on supported plans. Rewardful’s custom HTML guidance includes adding a no-index meta tag. Use it so affiliate login and signup pages do not compete with your public marketing pages in search results.
Use your own email system for communication
A custom domain does not automatically make every affiliate email look like it came from your brand.
Rewardful’s surfaced documentation points teams toward email provider integrations and webhook-based workflows. Use your existing tool, such as Customer.io, HubSpot, Mailchimp, or ActiveCampaign, for invite emails, onboarding sequences, payment reminders, and policy notices.
Rewardful webhooks can send events to your application or Zapier. Its webhook setup guide requires an HTTPS endpoint. Keep webhook secrets private and limit access to the systems that need them.
Protect Tracking, Payouts, and Customer Data
Affiliate programs attract legitimate partners and bad traffic. Your controls need to cover both.
Restrict portal administration to the few people who manage campaigns, payouts, and integrations. Use separate accounts where possible. Do not share Stripe credentials or place API keys in shared documents.
Set fraud rules before affiliates scale
Review referral activity for self-referrals, duplicate customer patterns, sudden spikes, unusually high refund rates, and traffic from sources you did not approve.
Rewardful offers traffic source controls that can ignore selected domains. Use this for sources that do not fit your terms. It is a traffic filter, not a full fraud system.
Set a manual review step for large commissions and first payouts. Keep a record of the affiliate, campaign, customer identifier, invoice period, reward amount, refund status, and approval owner.
If a paid commission later reverses, do not overwrite the original entry. Add an adjustment record with the date, reason, and recovery decision. Most small programs offset the amount against future approved earnings.
Track approved revenue, not dashboard activity
Clicks show attention. Pending commissions show possible value. Approved commissions show what passed your program rules.
Build a monthly affiliate report with:
- Affiliate name, campaign, referral link, and coupon code.
- Clicks, conversions, pending commissions, approved commissions, and reversals.
- Customer revenue, payout date, payout method, and reviewer.
- The reason for every manual adjustment.
A partner can generate 500 clicks and little usable revenue. Another can generate 30 clicks and five retained customers. Review approved referred revenue, refund rate, and paid commissions together.
Test Your White Label Affiliate Portal Before Launch
Do not invite partners after only checking the dashboard. Test the full buyer and affiliate path with a small internal group.
Use a test affiliate email. Create a referral link. Click it in a clean browser session. Complete a test purchase where your billing setup allows it. Then verify each record in Rewardful and Stripe.
Run this pre-launch check
Test desktop and mobile. Test the custom portal domain, the signup page, password reset flow, referral link, coupon code, checkout path, commission calculation, and payout details.
Check that a visitor keeps attribution when moving between your marketing site and checkout. Confirm that the affiliate sees the expected campaign, rate, and assets.
Use Rewardful’s post-install setup checklist as a final control. It covers the custom domain, branding, timezone, portal content, and email workflow connections.
Document exceptions before contacting support
When tracking looks wrong, collect the evidence first. Record the content URL, affiliate ID, campaign name, referral link, coupon code, customer email or Stripe customer ID, date range, and screenshots.
State what you expected to happen. Then state what Rewardful and Stripe actually recorded.
Do not assume every missing commission is a technical error. The customer may have abandoned checkout, used a different affiliate’s link later, purchased after the cookie expired, or failed a campaign condition.
Final Launch Decision
A white label affiliate portal on Rewardful works when the branding, tracking, terms, and payout process tell the same story. The custom domain makes the portal feel owned. The commission rules make it workable.
Launch with one clear campaign, a small approved affiliate group, and a tested checkout path. Expand only after your team can reconcile approved commissions without manual cleanup every month.
