Appearance
Partner Organisation Journey
Role: External organisation with scoped access to Kaya Sync audit and event data
Org: External (financier, DFI, bank, ESG reporting body, or business partner)
Scope: Configured per partnership agreement: typically a specific corridor, operator subset, or client org
Preconditions
- Partnership agreement signed with Kaya Sync
- Access scope defined in the agreement
- Account provisioned by System Admin
- Receives data via periodic scheduled exports (daily or weekly), no real-time access
1. Access & Authentication
Step 1.1: Login
- Partner Organisation representative logs in via email/password
- Access limited to the partner data portal
Step 1.2: Scope Confirmation
- On login, sees only data within the configured partnership scope
- Cannot query data outside their agreement
2. Receiving Periodic Exports
Step 2.1: Scheduled Export Delivery
- System automatically generates and delivers exports on the agreed schedule (daily or weekly)
- Delivery method: secure download link via email, or SFTP push (as configured)
Step 2.2: Export Contents (scoped to agreement)
Each export package includes:
- Custody chain summaries, condensed event trail for containers within scope
- Integrity outcome data, pass/hold/fail rates, reason code distributions
- Settlement data, payout statuses for covered operators (if included in agreement)
- Carbon impact data (if M11 enabled), aggregation plays executed, kgCO₂e saved, corridor benchmarking
- Operator-level summary, trust tier, compliance score, transaction volume (anonymised or identified per agreement)
Step 2.3: Data Format
- Structured JSON or CSV
- Schema versioned, Partner Org is notified of schema changes in advance
3. On-Demand Query (if enabled)
Depending on the partnership agreement, a Partner Org may also have on-demand portal access to:
- Query specific containers or orders by ID
- View custody chain for a specific shipment
- Download evidence bundles for financing or audit purposes
Common Use Cases
Financier / DFI
- Uses custody chain data and integrity outcomes as proof-of-delivery for trade finance
- Carbon impact data used for climate finance reporting
Bank
- Settlement data used to validate payment flows and operator earnings for credit scoring
- ESG reporting on corridor efficiency
ESG Reporting Body
- Carbon impact ledger exports for emissions reporting
- Corridor benchmarking data
Edge Cases
| Scenario | Behaviour |
|---|---|
| Partner queries data outside their scope | Access denied; returns empty result |
| Export contains sensitive PII beyond agreement | PII minimised at export layer, phone numbers masked per agreement terms |
| Partner reports missing data in export | System Admin investigates export job; redelivery triggered if confirmed missing |
| Partnership agreement updated (scope expanded) | System Admin updates scope; next scheduled export reflects new scope |