Tajji Payments Policy
Effective Date: February 2026
1. Purpose, Scope, and Constitutional Alignment
1.1 Purpose
This Payments Policy (the “Policy”) governs how payments, funds, ledgers, refunds, disputes, reversals, delegation, and enforcement operate across all Tajji platforms.
This Policy is a legal-operational instrument, not a pricing document. It does not introduce pricing, SKUs, tiers, or economic primitives. It implements payment-side procedure only.
1.2 Infrastructure Posture
Tajji provides payments functionality strictly as shared infrastructure.
Nothing in this Policy shall be interpreted to make Tajji a marketplace, broker, escrow agent, custodian, trustee, guarantor, insurer, tax agent, tax representative, withholding agent, collection agent, or market maker, except where expressly agreed in a separate written instrument executed by Tajji.
1.3 Binding Alignment
This Policy must be interpreted to implement, and never reinterpret, the following binding instruments:
- BomaOS Pricing Constitution (latest version)
- BomaOS Infrastructure Agreement (latest version)
Where conflict exists:
- The Pricing Constitution governs economic semantics (ALs, CAs, containment, refunds, closure).
- This Policy governs payment mechanics, fund handling, and ledger procedure only.
2. Definitions
2.1 Principals
Economic Principal
The party bearing ultimate financial responsibility for Platform Fees attributable to its obligation graphs.
Occupancy Principal
The party standing as obligor-of-record to an occupant under an Occupancy Relationship and bearing Active Lease
(AL) exposure.
Coordination Principal
The party whose authority initiates and controls coordination workflows and bears Coordination Action (CA) exposure.
2.2 Delegation
Delegated Operator (PMF / IPM)
An authorized operator acting under mandate without becoming a principal by implication.
Operator Payment Delegation
An explicit in-platform election authorizing a Delegated Operator to pay Platform Fees on behalf of an Economic
Principal.
Payment delegation alters payment facilitation only. It does not alter attribution, liability, containment attachment, or principal-of-record.
2.3 Fund Classes
- Platform Fees (owed to Tajji)
- Rent Pass-Through (tenant → landlord)
- Security Deposits (if supported)
- Maintenance Reserves (if supported)
- Utility / Third-Party Pass-Throughs
- Other expressly declared fiduciary funds
2.4 Governance and Enforcement
Evaluation Point (EP)
A formal, auditable checkpoint at which settlement status is resolved and containment transitions may occur.
Containment States
- GOOD_STANDING
- CONTAINED
- FINANCIAL_CONTAINMENT
Dispute Lock
A state preventing closure or irreversible ledger actions while a dispute is active.
Freeze Mode
A scoped restriction imposed due to fraud, court order, or regulator directive.
2.5 Payment Events
Billing Error
An incorrect charge due to duplication, miscalculation, or misattribution.
Overpayment Restitution
Return of excess funds resulting from a billing error. Restitution is not damages.
Chargeback / Reversal / Return
Rail-specific settlement events governed by payment processor rules.
3. Fund Classes and Fiduciary Separation
3.1 Absolute Separation
No set-off across fund classes is permitted under any condition.
3.2 Platform Fees
- Platform Fees are owed to Tajji.
- Platform Fees are independent of tenant payment behavior.
- Platform Fees are never satisfied from fiduciary funds.
3.3 Fiduciary Funds
- are not platform revenue
- are not pooled across principals
- are never used to satisfy Platform Fees
- remain attributable to the relevant principal-of-record
3.4 Custody Posture
By default, rent and pass-through funds are routed direct-to-beneficiary via permitted payment rails.
Where Tajji offers optional fiduciary holding (e.g., deposits or reserves), such holding:
- requires explicit consent
- is fund-class specific
- is governed by unwind, dispute, and closure rules
- must not survive the associated governed relationship
12. Edge Cases
- Partial payments do not cure Platform Fees unless expressly permitted.
- Overpayments are returned as restitution.
- Wrong beneficiary details are handled per rail rules without guarantee.
- Rail outages do not trigger containment.
- Reversals after closure request pause closure.
- Successions mid-dispute preserve Dispute Lock and evidence.