> ## 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. # Verification report of a KYC you ran (PDF/JSON) > Full compliance report of a verification you ran on your customer (company accounts only): verified profile, lifecycle, documents + OCR, liveness (one entry per session - the onboarding gate check plus any later evidence recaptures, each with its own session_id and purpose; for a KYB, every related party can carry more than one session too) and the FULL AML screening section with match detail - you are the data controller of your third parties. If the submission turns out to be your own onboarding, the AML section is aggregated instead. Use format=pdf (default) or format=json, and lang=en|es|zh. Free - reading an already-billed verification. If the submission has no linked AML screening yet, one is triggered on demand (idempotent, no fee); when unavailable the report ships with the gap declared in the partial field. ## OpenAPI ````yaml /openapi.yaml get /v1/kyc/submissions/{submissionID}/verification-report openapi: 3.1.0 info: title: CBPay API version: '2.62' 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) — convertible on demand with swaps. Payouts and service fees can be paid from any of the four 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 (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 (QR, transfers, dedicated accounts, pull collections, cards, checkout links) credited automatically — in USDT by default, 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 and GOLD 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 the balance of your choice (USDT, USDC, BTC or GOLD), 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. paths: /v1/kyc/submissions/{submissionID}/verification-report: get: tags: - KYC / KYB summary: Verification report of a KYC you ran (PDF/JSON) description: >- Full compliance report of a verification you ran on your customer (company accounts only): verified profile, lifecycle, documents + OCR, liveness (one entry per session - the onboarding gate check plus any later evidence recaptures, each with its own session_id and purpose; for a KYB, every related party can carry more than one session too) and the FULL AML screening section with match detail - you are the data controller of your third parties. If the submission turns out to be your own onboarding, the AML section is aggregated instead. Use format=pdf (default) or format=json, and lang=en|es|zh. Free - reading an already-billed verification. If the submission has no linked AML screening yet, one is triggered on demand (idempotent, no fee); when unavailable the report ships with the gap declared in the partial field. operationId: getKycVerificationReport parameters: - name: submissionID in: path required: true schema: type: string format: uuid description: Submission id. - name: format in: query schema: type: string enum: - pdf - json description: Report format - pdf (default) or json. - name: lang in: query schema: type: string enum: - en - es - zh description: Report language (en default, es, zh). responses: '200': description: >- The verification report (application/pdf, or application/json with format=json). content: application/pdf: schema: type: string format: binary example: '%PDF-1.7 (binary report content)' application/json: example: report_id: IDR-3C4D5E6F7A8B kind: kyc scope: third_party generated_at: '2026-07-28T15:04:05Z' generated_by: CBPay language: en aml_detail: true submission_id: 3c4d5e6f-7a8b-4c9d-8e0f-1a2b3c4d5e6f external_customer_id: customer-1042 status: approved risk_band: medium aml_decision: approved submitted_at: '2026-07-19T14:00:00Z' updated_at: '2026-07-19T14:52:00Z' decided_at: '2026-07-19T14:52:00Z' documents_received: - identity - proofOfAddress subject: type: person name: Maria Fernanda Rojas person: first_name: Maria middle_name: Fernanda last_name: Rojas date_of_birth: '1988-11-02' country_of_birth: PE nationality: PE tax_residence_country: PE id_type: national_id id_number: '45678912' id_issuing_country: PE id_expires_at: '2029-05-20' occupation: Regional sales manager email: maria.rojas@example.com phone: +51 9 8765 4321 address: line1: Av. Arequipa 1200 city: Lima state: Lima postal_code: '15046' country: PE economic_profile: source_of_funds: salary primary_purpose: personal_payments monthly_payments_usd: '5000' monthly_transaction_count: '20' employment_status: employed employer_name: Andes Retail SAC expected_chains: - tron attestations: - key: att_money_services value: false - key: att_prohibited_countries value: false bank_account: bank_name: BCP account_holder: Maria Fernanda Rojas account_masked: '****9911' country: PE currency: PEN third_party_account: false documents: - category: identity filename: dni.pdf status: validated outcome: MATCH score: '0.99' summary: >- Name, document number and date of birth match the verified profile. validated_at: '2026-07-19T14:40:00Z' - category: proofOfAddress filename: recibo-luz.pdf status: validated outcome: REVIEW score: '0.72' error: Address line partially legible. validated_at: '2026-07-19T14:41:00Z' liveness: - role: subject session_id: lv_e763e3465bf34f1dab826a263c1eaaaa purpose: gate status: completed outcome: PASS passed_gate: true liveness_score: '0.98' antispoof_score: '0.96' face_similarity: '0.94' gestures_expected: 3 gestures_passed: 3 updated_at: '2026-07-19T14:35:00Z' media: has_selfie: true has_video: false expires_in_sec: 900 selfie_sha256: >- 6f8a3b1c2d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e - role: subject session_id: lv_4cdd3a82903940cebd8cc95a77cdacb3 purpose: media_recapture status: completed outcome: FAIL passed_gate: false liveness_score: '0.98' antispoof_score: '0.59' face_similarity: '0.55' gestures_expected: 3 gestures_passed: 2 reasons: - Smile was not detected. updated_at: '2026-07-19T14:38:00Z' media: has_selfie: true has_video: true frame_gestures: - center - turn_right - smile video_mime_type: video/mp4 expires_in_sec: 900 selfie_sha256: >- a1b2c3d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e8f9 frame_sha256: - >- c3d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e8f9a1b2 - >- d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e8f9a1b2c3 aml: screening_id: 6b7c8d9e-0f1a-4b2c-9d3e-4f5a6b7c8d9e risk_level: medium status: under_review monitor: true screened_at: '2026-07-19T14:50:00Z' sanctions: clear pep: under_review adverse_media: under_review screening_result: has_hits rationale: >- One PEP profile and one adverse media article matched the declared identity. indicators: - key: ind_sanctions hit: false - key: ind_pep hit: true - key: ind_adverse_media hit: true - key: ind_warning hit: false - key: ind_fitness_probity hit: false subject_rows: - key: full_name value: Maria Fernanda Rojas - key: date_of_birth value: '1988-11-02' - key: nationality value: PE matches_total: 1 matches: - name: Maria F. Rojas score: 0.88 match_types: - name_fuzzy - year_of_birth risk_kinds: - pep - adverse_media aliases: - M. Rojas - Maria Rojas Vega identity: - key: date_of_birth value: '1988' - key: nationality value: PE - key: national_id value: 4567**** peps: - name: Advisor, regional government country: PE since: '2018' until: '2021' info: Non-elected advisory role. adverse_media: - title: Local outlet reports contract review published_at: '2020-09-14' source: Diario Local snippet: Regional contract under administrative review. associates: - name: Luis Rojas relation: relative cases: - case_id: CASE-4821 status: closed decision: no_action opened_at: '2026-07-19T14:51:00Z' closed_at: '2026-07-19T15:20:00Z' content_sha256: >- 1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c verification_code: K3c4d5e6f7a8b4c9d8e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5 verification_url: >- https://api.example.com/verify/reports/K3c4d5e6f7a8b4c9d8e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5 '400': description: Invalid format or language (invalid_format, invalid_language). content: application/json: example: error: invalid_format message: format must be pdf or json '401': $ref: '#/components/responses/Unauthorized' '403': description: >- Only company accounts can download reports of their third parties (company_account_required). content: application/json: example: error: company_account_required message: this action requires a company account '404': $ref: '#/components/responses/NotFound' components: responses: Unauthorized: description: Missing or invalid credential (`unauthorized`). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: unauthorized message: invalid or missing credentials NotFound: description: Resource not found (`not_found`). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: not_found message: resource not found schemas: Error: type: object properties: error: type: string description: Machine-readable error code (snake_case). example: insufficient_funds message: type: string description: Human-readable explanation. 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. ````