Payment Models

Tangle supports three pricing models at the blueprint level. The model determines when the customer pays; the protocol’s payment split determines who receives fees.

Pay Once (Upfront at Service Creation)

For PayOnce services, the customer pays once when the service is created. The protocol immediately splits and routes the payment:

• Developer share (blueprint owner, or manager override)
• Protocol share (treasury)
• Operator share (accrues as pending rewards)
• Restaker share (routed to ServiceFeeDistributor when configured)

Subscription (Escrow + Periodic Billing)

For Subscription services, the customer funds an on-chain escrow and the service is billed in intervals. Anyone can trigger billing; the recipients are naturally incentivized to keep billing moving.

Operational notes:

• Escrow must stay above the per-interval subscriptionRate to avoid billing failures.
• TTL (if set) gates billing once a service is expired.

Event Driven (Per Job / Event)

For EventDriven services, the protocol collects a fixed per-job fee during job submission.

Customer Guidance

• Use PayOnce when you want a simple “pay upfront for TTL” model.
• Use Subscription when you want predictable billing over time and the ability to top up.
• Use EventDriven when payment should scale with usage (each job/event).

Related

• Rewards & Incentives
• Blueprint Pricing (RFQ)