Not an account. A view into the same fictional network, limited to what Regional Credit Union would be authorized to see. Illustrative Product Concept.
Fictional example permissions · not a production configuration
Permission is bilateral and purpose-specific. Each direction of a relationship is configured separately, and the originating organization decides which signal categories may go to which counterparty, for which purpose. Everything else stays with the organization that holds it.
Regional Credit Union may send
Regional Credit Union → CIT Company
Permitted
- Permitted: Potential replenishment requirement
- Permitted: Device unavailable
- Permitted: Scheduled service may no longer be required
- Permitted: Asset identifier or token
- Permitted: Priority
- Permitted: Need-by time
- Permitted: Decision deadline
- Permitted: Confidence band where relevant
Not permitted
- Not permitted: Exact cash balance
- Not permitted: Transaction history
- Not permitted: Member information
- Not permitted: Forecasting model internals
No reverse permission: CIT Company cannot send signals to Regional Credit Union in this example.
This interactive environment demonstrates the proposed EXCORA workflow. Organizations, events, responses and outcomes shown here are fictional and do not represent production deployments.