DFTP Institutional Trade Finance
Service Origination

Create logistics card

Publish a logistics card with route scope, lane coverage, evidence capabilities, operating SLA, and document standards.

Role: Logistics provider Output: Logistics service card Flow: Draft -> ops review -> publish Required: Route + evidence design
Back to logistics cabinet View logistics offers
Service profile

Route and service setup

Define the logistics card that can be attached to a deal.

$
Operational card can be published once evidence requirements are complete.
Required attachments

Operational documents to attach

Route evidence sample pack

Sample BoL, airway bill, POD, or customs release records.

Pending
No file attached yet.
Milestone and telemetry map

Event structure, publish timing, fallback logic, and API / IoT description.

Pending
No file attached yet.
Accreditation and liability pack

Carrier accreditation, subcontractor controls, SOP, and liability cover.

Pending
No file attached yet.
Platform requirements

What DFTP expects

  • Named milestones that can support payout or hold triggers.
  • Evidence publication timing and fallback workflow.
  • Customs and warehouse visibility if route uses bonded handling.
  • Clear counterparty contacts for exporter, insurer, and ops.
Publication notes

Recommended visibility

  • Open marketplace for common lanes and sectors.
  • Private publication for strategic routes or special cargo.
  • Invite-only for routes with custom telemetry or insurance integration.