> ## Documentation Index > Fetch the complete documentation index at: https://docs.fintoc.com/llms.txt > Use this file to discover all available pages before exploring further. # List account verifications > Lists the account verifications of your organization for the mode (`live` or `test`) of the API key used. Filter by `account_number`, `transfer_id`, or by date range with `since` and `until`. The list is paginated. Use the `starting_after`, `ending_before`, and `limit` query parameters to move through the list. The `Link` response header carries the URLs to navigate the paginated list. **`v2`** ยท Base URL `https://api.fintoc.com/v2` ## OpenAPI ````yaml reference/pacioli-api.json GET /account_verifications openapi: 3.1.0 info: title: Fintoc API version: v2026-02-01 servers: - url: https://api.fintoc.com/v2 security: [] paths: /account_verifications: get: tags: - Account verifications summary: List account verifications description: >- Lists the account verifications of your organization for the mode (`live` or `test`) of the API key used. Filter by `account_number`, `transfer_id`, or by date range with `since` and `until`. The list is paginated. Use the `starting_after`, `ending_before`, and `limit` query parameters to move through the list. The `Link` response header carries the URLs to navigate the paginated list. operationId: account-verifications-list parameters: - name: account_number in: query required: false schema: type: string description: >- Counterparty account number to filter by. Use the standardized Mexican bank account number (CLABE). - name: transfer_id in: query required: false schema: type: string description: >- Identifier of the verification transfer to filter by. Returns the account verification linked to this transfer. - name: since in: query required: false schema: type: string format: date-time example: '2026-01-01T00:00:00Z' description: >- Lower bound for the creation date. Returns account verifications created on or after this ISO 8601 datetime in UTC. - name: until in: query required: false schema: type: string format: date-time example: '2026-03-31T23:59:59Z' description: >- Upper bound for the creation date. Returns account verifications created on or before this ISO 8601 datetime in UTC. - name: starting_after in: query required: false schema: type: string example: accv_2rNxBkOrlHoOYsZTyQYhA0o8Ek0 description: >- Cursor that fetches the next page of account verifications. Use the ID of the last account verification from the current page. - name: ending_before in: query required: false schema: type: string example: accv_2rNxBkOrlHoOYsZTyQYhA0o8Ek0 description: >- Cursor that fetches the previous page of account verifications. Use the ID of the first account verification from the current page. - name: limit in: query required: false schema: type: integer example: 50 description: >- Maximum number of account verifications to return per page. Ranges from `1` to `300`. Defaults to `30`. responses: '200': description: List of account verifications for the current mode. headers: Link: schema: type: string description: URLs to navigate the paginated list, as defined by RFC 8288. content: application/json: examples: account_verifications_list: value: - id: accv_2daFu0zqqDtZGJaSi2TGI2Mm1nN object: account_verification counterparty: account_number: '132969000000000190' account_type: clabe holder_id: '000000000' holder_name: Test Customer 1 institution: id: '40012' name: BBVA Mexico country: mx mode: test reason: null receipt_url: null status: succeeded transaction_date: '2026-03-01T12:00:00.000Z' transfer_id: tr_2daFu0zqqDtZGJaSi2TGI2Mm1nN schema: type: array items: $ref: '#/components/schemas/account_verification' '401': description: Invalid or missing API key. content: application/json: examples: invalid_api_key: value: error: type: authentication_error code: invalid_api_key message: 'Invalid API Key: invalid-*oken' schema: $ref: '#/components/schemas/error_object' '403': description: Account verifications are available only for Mexico organizations. content: application/json: examples: account_verifications_not_available: value: error: code: invalid_account_verification message: >- Unable to get account verifications. Action not available in your region schema: $ref: '#/components/schemas/error_object' security: - api_key: [] components: schemas: account_verification: type: object properties: id: type: string description: Unique identifier of the account verification. example: accv_2daFu0zqqDtZGJaSi2TGI2Mm1nN object: const: account_verification description: Type of the object. Always `account_verification`. counterparty: type: object description: Details of the verified counterparty account. properties: account_number: type: string description: >- Account number of the verified counterparty. The 18-digit standardized Mexican bank account number (CLABE). example: '132969000000000190' account_type: type: string description: >- Type of the counterparty account, in lowercase. For Mexican account verifications, `clabe`. example: clabe holder_id: type: - string - 'null' description: >- Tax identifier of the account holder, or `null`. The Mexican tax ID (RFC). example: '000000000' holder_name: type: - string - 'null' description: Name of the account holder, or `null`. example: Test Customer 1 institution: type: object description: Financial institution of the counterparty. properties: id: type: string description: Institution identifier. example: '40012' name: type: string description: Institution name. example: BBVA Mexico country: type: string enum: - mx description: >- ISO 3166-1 alpha-2 country code of the institution, in lowercase. Always `mx`. example: mx required: - id - name - country required: - account_number - account_type - holder_id - holder_name - institution mode: type: string enum: - live - test description: Whether the verification is `live` or `test` data. example: test reason: type: - string - 'null' enum: - transfer_fail - cep_unavailable - non_existing_account - blocked_account - canceled_account - wrong_currency - account_not_from_receiving_institution - missing_information - wrong_payment_type - wrong_operation_type - account_type_does_not_correspond - invalid_character - exceeds_account_limit - exceeds_account_monthly_payments_limit - non_registered_mobile_phone - does_not_accept_non_banxico_payments - invalid_additional_information - missing_payment_instruction_due_to_balance_limit_reached - sender_client_protection_agreement - optional_payment_not_accepted_by_recipient_institution - codi_payment_without_quick_credit_notification - duplicated_tracking_key - expired_sender_institution_certificate - unknown - null description: >- Reason code explaining why the verification failed, or `null` when the verification succeeded. `transfer_fail` means Fintoc could not send the verification transfer. `cep_unavailable` means the Mexican central bank (Banxico) had not yet published the payment receipt (CEP) when the verification timed out, so Fintoc could not confirm the account; you can retry the verification later. `unknown` means the reason could not be determined. The remaining codes mirror the transfer `return_reason` and report why the counterparty institution returned the verification transfer: `non_existing_account`, `blocked_account`, `canceled_account`, `wrong_currency`, `account_not_from_receiving_institution`, `missing_information`, `wrong_payment_type`, `wrong_operation_type`, `account_type_does_not_correspond`, `invalid_character`, `exceeds_account_limit`, `exceeds_account_monthly_payments_limit`, `non_registered_mobile_phone`, `does_not_accept_non_banxico_payments`, `invalid_additional_information`, `missing_payment_instruction_due_to_balance_limit_reached`, `sender_client_protection_agreement`, `optional_payment_not_accepted_by_recipient_institution`, `codi_payment_without_quick_credit_notification`, `duplicated_tracking_key`, and `expired_sender_institution_certificate`. example: null receipt_url: type: - string - 'null' description: URL of the verification receipt, or `null`. example: null status: type: string enum: - pending - succeeded - failed description: >- Status of the verification. One of `pending` (in progress), `succeeded` (ownership confirmed), or `failed` (could not be completed). example: pending transaction_date: type: - string - 'null' format: date-time description: >- Date and time when the verification was performed, as an ISO 8601 datetime in UTC, or `null`. example: null transfer_id: type: - string - 'null' description: Identifier of the transfer issued to verify the account, or `null`. example: tr_2daFu0zqqDtZGJaSi2TGI2Mm1nN required: - id - object - counterparty - mode - reason - receipt_url - status - transaction_date - transfer_id error_object: type: object properties: error: type: object description: Details of the error that caused the request to fail. properties: code: type: string description: >- Machine-readable code identifying the specific error, for example `invalid_request`. example: invalid_request doc_url: type: string description: >- URL of a documentation page with more details about the error. Not returned by every error. example: https://docs.fintoc.com/reference/errors message: type: string description: Human-readable message describing the error. example: 'Missing required param: account_id' param: type: - string - 'null' description: >- Name of the request parameter that caused the error. Not returned by every error. example: account_id type: type: string description: >- Category of the error, for example `invalid_request_error` or `authentication_error`. Not returned by every error. example: invalid_request_error required: - code - message required: - error securitySchemes: api_key: type: apiKey name: Authorization in: header ````