Checkout and Cache

Goal

Manage checkout sessions safely when Pay API access may be partial or intermittent.

Sequence

1. Preview a new session

peer checkout create --amount 100 --description "Order 123" --recipient 0x1111111111111111111111111111111111111111

2. Execute when confirmed

peer checkout create --amount 100 --description "Order 123" --recipient 0x1111111111111111111111111111111111111111 --yes

3. Inspect the resulting session

peer checkout show --session-id order_123
peer checkout list --status pending

4. Cancel if required

peer checkout cancel --session-id order_123
peer checkout cancel --session-id order_123 --yes

Cache-Aware Behavior

Checkout reads can fall back to ~/.peer/checkout-sessions.json.

That means:

• list and show may still be useful without fresh API access
• cached status aliases still normalize pending and completed
• local reconciliation is possible after interrupted runs

Agent Guidance

• Prefer a fresh API-backed show when credentials are available.
• Use the cache for recovery and operator continuity, not as the only source of truth for long-lived workflows.