OAuth scope: payment.write
Verifies multiple payees information by matching IBAN and beneficiary name for each request. Returns match results for each verification request, including success responses and error codes for failed verifications. This endpoint allows processing multiple payee verifications in a single request.
Token requirement
The 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 limits
A 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.
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.
Required only for Sandbox API requests; to get one, please sign up to the Developer Portal.
List of verification requests to be processed in bulk
1 - 400 elementsBulk verification completed (may contain mixed success/error results)
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.
List of verification request results