KHATTAH Membership Rules
Draft for review — not approved for a live launch.
Version 2026-10-21-draft-1 · Effective date pending approval. Bracketed details must be completed.
These rules describe the membership and invitation flow agreed for KHATTAH. They are a proposed operating policy, not confirmation that every deployed feature already follows it. The live operator must approve the rules and complete the legal and operational decisions identified below before real payments begin.
1 Registration and member access
A person who completes registration receives a unique Member ID and may sign in before making a package payment. The member must provide accurate information, control the registered email address and protect their login credentials. Proposed eligibility is adults aged 18 or older in approved locations only; the operator must approve the eligible locations before launch.
After an ordinary member signs in, Request Invitation is the default destination. Administrators have a separate administration destination.
2 Packages and participation
Only an authorized administrator may create a package or change the package catalogue. Members may request participation in an existing package. Creating a member participation record within an existing package does not create a new package definition.
Each package must disclose its ID, actual goods or services, price, currency, applicable taxes and fees, reward calculation, refund rights and payment methods before payment. The goods or services and their independent commercial value remain [TO BE SPECIFIED]. No real payment may be accepted until these details and the legal basis of the reward model are approved.
A member may participate in more than one approved package through separate participation records. A contribution counts only toward an invitation for the same package. Neither the member nor an administrator may silently move a payment to another inviter, package or link.
3 The shared Request Invitation page
All members who have completed registration can access Request Invitation, including members who have not paid. The shared page displays both yellow and green invitation links. Yellow means available for requests. Green means a requester’s payment has been confirmed and that link is complete and unclickable.
A paid member has five invitation positions for the relevant package, labelled A, B, C, D and E. Before a position is completed, its owner Member ID, Package ID and link letter are defined. The owner cannot use their own link to fulfil an objective.
4 Requesting an invitation and opening checkout
A member chooses a yellow link. KHATTAH records their request and sends an invitation to their registered email address identifying the Package ID, owner or inviter Member ID, requesting Member ID and selected link letter.
More than one member may request the same yellow link. Registration, requests and invitation emails do not reserve or consume it. A request does not guarantee that the link will still be available when payment is attempted.
Opening the emailed link leads to checkout for the matching participation. If necessary, the requester must first sign in to the intended account. The email link does not replace account authentication. The package price and currency are fixed at checkout; the member chooses an available payment method.
5 The five identifying values
Each completed link is identified by these five values: requesting Member ID; Package ID; owner or inviter Member ID; confirmed payment date and time; and link letter A, B, C, D or E. Before payment, the confirmation time is absent. The selected letter remains fixed regardless of the order in which different members pay.
The platform must preserve a consistent recorded timezone and display it clearly. A later configuration change must not rewrite the historical identities, price or reward terms of an already confirmed participation.
6 Payment confirmation and completed links
Only a successfully verified payment of the correct package value completes a link. Pending, failed, cancelled, unverified or reversed transactions do not establish a completed objective. Repeated processing of the same confirmed transaction must not create another objective.
On confirmation, that specific inviter link changes from yellow to green, becomes unclickable and expires for every other requester. Its green record remains visible on Request Invitation. A copy appears on the owner’s Activity page, which shows only that owner’s confirmed paid links, not yellow links or another owner’s activity.
After their own package payment is confirmed, the paying member’s five yellow links A–E become available for requests in that same package.
Only one requester may complete a particular link. If another payment arrives after it is completed, it must not be credited to the link or silently reassigned. The operator must resolve the payment exception under a published refund and failed allocation policy [TO BE APPROVED].
7 Completing five objectives and rewards
When five distinct members have confirmed payments for an owner’s links A–E in the same package, the owner completes five objectives and the package reward becomes due for issuance under the disclosed reward terms. Four completed links do not create the fifth objective.
Reward due and reward paid are different states. A reward is marked paid only when its actual payout is confirmed. The reward amount, source of funding, processing deadline, payout method, fees and any verification requirements must be disclosed before participation [DETAILS REQUIRED]. Completing five objectives does not automatically create a new package.
Fraud, a reversal or a payment dispute may require a documented review of the affected qualification or reward. The operator must explain the reason and provide a dispute channel; it must not erase the original transaction history.
8 Conduct and testing
Members must not create false identities, make fictitious payments, use another person’s account, exploit duplicate transactions, send unauthorized invitations or promise guaranteed earnings. Authorized administrator support access must be logged; viewing as a member must not disclose passwords or permit payments or account changes.
Local and sandbox activity is simulation only. Test payment labels, test rewards and successful software tests do not represent bank settlement, actual earnings or legal approval.
Operator review before publication
The described paid participation and five payer reward model requires specialist legal review before launch. In Canada, section 55.1 of the Competition Act prohibits certain recruitment compensation arrangements. A package label, consent or a disclaimer does not remove that risk. Keep real payments and recruitment for a paid launch disabled until the model and operating jurisdictions have been reviewed.
Complete the actual operator identity, permitted countries, package value, funding model, reward deadline, refund and failed allocation rules, complaint contact and legal review. These rules do not themselves authorize a live launch.
Reviewer reference Competition Act section 55.1 https://laws-lois.justice.gc.ca/eng/acts/C-34/section-55.1.html