Not an account. A view into the same fictional network, limited to what Metro Cash Center 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.
Metro Cash Center may send
Metro Cash Center → XYZ Bank
Permitted
- Permitted: Preparation timing exception
- 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: Vault inventory
- Not permitted: Physical-security information
- Not permitted: Other customers' orders
- Not permitted: Staffing
Reverse direction configured separately: XYZ Bank may send 1 category back.
Metro Cash Center may receive
- XYZ Bank
Cash order changed
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.