Skip to main content
The Inventi Verification of Payee (VoP) service validates account ownership before you initiate a payment. Reduce fraud and prevent misdirected payments with real-time verification for financial institutions and payment service providers (PSPs).

​
Use Cases

VoP Requests PSP

Send verification requests to confirm account holder details before executing payments

VoP Responding PSP

Provide account ownership data to validate incoming verification requests

​
Core APIs

The VoP service provides two complementary APIs:

VoP API

Real-time verification of IBAN and account holder details

Account Data Import API

Manage the account holders for verification requests

​
Getting Started

1

Authenticate

Obtain an OAuth 2.0 bearer token and whitelist your IP addressView authentication guide →
2

Integrate the API

For requesting PSPs, integrate the VoP verification endpoint. For responding PSPs, import your account data first.
3

Test and Go Live

Test in the sandbox environment before moving to production

​
API Details

This API allows you to verify whether a specified IBAN corresponds to a particular payee before executing a transaction.

​
Verification Methods

  • Name-Based Check
Purpose: Verify individuals or legal entities based on account holder namesUse case: Validating individual consumers or business namesReturns: MATCH, CLOSE_MATCH, NO_MATCH, or CANNOT_VERIFY

​
Verification Outcomes

  • MATCH: The provided details exactly match the account holder information
  • CLOSE_MATCH: The details are similar but not an exact match (e.g., minor spelling differences)
  • NO_MATCH: The details do not match the account holder
  • CANNOT_VERIFY: Unable to verify (account not found or verification unavailable)
This API is designed for real-time use during payment initiation. Response times are optimized for immediate user feedback.
This API enables Responding PSPs to manage the dataset against which VoP checks are validated.

​
Supported Operations

Import

Add new IBAN-to-holder mappings (single or batch)

Update

Modify existing records (single or batch by clientId)

Delete

Remove outdated records (single or batch by clientId)
All imported data is stored in an internal Accounts database and becomes immediately available for matching.
No validation is performed on input data. The system does not verify whether IBANs are genuine or names are formatted correctly. Ensure data quality before import.

​
Development Roadmap

Coming Soon: Batch request functionality for VoP verification is currently under development and will be released in a future update.

​
Error Handling

All API endpoints return standardized error responses. This guide currently covers general error types. Specific use case errors will be documented in future updates.

​
Common Error Codes

  • 401 Unauthorized: Invalid or expired bearer token
  • 403 Forbidden: IP address not whitelisted
  • 404 Not Found: Account not found in the system
  • 422 Unprocessable Entity: Invalid request parameters
  • 500 Internal Server Error: System error (contact support)

​
Next Steps

Authentication

Set up OAuth 2.0 authentication and IP whitelisting

Verify Account Holder

Start verifying IBAN and account holder details

Import Account Data

Import account data for verification matching