> ## 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. # Telegram bot webhook for OTC Desk callbacks (called by Telegram) > Receives Telegram Bot API updates for the organization's OTC DESK group (inline button callbacks on BOB inventory offers). Called by Telegram, not by integrators: authenticated with the X-Telegram-Bot-Api-Secret-Token header (fail-closed 403), button payloads carry an HMAC signature, and duplicate deliveries converge on the callback id. Business outcomes always answer 200 (Telegram must not retry); 503 means store unavailable and is safe to retry. ## OpenAPI ````yaml /openapi.yaml post /v1/public/telegram/otc-desk/{orgID}/webhook openapi: 3.1.0 info: title: CBPay API version: '2.166' 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 ten independent virtual balances — USD (the principal currency), USDT, USDC, BTC, GOLD, SILVER and PLATINUM (grams of fine metal), plus BOB, MXN and ARS (local fiat with two decimals) — convertible on demand with swaps. Payouts and service fees can be paid from any of the ten balances (`PUT /v1/settlement` or per-payout `settlement_asset`), and payins can auto-convert to the asset of your choice (`default_payin_asset`). All amounts are decimal strings in each currency's precision (2 decimals for USD/BOB/MXN/ARS, 6 for USDT/USDC/GOLD/SILVER/PLATINUM, 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 final-state responses/webhooks and automatic email delivery on final states. A pending payout before debit does not expose receipt_url. - 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 (USD is the principal balance). - name: Payins description: >- Fiat top-ups (QR, transfers, dedicated accounts, pull collections, cards, checkout links) credited automatically — in USD, or auto-converted to the settlement asset of your choice. - name: Checkout description: >- Universal checkout links (`POST /v1/payins` with `method: "checkout"`) and the public payment-page endpoints — multi-country fiat, crypto with an ephemeral wallet per link and direct CBPay payment, settled in the asset of your choice. - name: Stored cards description: >- Cards saved with the payer's explicit consent during a 3-D Secure payment (COF). List, revoke and charge them on demand (MIT) without asking for the card again. - name: Subscriptions description: >- Recurring charges on a stored card managed by the platform scheduler — daily, weekly, monthly or yearly, with pause/resume/cancel and automatic dunning. - name: Transfers description: >- Free internal transfers between CBPay accounts (person or company, any combination). - name: Contacts description: >- Per-account address book of beneficiaries (CBPay, bank and crypto destinations) with phone matching and auto-save on every send. - name: Swaps description: >- Instant conversion between the account's USDT, USDC, BTC, GOLD, SILVER and PLATINUM balances at the account's quoted rate. - 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: Signature proofs description: >- Cryptographic message signing with wallets (EIP-191 ETH/EVM, TIP-191 TRON) — create, list, get and revoke signature proofs with public verification. - name: Wallet links description: >- Link external wallets (custody=client) to your account by signing a nonce challenge — create challenges, verify signatures, list and revoke links. - 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 description: >- Identity verification: KYC for persons, KYB for companies — your own onboarding and third-party verifications for company accounts. - name: AML screening description: >- Standalone AML screening of persons and companies against sanctions, PEP and adverse media lists, with rescreening, continuous monitoring and a downloadable PDF report. - 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: Qscore description: >- API-first credit bureau. Issues complete credit reports with a 1-999 score (bands A-E, or SC when there is no data), reads the latest score of a subject and manages ARCO disputes. Chile first, with a country-agnostic design. Every issued report carries a public verification code. - 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 any of the seven spending assets (USD, USDT, USDC, BTC, GOLD, SILVER or PLATINUM), 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. - name: Real-time events description: >- Server-Sent Events stream with everything that happens in the account (or across the organization for admins), replay with `Last-Event-ID`, optional initial snapshot and a 90-day queryable history. - name: Contracts description: Pre-filled Grupo CB framework agreements for verified company accounts. paths: /v1/public/telegram/otc-desk/{orgID}/webhook: post: tags: - OTC Desk summary: Telegram bot webhook for OTC Desk callbacks (called by Telegram) description: >- Receives Telegram Bot API updates for the organization's OTC DESK group (inline button callbacks on BOB inventory offers). Called by Telegram, not by integrators: authenticated with the X-Telegram-Bot-Api-Secret-Token header (fail-closed 403), button payloads carry an HMAC signature, and duplicate deliveries converge on the callback id. Business outcomes always answer 200 (Telegram must not retry); 503 means store unavailable and is safe to retry. operationId: otcDeskTelegramWebhook parameters: - name: orgID in: path required: true schema: type: string format: uuid description: Organization that owns the OTC Desk bot and group. - name: X-Telegram-Bot-Api-Secret-Token in: header required: true schema: type: string description: Webhook secret configured for the organization. requestBody: required: true content: application/json: schema: type: object example: update_id: 123456789 callback_query: id: '3486293628410185798' from: id: 123456789 username: traderuno data: v1.AbC123XyZ456.a.1758600000.9f2c4a1b7d30e5c8 responses: '200': description: Update received (accepted, passed, duplicate or ignored). content: application/json: example: ok: true accepted: true offer_id: 8f3k2m9d-1a2b-4c3d-8e4f-5a6b7c8d9e0f '400': description: invalid_payload (malformed update). content: application/json: example: error: invalid_payload message: malformed update '403': description: Invalid webhook secret. content: application/json: example: error: forbidden message: invalid webhook secret '404': description: Unknown organization. content: application/json: example: error: not_found message: resource not found '503': description: store_unavailable (safe to retry; dedupe makes it idempotent). content: application/json: example: error: store_unavailable message: try again security: [] 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. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.