> For the complete documentation index, see [llms.txt](https://docs.keeta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeta.com/anchors/example-cross-border-payroll.md).

# Example: Cross-Border Payroll

Let’s break down how a U.S.-based company can use the Keeta anchor system to pay EU-based contractors in euros, leveraging both fiat and FX anchors. This illustrates instant, compliant, and cost-efficient global payroll without relying on legacy banking settlement delays.

**FLOW IMAGE COMES HERE**

## Key Benefits

* **Sub-second settlement:** No multi-day payment delays.
* **Unified compliance:** All regulatory requirements (KYC/AML, sanctions) are enforced at protocol level.
* **Cost-efficiency:** Eliminates intermediary fees and reduces FX markup.
* **Transparency:** Real-time on-chain audit trails for all steps.

This process allows a business to pay international employees or contractors with the speed and certainty of sending a domestic instant payment—combining traditional bank rails with the transparency and programmability of a fast, interoperable blockchain network.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeta.com/anchors/example-cross-border-payroll.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.