Not an account. A view into the same fictional network, limited to what Internal Cash Fleet 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.
Internal Cash Fleet may send
Internal Cash Fleet → XYZ Bank
Permitted
- Permitted: Scheduled service may no longer be required
- Permitted: Service cannot be accommodated as requested
- Permitted: Asset identifier or token
- Permitted: Priority
- Permitted: Need-by time
- Permitted: Decision deadline
- Permitted: Confidence band where relevant
Not permitted
- Not permitted: Route information
- Not permitted: Crew information
- Not permitted: Security procedures
- Not permitted: Vehicle schedules
Reverse direction configured separately: XYZ Bank may send 3 categories back.
Internal Cash Fleet may receive
- XYZ Bank
Potential replenishment requirement · Service requirement changed · Device unavailable
Never includes: exact cash balance, transaction history, customer / card information, forecasting model internals.
This interactive environment demonstrates the proposed EXCORA workflow. Organizations, events, responses and outcomes shown here are fictional and do not represent production deployments.