# Caliza Documentation

> Documentation for Caliza

## Guides
- [Introduction to Caliza](https://docs.caliza.com/docs/what-is-caliza.md)
- [Caliza Core Concepts](https://docs.caliza.com/docs/calizas-core-concepts.md)
- [Coverage](https://docs.caliza.com/docs/coverage.md)
- [Authenticate](https://docs.caliza.com/docs/authenticate.md)
- [Get the Integrator ID](https://docs.caliza.com/docs/get-the-integrator-id.md)
- [Create a Beneficiary](https://docs.caliza.com/docs/create-beneficiaries.md)
- [Create USD Virtual Accounts](https://docs.caliza.com/docs/create-virtual-accounts.md)
- [Create Recipients](https://docs.caliza.com/docs/manage-recipients.md)
- [Send Your First Payment](https://docs.caliza.com/docs/send-your-first-payment.md)
- [Webhooks](https://docs.caliza.com/docs/webhooks.md): Real-time notifications for transaction and beneficiary lifecycle events
- [Beneficiaries](https://docs.caliza.com/docs/manage-beneficiaries.md)
- [Related Persons](https://docs.caliza.com/docs/related-persons.md)
- [KYC/KYB Verification](https://docs.caliza.com/docs/kyc-kyb-verification.md)
- [Payments](https://docs.caliza.com/docs/payments.md)
- [Exchanges](https://docs.caliza.com/docs/exchanges.md)
- [FX Rate Locks](https://docs.caliza.com/docs/fx-rate-locks.md)
- [Stablecoin Deposits](https://docs.caliza.com/docs/stablecoin-deposits.md)
- [Retrieving Transactions and Payments](https://docs.caliza.com/docs/retrieving-transactions-and-payments.md)
- [Internal Transfers](https://docs.caliza.com/docs/internal-transfers.md): Move funds between beneficiaries within the same integrator account
- [Account Sweeps](https://docs.caliza.com/docs/account-sweeps.md)
- [Fiat Deposits](https://docs.caliza.com/docs/fiat-deposits.md)
- [Webhook Events](https://docs.caliza.com/docs/webhook-events.md): Complete reference of all webhook event types and their payloads
- [Webhook Signature Validation](https://docs.caliza.com/docs/webhook-signature-validation-guide.md): How to verify the authenticity of incoming webhook requests
- [API Error Catalog](https://docs.caliza.com/docs/api-error-catalog.md): Complete reference of error codes and validation errors across all API endpoints
- [Mock Fiat Deposits](https://docs.caliza.com/docs/mock-fiat-deposits.md)
- [Mock Stablecoin Deposits](https://docs.caliza.com/docs/mock-stablecoin-deposits.md)

## API Reference
- [Overview](https://docs.caliza.com/reference/overview.md)
- [Authentication](https://docs.caliza.com/reference/authentication-1.md)
- [Response Codes](https://docs.caliza.com/reference/response-codes.md)
- [Simulate transaction or payment](https://docs.caliza.com/reference/createsimulation_1.md): Creates a simulation to preview and calculate all costs associated with a transaction before executing it. The simulation returns estimated total costs, itemized fees, exchange rates (if currency conversion is involved), expected settlement time, and any compliance requirements. Simulations are typically valid for 24 hours, after which exchange rates may change and a new simulation should be created. Always create a simulation before executing a transaction to show users accurate costs and get a simulation ID required for transaction creation. For more detailed breakdowns, consider using the v2 simulation endpoint.
- [Create new transaction](https://docs.caliza.com/reference/createtransaction.md): Initiates a new financial transaction including payments, payouts, or currency conversions between accounts. Before calling this endpoint, you must create a simulation to preview fees and exchange rates. The simulation ID is required and must be valid (not expired, typically valid for 24 hours). Once created, the transaction moves through various statuses (CREATED, PROCESSING, COMPLETED, FAILED) which can be tracked via webhooks or polling.
- [Retrieve a simulation](https://docs.caliza.com/reference/getsimulationbyid.md): Retrieves the details of a previously created transaction simulation including estimated fees, exchange rates, settlement times, and total costs. Use this to review simulation parameters before executing the actual transaction. Simulations are typically valid for 24 hours from creation.
- [Retrieve transaction details](https://docs.caliza.com/reference/gettransactionbyid.md): Retrieves comprehensive information about a specific transaction including current status with timestamp (created, processing, completed, failed, cancelled), source and destination details, original amount and currency, converted amount if applicable, all applied fees with breakdown, exchange rates used, payment method/rail, blockchain transaction hash if crypto, expected and actual settlement times, error messages and codes if failed, and full audit trail of status changes. Use this for transaction tracking, customer support, accounting reconciliation, or displaying transaction history.
- [Download proof of payment document](https://docs.caliza.com/reference/gettransactionproofofpayment.md): Downloads the proof of payment document for a specific transaction in the specified format. If no format type is specified, the system will auto-detect the appropriate format based on transaction properties.
- [Execute batch payout](https://docs.caliza.com/reference/payouts.md): Processes multiple payout transactions in a single batch operation, efficiently distributing funds to multiple recipients according to defined amounts and settlement methods. This is ideal for use cases like payroll, affiliate commissions, marketplace seller payments, or any scenario where you need to pay multiple parties simultaneously. Batch processing typically results in lower fees and faster processing compared to individual transactions.
- [List transactions](https://docs.caliza.com/reference/getalltransactions.md): Retrieves a paginated list of transactions associated with your integrator account. Use query parameters to filter by beneficiary, currency, status, date range, and amount range. Results are returned in a paginated format with sorting support. This endpoint is useful for building transaction history views, reconciliation workflows, and monitoring transaction statuses.
- [Retrieve transaction simulation (v2)](https://docs.caliza.com/reference/getsimulationbyidv2.md): Retrieves the details of a previously created transaction simulation with enhanced v2 data including detailed fee breakdown by type (network fees, service fees, conversion fees), step-by-step conversion details for multi-hop currency paths, and specific compliance requirements. Use v2 simulations when you need more granular cost transparency or are working with complex multi-currency conversion scenarios.
- [Retrieve transaction with documents](https://docs.caliza.com/reference/gettransactionbyidwithdocuments.md): Retrieves complete transaction details along with all attached supporting documents including invoices, receipts, contracts, proof of payment PDFs, and any compliance-related files. Use this when you need to download transaction records with full documentation for audit purposes, accounting reconciliation, or customer support inquiries. Documents are returned as base64-encoded data or download URLs.
- [Upload a supporting document to a transaction](https://docs.caliza.com/reference/uploaddocument.md): Attaches a single supporting document to an existing transaction and triggers document validation. Use this to provide documentation after a transaction has been created — most importantly to satisfy or retry a transaction that is held for document review. Documents cannot be uploaded once a transaction has reached a final state.
- [Create transaction with supporting documents](https://docs.caliza.com/reference/createtransaction_1.md): Initiates a new transaction and simultaneously attaches required supporting documentation. This is particularly important for high-value transactions, cross-border payments, or transactions requiring compliance documentation. Accepted documents include invoices (for goods/services payment proof), contracts (for agreement evidence), proof of goods/services delivery, import/export licenses, or regulatory certificates. Documents should be uploaded as multipart form-data. Maximum file size and supported formats depend on your integrator configuration.
- [Get deposit instructions](https://docs.caliza.com/reference/getdepositinstructions.md): Retrieves detailed, step-by-step instructions for a beneficiary to deposit funds using the specified payment rail. Returns beneficiary-specific bank account details (account number, routing number), reference codes that must be included in the transfer, required documentation, transfer amount limits, expected processing times, any fees charged by intermediary banks, and special notes for the selected payment method. These instructions can be displayed to users or sent via email to guide them through the deposit process.
- [Execute account sweep payout](https://docs.caliza.com/reference/sweeppayouts.md): Automatically consolidates and transfers available balances from multiple beneficiary accounts to a designated destination account in a single operation. This is commonly used for treasury management, revenue collection, or balance consolidation. You can sweep all beneficiaries or specify a subset. The destination can be a master account, external bank account, or cryptocurrency wallet. Sweep operations are atomic - either all transfers succeed or all fail. Useful for end-of-day settlements, collecting marketplace fees, or pooling funds.
- [Simulate transaction or payment (v2)](https://docs.caliza.com/reference/createsimulation.md): Creates an enhanced v2 transaction simulation that calculates and previews all costs, exchange rates, and requirements before executing a transaction. The v2 version provides more detailed breakdowns including itemized fees (network fees, service fees, FX fees), step-by-step multi-currency conversion paths for complex transactions, compliance requirements based on amount and destination, and improved exchange rate accuracy. Simulations are valid for 24 hours and should be used to show users exact costs before they confirm a transaction. Use v2 for better transparency and accuracy, especially for cross-border or multi-hop currency conversions.
- [Export transactions to CSV](https://docs.caliza.com/reference/getalltransactions_1_1.md): Generates and downloads a CSV file containing all transactions matching the specified filter criteria (date range, status, currency, beneficiary, etc.). The CSV includes transaction details, amounts, fees, timestamps, and status information. This is useful for accounting reconciliation, financial reporting, tax preparation, and integration with external accounting systems. Supports pagination for large datasets.
- [Simulate SPEI deposit (sandbox)](https://docs.caliza.com/reference/createfakespeiindeposit.md): Creates a simulated SPEI (Sistema de Pagos Electrónicos Interbancarios - Mexican interbank electronic payment system) deposit for testing purposes in the sandbox environment. This allows you to test deposit flows, balance updates, and webhook notifications without processing real funds or connecting to actual Mexican banking infrastructure. Only available in sandbox mode.
- [Simulate PIX deposit (sandbox)](https://docs.caliza.com/reference/createfakepixindeposit.md): Creates a simulated PIX (Pix Instant Payment - Brazilian instant payment system) deposit for testing deposit flows, balance updates, and webhook notifications in the sandbox environment. PIX is Brazil's instant payment infrastructure. This endpoint allows you to test the complete deposit lifecycle without real funds or connecting to the Brazilian Central Bank's PIX network. Only available in sandbox mode.
- [Simulate USD deposit (sandbox)](https://docs.caliza.com/reference/createfakeusddeposit.md): Creates a simulated USD deposit via wire transfer for testing international payment flows, balance updates, and webhook notifications in the sandbox environment. This simulates deposits from U.S. banks or international wire transfers. Use this to test your deposit handling logic, webhook processing, and balance reconciliation without processing actual funds or connecting to real banking infrastructure. Only available in sandbox mode.
- [Simulate crypto deposit (sandbox)](https://docs.caliza.com/reference/createfakecryptodeposit.md): Creates a simulated cryptocurrency deposit arriving at a DFNS wallet in the sandbox environment. Use this to test crypto deposit detection, balance updates, webhook notifications, and any custom business logic that triggers on incoming blockchain transactions. Specify the beneficiary, wallet address, amount, blockchain network, and currency. Only available in sandbox mode.
- [Simulate PIX payout confirmation (sandbox)](https://docs.caliza.com/reference/createfakepixindeposit_1.md): Triggers a simulated webhook event notification for PIX payout confirmation in the sandbox environment. Use this to test your webhook handlers for successful payout completion, verify your webhook processing logic handles PIX payout confirmations correctly, and test your user notification flows without waiting for real PIX network confirmations. This simulates the webhook that would be sent when a real PIX payout is confirmed by the Brazilian payment infrastructure. Only available in sandbox mode.
- [Create payment with supporting documents](https://docs.caliza.com/reference/createpaymentwithdocuments.md): Initiates a new payment transaction and attaches required supporting documentation such as invoices, receipts, purchase orders, commercial agreements, or proof of goods/services. This is particularly important for high-value transactions or cross-border payments that require additional compliance documentation. Documents should be provided as multipart form-data attachments.
- [Create new payment](https://docs.caliza.com/reference/createpayment.md): Initiates a payment transaction to transfer funds between accounts or to external recipients. Before calling this endpoint, you must first create a simulation using the /v1/simulations or /v2/simulations endpoint to get estimated fees and exchange rates. The simulation ID is required in the request. This endpoint processes the payment according to the simulated parameters and returns a transaction object with status tracking information.
- [Get payment instructions](https://docs.caliza.com/reference/getpaymentinstructions.md): Retrieves detailed, step-by-step payment instructions for a beneficiary to deposit funds using the specified payment rail. Instructions include recipient bank details (account number, routing number, SWIFT/BIC), reference codes to include in the transfer, required documentation, transfer limits, processing times, and any special notes. Use this to generate deposit instructions that you can display to end users or send via email.
- [Update payment blockchain hash](https://docs.caliza.com/reference/updatetransactionhash_1.md): Associates a blockchain transaction hash (transaction ID) with a payment deposit record, enabling on-chain verification and providing immutable proof of cryptocurrency payment execution. After a user deposits cryptocurrency, use this endpoint to link their on-chain transaction to their account balance update. This allows users to verify their payment on blockchain explorers and provides transparent audit trails.
- [Retrieve payment details](https://docs.caliza.com/reference/gettransactionbyid_1.md): Retrieves complete information about a specific payment transaction including current status (created, processing, completed, failed), amounts sent and received, applied fees and exchange rates, recipient details, beneficiary information, payment method used, timestamps for each stage, and any error messages if the payment failed. Use this to track payment progress or for customer support inquiries.
- [Retrieve beneficiary details](https://docs.caliza.com/reference/getbeneficiary.md): Retrieves all information about a specific beneficiary including personal or business details, KYC/KYB verification status, account status, balances, and associated metadata. Use this to check a beneficiary's current state, verification progress, or account information before initiating transactions.
- [Update beneficiary information](https://docs.caliza.com/reference/updatebeneficiary.md): Modifies existing beneficiary details such as contact information, addresses, identification documents, or business data. Use this when a beneficiary's information changes (such as a new address, phone number, or business registration details). All updates undergo validation and may trigger additional compliance checks if sensitive fields are modified.
- [Remove beneficiary](https://docs.caliza.com/reference/deletebeneficiary.md): Permanently deletes a beneficiary from the system. This action cannot be undone and will remove all associated data including virtual accounts, wallet addresses, and preferences, except for transaction history and audit records required by regulation. Beneficiaries with pending transactions or non-zero balances cannot be deleted.
- [Retrieve multi-currency balance details](https://docs.caliza.com/reference/getbeneficiarydetailedbalancebycurrencies.md): Returns comprehensive balance information across multiple currencies for a specific beneficiary. For each requested currency, this endpoint provides available balance (funds ready for withdrawal), pending balance (funds in processing), and reserved balance (funds held for pending transactions). Use this when you need a complete financial overview of a beneficiary across different currencies or before initiating multi-currency operations.
- [Record terms and conditions acceptance](https://docs.caliza.com/reference/accepttermsandconditions.md): Registers a beneficiary's explicit acceptance of the platform's terms and conditions, creating an auditable record of consent with timestamp, IP address, and version information. This is typically required before a beneficiary can initiate their first transaction or access certain platform features. The acceptance is legally binding and stored for regulatory compliance.
- [Enable beneficiary account](https://docs.caliza.com/reference/enablebeneficiary.md): Activates a previously disabled beneficiary account, restoring full access to all platform features and transaction capabilities. Use this when re-enabling an account that was temporarily suspended for security review, compliance hold, or at the user's request. Once enabled, the beneficiary can immediately resume transacting.
- [Disable beneficiary account](https://docs.caliza.com/reference/disablebeneficiary.md): Temporarily suspends a beneficiary account, immediately preventing new transactions from being initiated while preserving all existing data, transaction history, and pending transactions for compliance and audit purposes. This is reversible via the enable endpoint. Use this for security holds, compliance reviews, or when a user requests account suspension.
- [List beneficiary virtual accounts](https://docs.caliza.com/reference/listvirtualaccounts.md): Retrieves all virtual accounts associated with a beneficiary. Virtual accounts are unique account numbers assigned to a beneficiary for receiving funds in specific currencies. Each virtual account includes account number, routing information, currency, status (active/inactive), and the payment rails it supports (ACH, Wire, PIX, SPEI, etc.). Use this to display deposit instructions to users.
- [Generate new virtual account](https://docs.caliza.com/reference/createvirtualaccount.md): Creates a new virtual account for the beneficiary in the specified currency and region. Virtual accounts enable beneficiaries to receive funds through unique account identifiers (account number + routing number) without having an actual bank account. Each virtual account is tied to a specific currency and can receive deposits via supported payment rails. You can create multiple virtual accounts per beneficiary for different currencies.
- [Retrieve beneficiary account balance](https://docs.caliza.com/reference/getbeneficiarybalance.md): Returns the current balance for a beneficiary's account in the specified currency. The balance includes available funds (ready for withdrawal or payment) and may also show pending transactions that will affect the balance once settled. Use this before initiating transactions to verify sufficient funds or to display balance information in your user interface.
- [List all beneficiaries](https://docs.caliza.com/reference/getall.md): Retrieves a paginated list of all beneficiaries associated with your integrator account. Beneficiaries are the individuals or businesses that can send or receive funds through your platform. Results can be filtered by status (active, inactive, pending verification), type (individual, business), creation date range, or search by name/email. Each result includes beneficiary ID, name, type, status, KYC/KYB verification state, and creation date. Use this for beneficiary management interfaces or to search for specific users.
- [Register new beneficiary](https://docs.caliza.com/reference/savebeneficiary.md): Creates a new beneficiary record for an individual or business with initial KYC/KYB information and account settings. For individuals, provide personal details (name, date of birth, ID number, address). For businesses, include company information (business name, tax ID, incorporation details, beneficial owners). This triggers identity verification workflows based on beneficiary type, transaction thresholds, and regulatory requirements for their jurisdiction. The beneficiary must be verified before they can transact.
- [Retrieve detailed balance breakdown](https://docs.caliza.com/reference/getbeneficiarydetailedbalance.md): Provides a comprehensive, itemized breakdown of a beneficiary's balance in the specified currency. This includes available balance (funds that can be withdrawn immediately), pending balance (deposits or transactions being processed), reserved balance (funds held for pending outgoing transactions), recent transaction history affecting the balance, and projected available balance after pending items settle. Use this for detailed balance reconciliation or to explain balance discrepancies to users.
- [Get or create cryptocurrency wallet](https://docs.caliza.com/reference/findorcreatewallet.md): Retrieves an existing cryptocurrency wallet address for the beneficiary on the specified blockchain network, or automatically creates a new wallet if none exists. Each beneficiary can have multiple wallets (one per blockchain network). The wallet address can be used to receive cryptocurrency deposits. Supported networks include Ethereum (ETH), Polygon, Tron (TRX), Stellar (XLM), Base, and Solana. The wallet is managed by Caliza, so users don't need to manage private keys.
- [Create related person](https://docs.caliza.com/reference/createrelatedperson.md): Creates a new related person for a beneficiary such as a beneficial owner, director, legal representative, or authorized signatory. Provide personal details including name, date of birth, citizenship, government ID, contact information, and residential address. Related persons are required for KYB compliance to identify individuals who own or control the beneficiary entity.
- [List related persons](https://docs.caliza.com/reference/listrelatedpersons.md): Retrieves all related persons associated with a beneficiary including beneficial owners, directors, legal representatives, and authorized signatories. Each entry includes full personal details, contact information, and address. Use this to review compliance information or display all individuals linked to a business beneficiary.
- [Get related person](https://docs.caliza.com/reference/getrelatedperson.md): Retrieves detailed information about a specific related person including personal details, contact information, residential address, and any uploaded compliance documents. Use this to inspect individual related person records for verification or compliance review.
- [Update related person](https://docs.caliza.com/reference/updaterelatedperson.md): Updates the information of an existing related person including personal details, contact information, and residential address. Use this when a related person's information changes or when correcting previously submitted data during the compliance review process.
- [Delete related person](https://docs.caliza.com/reference/deleterelatedperson.md): Removes a related person from a beneficiary's record. Use this when a related person is no longer associated with the beneficiary entity, for example when an owner sells their stake or a director resigns.
- [Upload document for related person](https://docs.caliza.com/reference/addrelatedpersondocument.md): Uploads an identity or compliance document for a specific related person of a beneficiary. Documents can include government-issued IDs (passport, driver's license, national ID), proof of address, or other verification documents. Provide the front of the document as required, and optionally the back. Supported formats include JPG, PNG, and PDF.
- [Retrieve webhook secret key](https://docs.caliza.com/reference/getintegratorwebhooksecret.md): Retrieves the current webhook secret key used to validate webhook signatures from Caliza. Use this secret to verify that webhook notifications genuinely originate from Caliza and haven't been tampered with. Store this secret securely and use it to compute HMAC signatures when validating incoming webhook requests.
- [Rotate webhook secret key](https://docs.caliza.com/reference/updateintegratorwebhooksecret.md): Generates and sets a new webhook secret for enhanced security. Use this periodically to rotate secrets as a security best practice or immediately if you suspect the current secret has been compromised. Warning: After rotation, all webhook signatures using the previous secret will become invalid, so update your webhook verification code immediately after calling this endpoint.
- [Get current integrator profile](https://docs.caliza.com/reference/getme.md): Retrieves complete profile information for the currently authenticated integrator including business details, contact information, configuration settings, enabled features, webhook URLs, and account status. Use this to display integrator information in your application, verify configuration, or check account capabilities before initiating operations.
- [Update integrator profile](https://docs.caliza.com/reference/updateme.md): Modifies integrator account information such as business details, contact information (email, phone), banking preferences, notification settings, and webhook configurations. Some fields may require additional verification if they impact compliance or financial operations. Changes to critical fields may trigger a review process before taking effect.
- [Retrieve integrator account balances](https://docs.caliza.com/reference/getintegratorbalances.md): Returns current balance information across all currencies and accounts associated with the integrator. For each currency, this shows available balance (funds ready for use), pending balance (funds being processed), and reserved balance (funds held for pending transactions). Use this to monitor your platform's liquidity, track fund flows, or implement balance alerts and treasury management.
- [Get webhook configuration](https://docs.caliza.com/reference/getintegratorwebhooks.md): Retrieves the currently configured webhook URL and event subscription settings. Webhooks enable real-time event notifications from the Caliza platform to your application. The configuration includes the webhook endpoint URL, enabled event types (transaction status changes, KYC updates, balance changes, etc.), retry settings, and last delivery status. Use this to verify your webhook configuration or debug delivery issues.
- [Configure webhook endpoint](https://docs.caliza.com/reference/updatewebhookconfig.md): Sets or updates the webhook URL and event subscription preferences for receiving automated, real-time notifications about platform events. Configure which events trigger webhooks (transaction completed, beneficiary verified, payment failed, balance updated, etc.), the HTTPS endpoint URL where notifications should be sent, and retry behavior. Your webhook endpoint must respond with 200 OK within 5 seconds and should validate webhook signatures using your webhook secret.
- [List integrator capabilities](https://docs.caliza.com/reference/getcapabilitiesbyintegratorid.md): Retrieves all enabled features, permissions, and access levels for your integrator account. This includes supported currencies (fiat and crypto), available transaction types (payments, payouts, conversions), payment rails (WIRE, ACH, PIX, SPEI, blockchain networks), regional availability, transaction limits, and any special features enabled for your account. Use this to dynamically adjust your UI based on available capabilities or to validate operations before attempting them.
- [List all recipients](https://docs.caliza.com/reference/getrecipients.md): Retrieves a paginated list of all saved payment recipients for a specific beneficiary. Recipients are individuals or businesses that have been registered as payout destinations. Each recipient includes bank account details, contact information, recipient type (individual/business), supported currencies, and verification status. Use this to display saved recipients in a 'send money' interface or recipient management screen.
- [Register new recipient](https://docs.caliza.com/reference/createrecipient.md): Creates a new payment recipient profile with complete bank account details, contact information, and payment preferences. Recipients are destinations where you can send payouts. Include details like bank name, account number, routing number (or equivalent), SWIFT/BIC for international transfers, recipient address, and currency. Once created, the recipient can be used repeatedly for future transactions without re-entering bank details.
- [Retrieve recipient details](https://docs.caliza.com/reference/getrecipient.md): Retrieves complete information about a specific saved recipient including full name (individual) or business name, bank account details (account number, routing number, SWIFT/BIC), contact information (email, phone), recipient address, supported currencies, verification status, number of transactions sent to this recipient, total amount sent, and last transaction date. Use this to review recipient information before sending a payment.
- [Update recipient information](https://docs.caliza.com/reference/updaterecipient.md): Modifies existing recipient details such as bank account information (if bank changed accounts), contact details (email, phone), recipient address, or payment preferences. Sensitive changes like bank account numbers are validated and may require additional verification. Some changes might put the recipient in a pending verification state until the new details are confirmed. This does not affect past transactions.
- [Remove recipient](https://docs.caliza.com/reference/deleterecipient.md): Permanently deletes a recipient from your saved recipients list. This only removes the recipient profile - all past transactions with this recipient will remain in your transaction history for audit and accounting purposes. The recipient cannot be recovered after deletion, so you would need to re-create them if needed in the future. Recipients cannot be deleted if they have pending transactions.
- [Create verification](https://docs.caliza.com/reference/createverification.md): Creates an interactive KYC or KYB verification session for a beneficiary. The system determines whether to run KYC (for individuals) or KYB (for businesses) based on the beneficiary type. Returns a verification URL where the end user must be redirected to complete identity verification with a third-party provider. If an active verification session already exists, the existing session is returned.
- [Get verification status](https://docs.caliza.com/reference/getverificationstatus.md): Retrieves the current verification status for a beneficiary. Returns the verification session details including the current status, verification URL (if still pending), and timestamps. Use this endpoint to poll for verification progress after redirecting the user to the verification URL.
- [Approve verification (sandbox)](https://docs.caliza.com/reference/approveverificationsandbox.md): Manually approves a KYX verification in sandbox environments without going through the third-party verification provider. After approval, the beneficiary status is updated and all downstream flows are triggered normally. Only available in sandbox environments.
- [Retrieve T&C document](https://docs.caliza.com/reference/gettermsandconditions.md): Retrieves the current version of the platform's terms and conditions document in PDF or HTML format. The response includes the version number and effective date for compliance tracking and audit purposes. Use this to display terms to users before they accept, or to retrieve the specific version that a user accepted for regulatory record-keeping.