feature request: user rebate when service/provider fails the SLA (escrow & slashing)

In many real-world use cases, clients want to go beyond simply paying for fulfilled services — they also expect compensation or rebates when service quality is degraded or when SLAs are not met, despite an agreed deal.

To support this, we should explore whether the FWS payment system can be extended in the future to include:

- Optional escrow deposits from the service provider (or creator) as part of the payment rail setup
- Automated slashing of the provider's escrow/or upon rail settlement if the service fails to meet its SLA
- Configurable rebate logic for slashed funds — e.g.:

- A portion is refunded to the client
- Some is retained by the creator
- Some may be burned

This allows more robust, trust-minimized outcomes for service users while incentivizing high-quality performance from providers.

👉 Note: This is not something we intend to build immediately, but we’d love to gather more use cases and signals from teams or applications that would benefit from this type of feature. Please comment or share your thoughts!

Start by reviewing the FWS payment system, payment rail setup, and rail settlement flow described in the issue. Gather concrete use cases and signals from teams or applications, then document whether escrow deposits, SLA-based slashing, and configurable rebate destinations should be pursued; the issue does not define an implementation-ready completion condition.

Written by the indexing model from the issue text.