# Partner Contract Explained ## Partner principle * The partner contract sits between your end users and the Celestium platform. Every transaction a member makes through your front-end is routed via the Partner contract to the Core, which means attribution and revenue accounting are handled on-chain without any off-chain reconciliation step. * Betting and staking still require the participant to hold a Celestium Pass NFT. The partner contract does not bypass membership gating — it sits on top of it. * A partner contract combines the benefits of a white-label solution and a license agreement in a single deployable unit. There is no separate operating agreement to negotiate; the on-chain terms are the agreement. ## How the business works * **Compensation** is defined by the [Partner Tariff Terms](/for-partners/faq-and-terms/partner-tariff-terms.md) and is driven by the volume your users generate across staking and betting. Payments are sourced from platform revenue (for staking and lotto-style games) or from the shared betting fee (for PvP games like Predict). Settlement happens atomically in the same transaction as the underlying user action. * **Technical flexibility:** the partner contract exposes a stable interface that you can wire into a custom front-end with your own branding, your own domain, or even a hardware device such as a kiosk or slot machine. Celestium does not enforce any UI standard — your brand is yours. A reference UI is available for partners who want to start from a working clone rather than build from scratch; contact `TODO_PARTNER_BRAND_CONTACT` for source files and brand cooperation. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.celestium.digital/for-partners/about-partner-contract/partner-contract-explained.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.