> 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/cross-border-payments-and-multi-jurisdictional-compliance.md).

# Cross-Border Payments and Multi-Jurisdictional Compliance

**Proof of payment** becomes instantly verifiable across jurisdictions using SPV. A remittance service sending payments from Country A to Country B must satisfy compliance requirements in both jurisdictions. The sender's bank needs proof that funds were transferred. The recipient's bank needs verification of payment receipt. Regulators in both countries may require transaction records.

SPV solves this multi-jurisdictional complexity elegantly. The payment transaction, once included in a block, can be verified by all parties **using SPV proofs that reference the same public blockchain**. The sender's bank generates an SPV proof demonstrating payment. The recipient's bank independently verifies the proof. Regulators in both countries can verify the same proof against the blockchain. No party needs to trust another's record-keeping—the blockchain provides the **shared source of truth**, and SPV provides efficient verification.


---

# 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/cross-border-payments-and-multi-jurisdictional-compliance.md?ask=<question>&goal=<user_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.