Kaya Sync

Appearance

Partner Organisation Journey ​

Role: Institutional data-consumer with controlled access to aggregated Kaya Sync 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, with access scope explicitly defined
  • Account provisioned by System Admin
  • Receives data via periodic scheduled exports (daily or weekly); no real-time access by default

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: Permitted Data ​

Partner Organisation exports may include only the following:

  • Aggregated corridor performance reports — order volumes, delivery rates, SLA compliance by corridor
  • Verified activity summaries — confirmed delivery counts, custody transfer counts
  • Operator performance summaries — anonymised by default; identified only if explicitly agreed
  • Finance-readiness indicators — delivery verification status for use in trade finance processes
  • ESG and carbon impact data — aggregation plays executed, kgCO₂e saved, corridor benchmarking (if M11 enabled)
  • Contract-defined scheduled exports — any additional fields explicitly named in the partnership agreement

Step 2.3: Data That Is Never Accessible ​

Regardless of agreement scope, the following are not available to Partner Organisations:

  • Raw personal data (operator or designee PII beyond what the agreement explicitly names)
  • Fraud detection logic or fraud flag reason codes
  • Integrity assessment thresholds or scoring rules
  • Settlement scoring algorithms or trust-tier calculation logic
  • Unrestricted evidence bundles (raw video scans)
  • Proprietary orchestration and optimisation logic

Step 2.4: Data Format ​

  • Structured JSON or CSV
  • Schema versioned; Partner Organisation is notified of schema changes in advance

3. On-Demand Query (if enabled) ​

Depending on the partnership agreement, a Partner Organisation may have on-demand portal access to query specific containers or orders explicitly named in the agreement. This is scoped to identifiers agreed in advance — no open corridor-wide or unscoped queries.

If on-demand query is enabled:

  • Query by specific container ID or order ID only
  • View custody chain summary for that shipment
  • Download evidence summary (not raw video) for financing or audit purposes

Common Use Cases ​

Financier / DFI ​

  • Uses custody chain summaries and delivery verification indicators as proof-of-delivery for trade finance
  • Carbon impact data for climate finance reporting

Bank ​

  • Operator performance summaries and finance-readiness indicators for credit scoring
  • ESG reporting on corridor efficiency

ESG Reporting Body ​

  • Carbon impact ledger exports for emissions reporting
  • Corridor benchmarking data

Edge Cases ​

ScenarioBehaviour
Partner queries data outside their scopeAccess denied; returns empty result
Export contains fields beyond agreementFields suppressed at export layer before delivery
Partner reports missing data in exportSystem Admin investigates export job; redelivery triggered if confirmed missing
Partnership agreement updated (scope expanded)System Admin updates scope; next scheduled export reflects new scope

Kaya Sync Internal Documentation