OAuth scope: payment.write
Verifies payee information by matching IBAN and beneficiary name for internal and external accounts. Returns a match result indicating whether the provided information matches the account holder’s details. In the case of close matches, the matched name is returned.
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.
Rate limits
A verification is only intended to be used before initiating a SEPA transfer. Rate limits will apply to verifications that are not followed by a transfer initiation. Please perform each individual verification before its corresponding transfer.
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.
Verification completed successfully
Result of the payee verification
MATCH_RESULT_MATCH, MATCH_RESULT_NO_MATCH, MATCH_RESULT_CLOSE_MATCH, MATCH_RESULT_NOT_POSSIBLE, MATCH_RESULT_UNSPECIFIED "MATCH_RESULT_MATCH"
The actual name associated with the account (present for close matches)
"Jon Jones"
Token ensuring verification of payee was performed for the beneficiary in the request. This token must be used to initiate a transfer to this beneficiary, validation will fail otherwise. The token can be used regardless of the VOP match result.