Skip to main content

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 valueFinal StatusFinal RefusedReasonType
acceptVALIDATEDnull
refuse_unreadableREFUSEDUNREADABLE
refuse_not_acceptedREFUSEDDOCUMENT_NOT_ACCEPTED
refuse_expiredREFUSEDDOCUMENT_HAS_EXPIRED
refuse_incompleteREFUSEDDOCUMENT_INCOMPLETE
refuse_missingREFUSEDDOCUMENT_MISSING
refuse_no_user_data_matchREFUSEDDOCUMENT_DO_NOT_MATCH_USER_DATA
refuse_falsifiedREFUSEDDOCUMENT_FALSIFIED
refuse_underageREFUSEDUNDERAGE_PERSON
refuse_specific_caseREFUSEDSPECIFIC_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 valueFinal Status
AcceptUBOVALIDATED
RefuseUBOREFUSED
IncompleteUBOINCOMPLETE
I