> ## 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. # List payouts > Returns the payouts of the calling account. ## OpenAPI ````yaml /openapi.yaml get /v1/payouts 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/payouts: get: tags: - Payouts summary: List payouts description: Returns the payouts of the calling account. operationId: listPayouts parameters: - $ref: '#/components/parameters/page' - $ref: '#/components/parameters/pageSize' - name: status in: query schema: type: string enum: - pending - processing - completed - failed - name: country in: query schema: type: string description: Filter by destination country (ISO 3166-1 alpha-2, e.g. CL, PE, MX). - name: from in: query schema: type: string format: date description: Filter from this date (YYYY-MM-DD, UTC, inclusive). - name: to in: query schema: type: string format: date description: Filter up to this date (YYYY-MM-DD, UTC, inclusive). - name: format in: query description: >- Export the same rows as a file: `csv` or `xlsx` (accounting-grade download, up to 10,000 rows; same filters and date range). Omit for the JSON view. schema: type: string enum: - csv - xlsx responses: '200': description: Paged payouts. content: application/json: schema: type: object properties: page: type: integer page_size: type: integer payouts: type: array items: $ref: '#/components/schemas/Payout' example: page: 1 page_size: 50 payouts: - payout_id: 7d5c2f0a-1e9b-4a6d-8f3c-0b2a1d9e8c7f account_id: 9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d idempotency_key: invoice-8841 country: MX currency: MXN method: bank_transfer local_amount: '1500.00' fx_rate: '17.50' usdt_amount: '85.714286' fee: '0.300000' total_debit: '86.014286' settlement_asset: USDT settlement_amount: '86.014286' settlement_rate: '1' beneficiary: name: Maria Lopez account_type: clabe account_number: 12180001234567896 description: Invoice 8841 status: processing status_code: '' status_message: '' created_at: '2026-07-07T12:00:00Z' updated_at: '2026-07-07T12:00:00Z' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' components: parameters: page: name: page in: query schema: type: integer default: 1 minimum: 1 pageSize: name: page_size in: query schema: type: integer default: 50 maximum: 200 schemas: Payout: type: object properties: payout_id: type: string format: uuid account_id: type: string format: uuid idempotency_key: type: string country: type: string currency: type: string method: type: string local_amount: type: string fx_rate: type: string description: Your account's rate at execution time (local units per 1 USDT). usdt_amount: type: string fee: type: string total_debit: type: string settlement_asset: type: string enum: - USDT - USDC - BTC - GOLD description: Virtual balance the operation was actually debited from. settlement_amount: type: string description: >- Exact amount debited from the settlement asset's balance (in that asset's units). Equals `total_debit` when the asset is USDT. If the payout fails this exact amount is refunded — never re-quoted. settlement_rate: type: string description: >- Effective USD price per unit of the settlement asset used to convert the USDT total ("1" for USDT/USDC). beneficiary: type: object description: type: string status: type: string enum: - pending - processing - completed - failed status_code: type: string status_message: type: string created_at: type: string format: date-time updated_at: type: string format: date-time idempotency_hit: type: boolean description: Present (true) when the response is an idempotent replay. Error: type: object properties: error: type: string description: Machine-readable error code (snake_case). example: insufficient_funds message: type: string description: Human-readable explanation. responses: Unauthorized: description: Missing or invalid credential (`unauthorized`). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: unauthorized message: invalid or missing credentials Forbidden: description: Credential level not allowed for this endpoint (`forbidden`). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: forbidden message: credentials required 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. ````