Skip to main content
POST
Bulk verify SEPA payees
Authentication: API key OAuth 2.0
Scope: payment.write Sensitive
Related guide: Verification of Payee
You can also use the Sandbox environment to test the endpoint with mocked IBANs.
Token requirementThe proof_token included in the response is required for initiating a SEPA transfer and will be valid regardless of the verification result. Please review the response, results that are not a MATCH_RESULT_MATCH may indicate a transfer will be sent to a wrong beneficiary. Please note the token will only be valid for the exact set of IBANs included in this request.
Rate limitsA verification is only intended to be used before initiating SEPA transfers. Rate limits will apply to verifications that are not followed by a transfer initiation. Please perform verification for transfers that will be initiated shortly.

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)

proof_token
object
required

Token ensuring verification of payee was performed for the set of requests. This token must be used to initiate a bulk transfer to the exact same set of payees, validation will fail otherwise. The token can be used regardless of the VOP match result.

requests
object[]
required

List of verification request results