> ## Documentation Index > Fetch the complete documentation index at: https://docs.cbpayapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Send crypto from the wallet > Sends crypto **from the wallet itself** (real source address, signed by the custodian). `idempotency_key` is required. Gas is on the client: if the wallet lacks native gas the send is rejected with `422 insufficient_gas` before any charge. May bill the `wallet_send` fee (from the account ledger settlement balance, never the wallet's on-chain funds; refunded if the core rejects). Requires a verified account and OTP. On an ambiguous failure the send stays `pending` — retry with the same key, never re-sent. ## OpenAPI ````yaml /openapi.yaml post /v1/segregated-wallets/{walletID}/sends openapi: 3.1.0 info: title: CBPay API version: '1.89' description: | CBPay is a multi-currency payment platform: fiat payouts and collections across Latin America, internal transfers, on-chain funding and withdrawals, and KYC screening. Every account holds four independent virtual balances — USDT (the operating currency), USDC, BTC and GOLD (grams of fine gold) — that never mix or convert automatically. Payouts and service fees can be paid from any of the four balances: set a default with `PUT /v1/settlement` or override per payout with `settlement_asset`. All amounts are decimal strings in each currency's precision (6 decimals for USDT/USDC/GOLD, 8 for BTC). Errors always return `{"error": "", "message": ""}`. servers: - url: https://api.qbank.cl/platform description: Live (production, real money) - url: https://cryptobank.qbank.cl/platform description: Test (sandbox, simulated money — pk_test_ keys) security: - bearerAuth: [] tags: - name: Receipts description: >- Branded PDF receipt per operation, with a public signed-QR authenticity check, receipt_url on every response/webhook and automatic email delivery on final states. - name: Authentication description: Register and log in account members. Sessions last 24 hours. - name: Account description: Profile, members and API keys of the calling account. - name: Balances description: Balances, movement history and FX rates. - name: Payouts description: >- Fiat dispersals debited from the settlement balance of your choice (USDT by default). - name: Payins description: Fiat top-ups credited to the USDT balance. - name: Transfers - name: Contacts - name: Swaps description: >- Free internal transfers between CBPay accounts (person or company, any combination). - name: Crypto description: On-chain funding and withdrawals (TRON, Ethereum and Bitcoin). - name: Segregated wallets description: >- On-chain wallets with their own balance (companies unlimited; persons 1 per network+asset pair) — create, import, send, export the private key and auto-forward. The balance lives on-chain, never in the ledger. - name: QR Crypto POS description: >- Amount-bearing crypto QR charges for processors with physical POS terminals (company accounts): verified merchants, exclusive address + QR per charge, early payment detection, per-merchant reconciliation and refunds over the crypto withdrawal rail. - name: KYC / KYB - name: AML screening description: >- Identity verification: KYC for persons, KYB for companies, with AML screening, rescreening and continuous monitoring. - name: Wallet screening description: >- AML risk assessment of blockchain addresses (sanctions, illicit-fund exposure) with a per-scan fee, plus free automatic protection on withdrawals and deposits. - name: Analytics - name: Webhooks description: Subscriptions to receive signed event notifications. - name: Status description: Service availability. - name: Banking description: >- Real bank accounts: receive, hold and send money over international banking rails. - name: Cards description: >- Virtual and physical cards that spend Just-In-Time from the account's USDT balance, with per-card spending limits. - name: Security (OTP) description: >- One-time verification codes over SMS/WhatsApp/email protecting sensitive actions, plus self-service 2FA preferences. Applies to user sessions only — API keys are exempt. - name: Passkeys description: >- Passwordless sign-in with the device's biometrics (Face ID, Touch ID, Windows Hello, security keys) via WebAuthn, authenticator apps (TOTP) with backup codes, and session/device management. - name: Social login description: >- Passwordless sign up and sign in with Google, Apple, Microsoft and Facebook via token exchange. The front end obtains the provider credential; the API verifies it and issues the CBPay session. paths: /v1/segregated-wallets/{walletID}/sends: post: tags: - Segregated wallets summary: Send crypto from the wallet description: >- Sends crypto **from the wallet itself** (real source address, signed by the custodian). `idempotency_key` is required. Gas is on the client: if the wallet lacks native gas the send is rejected with `422 insufficient_gas` before any charge. May bill the `wallet_send` fee (from the account ledger settlement balance, never the wallet's on-chain funds; refunded if the core rejects). Requires a verified account and OTP. On an ambiguous failure the send stays `pending` — retry with the same key, never re-sent. operationId: createSegregatedWalletSend parameters: - name: walletID in: path required: true schema: type: string - name: X-OTP-Token in: header schema: type: string requestBody: required: true content: application/json: schema: type: object required: - to_address - idempotency_key properties: asset: type: string enum: - usdt - usdc - eth to_address: type: string amount: type: string description: Decimal amount in the asset unit (use this or amount_raw). amount_raw: type: string description: Amount in minimal on-chain units. idempotency_key: type: string examples: by_amount: summary: By decimal amount value: asset: usdt to_address: TXYZdestination00000000000000000000 amount: '25.50' idempotency_key: send-2026-07-11-a by_raw: summary: By minimal units value: asset: usdt to_address: TXYZdestination00000000000000000000 amount_raw: '25500000' idempotency_key: send-2026-07-11-b responses: '200': description: Idempotent replay of a previous send. content: application/json: schema: $ref: '#/components/schemas/SegregatedWalletSend' example: send_id: 9c8b7a6d-5e4f-3a2b-1c0d-9e8f7a6b5c4d status: processing idempotency_key: send-2026-07-11-a idempotency_hit: true '202': description: Send broadcast (asynchronous; final state via webhook). content: application/json: schema: $ref: '#/components/schemas/SegregatedWalletSend' example: send_id: 9c8b7a6d-5e4f-3a2b-1c0d-9e8f7a6b5c4d wallet_id: b7e3a1c2-9f4d-4a8b-8c1e-2d3f4a5b6c7d chain: tron asset: USDT to_address: TXYZdestination00000000000000000000 amount_raw: '25500000' fee: '0.000000' fee_asset: USDT status: processing tx_id: >- b1946ac92492d2347c6235b4d2611184e0f0f8c9d3a1e2b3c4d5e6f708192a3b idempotency_key: send-2026-07-11-a created_at: '2026-07-11T12:05:00Z' '422': description: Not enough gas in the wallet, or the core rejected the send. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: insufficient_gas message: >- the wallet does not hold enough TRX to pay the network fee (minimum 5.000000 TRX); fund the wallet address with TRX and retry components: schemas: SegregatedWalletSend: type: object properties: send_id: type: string format: uuid wallet_id: type: string format: uuid account_id: type: string format: uuid chain: type: string enum: - tron - eth - btc asset: type: string example: USDT to_address: type: string amount_raw: type: string description: Amount in minimal on-chain units. fee: type: string description: Service fee charged from the ledger settlement balance. fee_asset: type: string example: USDT status: type: string enum: - pending - processing - completed - failed status_code: type: string status_message: type: string tx_id: type: string idempotency_key: type: string created_at: type: string format: date-time updated_at: type: string format: date-time Error: type: object properties: error: type: string description: Machine-readable error code (snake_case). example: insufficient_funds message: type: string description: Human-readable explanation. securitySchemes: bearerAuth: type: http scheme: bearer description: | Session JWT (from register/login) or API key (`pk_...`). `X-API-Key: ` is accepted as an alternative header. ````