> ## 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. # List crypto payment customer wallets ## OpenAPI ````yaml openapi/payments.yaml get /v1/payments/customers/{customerId}/wallets openapi: 3.0.2 info: version: ${version} title: Crypto Deposits API description: > The Circle Payments API allows you to take payments from your end users via traditional methods such as debit & credit cards and receive settlement in USDC. The Circle Payments API has been designed with any business or internet commerce in mind, not just crypto applications, and it's based on Circle's extensive experience processing millions of card payments since 2014. servers: - url: https://api-sandbox.circle.com - url: https://api.circle.com security: [] tags: - name: Payments description: Create, cancel, refund, and get updates on card payments. - name: Crypto Payment Intents description: Create and track intent for end user to pay via crypto. - name: Crypto Payment Customers description: >- Create and manage Travel Rule customers and customer wallets for crypto payment attribution. - name: Crypto Payment Refund Addresses description: Create refund address-book entries for crypto payment refunds. paths: /v1/payments/customers/{customerId}/wallets: get: tags: - Crypto Payment Customers summary: List crypto payment customer wallets operationId: listPaymentCustomerWallets parameters: - name: customerId description: Customer identifier. in: path required: true schema: type: string format: uuid - $ref: '#/components/parameters/PageBefore' - $ref: '#/components/parameters/PageAfter' - $ref: '#/components/parameters/PageSize' responses: '200': description: Successfully retrieved customer wallets. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: title: ListPaymentCustomerWalletsResponse properties: data: type: array items: $ref: '#/components/schemas/PaymentCustomerWallet' examples: wallets: value: data: - id: 9b8a7d6c-5e4f-4321-9c8b-123456789abc customerId: 7d4f71c1-7e2e-4a1d-9df3-3a4d8d6d5a11 chain: ETH type: hosted vaspId: 581b9b20-28e1-464d-a257-e408733d0857 '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/NotAuthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '500': $ref: '#/components/responses/InternalServerError' security: - bearerAuth: [] components: parameters: PageBefore: name: pageBefore description: > A collection ID value used for pagination. It marks the exclusive end of a page. When provided, the collection resource will return the next `n` items before the id, with `n` being specified by `pageSize`. The items will be returned in the natural order of the collection. The resource will return the first page if neither `pageAfter` nor `pageBefore` are specified. SHOULD NOT be used in conjuction with pageAfter. in: query required: false schema: type: string PageAfter: name: pageAfter description: > A collection ID value used for pagination. It marks the exclusive begin of a page. When provided, the collection resource will return the next `n` items after the id, with `n` being specified by `pageSize`. The items will be returned in the natural order of the collection. The resource will return the first page if neither `pageAfter` nor `pageBefore` are specified. SHOULD NOT be used in conjuction with pageBefore. in: query required: false schema: type: string PageSize: name: pageSize description: > Limits the number of items to be returned. Some collections have a strict upper bound that will disregard this value. In case the specified value is higher than the allowed limit, the collection limit will be used. If avoided, the collection will determine the page size itself. in: query required: false schema: type: integer minimum: 1 example: 5 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: PaymentCustomerWallet: type: object description: Customer wallet linked to a Travel Rule customer. required: - id - customerId - chain - type properties: id: $ref: '#/components/schemas/Id' customerId: type: string format: uuid description: Identifier of the customer this wallet belongs to. example: 7d4f71c1-7e2e-4a1d-9df3-3a4d8d6d5a11 chain: $ref: '#/components/schemas/Chain' type: $ref: '#/components/schemas/PaymentCustomerWalletType' address: type: string description: Customer wallet address, when provided. example: '0x57414adbBbc4BBA36f1dE26b2dc1648b28ae7799' addressTag: $ref: '#/components/schemas/AddressTag' vaspId: type: string format: uuid description: Hosted VASP identifier for the customer wallet. example: 581b9b20-28e1-464d-a257-e408733d0857 Id: type: string description: Unique system generated identifier for the entity. format: uuid example: b8627ae8-732b-4d25-b947-1df8f4007a29 Chain: type: string description: > A blockchain that a given currency is available on. **Note:** Arc (`ARC`) is only available in the sandbox environment (`api-sandbox.circle.com`). enum: - ALGO - APTOS - ARB - ARC - AVAX - BASE - BTC - CELO - CODEX - ETH - HBAR - HYPEREVM - INK - LINEA - NEAR - NOBLE - OP - PLUME - PAH - POLY - SEI - SOL - SONIC - SUI - UNI - WORLDCHAIN - XLAYER - XDC - XLM - XRP - ZKS - ZKSYNC PaymentCustomerWalletType: type: string description: >- Customer wallet type. Hosted customer wallets are currently supported for API creation. enum: - hosted example: hosted AddressTag: type: string description: >- The secondary identifier for a blockchain address. An example of this is the memo field on the Stellar network, which can be text, id, or hash format. nullable: true example: '123456789' responses: BadRequest: description: The request cannot be processed due to a client error. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: BadRequest required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 400 message: Bad request. examples: response: value: code: 400 message: Bad request. 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. Forbidden: description: >- The request provides authentication, but the authenticated user does not possess sufficient permissions for accessing this resource. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: Forbidden required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 3 message: Forbidden examples: response: value: code: 3 message: Forbidden 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. InternalServerError: description: Unexpected server error. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: InternalServerError required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 500 message: Internal server error. examples: response: value: code: 500 message: Internal server error. securitySchemes: bearerAuth: type: http scheme: bearer ````