Activate real owner decisions, payment collection and paid confirmation

[zaingulel]

Parent

Public-launch activation for #33, #34 and #35, and launch-readiness evidence for #51.

What to build

Run the real owner decision, payment collection and paid-confirmation journey with the approved legal sequence, live notification supplier and licensed payment provider, preserving the domain behaviour proved in the pre-live stories.

Owner decision — 6 September 2026

Qi Card is the selected direction for payment validation and integration. #79 owns Qi product/capability validation and sandbox access; #45 owns the Qi integration. This selects the development direction, not production activation: licensing, sandbox proof, commercial terms and Cottage Owner settlement must still pass. ZainCash and AsiaPay are fallback research only if the owner reopens the choice. Existing booking rules and simulated-work acceptance criteria remain unchanged.

Acceptance criteria

• A real Cottage Owner receives the permitted live alert and can accept or decline the complete immutable request within the four-hour deadline.
• Decline, customer withdrawal and timeout release the real provider authorisation and inventory hold exactly once and notify both parties without exposing restricted contact details.
• Acceptance captures the exact Customer Total through the licensed provider and creates one Confirmed Booking only after authoritative capture success.
• Real pending, failed and recoverable capture outcomes enter the correct 20-minute recovery path without presenting an unpaid request as confirmed.
• Paid confirmation releases the exact address, directions and permitted mutual contact details only to the authorised customer and owner.
• Duplicate, delayed and out-of-order provider or notification events cannot duplicate money movement, bookings, inventory transitions or messages.
• Definitive provider release or corrective-refund failure enters a durable, support-actionable quarantine without releasing held inventory, retrying automatically forever or reporting a safe terminal outcome.
• Authorised support can reconstruct the ordered, redacted capture and recovery history across multiple attempts, including authoritative provider occurrence time separately from RentCottage receipt time.
• Production-like end-to-end evidence covers success, decline, withdrawal, timeout, recovery success and recovery expiry against the exact release candidate.
• The journey fails closed if approved legal content, provider capability, credentials, callbacks, reconciliation or notification delivery is not ready.

Blocked by

• Let the owner decide and release unsuccessful requests #33
• Capture payment and recover safely for 20 minutes #34
• Confirm a paid booking and release access details #35
• Integrate Qi payments after capability and sandbox validation #45
• Integrate Iraqi phone verification and booking notifications #47
• Install approved legal content and enforce immutable acceptance #119