> 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/anchor-types/asset-movement/fiat-anchors.md). # Fiat Anchors Fiat Asset Movement Anchors provide on-ramps and off-ramps between traditional fiat currency systems and Keeta. They connect bank accounts, wire transfers, ACH, and other payment rails to Keeta tokens. ### **Benefits of Fiat Asset Movement Anchors** Fiat Asset Movement Anchors enable: * **Fiat On-Ramps**: Deposit USD, EUR, etc. from your bank to receive Keeta tokens * **Fiat Off-Ramps**: Withdraw Keeta tokens to receive fiat in your bank account * **Traditional Payment Compatibility**: Accept ACH, wires, SEPA, PIX, etc. * **Regulatory Compliance**: Anchors handle KYC/AML requirements * **Multiple Currencies**: Support for various fiat currencies and regions #### **Supported Rails** Common banking rails: * **ACH**: US bank transfers * **ACH\_DEBIT**: Pull funds from bank account * **WIRE**: Fast domestic wire transfers * **WIRE\_RECEIVE**: Incoming wire transfers * **WIRE\_INTL\_PUSH**: International wire transfers * **SEPA\_PUSH**: European bank transfers * **PIX\_PUSH**: Brazilian instant payments * **CLABE\_PUSH**: Mexican bank transfers * **SPEI\_PUSH**: Mexican electronic transfers ### KYC Requirements Most Fiat Anchors require KYC (Know Your Customer) verification to comply with anti-money laundering (AML) regulations. The Keeta Anchor SDK provides a powerful integration between KYC Anchors and Fiat Asset Movement Anchors that enables **on-chain KYC flows** where identity verification can be performed once and shared securely across multiple service providers. #### **How KYC and Fiat Anchors Work Together** The integration works through a three-step process: 1. **Verification with KYC Anchor**: Users complete identity verification with a KYC provider, submitting required documents and information 2. **Certificate Issuance**: The KYC provider issues cryptographically signed certificates that prove verification status 3. **Secure Sharing**: These certificates are securely shared with Fiat Anchors using [encrypted containers](/anchors/overview/encrypted-containers.md), allowing the Fiat Anchor to verify compliance without re-collecting sensitive documents This approach provides several key benefits: * **Single Verification**: Users verify their identity once and reuse certificates across multiple Anchors * **Privacy**: Personal documents remain with the KYC provider; Fiat Anchors only receive verification certificates * **Compliance**: Fiat Anchors can cryptographically verify that proper KYC has been performed * **Efficiency**: Eliminates redundant verification processes across different providers * **On-Chain Provenance**: KYC status can be verified on-chain through certificate signatures --- # 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.keeta.com/anchors/anchor-types/asset-movement/fiat-anchors.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.