Logs

Analyze and audit VOP transaction history

Audit and analyse your VOP verification history. Use these endpoints to monitor activity, study match patterns, troubleshoot discrepancies, and keep compliance records.

There are two sides, mirroring the two roles in VOP:

  • Request logs — the verifications you initiated against accounts held by other PSPs.
  • Response logs — the verifications you received from other PSPs querying accounts you hold.

Endpoints

MethodPathPurpose
POST/vop/v1/logs/request/searchSearch VOP requests you sent.
POST/vop/v1/logs/response/searchSearch VOP requests you received.

What's in each log

Request logs capture the full verification you ran:

  • Verification details — IBAN, target PSP BIC, timestamp, algorithm version.
  • Input data — name, first/last name pair, or company identifiers (SIRET, SIREN, LEI, …).
  • Match results — match status, match code, and an optional additional match code.
  • Context — matched name, execution time, country code.
  • History metrics — how many times the IBAN was seen, its age, whitelist status, FNC-RF status.
  • Tests performed — the checks that were executed.

Response logs capture what was asked of you:

  • Request details — origin PSP BIC, IBAN, timestamp, algorithm version.
  • Input — the verification type (name, BIC, LEI, SIRET, …) and the value provided.
  • Match results — match code, matched name (if any), match score.
  • Performance — execution time, country code.

Filtering & search

Both endpoints accept flexible filters (IBAN, BIC, date range, match codes, input, and more) and are paginated at 100 logs per page, ordered by creation date with the most recent first. Send { "page": 1 } to fetch the first page.