Skip to content

Write CBP Customs Bond Compliance FAQ Explaining Bonds, Collateral Requirements, and TariffShield's Role #299

Description

@vjuliaife

Description:
TariffShield's business value proposition depends on prospects and integrators understanding what a U.S. Customs and Border Protection (CBP) customs bond is, why importers are legally required to obtain one, and how TariffShield's collateral model differs from traditional surety bond arrangements. Without this context, technical evaluators cannot accurately assess compliance implications, and business stakeholders cannot communicate the product's value to customers.

Acceptance Criteria:

  • docs/compliance/cbp-customs-bond-faq.md created with a disclaimer that the document is informational and does not constitute legal or compliance advice
  • "What is a customs bond?" section explaining the three parties (importer/principal, surety company, CBP), the bond's legal purpose (guaranteeing duty payment), and the two types (single-entry and continuous)
  • "Who needs a customs bond?" section covering the CBP threshold ($2,500+ commercial shipments), the ISF bond requirement for ocean freight, and common importer exemptions
  • "How is bond amount calculated?" section explaining the standard CBP formula for continuous bonds (10% of total duties/taxes/fees paid in prior year, minimum $50,000), and how TariffShield's required collateral of annual_duty × 10% × 50% maps to this
  • "What happens if the bond is insufficient?" section explaining bond insufficiency notices, supplemental bonds, CBP enforcement, and how TariffShield's auto top-up feature mitigates this risk
  • "How does TariffShield differ from a traditional surety?" section contrasting paper-based surety bonds with TariffShield's on-chain collateral model, including settlement speed and transparency
  • "What data does CBP require?" section listing the data fields importers must provide (EIN, bond type, HTS codes, duty estimates) and mapping each to TariffShield's data model
  • FAQ answers written at a business-audience reading level (no smart contract jargon) with a "Technical details" callout box for developers linking to the relevant code sections

Relevant Files:

  • PITCH.md — market context and differentiation claims to align with
  • docs/compliance/cbp-customs-bond-faq.md — FAQ file to create
  • contracts/tariff-shield/src/lib.rs — collateral calculation logic (technical reference)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stellar WaveIssues in the Stellar wave programdocsAuto-created by repotool publish-folderdxDeveloper experience / docs / naming

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions