> ## 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. # Register an account > Creates a person or company account with its owner login member and returns a session token. One endpoint for both types: `type` is data. ## OpenAPI ````yaml /openapi.yaml post /v1/auth/register 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/auth/register: post: tags: - Authentication summary: Register an account description: | Creates a person or company account with its owner login member and returns a session token. One endpoint for both types: `type` is data. operationId: register requestBody: required: true content: application/json: schema: type: object required: - org - type - email - password - display_name properties: org: type: string description: CBPay organization slug (`cbpay`). type: type: string enum: - person - company email: type: string format: email password: type: string minLength: 8 display_name: type: string tax_id: type: string phone: type: string country: type: string description: ISO 3166-1 alpha-2 country code. profile: type: object description: Free-form profile data. example: org: cbpay type: person email: ana@example.com password: a-secure-password display_name: Ana Perez country: CL responses: '201': description: Account created. content: application/json: schema: type: object properties: account: $ref: '#/components/schemas/Account' access_token: type: string description: Session JWT, valid for 24 hours. expires_at: type: string format: date-time refresh_token: type: string description: >- Single-use rotating refresh token for `POST /v1/auth/refresh`. refresh_expires_at: type: string format: date-time example: account: id: 9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d org_id: 1c9e7a2b-5f6d-4e3a-8c1b-2a9d8e7f6a5b type: person status: active kyc_status: approved email: ana@example.com display_name: Ana Perez tax_id: 12345678-9 phone: '+56912345678' country: CL profile: {} created_at: '2026-07-07T12:00:00Z' updated_at: '2026-07-07T12:00:00Z' access_token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9… expires_at: '2026-07-08T12:00:00Z' refresh_token: >- rt_6a1e6c22-93a1-4f0e-a7d1-1f2e3c4b5a69.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX refresh_expires_at: '2026-08-06T12:00:00Z' '400': $ref: '#/components/responses/BadRequest' '403': description: Service suspended (`org_suspended`); contact the CBPay team. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: org_suspended message: organization is not active '409': description: An account with that email already exists (`duplicate`). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: duplicate message: resource already exists security: [] components: schemas: Account: type: object properties: id: type: string format: uuid org_id: type: string format: uuid type: type: string enum: - person - company status: type: string enum: - active - blocked - closed kyc_status: type: string enum: - none - pending - approved - rejected email: type: string display_name: type: string tax_id: type: string phone: type: string country: type: string profile: type: object 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: BadRequest: description: Invalid request (see `error` code for the specific validation). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: invalid_json message: 'request body is not valid JSON: unknown field' 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. ````