---
title: "Create payee verification requests in bulk"
method: POST
path: "/bulk_actions/payee_verification_requests"
tags: ["payee-verification-requests"]
---

# Create payee verification requests in bulk

`POST /bulk_actions/payee_verification_requests`

Create up to 5,000 payee verification requests in a single bulk action. Requests are processed asynchronously and you can choose whether to fail immediately on validation errors, or process valid items while marking invalid ones as failed.

## Request body

- BulkActionCreation — Details required to create a bulk action for payee verification requests.
  - `fail_on_validation_error` boolean — If true, all items must pass validation or the request returns a 400 error. If false, items that fail validation are marked as failed, and valid items are processed. Default is true.
  - `items` BulkActionItem[], required — Array of payee verification requests to create in bulk.
    - `idempotency_key` string — Optional idempotency key for this specific item.
    - `scheme` 'vop', required — The scheme on which the request will be sent. Only `vop` is supported today.
    - `payee_identification_type` 'name' | 'inac' | 'legal_entity_identifier' | 'business_identification_code' | 'bank_identification' | 'central_bank_identification' | 'clearing_house_identification' | 'company_incorporation_number' | 'company_identification' | 'customer_number' | 'duns_number' | 'employee_number' | 'global_location_number' | 'siren' | 'siret' | 'tax_number' | 'business_domain_identification' | 'other_identification' | 'proprietary_code', required — The type of identification used in the request. See Supported identification type for more information.
    - `payee_identification` string, required — The identification of the payee.
    - `payee_account_number` string, required — The account number of the payee. Must be an IBAN.
    - `payee_additional_information` string — Additional information about the payee.
    - `requesting_agent_bank_code` string — The BIC11 you want to use to send your request.
    - `metadata` CommonMetadata — Additional client data in JSON format. See [Metadata](https://docs.numeral.io/reference/metadata).

## Response `200`

Successfully created bulk action

- BulkActionDetails
  - `id` string, required — The bulk action ID.
  - `object` string, required — Type of the object, `bulk_action`.
  - `target_object` 'payment_order' | 'internal_account', required — The object related to the bulk action.
  - `action` 'create' | 'approve' | 'cancel', required — The action to execute on the items included in the bulk action. If `target_action` is `payment_order`, can be `create`, `approve` or `cancel`. If `target_action` is `internal_account`, can be `create`.
  - `status` 'created' | 'processing' | 'executed', required — The status of the bulk action. Either created, processing, or executed.
  - `total_items` integer, required — The number of items included in the bulk action.
  - `total_successful` integer, required — The number of items successfully processed.
  - `total_failed` integer, required — The number of items that failed to be processed.
  - `processed_at` string, date-time, nullable, required — The UTC timestamp when the bulk action was processed.
  - `created_at` string, date-time, required — The UTC timestamp of the creation of the bulk action.

## Other responses

- `400` — Validation error.
- `500` — Internal server error.

---

[API](https://skmtc.net/numeral/apis/payments.md) · [All operations](https://skmtc.net/numeral/apis/payments/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/numeral/payments/versions/220f101cc2ef/schema)