# Trendtech VOP API Reference

Technical specification for the Verification of Payee VOP API based on EPC103-24 VOP Inter-PSP API Specifications.

This API enables Payment Service Providers (PSPs) to verify payee information before executing SEPA payments, 
reducing fraud and payment errors through real-time verification.

Benefits
- Reduces fraud and misdirected payments
- Supports real-time name or identifier verification
- Complies with SEPA and EPC requirements

Standards
- VOP Scheme Rulebook (EPC218-23)
- Inter-PSP API Specification (EPC103-24)
- EPC API Security Framework (EPC164-22)


Version: 1.0.0

## Servers

Base URL will be provided by TrendTech (sandbox or production)
```
https://{environment}.trendtech.uk
```

## Security

### bearerAuth

JWT token from Auth0 authentication

Type: http
Scheme: bearer
Bearer Format: JWT

## Download OpenAPI description

[Trendtech VOP API Reference](https://trendtech-vop-api.redocly.app/_bundle/trendtech_vop_api.yaml)

## VOP Request

Core endpoint used for initiating and receiving payee verification requests

### VOP_Request

 - [POST /vop/v1/request](https://trendtech-vop-api.redocly.app/trendtech_vop_api/vop-request/vop_request.md): Submit a payee verification request as a Requesting PSP. This endpoint is used by the Requesting PSP or its RVM
to initiate a verification check before a SEPA payment.

## Verification Types Supported
- Name + IBAN: For natural persons or organizations
- Organization ID + IBAN: LEI, BIC, or 14 other organization ID types
- Name/ID + IBAN + With remittance info: For e-money institutions (INACNO support)

## Business Rule: Mutual Exclusivity
The request must contain EITHER:
- party.name for name verification
- party.identification for organization ID verification

These fields are mutually exclusive - including both will result in a 400 error.

## Authentication
- Method: JWT Bearer Token
- Header: Authorization: Bearer