The Account Holder Verification (AHV) endpoint allows for the verification of an account holder's identity before initiating a payment.

This helps reduce fraud and prevents payments from being misdirected, ensuring that payments are either sent to the correct recipient or debited from the correct payer account before processing.

The AHV will support two verification types depending on the payment method:

• Confirmation of Payee (CoP): used for GBP payments via Faster Payments
• Verification of Payee (VoP): used for EUR payments via SEPA. Support of VoP requests via the API will be available in the beginning of October, 2025, and available for testing in the sandbox during September, 2025.

How it works

After you have submitted an AHV request, we will verify the provided details through either the VoP scheme or CoP service. You can get the result of the verification via the Webhook service, the AccountHolderVerification event type, or by calling the AHV GET endpoint. The result will indicate whether the provided details generate a Match, a Close Match, No Match, or anError.

See the request example and response example for implementation details.

The response also includes a reason code that provides further details on the verification result.

Request Rules

When making a request, the following rules apply:

• Either individualFullName or companyName must be provided - only one of the options should be provided
• Either bban (for CoP) or iban (for VoP) must be provided — not both

Verification results

When the result of the VoP or CoP is available (status is succeeded or failed), the result object will be populated in the AHV GET endpoint and in the Webhook payload.

Details of each property in the result object

Reason Codes

The reason codes in the response payload provide additional context on the verification result, indicating the level of match or any issues identified during the verification process.