Trust is infrastructure.

Publisher onboarding

Applicants tell us who they are, what they operate and how they intend to distribute offers. CommissionAPI intends to review the property, the integration method and the declared traffic model before activating access to eligible programs. Access can be granted per program rather than as a blanket approval.

Traffic-source declaration

Publishers declare the channels they intend to use. Declared sources are matched against each program’s permissions before an offer is made available.

• Website
• Application
• Social
• Email
• Paid search
• Organic search
• AI integration
• Other

Program restrictions

Programs may individually permit or prohibit specific channels, geographies, brand-term bidding, coupon and incentive models. CommissionAPI treats these as program-level configuration, not as global defaults, so a channel allowed by one advertiser is not assumed to be allowed by another.

Sub-publisher identification

Where provider infrastructure supports SubID or equivalent parameters, CommissionAPI intends to pass a stable identifier for the downstream publisher, application or integration so providers and advertisers can attribute traffic to its actual source.

Prohibited behaviour

The following are prohibited across all CommissionAPI integrations, in addition to any restrictions a specific program imposes.

• Fraudulent clicks
• Cookie stuffing
• Misleading advertising
• Unapproved paid search
• Unauthorized trademark bidding
• Spam
• Incentivized traffic where prohibited
• Fake leads
• Artificial calls
• Self-referrals where prohibited
• Misrepresentation of an advertiser relationship

Enforcement

CommissionAPI may suspend integrations, withhold disputed commissions and share relevant traffic information with providers or advertisers where permitted by applicable agreements and law.