Proposed coverage framework
Say what can be confirmed—and what cannot.
Zilch is exploring capability classes that could distinguish documented paths, user-present fallbacks, and unsupported requests without implying universal coverage.
No biller, bank, provider, or payment method is currently supported or connected.
Capability classes
| Class | Meaning | Prototype status |
|---|---|---|
| Documented interface | A future documented interface could confirm required details and return defined states. | Future concept |
| Approved partner path | A future reviewed provider path could carry a bounded proposal. | Future concept |
| User-present hosted flow | A future disclosed flow could leave the final action with the user. | Future concept |
| User-present assistance | A future helper could organize information without hiding the final action. | Fallback concept |
| Unsupported | No verified path or sufficient reconciliation evidence is available. | Do not continue |
What a coverage claim would need
- A documented route and responsible owner
- Known inputs, limits, and failure states
- A tested approval and cancellation boundary
- Defined evidence for accepted, settled, and credited
- A public status that does not exceed the evidence
Synthetic example: Household internet · Maximum $126.40 USD · No provider, affiliation, account, or active coverage is implied.