Getting startedRelease notes

API - Sep 30, 2025

Added

Verification of Payee (VOP) in Sandbox

In Sandbox, the API fields showing the result of Verification of Payee (VOP) checks are now returned on the following endpoints:

On these endpoints, the RecipientVerificationOfPayee object is returned if the Recipient uses local SEPA schemes (SCT and SCT Int), meaning if its Currency is EUR, its PayoutMethod is LocalBankTransfer, and its Country is a SEPA country.

Take advantage of the new testing data to simulate the results of the check in Sandbox:

Added

Sandbox test data to simulate KYC Document processing

In Sandbox, platforms can now programmatically simulate the acceptance or refusal of a KYC Document, thanks to new test values.

To do so, when you call the POST Create a KYC Document endpoint, set the Tag to the relevant value to produce the desired outcome after submission.

For more details, see how to submit a KYC document

Tag value

Final Status

Final RefusedReasonType

accept

VALIDATED

null

refuse_unreadable

REFUSED

UNREADABLE

refuse_not_accepted

REFUSED

DOCUMENT_NOT_ACCEPTED

refuse_expired

REFUSED

DOCUMENT_HAS_EXPIRED

refuse_incomplete

REFUSED

DOCUMENT_INCOMPLETE

refuse_missing

REFUSED

DOCUMENT_MISSING

refuse_no_user_data_match

REFUSED

DOCUMENT_DO_NOT_MATCH_USER_DATA

refuse_falsified

REFUSED

DOCUMENT_FALSIFIED

refuse_underage

REFUSED

UNDERAGE_PERSON

refuse_specific_case

REFUSED

SPECIFIC_CASE

Added

Sandbox test data to simulate UBO Declaration processing

In Sandbox, platforms can now programmatically simulate the acceptance, refusal, or marking as incomplete of a UBO Declaration, thanks to new test values.

To do so, when you call the POST Create UBO endpoint to register the first UBO, set the FirstName to the relevant value to produce the desired outcome after submission.

For more details, see how to submit a UBO declaration

First UBO FirstName value

Final Status

AcceptUBO

VALIDATED

RefuseUBO

REFUSED

IncompleteUBO

INCOMPLETE