Hapag-Lloyd Leaves FMC-Filed GSBN Carrier Cooperation Agreement
🔔 Subscribe to ShipUniverse Weekly →
Hapag-Lloyd AG has resigned from the Federal Maritime Commission-filed Global Shipping Business Network Agreement, effective September 14, 2026, leaving COSCO Shipping Lines and OOCL as the agreement’s only remaining carrier parties. The September 22 Federal Register notice says Amendment No. 002 deletes Hapag-Lloyd and reflects its resignation, while the FMC’s current agreement history confirms the change. The amended agreement also provides an important additional detail: Article 9.2 states that a party may resign by terminating its ownership interest in GSBN under the GSBN Shareholders’ Agreement and filing the appropriate FMC amendment. That means the filing indicates Hapag-Lloyd’s resignation was tied to termination of that ownership interest, although the public documents do not disclose the transfer mechanics, counterparty or any continuing commercial arrangements. It would still be too broad to report that Hapag-Lloyd has simply “left GSBN.” Hapag-Lloyd’s current eBL page continues to offer IQAX, which it describes as operating on GSBN blockchain infrastructure, and GSBN documented a live Hapag-Lloyd eBL shipment through its connected infrastructure earlier this year.
Hapag-Lloyd exits the carrier cooperation agreement behind GSBN's U.S.-regulated framework
The filing reduces the agreement from three carrier parties to two. It does not establish that Hapag-Lloyd has stopped using technology or services operating over GSBN infrastructure.
How the carrier agreement narrowed from four parties to two
The agreement authorizes carrier cooperation around the GSBN digital platform, including data exchange, documents, APIs and electronic bills of lading.
Amendment No. 001 deletes CMA CGM as a party.
Amendment No. 002 deletes Hapag-Lloyd, leaving two carrier parties under the FMC-filed cooperative working agreement.
The agreement says a party may resign by terminating its ownership interest in GSBN under the GSBN Shareholders' Agreement and filing the corresponding FMC amendment. The FMC says Hapag-Lloyd resigned pursuant to Article 9.2.
The same agreement expressly distinguishes GSBN membership from subscriptions to the platform. Hapag-Lloyd also continues to publicly offer IQAX eBL, which its website describes as running on GSBN infrastructure.
What Changed, What Did Not, and What Remains Unclear
| Relationship | Before Sept. 14 | After Amendment No. 002 | Evidence | What Can Be Reported | Status |
|---|---|---|---|---|---|
| FMC Agreement Membership | Hapag-Lloyd was one of three carrier parties alongside COSCO and OOCL. | Hapag-Lloyd has been deleted. COSCO and OOCL remain. | FMC Agreement No. 201344-002 and September 22 Federal Register notice. | Hapag-Lloyd has resigned from the FMC-filed Global Shipping Business Network Agreement. | Confirmed |
| GSBN Ownership Interest | Hapag-Lloyd was historically identified as a GSBN shareholder. | The FMC agreement says resignation under Article 9.2 occurs by terminating the party's ownership interest under the GSBN Shareholders' Agreement. | Article 9.2 of the amended FMC agreement and FMC's statement that the resignation was made pursuant to Article 9.2. | The filing framework indicates Hapag-Lloyd's resignation was tied to termination of its ownership interest. | Changed |
| Ownership Transfer Details | Hapag-Lloyd was listed among GSBN's founding shareholders in 2021. | The public amendment does not identify who acquired or received any ownership interest, its value, or transaction terms. | No transfer mechanics are disclosed in Amendment No. 002. | The mechanics and financial terms of the ownership exit remain undisclosed. | Not Disclosed |
| IQAX eBL Availability | Hapag-Lloyd offered IQAX as an eBL option over GSBN infrastructure. | Hapag-Lloyd's current eBL webpage continues to list IQAX among its supported eBL partners. | Hapag-Lloyd's Electronic Bill of Lading product page. | There is current public evidence of continued Hapag-Lloyd support for a GSBN-connected technology workflow. | Still Listed |
| 2026 Live eBL Workflow | GSBN, ODeX and IQAX supported a Hapag-Lloyd shipment from Mundra to Chicago. | The shipment predates the September resignation, but demonstrates that GSBN infrastructure was actively used by a Hapag-Lloyd workflow in 2026. | GSBN announcement and September 8 Maritime Gateway report. | The regulatory resignation should not be described as proof that Hapag-Lloyd stopped using GSBN infrastructure. | Documented |
| GSBN Platform Subscription | Platform usage and FMC agreement membership are legally distinct concepts. | The filing does not state that all platform subscriptions or technology connections have ended. | Footnote 1 of the FMC agreement says subscriptions to the platform do not necessarily require amendment of the FMC agreement. | Do not equate departure from the FMC agreement with termination of every GSBN-connected service. | Separate Issue |
| Reason for Resignation | No reason stated in the prior agreement. | No commercial or strategic explanation appears in the amendment notice. | Federal Register and FMC amendment synopsis. | Motive should remain open unless Hapag-Lloyd or GSBN provides an explanation. | Unknown |
FMC membership, ownership in the GSBN joint venture and access to GSBN-connected products are related but distinct layers.
Article 9.2 expressly makes termination of the party's GSBN ownership interest part of the resignation mechanism used by Hapag-Lloyd.
GSBN Filing Claim Checker
Select a statement to see whether the September filing confirms it, supports it with qualifications, or leaves the question unresolved.
Hapag-Lloyd has left the FMC-filed carrier cooperation agreement.
Amendment No. 002 deletes Hapag-Lloyd AG as a party and the FMC specifically says the change reflects its resignation from the agreement.
FMC Agreement No. 201344-002, effective September 14, 2026, and the Federal Register notice published September 22.
“Hapag-Lloyd has resigned from the FMC-filed Global Shipping Business Network Agreement.”
We welcome your feedback, suggestions, corrections, and ideas for enhancements.
Please click here to get in touch