Italian Version

Information related to the API Package: Payments | Money Transfers (v4.1) by Banca Sella

The following article contains information on how to integrate APIs related to the Verification of Payee (VoP) Service within the Money Transfer package.

Please note that the decision whether or not to apply Verification of Payee in your API flows must be expressly communicated to your Sella Branch/Sales Office, which will provide the appropriate documentation in order to correctly track the Customer's intention to use this control tool.

Introduction

The Verification of Payee (VoP) allows checking the correspondence between the IBAN and the beneficiary's name (or other identifiers such as VAT number / LEI Code in the case of transfers between companies) indicated by the payer of a transfer before authorizing the sending of funds to the recipient. The service is active for both instant transfers and ordinary transfers between banks within the European area (headquartered in an EU Member State whose currency is the euro).

How it works

1. Payment creation: when a customer initializes a payment, they enter the beneficiary's name (or other identifiers such as VAT number or LEI code) together with the payment account identifier (IBAN).
2. Beneficiary verification: before authorizing the operation, a VoP request is sent to the beneficiary's bank to verify if the IBAN and the beneficiary's name (or other identifiers such as VAT number or LEI code) match.
3. Beneficiary verification results: the service returns one of the following possible results:
   • MATCH: the beneficiary's name (or other identifiers such as VAT number or LEI code) matches the account holder of the credit account.
   • CLOSE MATCH: the provided name is similar but not identical to the account holder's name.
   • NO MATCH: what indicated by the payer does not correspond with the account holder of the credit account.
   • NOT APPLICABLE: it was not possible to proceed with the verification.
4. Execution of the payment order: in the case of MATCH, CLOSE MATCH and NOT APPLICABLE results, the payment order will be executed without requesting further authorization from the customer. However, in the case of NO MATCH, the order will not be executed unless the customer expresses a different wish.

For more information on the VoP scheme within the SEPA area, you can visit the EPC (European Payments Council) website at this link.

Variations on API integration flows

This paragraph describes the alternatives available to clients.

CASE 1: Requesting the execution of the Verification of Payee (VoP)

In order to obtain greater control and security in the execution of money transfers from the transfer system, it is recommended to perform VoP verification by evaluating the following header:

• X-VoP-Force-Verification: if set to true, the header indicates to execute the VoP verification for the related call.

If not specified, the default value of the header is false(i.e., no Verification of Payee is executed).

In this scenario, the POST Create Money Transfer API returns a ‘400 - Bad Request’ error if the Verification of Payee result is NO MATCH, and the payment order will not be executed.

The following schema shows a use case of the X-VoP-Force-Verification header.

If, during the request to execute a transfer, a 400 Bad Request error is returned, it is still possible to force the execution of the same with the request through the POST Create Money Transfer API, using the same request body and setting the following header:

• X-VoP-Id: containing the ID contained in the vopResponse result of the previous call.

If not specified, the default value of the header is null. The system verifies the correspondence of the previously provided data with the new request and in case of match, the transfer is executed. The following schema shows the interaction in the case of using the X-VoP-Id header.

CASE 2: Not performing the Verification of Payee (VoP)

The customer may request that the VoP verification not be carried out when executing transfers via API (Money Transfer). For those who implemented the Fabrick API before 9 October 2025, no technological adjustments will be necessary to exclude the application of the VoP; however, it will be necessary to contact your sales representative in order to make your decision on the VOP verification usage clear.

Integration environments

The VoP service will soon be available in the following environments to support the development lifecycle: