Defining Tiers & Usage Modes

In FX402, tiers and modes define what users pay for and what they can do after payment.
Together, they form the backbone of the R402 payment model.

🧩 1. What Is a Tier?

A tier is a named pricing option specifying how long access lasts and how much it costs.

Example Tier


{
  "id": "7d",
  "label": "1 Week Access",
  "duration_seconds": 604800,
  "price": {
    "amount": "2.00",
    "currency": "USDC",
    "chain": "solana"
  }
}

Field	Type	Description
`id`	string	Unique key for this tier (e.g., `1d`, `7d`, `30d`).
`label`	string	Optional, human-readable label.
`duration_seconds`	number	How long access lasts, in seconds.
`price.amount`	string	Payment amount.
`price.currency`	string	The currency (e.g., USDC, SOL).
`price.chain`	string	Blockchain used for settlement.

⚙️ 2. Recommended Tier Patterns

Here are common tier setups:

Tier	Duration (seconds)	Ideal For
1d	86,400	Trials, demo access
7d	604,800	Short-term licenses
30d	2,592,000	Monthly subscriptions
90d	7,776,000	Long-term/enterprise use

🧠 3. Usage Modes

Usage modes describe what renters can do with a resource.


"modes": ["view", "remix", "commercial-lite"]

Mode	Description
`view`	Read-only access; user may view or consume
`remix`	Allows modification, reuse, or derivative works
`commercial-lite`	Limited commercial use (e.g., social media sharing)
`download` (opt)	Allows file download or local caching

Developers can define custom modes, as long as they’re clear and JSON-compatible.

🔗 4. Combining Tiers & Modes

Both can be included in a single R402 usage block:


{
  "usage": {
    "tiers": [
      { "id": "1d", "price": { "amount": "0.25", "currency": "USDC" } },
      { "id": "7d", "price": { "amount": "1.00", "currency": "USDC" } }
    ],
    "modes": ["view", "remix"]
  }
}

🧰 5. Design Tips

Keep tiers simple and predictable.
Prefer fewer tiers (1–3) for clarity.
Avoid fractional durations (e.g., 1.5d).
Label your modes clearly—they’re human-readable.

📚 Next Steps

Issuing & Verifying Receipts →