Not an account. A view into the same fictional network, limited to what CIT Company 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.
CIT Company may send
CIT Company → XYZ Bank
Permitted
- Permitted: Service cannot be accommodated as requested
- Permitted: Service requirement changed
- 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 credentials and procedures
- Not permitted: Other customers' activity
Reverse direction configured separately: XYZ Bank may send 4 categories back.
CIT Company → ABC Retail
Permitted
- Permitted: Service requirement changed
- 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 credentials and procedures
- Not permitted: Other customers' activity
Reverse direction configured separately: ABC Retail may send 4 categories back.
CIT Company may receive
- XYZ Bank
Potential replenishment requirement · Service requirement changed · Device unavailable · Scheduled service may no longer be required
Never includes: exact cash balance, transaction history, customer / card information, forecasting model internals.
- ABC Retail
Earlier pickup requested · Skip or reschedule service · Service requirement changed · Device unavailable
Never includes: store cash positions, sales data, smart-safe contents, store security arrangements.
- Regional Credit Union
Potential replenishment requirement · Device unavailable · Scheduled service may no longer be required
Never includes: exact cash balance, transaction history, member 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.