# Creator Network: self-service setup

Every Creator uses one of the same three supported sales paths. App ownership and content are reviewed by Power CM. The technical setup and publication are completed by the Creator using the checks in **Creators → Payments & access**.

## 1. Choose your sales path

| Sales path | Where the customer pays | One-time installation | Commission settlement |
| --- | --- | --- | --- |
| Power CM checkout (web/desktop) | Stripe checkout opened by Power CM | Server connector validates an authenticated purchase intent and applies payment/refund updates to app access | Stripe allocates proceeds and commissions under the programme rules |
| Existing Stripe checkout | Your existing Stripe checkout | Referral helper forwards `cn_ref`; restricted read key and signed webhooks verify purchases, renewals and refunds | Separate, explicitly authorized Creator funding charge; Stripe transfers available Partner funds |
| RevenueCat (Android/iOS) | Your existing app store purchase flow | Server helper binds the authenticated app user to the referral before purchase; RevenueCat and store read access verify purchases | Fixed commission base agreed per plan, separately funded under the Creator's explicit authorization |

Direct Google Play / Apple integration, Paddle, Lemon Squeezy and generic affiliate-provider connectors are not selectable publication paths. Creator-managed and tracking-only records from earlier versions remain historical ledgers; they are not alternative self-service publication paths. No bespoke integration is promised for unsupported combinations.

## 2. Set your plans and commission

Create the app, its plans and commission in the dashboard. Recurring commission windows are 1–48 months; attribution is 1–90 days and validation is 7–180 days. Lifetime commissions are not supported. Existing attributed purchases retain their original agreements.

Joining and listing have no subscription fee. The Partner commission and Power CM's 3% network fee are separate. On an eligible EUR 10 Stripe payment and a 20% Partner commission: EUR 2 belongs to the Partner and EUR 0.30 is the network fee; actual provider processing costs are additional. Taxes and shipping are excluded and discounts reduce the eligible base. RevenueCat uses the fixed base explicitly accepted for each plan, not an estimate of store net proceeds; see the plan agreement in the dashboard.

## 3. Install once and verify

- Power CM checkout: [installation contract](INTEGRATION.md), [server connector](connector.mjs). Click **Verify connection**. The server sends a signed, nonce-bound protocol challenge. A generic HTTP 200 does not pass. Verify purchased access and refund updates in your app before confirming publication.
- Existing Stripe: [installation contract](EXISTING-STRIPE.md), [referral helper](stripe-referral.mjs). Connect test and live prices, generate a sandbox referral, then verify attributed purchases, applicable renewals and full refunds for each plan. Confirm that your existing app delivers access.
- RevenueCat: [binding contract](NATIVE-ATTRIBUTION.md), [server helper](native-binding.mjs). Map store products, accept per-plan commission terms, configure server binding and store read access, and receive a signed notification. The checklist distinguishes required configuration from optional prior sandbox purchase history. Android must preserve Install Referrer through login; iOS uses authenticated website signup before installation. An App Store listing link alone cannot preserve the referral.

Keys stay on the server. Test credentials and referrals never create live commissions. No full Stripe secret key from the Creator is required.

## 4. Authorize funding and publish

Existing Stripe and RevenueCat Creators explicitly authorize a separate commission payment method with charge/monthly limits and a processing reserve. This is not the Stripe account used to receive product sales. A saved connection alone cannot debit or publish. Supported currencies and recipient countries follow the currently verified provider circuit, not a promise of global coverage.

After app review and connection checks pass, the Creator confirms publication. There is no per-app manual technical approval. A checkout publication repeats the connector, Stripe, tax, country and worker checks. External connections show the exact outstanding requirements before enabling publication. Publication is not evidence of a purchase, a transfer or a bank payout.

## 5. Daily operation

Partners accept the programme, create their referral links and promote the app. Verified eligible purchases produce attributed commissions under the saved rule. Renewals retain that attribution within the agreed window. The validation period, actual available funds and payout readiness govern transfers. Refunds and disputes adjust both commissions and network fees; failed collection does not become a paid commission.

The dashboard separates purchase received, attributed commission, funding, transfer and bank payout. Stripe onboarding and bank availability still apply. Creators manage plan changes, funding revocation, new-payment pauses and retirement through the dashboard; existing obligations and purchase agreements are preserved.

## Recorrido en español

1. Guarda la ficha, los planes y la comisión; envía la app a revisión de titularidad y contenido.
2. Elige checkout de Power CM, tu Stripe actual o RevenueCat. Cada integración tiene una guía y un conector estándar.
3. Instala el conector una vez con tu constructor o desarrollador; conserva la referencia del Partner y ejecuta las comprobaciones del panel.
4. Con Stripe propio o RevenueCat, autoriza el medio de financiación y sus límites. Cuando esté todo comprobado, confirma tú la publicación, sin una segunda aprobación técnica del equipo.
5. Los Partners crean sus enlaces; el sistema verifica las compras, atribuye comisiones, procesa renovaciones, financiación y reembolsos. Consulta cada estado en el panel.

Alta sin suscripción. Comisión del Partner elegida por el Creator, más 3% de Power CM y costes reales de procesamiento. Comisiones recurrentes de hasta 48 meses; no se ofrece duración vitalicia. Los acuerdos anteriores se conservan.