> ## 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. # Update my 2FA preferences > Lets the account owner configure its own 2FA. You can always harden (enable actions, move to a stronger channel: totp > email > sms/whatsapp) but never go below the organization floor. Weakening (disabling an active action or lowering the channel) requires an `X-OTP-Token` for the `security_settings` action. Choosing `channel:totp` requires the authenticator app already enrolled. Enabling 2FA for the `login` action over a phone channel (`sms`/`whatsapp`) requires the account phone number to be verified first (complete any SMS/WhatsApp OTP challenge); otherwise the request is rejected with `409 phone_verification_required` — this prevents locking yourself out with a mistyped number. ## OpenAPI ````yaml /openapi.yaml put /v1/otp/preferences 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/otp/preferences: put: tags: - Security (OTP) summary: Update my 2FA preferences description: >- Lets the account owner configure its own 2FA. You can always harden (enable actions, move to a stronger channel: totp > email > sms/whatsapp) but never go below the organization floor. Weakening (disabling an active action or lowering the channel) requires an `X-OTP-Token` for the `security_settings` action. Choosing `channel:totp` requires the authenticator app already enrolled. Enabling 2FA for the `login` action over a phone channel (`sms`/`whatsapp`) requires the account phone number to be verified first (complete any SMS/WhatsApp OTP challenge); otherwise the request is rejected with `409 phone_verification_required` — this prevents locking yourself out with a mistyped number. operationId: putOTPPreferences parameters: - name: X-OTP-Token in: header required: false schema: type: string requestBody: required: true content: application/json: schema: type: object required: - action - required properties: action: type: string enum: - login - payout - crypto_withdrawal - transfer - banking_operation - card_reveal - api_key_create - member_add - phone_change - password_change - email_change - security_settings required: type: boolean channel: type: string enum: - sms - whatsapp - email - totp default: sms example: action: payout required: true channel: totp responses: '200': description: Updated effective policy. content: application/json: example: enabled: true actions: - action: payout required: true channel: totp source: account '403': description: >- Locked by org (`policy_locked_by_org` / `channel_locked_by_org`) or OTP required to weaken (`otp_required`). '409': description: >- Authenticator app not enrolled for `channel:totp` (`totp_enrollment_required`), or unverified phone when enabling login 2FA over a phone channel (`phone_verification_required`). components: 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. ````