> For the complete documentation index, see [llms.txt](https://docs.nfh.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfh.global/use-cases/cross-border-commerce.md). # Cross-border commerce Federated commerce across borders without the card-network chain. A seller in one country, a buyer in another. Today the payment threads through a card network, an FX intermediary, and a payout provider — three to five days to settle, a fee at every hop, and compliance (KYC, sanctions, tax status) re-collected by each party in the chain. The smaller the seller, the worse the terms, and often the deal simply doesn't happen. On NFH fabric, the two participants — or their regulated [tokenisation](https://docs.finternetlab.io/) instances — **federate directly**. Value settles in seconds under a shared protocol, FX becomes a decision between two instances rather than a multi-fee chain, and compliance travels forward as signed [credentials](/product-documentation/products/vc-on-edge.md) instead of being re-collected at each border. ## What changes * **Settlement goes from days to seconds** — the two instances commit atomically instead of waiting on a correspondent chain. * **FX becomes a protocol-level decision** between two instances, not a stack of intermediary spreads and fees. * **Compliance moves from re-onboarding to credential verification** — KYC/KYB and sanctions status are proven, not re-gathered. * **Smaller sellers reach foreign demand** without acquiring foreign payment partners or a local entity. * **Disputes and refunds are protocol-native** — resolved against a signed, replayable record rather than a card-network chargeback process. ## Where to start Pair up with one counterparty on another regulated tokenisation instance and federate against the sandbox first, then production. Model the compliance-on-credential flow early — it usually drives the longest design conversation, so agree the credential schemas (KYC, sanctions, tax) with both sides' compliance teams before wiring settlement. --- # 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://docs.nfh.global/use-cases/cross-border-commerce.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.