Select an eBL platform provider that has confirmed DCSA eBL 3.0 compliance and PINT API support; verify that both shipper and consignee banks accept the chosen platform for presentation.
Submit shipping instructions to the carrier via the DCSA Shipping Instructions API; the carrier issues the eBL on their platform and notifies you with the transport document reference.
To transfer the eBL to a consignee on a different platform, initiate a PINT transfer through the Platform Interoperability API; the PINT API routes the transfer via the Control Tracking Registry (CTR) to the receiving platform.
Confirm receipt and chain of custody by querying the CTR for the eBL transfer status; only the current holder can endorse or surrender the document.
For bank presentation, instruct the eBL platform to present the document to the nominated bank; the bank must be enrolled on a PINT-compatible platform to accept programmatic presentation.
On cargo delivery, surrender the eBL through the platform API to release the goods; the carrier marks the document as surrendered in the CTR, closing the document lifecycle.
Known gotchas
Paper B/L and eBL cannot be used simultaneously for the same shipment; switching from paper to eBL after issuance requires formal carrier consent and a new issuance process.
Not all Letter of Credit banks accept eBL for documentary credit presentation as of 2026; confirm bank acceptance before committing to eBL issuance on trade finance transactions.
PINT transfers require both source and destination platforms to be live PINT participants; attempting a transfer to a non-PINT platform will fail silently or return a platform-not-found error.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp