> ## Documentation Index > Fetch the complete documentation index at: https://docs.breet.io/llms.txt > Use this file to discover all available pages before exploring further. # Update Bank For Existing Wallet Address > Update the bank account linked to an existing wallet address. Optionally set `autoSettlement` so incoming crypto to this address is paid out to that bank. ## OpenAPI ````yaml /api-reference/openapi.json put /trades/wallets/{id}/bank openapi: 3.0.0 info: title: BREET PUBLIC API version: 1.0.0 license: name: Proprietary url: https://breet.io/terms servers: - url: https://api.breet.io/v1 security: - appId: [] appSecret: [] breetEnv: [] tags: - name: Crypto Wallet description: Generate and manage crypto wallet addresses for receiving deposits. x-group: Wallets and Deposits - name: Withdrawals description: >- ## Withdrawals To help protect your funds, withdrawals support an additional security layer through **IP whitelisting**. ### IP Whitelisting When IP whitelisting is enabled, all withdrawal requests must originate from an approved IP address. Any withdrawal request coming from an IP not on the whitelist will be automatically blocked. You can add up to **7 IP addresses** from your dashboard. This feature is recommended for: - Production servers - Preventing unauthorized withdrawal attempts ### How it works - Enable IP whitelisting from your dashboard - Add up to 7 trusted IP addresses - Only requests from those IPs will be allowed to initiate withdrawals If IP whitelisting is disabled, withdrawals can be initiated from any IP address. - name: Banks description: List, validate, add, and remove bank accounts for fiat withdrawals. - name: Transactions description: Retrieve deposit and trade transaction history. - name: Webhooks description: >- Inspect and retry **outgoing** webhooks we send to your server (trade and withdrawal events). Requires an active integration with API access (VIP partners). For **incoming** payload shapes and verification, see the Webhooks guide in the Guides tab. - name: Assets description: >- Retrieve the list of supported deposit/sell assets and their configuration. - name: Rates and Prices description: >- Get live market prices and calculate conversion rates. These endpoints are public and do not require authentication. - name: Account description: Retrieve and update integration account details and preferences. - name: Testing description: Endpoints for testing your integration in development. - name: Conversion description: >- Convert between USD and local fiat (NGN | GHS). Available for both user and integration (business) flows. - name: Wallet addresses description: >- Add and remove withdrawal (payout) wallet addresses. If the same address, network, and token are sent with a different label, the existing address is updated. paths: /trades/wallets/{id}/bank: put: tags: - Crypto Wallet summary: Update Bank For Existing Wallet Address description: >- Update the bank account linked to an existing wallet address. Optionally set `autoSettlement` so incoming crypto to this address is paid out to that bank. operationId: updateWalletBank parameters: - name: id in: path required: true schema: type: string description: ID of the wallet to update. requestBody: content: application/json: schema: type: object example: id: '25' narration: Breet payout account accountNumber: 802920XXXX autoSettlement: true properties: id: type: string description: Bank identifier from the GET /payments/banks endpoint. narration: type: string description: >- A short note included with bank settlement payouts. Maximum 32 characters. accountNumber: type: string description: Bank account number for settlement payouts. autoSettlement: type: boolean description: >- Optional. When `true`, incoming crypto to this address is auto-settled to the linked bank. Omit or use `false` to keep funds in the wallet. example: id: '25' narration: Breet payout account accountNumber: 802920XXXX autoSettlement: true responses: '200': description: Bank details updated successfully content: application/json: example: message: bank added to wallet successfully success: true data: {} meta: {} summary: {} stats: {} '400': description: Invalid wallet ID format content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false message: you have entered an invalid _id meta: {} errors: [] data: {} '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: Wallet not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false message: wallet not found meta: {} errors: [] data: {} '422': $ref: '#/components/responses/ValidationError' '500': $ref: '#/components/responses/InternalServerError' components: schemas: ErrorResponse: type: object required: - success - message properties: success: type: boolean enum: - false message: type: string meta: type: object errors: type: array items: type: object data: type: object responses: Unauthorized: description: Invalid or missing API credentials content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: notAuthenticated: summary: Missing credentials value: success: false message: you're not authenticated meta: {} errors: [] data: {} wrongCredentials: summary: Invalid app ID or secret value: success: false message: wrong app id and secret combination meta: {} errors: [] data: {} Forbidden: description: The integration is inactive or the action is not permitted content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false message: you do not have api access meta: {} errors: [] data: {} ValidationError: description: >- Request validation failed — check the errors array for field-level details content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false message: validation errors meta: {} errors: - message: Invalid value field: amount location: body data: {} InternalServerError: description: An unexpected server error occurred content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false message: something went wrong! meta: {} errors: [] data: {} securitySchemes: appId: type: apiKey in: header name: x-app-id description: Your application ID from the Breet dashboard appSecret: type: apiKey in: header name: x-app-secret description: Your application secret from the Breet dashboard breetEnv: type: apiKey in: header name: X-Breet-Env description: 'Environment selector: development or production' ````