POST
/
v2
/
sepa
/
bulk_verify_payee
Bulk verify SEPA payee
curl --request POST \
  --url https://thirdparty.qonto.com/v2/sepa/bulk_verify_payee \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "requests": [
    {
      "id": "req_001",
      "beneficiary_name": "John Doe",
      "iban": "FR1420041010050500013M02606"
    },
    {
      "id": "req_002",
      "beneficiary_name": "Jane Smith",
      "iban": "GB82WEST12345698765432"
    },
    {
      "id": "req_003",
      "beneficiary_name": "ACME Corp",
      "iban": "DE89370400440532013000"
    }
  ]
}'
{
  "proof_token": "proof_1234567890abcdef",
  "requests": [
    {
      "id": "req_001",
      "response": {
        "match_result": "MATCH_RESULT_MATCH"
      }
    },
    {
      "id": "req_002",
      "response": {
        "match_result": "MATCH_RESULT_CLOSE_MATCH",
        "matched_name": "J. Smith"
      }
    },
    {
      "id": "req_003",
      "error_code": "BAD_REQUEST_ERROR_RESPONDING_BANK_NOT_AVAILABLE"
    }
  ]
}

Authorizations

​
Authorization
string
header
required

Bearer authorization header: Bearer <token>, where <token> is the access token received from the authorization server at the end of the OAuth 2.0 flow.

Headers

​
X-Qonto-Staging-Token
string

Required only for Sandbox API requests; to get one, please sign up to the Developer Portal.

Body

application/json
​
requests
object[]
required

List of verification requests to be processed in bulk

Required array length: 1 - 400 elements

Response

Bulk verification completed (may contain mixed success/error results)

​
requests
object[]
required

List of verification request results

​
proof_token
string
required

Token representing proof of any verification attempt (successful or failed) of a payee's details in bulk verification. This token is only valid for the entire bulk request, not for individual requests within it. The token is valid for 23 hours to initiate a bulk transfer. This limit might change depending on further security considerations.

Example:

"proof_1234567890abcdef"