An approved H200-class export license does not lapse when the Department of Defense later designates the Chinese customer under Section 1260H, and the designation by itself does not bar the export. Its legal effect runs instead through the certificate that paragraph (dd)(1)(iv) of Supplement No. 2 to part 748 requires, which confirms that the chips are not for a 'military end user' as 15 CFR 744.21(g) defines the term. Paragraph (dd)(2) has the applicant submit that certificate through SNAP-R before export. For any shipment still pending when DoD published its June list, the designation arrived before export, either before the certificate was signed or while a filed certificate remained in effect.
Section 1260H and the EAR ask different things, so the designation does not settle what the certificate may say. Section 1260H(g) reaches entities owned by, controlled by or "affiliated with" the People's Liberation Army, MIIT, SASAC and related bodies, and separately reaches "military-civil fusion" contributors. The EAR definition turns on function. Beyond armed services, police and intelligence bodies, it covers "any person or entity whose actions or functions are intended to support" the military end uses in 744.21(f), which are tied to USML, "A018" and "600 series" items. If DoD's stated bases show that a customer's functions support such an end use, a certificate saying otherwise would be false, and 15 CFR 764.2(g) prohibits a false certification or the concealment of a material fact. Section 750.7(a)(2) treats a license obtained through a false or misleading representation as void from issuance.
For an export compliance lead holding such a license, the choice is to certify and ship, hold, or take the matter to BIS, and the pre-export certification record for each designated end user decides which. Licensing data released by the House Foreign Affairs Committee on November 19 show approvals for customers in four corporate groups now tied to the 1260H list, Alibaba, Baidu, BYD and Tencent. Tencent was already listed when BIS approved its licenses, and the other three were designated afterward. On the same day, a new BIS rule on data center access added a separate license requirement that can reach the same shipments, and the rule leaves open how it applies to licenses already approved.
Four corporate groups, two designation dates
A BIS status table the committee released marks 21 license applications "Approved, not shipped" as of May 11, 2026, and the committee's two-page summary puts those approvals at 879,868 Nvidia H200 and AMD MI325X chips. The summary rests on the national-interest determination in 50 U.S.C. 4820(h)(2)(B), which an earlier analysis of how committees obtain and release BIS license records explains, and Ranking Member Meeks's release says the committee approved the disclosure by unanimous consent.
Tencent approvals total 150,000 chips, split between Nvidia's application for Tencent Technology (Shenzhen) and AMD's for Oriental Power Holdings, which the table calls a wholly owned Tencent subsidiary. Approvals for Alibaba Group cover 75,000 chips, Baidu 43,000 and BYD 4,000.
Tencent Holdings was already on DoD's January 2025 list, so BIS approved those licenses with the designation in place. Alibaba Group Holding, Baidu and BYD first appear in DoD's June 2026 Section 1260H notice, published June 10, after all of their approvals were recorded. That notice describes Alibaba and Baidu as indirectly affiliated with SASAC and as military-civil fusion contributors through MIIT. BYD is tied to SASAC, MIIT and a military-civil fusion enterprise zone, and Tencent to indirect affiliation with the PLA.
The record has gaps. It gives no approval dates and no status after May 11, and it does not show whether an applicant filed the (dd) certificate with the application or only committed to file it before export, as the paragraph (dd) lead-in permits. The 3,444,160-chip applications total counts companies located in China, headquartered there or with an ultimate parent headquartered there, so it includes rows in Malaysia, Thailand and Indonesia. Those rows and four China rows carry an "RWA" status the table never defines, while all 21 approved rows are in China.
How the 1260H test differs from the EAR test
| Element | Section 1260H designation | EAR 'military end user' test |
|---|
| Legal source | Section 1260H of the FY2021 NDAA, 10 U.S.C. 113 note, and DoD Federal Register notices | 15 CFR 744.21(f) and (g), applied to H200-class licenses through Supplement No. 2 to part 748, paragraph (dd)(1)(iv) |
| What the test asks | Ownership, control, agency or affiliation with the PLA, MIIT, SASAC and related bodies, or military-civil fusion contribution | Whether the entity is an armed service, police or intelligence body, or acts or functions to support USML, "A018" or "600 series" military end uses |
| Who decides | DoD, by designation and removal notice | The applicant certifies before export, and BIS may verify, revise, suspend or revoke |
| Effect on an approved, unshipped H200 license | No EAR license condition by its own force, and its stated bases are evidence the certificate file should address | A false certificate is prohibited and may be read as voiding the license under 750.7(a)(2) |
Section 1260H designation compared with the EAR 'military end user' test, as of November 19, 2026, drawn from the cited DoD notices, statute and eCFR text, which the November 19 BIS rule did not amend on these points.
Title 15 of the eCFR, searched as of November 17, 2026, contains no reference to Section 1260H and names none of the four firms on the Entity List or the Military End-User List, the same separation a June analysis of the 1260H list and export-control listings found. The November 19 rule is equally silent on Section 1260H. That absence does not clear the certificate, because Note 1 to 744.21(a) leaves exporters responsible for deciding whether an entity is a 'military end user' even without notice from BIS. The designation's direct legal effect lies in Pentagon contracting, where section 805 of the FY2024 NDAA barred new DoD contracts with listed entities and those they control from June 30, 2026, with a wider bar on contracts that include their goods or services from June 30, 2027.
A second license question from the November 19 rule
BIS's interim final rule on remote access to advanced semiconductors, effective November 19, 2026, adds 15 CFR 744.24, a requirement that can reach chips after delivery. It requires a license "in addition to the license requirements set forth elsewhere in the EAR" when an exporter knows that 3A090 chips are bound for a data center providing, or set to provide, more than 12,000,000 aggregate TPP to companies headquartered, or with an ultimate parent headquartered, in Macau or an arms-embargoed destination such as China. A data center that declines or is unable to provide its know-your-customer information raises a red flag that presumptively supplies that knowledge unless the exporter resolves it.
The rule's savings clause covers only shipments en route that lose license exception or no-license eligibility, and 744.24(b)(3) gives data centers already serving such companies 90 days to obtain a license. Neither addresses licenses BIS approved earlier under 742.6, so it is unsettled whether those approvals also satisfy 744.24 for data centers serving these four groups. An exporter can raise that point in the same request to BIS that covers the certificate.
Building the certification file for each designated customer
To certify and ship, the file should describe what the consignee and its listed parent do, explain why none of those functions is intended to support a 744.21(f) military end use, and answer each basis DoD stated rather than set the notice aside. Tencent's file has an extra layer, because DoD lists Tencent Holdings while the license parties are subsidiaries. Section 1260H(g)(2)(C) brings wholly owned subsidiaries such as Oriental Power within the statutory definition, though DoD has not listed either subsidiary by name, so the file should answer the parent's listing directly. Paragraph (dd)(1)(iv) also bars remote access by any 'military end user', which makes a consignee-only file incomplete. The volume and testing terms of BIS's January 2026 H200 review rule still apply, as the earlier analysis of H200 license market access explains.
Holding is the defensible course when the file cannot separate a DoD finding, such as Tencent's stated PLA affiliation, from the consignee's own functions. An applicant that certified or committed before the June notice also has a reporting duty to weigh. Section 764.2(g)(2) treats every representation and certification as continuing in effect and requires immediate written notice to BIS of information that would lead a reasonably prudent person to know a material fact has changed. A designation published after the representation may be read as that kind of information, and the notice can carry a request for guidance on both the certificate and 744.24.
Applying the void-license rule to a certificate filed after approval rests on interpretation. Section 750.7(a)(2) speaks of a license "obtained" with a false representation in any document submitted in connection with the application. Because paragraph (dd) makes the certificate part of the application or a commitment to it, the rule may be read as reaching a certificate filed through SNAP-R after approval. Neither paragraph (dd) nor the November 19 rule addresses the point.
BIS and DoD moves that would change the certificate analysis
A BIS revision, suspension or revocation under 15 CFR 750.8(a) would decide the matter for the affected license. Adding any of the four to the Entity List or the Military End-User List would make the (dd)(1)(iv) certificate impossible to give as written. A Military End-User List entry would also bring the presumption of denial in 744.21(e)(3) to new applications, while an Entity List entry would carry its own stated review policy. BIS guidance on 1260H findings under paragraph (dd)(1)(iv), or on whether earlier 742.6 licenses satisfy 744.24, would replace this reading with the agency's own.
On the DoD side, the November 2026 removal of WuXi AppTec, made to comply with a federal district court's preliminary injunction and without prejudice to relisting, shows how a court ruling or removal could take a basis out of the file. The FY2026 NDAA also rewrites the ownership, control and affiliation prong of the Section 1260H definition from December 18, 2026, adding the words "whether operating inside or outside of China" in a section aimed at circumvention through third countries, which could change how DoD states future bases.