> ## 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. # Get repayment account details > Returns repayment account details and wire instructions for making a credit repayment using the specified fiat account. ## OpenAPI ````yaml openapi/credit.yaml get /v1/credit/repaymentAccounts/{fiatAccountId} openapi: 3.0.2 info: version: ${version} title: Credit API description: > The Circle Credit API provides access to credit facilities including Line of Credit and Settlement Advance products. **Line of Credit** enables direct drawdowns with auto-approval and asynchronous disbursement. Supports both fiat and crypto repayment. **Settlement Advance** requires a reserve-then-request flow with manual approval. Requires wire proof upload for disbursement approval. Supports fiat repayment only. servers: - url: https://api-sandbox.circle.com - url: https://api.circle.com security: [] tags: - name: Credit description: Get credit line details. - name: Credit Transfers description: Create, reserve, and manage credit transfers (drawdowns). - name: Credit Fees description: View fees charged on credit transfers. - name: Credit Repayments description: View and initiate repayments on credit transfers. paths: /v1/credit/repaymentAccounts/{fiatAccountId}: get: tags: - Credit Repayments summary: Get repayment account details description: >- Returns repayment account details and wire instructions for making a credit repayment using the specified fiat account. operationId: getRepaymentAccountDetail parameters: - name: fiatAccountId in: path required: true description: The ID of the wire bank account to retrieve repayment details for. schema: type: string format: uuid responses: '200': description: Successfully retrieved repayment account details. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: title: GetRepaymentAccountDetailResponse properties: data: $ref: '#/components/schemas/RepaymentAccountDetail' examples: Repayment Account Detail: value: data: id: a1b2c3d4-5678-90ab-cdef-1234567890ab description: WELLS FARGO BANK, NA ****1111 status: active wireInstructions: trackingRef: CIR28XYS2F beneficiary: name: CIRCLE INTERNET FINANCIAL INC address1: 1 Main Street address2: Suite 1 beneficiaryBank: swiftCode: SVBKUS6S routingNumber: '121140399' accountNumber: '3302726104' currency: USD name: SILICON VALLEY BANK address: 3003 TASMAN DRIVE city: SANTA CLARA postalCode: '95054' country: US '401': $ref: '#/components/responses/NotAuthorized' '404': $ref: '#/components/responses/NotFound' security: - bearerAuth: [] components: headers: XRequestId: description: >- Universally unique identifier (UUID v4) for the request. Helpful for identifying a request when communicating with Circle support. schema: type: string format: uuid example: 2adba88e-9d63-44bc-b975-9b6ae3440dde schemas: RepaymentAccountDetail: type: object description: >- Repayment account details including wire instructions for making a credit repayment. required: - id - status - wireInstructions properties: id: description: Unique identifier for the repayment account record. type: string format: uuid example: a1b2c3d4-5678-90ab-cdef-1234567890ab description: description: >- Human-readable description of the bank account (e.g. bank name and masked account number). type: string example: WELLS FARGO BANK, NA ****1111 status: description: > Verification status of the repayment account. - `active`: At least one completed credit repayment has been matched to this account. - `unverified`: No matched credit repayment yet. type: string enum: - active - unverified example: active wireInstructions: $ref: '#/components/schemas/CreditWireInstructions' CreditWireInstructions: type: object description: Wire transfer instructions for making a fiat repayment on a credit line. required: - trackingRef - beneficiary - beneficiaryBank properties: trackingRef: description: A tracking reference for the wire transfer. type: string example: CIR3XBZZ4N beneficiary: description: Beneficiary details. type: object required: - name - address1 - address2 properties: name: description: Beneficiary name. type: string example: CIRCLE INTERNET FINANCIAL INC address1: description: Beneficiary address line 1. type: string example: 1 Main Street address2: description: Beneficiary address line 2. type: string example: Suite 1 beneficiaryBank: description: Beneficiary bank details. type: object required: - swiftCode - routingNumber - accountNumber - currency - name - address - city - postalCode - country properties: swiftCode: description: SWIFT/BIC code of the bank. type: string example: SVBKUS6S routingNumber: description: ABA routing number. type: string example: '121140399' accountNumber: description: Bank account number. type: string example: '3302726104' currency: description: Currency code. type: string enum: - USD example: USD name: description: Name of the bank. type: string example: SILICON VALLEY BANK address: description: Bank address. type: string example: 3003 TASMAN DRIVE city: description: Bank city. type: string example: SANTA CLARA postalCode: description: Bank postal code. type: string example: '95054' country: description: Bank country code. type: string example: US responses: NotAuthorized: description: >- The request has not been applied because it lacks valid authentication credentials. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: NotAuthorized required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 401 message: Malformed authorization. examples: response: value: code: 401 message: Malformed authorization. NotFound: description: The specified resource was not found. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: NotFound required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 404 message: Not found. examples: response: value: code: 404 message: Not found. securitySchemes: bearerAuth: type: http scheme: bearer ````