Not an account. A view into the same fictional network, limited to what XYZ Bank 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.
XYZ Bank may send
XYZ Bank → CIT Company
Permitted
- Permitted: Potential replenishment requirement
- Permitted: Service requirement changed
- 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: Customer / card information
- Not permitted: Forecasting model internals
Reverse direction configured separately: CIT Company may send 2 categories back.
XYZ Bank → Metro Cash Center
Permitted
- Permitted: Cash order changed
- 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: Customer / card information
- Not permitted: Forecasting model internals
Reverse direction configured separately: Metro Cash Center may send 2 categories back.
XYZ Bank → Internal Cash Fleet
Permitted
- Permitted: Potential replenishment requirement
- Permitted: Service requirement changed
- Permitted: Device unavailable
- 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: Customer / card information
- Not permitted: Forecasting model internals
Reverse direction configured separately: Internal Cash Fleet may send 2 categories back.
XYZ Bank may receive
- CIT Company
Service cannot be accommodated as requested · Service requirement changed
Never includes: route information, crew information, security credentials and procedures, other customers' activity.
- Metro Cash Center
Preparation timing exception · Cash order changed
Never includes: vault inventory, physical-security information, other customers' orders, staffing.
- Example Technology Co.
Forecast exception · Device unavailable
Never includes: raw device telemetry, forecasting models, other clients' data.
- Internal Cash Fleet
Scheduled service may no longer be required · Service cannot be accommodated as requested
Never includes: route information, crew information, security procedures, vehicle schedules.
This interactive environment demonstrates the proposed EXCORA workflow. Organizations, events, responses and outcomes shown here are fictional and do not represent production deployments.