> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/how-spv-supports-legal-compliance-in-blockchain-technology/real-world-compliance-applications/customs-and-import-export-compliance.md). # Customs and Import/Export Compliance International trade involves extensive compliance documentation for customs authorities. **Commercial invoices**, **bills of lading**, **certificates of origin**, and **import declarations** must all be maintained and presented to customs authorities. Historically, these documents exist in paper form or siloed digital systems, making verification time-consuming and fraud detection difficult. Blockchain-based trade documentation with SPV verification creates **tamper-evident trade records** that customs authorities can verify independently. A shipment from Country A to Country B generates blockchain transactions for each compliance document. SPV proofs demonstrate that documents existed at specific times (important for establishing regulatory compliance timeline) and haven't been altered (critical for fraud prevention). Customs authorities benefit from **instant document verification**. Rather than manually checking paper documentation or calling exporters to verify document authenticity, customs officials can verify SPV proofs in seconds. The blockchain timestamp proves when documents were created (detecting backdated documentation), and the Merkle proof structure ensures documents haven't been modified after creation. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/how-spv-supports-legal-compliance-in-blockchain-technology/real-world-compliance-applications/customs-and-import-export-compliance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.