> ## 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 a bank payment > Executes a TRANSFER (between your own bank accounts) or WITHDRAW (to a registered beneficiary). Requires an idempotency key; retries with the same key return the original operation without re-charging. Billed as the fixed `banking_operation` fee; refunded if the corridor rejects. The final state arrives via the banking_operation_status_changed webhook. ## OpenAPI ````yaml /openapi.yaml post /v1/banking/operations 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/banking/operations: post: tags: - Banking summary: Send a bank payment description: >- Executes a TRANSFER (between your own bank accounts) or WITHDRAW (to a registered beneficiary). Requires an idempotency key; retries with the same key return the original operation without re-charging. Billed as the fixed `banking_operation` fee; refunded if the corridor rejects. The final state arrives via the banking_operation_status_changed webhook. operationId: createBankingOperation parameters: - $ref: '#/components/parameters/idempotencyKeyHeader' requestBody: required: true content: application/json: schema: type: object required: - currency - type - sourceRequisit - destinationRequisit - amount properties: currency: type: string example: USD type: type: string enum: - TRANSFER - WITHDRAW paymentType: type: string description: EMPTY for TRANSFER; rail code (e.g. SEPA_CT) for WITHDRAW. sourceRequisit: type: object properties: account: type: string destinationRequisit: type: object properties: account: type: string description: Destination account (TRANSFER). beneficiar: type: string description: Beneficiary account (WITHDRAW). amount: type: object properties: currencyCode: type: string units: type: string nanos: type: integer comment: type: string idempotency_key: type: string examples: withdraw: summary: WITHDRAW to a beneficiary (SEPA) value: currency: USD type: WITHDRAW paymentType: SEPA_CT sourceRequisit: account: c4d1e2f3-a4b5-c6d7-e8f9-a0b1c2d3e4f5 destinationRequisit: beneficiar: BNK-CPACC-11 amount: currencyCode: USD units: '250' nanos: 0 comment: Invoice 8841 idempotency_key: acme-payment-0071 transfer: summary: TRANSFER between own accounts value: currency: USD type: TRANSFER paymentType: EMPTY sourceRequisit: account: c4d1e2f3-a4b5-c6d7-e8f9-a0b1c2d3e4f5 destinationRequisit: account: d5e2f3a4-b5c6-d7e8-f9a0-b1c2d3e4f5a6 amount: currencyCode: USD units: '100' nanos: 0 idempotency_key: internal-move-0012 responses: '200': description: Idempotency replay of an existing operation (no new charge). content: application/json: schema: type: object additionalProperties: true example: operation_id: 7e8a9b0c-1d2e-3f4a-5b6c-7d8e9f0a1b2c provider_id: BNK-OP-90213 status: pending idempotency_key: platform:9b1deb4d:acme-payment-0071 data: type: WITHDRAW paymentType: SEPA_CT idempotency_hit: true '202': description: Operation accepted (final state via webhook). content: application/json: schema: type: object additionalProperties: true example: operation_id: 7e8a9b0c-1d2e-3f4a-5b6c-7d8e9f0a1b2c provider_id: BNK-OP-90213 status: pending idempotency_key: platform:9b1deb4d:acme-payment-0071 data: type: WITHDRAW paymentType: SEPA_CT banking_fee: '2.000000' '400': description: idempotency_key_required / invalid payload. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: idempotency_key_required message: provide idempotency_key (body or Idempotency-Key header) '401': $ref: '#/components/responses/Unauthorized' '402': $ref: '#/components/responses/InsufficientFunds' '409': description: No banking profile yet (no_banking_customer). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: no_banking_customer message: create your banking customer first (POST /v1/banking/customer) '502': description: >- Banking corridor error; any fee was refunded (banking_request_failed). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: banking_request_failed message: request rejected components: parameters: idempotencyKeyHeader: name: Idempotency-Key in: header required: false description: Alternative to the `idempotency_key` body field. schema: type: string schemas: 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 InsufficientFunds: description: Account balance is not enough for this operation (`insufficient_funds`). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: insufficient_funds message: account balance is not enough for this operation 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. ````