> ## 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. # Create a KYB submission with API data > Company accounts only: verifies one of YOUR end customers (a business) sending the data directly. Body: external_customer_id, country?, business (the company fields), ubos?, directors?, signers?, bank_info?, metadata?. Bills the fixed `kyb_verification` fee; `idempotency_key` required. Re-sending while open updates the same submission without charging again. ## OpenAPI ````yaml /openapi.yaml post /v1/kyb/submissions 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/kyb/submissions: post: tags: - KYC / KYB summary: Create a KYB submission with API data description: >- Company accounts only: verifies one of YOUR end customers (a business) sending the data directly. Body: external_customer_id, country?, business (the company fields), ubos?, directors?, signers?, bank_info?, metadata?. Bills the fixed `kyb_verification` fee; `idempotency_key` required. Re-sending while open updates the same submission without charging again. operationId: createKybSubmission requestBody: required: true content: application/json: schema: type: object required: - external_customer_id - idempotency_key properties: external_customer_id: type: string idempotency_key: type: string country: type: string business: type: object description: Company fields (legal name, tax id, address, activity...). ubos: type: array items: type: object directors: type: array items: type: object metadata: type: object example: external_customer_id: cust_456 idempotency_key: kyb-sub-cust-456-1 country: cl business: legal_name: Comercial Andina SpA tax_id: 76.543.210-8 ubos: - first_name: Carlos last_name: Soto ownership_percent: 60 responses: '201': description: Submission created (enters the compliance review queue). content: application/json: schema: $ref: '#/components/schemas/VerificationSubmission' example: submission_id: e5f6a7b8-c9d0-4e1f-2a3b-4c5d6e7f8091 kind: kyb external_customer_id: cust_456 status: pending_review verification_fee: '2.000000' idempotency_key: kyb-sub-cust-456-1 created_at: '2026-07-10T12:10:00Z' updated_at: '2026-07-10T12:10:00Z' '400': description: idempotency_key_required / invalid_payload / invalid_country 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' '403': description: verification_required / company_account_required / service_disabled content: application/json: schema: $ref: '#/components/schemas/Error' example: error: company_account_required message: >- third-party KYC/KYB verification is available to company accounts only components: schemas: VerificationSubmission: type: object properties: submission_id: type: string format: uuid kind: type: string enum: - kyc - kyb external_customer_id: type: string status: type: string enum: - pending_review - in_review - changes_requested - more_info_required - escalated - approved - approved_partial - rejected risk_band: type: string liveness_pending: type: boolean description: KYC only. True until the video liveness check passes. pending_documents: type: array items: type: string rejection_reason: type: string aml_decision: type: string description: KYB only. verification_fee: 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. 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. ````