Verification of Payee (VoP)

Overview

Verification of Payee (VoP) is an optional validation step that can be applied to payouts in order to verify that the beneficiary’s account details match the intended payee.

When VoP is enabled, the platform performs an account ownership verification immediately before executing the payout, using the underlying payment service that supports this capability.

Depending on the configuration and the verification outcome, the payout may proceed, be blocked, or continue despite verification errors.

---

Configuration

VoP is configured through the extra_data.payment.vop object in the payout request:

"extra_data": {
  "payment": {
    "vop": {
      "enabled": true,
      "accepted_verification_results": ["MATCH", "NO_MATCH"],
      "skip_on_error": true
    }
  }
}

---

VoP Fields

Field	Type	Description
enabled required	boolean	Enables Verification of Payee. When set to true, the platform performs a VoP check before executing the payout.
accepted_verification_results	string[] (enum)	List of verification outcomes that are considered acceptable to proceed with the payout. If the actual VoP result is not included in this list, the payout will not be executed. If omitted or empty, the payout proceeds regardless of the VoP outcome. Allowed values: MATCH, NO_MATCH, CLOSE_MATCH, VERIFICATION_CHECK_NOT_POSSIBLE.
skip_on_error	boolean	Determines the behavior when a VoP check cannot be completed due to transient errors (e.g. timeouts or temporary unavailability). When true, such errors do not block the payout. When false or omitted, these errors may prevent execution.

---

Verification Results

A VoP check may return one of the following outcomes:

• MATCH – The payee name fully matches the account holder.
• CLOSE_MATCH – The payee name closely matches the account holder, with minor discrepancies.
• NO_MATCH – The payee name does not match the account holder.
• VERIFICATION_CHECK_NOT_POSSIBLE – The verification could not be completed (e.g. unsupported account, temporary service limitations).

Whether the payout proceeds depends on the values defined in accepted_verification_results and skip_on_error.

---

Sandbox Testing

In sandbox environments, specific IBANs can be used to simulate different VoP outcomes for testing purposes.

IBAN	Simulated Result	Description
ES8569400001160529041877	rejected	Always simulates a rejected verification.
ES6769400001110836662135	failed (NO_MATCH)	Always simulates a NO_MATCH result.
ES3369400001190536473836	confirmed (CLOSE_MATCH)	Always simulates a close match.
Any other IBAN	confirmed (MATCH)	Always simulates a full match.

---