AffiliPartnerCS / Integrations
Connect services deliberately, not by default.
Use community verification, reviewed provider payouts, account credit, subscription rules, and business events where your program needs them. Each connection keeps its own setup, authority, and data boundaries.
WooCommerce partner-commerce software · Customer Reference 1.3.9
Explore AffiliPartnerCS
Open the interactive workspace and try the controls.
Community verification
A trusted server confirms login state. Your store grants the benefit.
Each connected partner has its own site identity, trusted server secret, platform mode, merchant address, and connection status. Setup downloads, connection checks, restricted key controls, and member-access tests stay together. The secret remains on a trusted server, not in public scripts or links.
| Connection | Supported approach in the supplied guide |
|---|---|
| Self-hosted Discourse | A supplied server plugin signs the visitor’s signed-in or guest state and exact store destination. |
| Managed/hosted Discourse | A secret-free theme component starts the supported silent DiscourseConnect check. The merchant validates the response and produces the same verified or unverified result. |
| Self-hosted XenForo | A supplied server add-on signs state and destination on the forum server. |
| XenForo cloud hosting | The server add-on is usable where the hosting arrangement permits third-party add-ons. |
| Custom platforms, including WordPress | A trusted server can implement the documented signed-verification protocol. A platform selection in the application is not proof of a bundled connector. |
The accepted message is destination-bound, valid for no more than five minutes, and intended for one use. A signed-in result creates a separate temporary pricing session; a failed or signed-out result grants no protected discount. Ordinary affiliate links and public coupons do not need this connection.
Different paths, different privacy details
Do not flatten the privacy explanation into one promise.
Self-hosted community paths
Discourse and XenForo verification provide the login-state result without sending the forum password, username, private messages, or membership profile. The store does not copy the member database.
Managed Discourse callbacks
Mandatory identity fields briefly cross the signed callback and are discarded after verification rather than stored as local community-user accounts. Server/proxy/CDN/security/analytics logging must also exclude those details.
A host that cannot run the required server add-on does not become a browser-only signing workaround. The public merchant-address setting selects the intended secure origin; it does not migrate WordPress or authorize unrelated protected destinations.
Payout providers
Review the transfer. Reconcile the existing attempt.
PayPal Payouts
Configure sandbox/live credentials and webhook identity. Authorized finance reviews each batch before submission; verified provider callbacks and references track recipient-payment status. A normal manual Mark Paid action cannot replace native provider evidence.
Stripe Connect
Configure test/live credentials and webhook verification. Hosted Express onboarding supplies the connected-account reference and readiness state. A reviewed transfer to that account is not a separate confirmation of its downstream bank payout.
Schedules and callbacks may reconcile an existing payment but cannot authorize a new PayPal or Stripe send. Active, unknown, or successful attempts block another send. Provider Paid – Recover Ledger completes interrupted local closure against the successful reference; a reversal becomes a separate review state.
Local companion integration
Settle earnings as Store Credit, with one owner for each ledger.
Compatible AffStackDev Store Credit services provide account-bound issuance, balances, reservations, redemption, and credit adjustments. AffiliPartnerCS retains commission liability, frozen payout terms, and the settlement record. The connection is local and permission-scoped—not an outside credit database.
Merchants choose manual approval or explicitly allow automatic settlement for qualifying scheduled credit batches. Both paths require a matching beneficiary, amount, currency, account ownership, lifecycle, tax state, and stable source identity. Unsupported currencies, missing conversion rates, or unavailable services stop new issuance.
A durable payout reference is reused across retries, worker restarts, recovery, and notification resends. Matching prior issuance is reused; conflicting details require review. The commission closes only after credit is confirmed as durably issued. Changing a settled batch to cash cannot pay the same earnings again.
Optional credit incentive
A $300 commission payout with a 10% credit bonus and no fee issues $330. The $30 bonus remains separately recorded. Checkout eligibility, Apply/Remove controls, partial use, reservations, and refund restoration follow Store Credit and WooCommerce rules.
WooCommerce and subscriptions
Extend the existing order lifecycle.
Store and checkout
WooCommerce remains responsible for products, customers, discounts, gateway confirmation, orders, stock, shipping, tax, refunds, and order permissions. AffiliPartnerCS supports HPOS, classic checkout, and Checkout Block flows.
Optional renewal commissions
WooCommerce Subscriptions supplies subscription and renewal events. Captured attribution can follow eligible renewals with no-renewal, every-renewal, first-N, or declining policies. Repeated events do not duplicate the primary reward.
Shared Suite workspace
The Suite supplies common product navigation and dashboard summaries. It does not become the owner of partner, commission, or payout data; globally disabled enhancement returns merchant work to normal PHP pages.
Hosted tax status
Track approval without keeping completed tax forms.
The optional hosted process retains partner/year operational status, protected provider references, and payout context. The selected provider handles form completion and identity verification. AffiliPartnerCS does not prepare/file returns or store completed tax forms or tax identifiers.
The compensation threshold and reporting currency are merchant settings; the initial 2,000 USD value is not a statement of a statutory filing threshold. When configured blocking applies, threshold-crossing payouts require Approved status, not merely Received. Cash-to-credit selection does not bypass that check.
Signed provider status updates use timing and sequential event versions. A failed read is not zero compensation or clearance. Each payout retains its tax context even when the partner later changes its profile.
Business connections
Share selected events—not unrestricted control.
REST resources
Normal WordPress authentication plus product permissions govern status, partner, application, commission, and payout collections. Collections are paginated; lifecycle changes require the permitted action and a reason.
Signed business events
Select secure receivers and events for applications, partner lifecycle, order attribution, commission, payouts, fraud alerts, and tier changes. Each event retains its identity across bounded delivery retries.
Extension points
Documented hooks support merchandise eligibility, calculation basis, attribution, application/payout events, event content, hosted tax destinations, login paths, and additional portal content. Financial safeguards remain applicable.
Provider recipients, hosted tax services, event receivers, the optional QR renderer, and WordPress mail transport receive the information required for their enabled purpose. A successful event receipt or local mail handoff is not independent proof of the downstream action or inbox delivery.
Your programs. Your partners.
One connected way to manage them.
Choose the license package that fits your sites. Existing AffiliPartnerCS packages and purchase terms remain on the pricing page.