Tajji Payments Policy

4. Payment Rails, Custody, and Ledger Semantics

4.1 Permitted Rails

Payment rails may include cards, bank transfers, mobile money, and other jurisdiction-permitted methods.

4.2 Rail Neutrality

Rail choice affects settlement mechanics only. Rail selection does not alter:

• principal attribution
• fund-class separation
• liability allocation
• containment semantics

4.3 Ledger Model

All payment events produce immutable ledger entries recording, at minimum:

• initiator
• payer-of-record
• beneficiary
• fund class
• obligation graph reference
• rail event status
• timestamp and idempotency key

4.4 Auditability

Given ledgers and event logs, Tajji must be able to deterministically reconstruct:

• balances by fund class
• attribution by principal
• settlement posture at each Evaluation Point

4.5 Settlement Finality and Rail Dependency

A payment marked as successful, completed, or settled within BomaOS or Jirani reflects the current reported state of the underlying payment rail only.

Tajji does not certify, guarantee, or warrant legal settlement finality unless and until such finality is confirmed by the relevant payment processor, clearing system, or financial institution.

Delayed settlement, reversal windows, processor clawbacks, or rail-level adjustments do not alter principal attribution, fund class classification, or obligation existence.

4.6 Processor Substitution, Outages, and Rail Failure Neutrality

Tajji may integrate with, substitute, or route through one or more payment processors or financial institutions as required for availability, compliance, or operational resilience.

Payment rail outages, processor unavailability, retry exhaustion, or intermediary failure:

• do not constitute a breach of this Policy
• do not trigger containment
• do not modify obligations or liability attribution
• do not imply any guarantee of payment completion by Tajji

5. Principal Attribution, Delegation, and Liability

5.1 Deterministic Attribution

Every payment is attributable to a determinable principal-of-record.

5.2 Delegation Boundary

Delegation does not:

• transfer principal-of-record
• pool exposure across principals
• permit cross-fund-class set-off

5.3 Operator-Paid Platform Fees

Where a Delegated Operator pays Platform Fees under Operator Payment Delegation:

• the Economic Principal remains liable
• containment attaches to the Economic Principal
• fiduciary funds remain untouched

6. Payment Flows (Cross-Platform)

6.1 Platform Fees (BomaOS)

• Initiator: Economic Principal or Delegated Operator
• Payer-of-record: Economic Principal
• Beneficiary: Tajji
• Fund class: Platform Fees
• Disputes: Billing disputes only

6.2 Rent Collection (Jirani → BomaOS)

• Initiator: Tenant (via Jirani)
• Payer: Tenant
• Beneficiary: Landlord
• Fund class: Rent Pass-Through

Tajji does not guarantee rent and does not act as a collection agent.

6.3 Deposits (if supported)

• Holding posture: Optional, consent-based
• Release: Per lease terms, dispute resolution, or lawful order
• Closure: Must fully unwind prior to termination

6.4 Maintenance Reserves (if supported)

• Authorization: Principal-scoped governance
• Spend: Evidence-grade approvals
• Separation: Never offset Platform Fees

6.5 Utility Pass-Throughs

• Accuracy: Supplied by third parties
• Tajji role: Facilitation, ledgering, and evidence capture only

6.6 Transient Occupancy Payments

• Existing occupancies are preserved under containment
• New transient creation is blocked under containment
• Yield execution is disabled under containment

7. Non-Payment and Financial Containment

7.1 Sole Remedy

Non-payment is addressed exclusively through state-based financial containment.

7.2 Evaluation Points

Containment transitions occur only at Evaluation Points. Failed attempts, pending states, customer intent, or elapsed time do not trigger containment.

7.3 State Effects

7.4 Notifications

Notification cadence provides transparency only. It does not function as an enforcement clock or grace period.

8. Disputes, Chargebacks, Fraud, and Legal Orders

8.1 Dispute Types

• Billing disputes
• Rent disputes
• Deposit disputes
• Maintenance spend disputes
• Identity disputes

8.2 Dispute Effects

• Dispute Lock applies
• Evidence is sealed
• Closure is blocked

8.3 Chargebacks and Reversals

• Logged as rail events
• Liability follows fund class and principal attribution
• Platform Fees are not refunded absent billing error

8.4 Fraud and Holds

• Freeze Mode may be imposed
• Exposure-increasing actions may be blocked
• Continuity is preserved where lawful

8.5 Court and Regulator Orders

Tajji complies with lawful orders without assuming agency or representation.

8.6 Fiduciary Duty Limitation (Non-Expansion)

Where Tajji processes or temporarily holds fiduciary funds under explicit, consent-based configurations, such handling is strictly mechanical and evidentiary.

Nothing in this Policy shall be interpreted to expand Tajji’s duties beyond those of an infrastructure operator, or to create fiduciary, trustee, escrow, or advisory obligations beyond fund-class-specific handling expressly described herein.

9. Refunds, No-Credits Posture, and Error Remedies

• No credits, stored value, or prepaid entitlements exist.
• ALs and CAs are non-refundable once accrued.
• Anchors are non-refundable except BomaOS breach.
• Permitted remedies are limited to billing correction and overpayment restitution.

10. Termination, Closure, and Record Survival

10.1 Conditional Closure

• obligations unwind
• Platform Fees settle
• disputes resolve
• fiduciary funds are lawfully handled

10.2 No Surviving Fees

Unpaid Platform Fees do not survive closure because closure cannot proceed unless cured.

10.3 Record Survival

• Ledgers are never destroyed
• Access is revoked
• Lawful anonymization applies where permitted

11. Auditability and Minimum Exports

Upon closure, Tajji provides:

• invoices and ledger summaries
• payment event logs
• dispute evidence indexes
• payout instruction history

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.