> ## Documentation Index > Fetch the complete documentation index at: https://developers.circle.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Before reading these docs, install the relevant Circle Skill to get pre-loaded context — skills are LLM-optimized and cover architecture decisions, correct flows, and common pitfalls. In Claude Code: run /plugin marketplace add circlefin/skills then /plugin install circle-skills@circle. With Vercel Skills CLI: run npx skills add circlefin/skills. Available skills: use-usdc https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-usdc/SKILL.md (balances, transfers, approvals on EVM and Solana); EURC has no skill — see https://developers.circle.com/stablecoins/what-is-eurc.md; bridge-stablecoin https://github.com/circlefin/skills/blob/master/plugins/circle/skills/bridge-stablecoin/SKILL.md (crosschain transfers via CCTP, USDC, EURC, and third-party assets); use-arc https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-arc/SKILL.md (Arc chain config, contract deployment, USDC bridging — Arc docs: https://docs.arc.io/llms.txt); use-circle-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-circle-wallets/SKILL.md (choose wallet type); use-developer-controlled-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-developer-controlled-wallets/SKILL.md (custodial wallets for payouts and treasury); use-user-controlled-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-user-controlled-wallets/SKILL.md (embedded wallets with Web2 login); use-modular-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-modular-wallets/SKILL.md (smart contract wallets with passkeys and ERC-4337); use-gateway https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-gateway/SKILL.md (unified USDC balance, nanopayments); use-smart-contract-platform https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-smart-contract-platform/SKILL.md (deploy, interact, monitor contracts). Pair any skill with the Circle MCP server for live SDK signatures, contract addresses, and chain IDs: {"mcpServers":{"circle":{"url":"https://api.circle.com/v1/codegen/mcp"}}}. > Read the product overview first. Each product has an overview explaining when and why to use it. Read it before quickstarts. > Pick the right wallet type. Developer-controlled (you hold keys), user-controlled (end user holds keys via PIN/social login), or modular (smart contract wallets with passkeys). See https://developers.circle.com/wallets.md. > Use CCTP V2 for crosschain transfers. CCTP natively transfers USDC and EURC via burn-and-mint, and supports permissionless wrapping of third-party assets via lock-and-mint. V1 is legacy; always use V2 unless V1 is specified or the chain requires it (Noble, Sui, and Aptos still require V1). Migration guide: https://developers.circle.com/cctp/migration-from-v1-to-v2.md. > Use Bridge Kit for frontend bridging. Wraps CCTP with a simpler SDK for user-facing apps. Use CCTP directly for backend transfers. > Gas Station vs Paymaster. Gas Station sponsors gas for Circle Wallet transactions. Paymaster lets users pay gas in USDC. Different use cases — read both overviews. > Gateway Nanopayments for sub-cent payments. Gasless USDC micropayments down to $0.000001 via x402 and batched settlement. For pay-per-request APIs, AI agent payments, streaming. > Look up USDC addresses per chain. Never hardcode — use https://developers.circle.com/stablecoins/usdc-contract-addresses.md. > Prefer SDKs over raw API calls. Node.js and Python SDKs handle auth, retries, and errors. > API key required. Bearer token in Authorization header. Testnet and mainnet use separate keys and may use different base URLs depending on the product. > Set up webhooks when available. Most operations are async. Webhooks deliver transaction confirmations and state changes. > When calling list endpoints, paginate using pageSize and pageAfter until no nextPageAfter cursor is returned—stopping at the first page silently misses records. > Building an AI agent? Start with the Agent Stack—Circle CLI, agent wallets, and nanopayments built for autonomous use cases: https://developers.circle.com/agent-stack.md. # Compliance obligations > Regulatory and contractual obligations for Digital Asset Accounts distributors. Digital Asset Accounts (DAA) operates under a B2B2C model in which Circle is the licensed money transmitter and you are responsible for delivering compliance artifacts to your end users. Your obligations come from your Definitive Agreement with Circle and from the money transmission regulations Circle operates under, including its money transmitter licenses and the New York BitLicense. Circle generates the required artifacts and returns them to you through the API and the corresponding webhook events. You render and deliver them. ## Receipts | Circle's obligation | Your obligation | | - | - | | Returns receipt content on the API response and the corresponding webhook event. | Render and deliver the receipt to the end user at transaction completion. | Send a receipt when each transaction reaches its final state: a deposit is credited, a withdrawal settles, or an onchain transfer confirms. For the full implementation reference, including required data elements, field mappings by transaction type, and required footer text, see [Receipts and disclosures](/digital-asset-accounts/references/receipts-and-disclosures). ## Disclosures | Circle's obligation | Your obligation | | - | - | | Provides approved disclosure text and terms and conditions. | Present disclosures before account opening or each transaction; capture affirmative consent. | For implementation requirements, including the terms and conditions consent flow and per-transaction disclosure elements, see [Receipts and disclosures](/digital-asset-accounts/references/receipts-and-disclosures). ## Account limits | Circle's obligation | Your obligation | | - | - | | Publishes per-transaction, daily, and monthly limits. | Display limits and block submissions that exceed them. | Display account limits before the end user initiates a deposit or withdrawal so they can't submit amounts that exceed their limit. Reversals caused by submissions that exceed the limit harm the user experience and create operational overhead. * Display Circle's published per-transaction, daily, and monthly limits on your deposit and withdrawal screens. * Show the end user's current balance before they initiate a withdrawal. * Block submission when the entered amount exceeds the applicable limit. ## Regulated customer notices | Circle's obligation | Your obligation | | - | - | | Emits webhook events when account state changes. | Notify end users with the required content and timing. | For the full list of notice triggers, required content, and timing requirements, see [Regulated customer notices](/digital-asset-accounts/references/compliance-obligations/regulated-customer-notices). ## Record retention | Circle's obligation | Your obligation | | - | - | | Retains KYC and transaction records at the platform level. | Retain consent, receipt delivery, and customer communication records. | For the full list of record types, retention periods, and audit requirements, see [Record retention](/digital-asset-accounts/references/compliance-obligations/record-retention). ## Account statements | Circle's obligation | Your obligation | | - | - | | Doesn't require periodic statements. | Issue if required by applicable law or your product offering. | If you elect to issue statements, or if applicable law requires them for certain account types or jurisdictions, include the following fields on each statement: * The statement period (start and end date). * The opening and closing balance. * Each transaction with its date, type (deposit, withdrawal, or transfer), amount, fee, net amount, and reference. * Dispute contact information and process. * Circle's regulatory status and license information. ## Implementation checklist | Circle's obligation | Your obligation | | - | - | | Provides the APIs, webhooks, and compliance artifacts that enable each item. | Wire each item into your product before enabling live transactions. | Before you enable live transactions for any end user, confirm the following: * Wire deposit receipt is rendered and delivered on deposit completion. * Bank withdrawal receipt is rendered and delivered on withdrawal completion. * Onchain transfer receipt is rendered and delivered on confirmation. * The Digital Asset Account User Agreement is surfaced and explicit consent is captured before account opening. * Pre-transaction disclosures (fee, settlement time, irrevocability) are shown before each transaction. * Account approval, restriction, closure, and withdrawal return notices are wired to the corresponding webhook events. * Consent, receipt delivery, and customer communication records are retained for the required period. ## EEA compliance obligations | Circle's obligation | Your obligation | | - | - | | Issues and custodies EEA accounts through Circle France SAS under MiCA; files regulatory reports with the ACPR. | Sign EEA agreements, surface EEA Terms, capture SCA consent, and retain records under MiCA. | European Economic Area (EEA) accounts are issued under Markets in Crypto-Assets Regulation (MiCA) Article 60(4). Circle France SAS is the licensed entity and legal custodian for all EEA accounts, authorized by the Autorité des marchés financiers (AMF) on April 20, 2026. For a full overview of the EEA regulatory framework, see [EEA and MiCA](/digital-asset-accounts/concepts/eea-and-mica). For the EEA onboarding flow, see [Onboard EEA customers](/digital-asset-accounts/howtos/onboard-eea-customers). EEA accounts require two contracting layers before activation. You contract with Circle France SAS (not Circle LLC) at the partner level. Each end user must accept the custody terms of Circle France SAS. Both layers must be in place before you activate an EEA account. As an EEA distributor, you must do the following: * **Surface the EEA Terms**: Present the [EEA Terms](https://www.circle.com/legal/eea-terms) to end users before account activation and capture click-through acceptance. This is in addition to the standard Digital Asset Account User Agreement. * **Capture SCA consent**: Present the Strong Customer Authentication (SCA) challenge before any sensitive action and obtain authenticated consent. See [EEA API behavior](/digital-asset-accounts/references/eea-api-behavior) for the full list of actions that require SCA. * **Retain records**: Follow the same requirements in [Record retention](/digital-asset-accounts/references/compliance-obligations/record-retention) for a minimum of 5 years. EEA partners are also subject to Autorité de contrôle prudentiel et de résolution (ACPR) record retention requirements under MiCA. Confirm specific periods with your legal counsel. ### No burn fees or ROLR Digital Asset Accounts doesn't charge burn fees or apply redeemer of last resort (ROLR) programs for EEA accounts.