> ## 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. # List POS charges > Charges of the account with merchant_id/status filters and a mandatory date range — the per-client reconciliation view. ## OpenAPI ````yaml /openapi.yaml get /v1/pos/charges 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/pos/charges: get: tags: - QR Crypto POS summary: List POS charges description: >- Charges of the account with merchant_id/status filters and a mandatory date range — the per-client reconciliation view. operationId: listPosCharges parameters: - name: from in: query required: true schema: type: string format: date description: Start date (YYYY-MM-DD, UTC, inclusive). - name: to in: query required: true schema: type: string format: date description: End date (YYYY-MM-DD, UTC, inclusive). - name: merchant_id in: query schema: type: string format: uuid - name: status in: query schema: type: string enum: - pending - paid - expired - name: page in: query schema: type: integer default: 1 - name: page_size in: query schema: type: integer default: 50 maximum: 200 responses: '200': description: OK content: application/json: schema: type: object properties: page: type: integer page_size: type: integer charges: type: array items: $ref: '#/components/schemas/PosCharge' example: page: 1 page_size: 50 charges: - charge_id: 66773a3a-9911-4482-ae3c-09a481aba018 payin_id: bd3d88ca-af9c-4c05-a6f8-0982a2d187d5 status: paid amount: '25' settlement_asset: USDT crypto: tron:usdt due: '25.000000' received: '25.000000' merchant: id: d2875683-fc80-4c7b-876a-fb585d7c6982 name: La Terraza Restaurant external_ref: resto-001 paid_at: '2026-07-17T19:42:00Z' expires_at: '2026-07-17T19:55:00Z' created_at: '2026-07-17T19:40:00Z' '400': $ref: '#/components/responses/InvalidRange' '401': $ref: '#/components/responses/Unauthorized' components: schemas: PosCharge: type: object properties: charge_id: type: string format: uuid payin_id: type: string format: uuid account_id: type: string format: uuid status: type: string enum: - pending - paid - expired amount: type: string settlement_asset: type: string crypto: type: string chain: type: string asset: type: string address: type: string due: type: string received: type: string refunded_total: type: string qr_payload: type: string qr_png_base64: type: string confirming: type: boolean detected_amount: type: string merchant: type: object properties: id: type: string name: type: string external_ref: type: string reference: type: string quote_expires_at: type: string format: date-time paid_at: type: string format: date-time expires_at: type: string format: date-time conversion_status: type: string refunds: type: array items: $ref: '#/components/schemas/PosChargeRefund' receipt_url: type: string created_at: type: string format: date-time updated_at: type: string format: date-time PosChargeRefund: type: object properties: refund_id: type: string format: uuid charge_id: type: string format: uuid withdrawal_id: type: string amount: type: string asset: type: string to_address: type: string status: type: string tx_id: 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: InvalidRange: description: Invalid `from`/`to` date filter (`invalid_range`). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: invalid_range message: invalid from date (YYYY-MM-DD) Unauthorized: description: Missing or invalid credential (`unauthorized`). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: unauthorized message: invalid or missing credentials 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. ````