📘

Verification requirements for international payments

In order to enable International payments for an organisation we need to collect additional information about the organisation and verify the identities of certain individuals involved with it. These checks are required to meet regulatory obligations and protect users.

These additional verification requirements are not required for standard onboarding of organisations

Verifying an organisation to enable features

Before enabling advanced features like international payments, an organisation must undergo a verification process. This includes Crezco validating additional information such as:

• Detailed organisational information (e.g., business structure, registration details)
• Proof of identification for key individuals, such as Ultimate Beneficial Owners (UBOs), directors, and authorised signatories
• Completing additional compliance checks, including sanctions and politically exposed persons (PEP) screenings

Wherever possible, Crezco automatically sources the information required to verify an organisation to minimise potential friction with end-users and ensure a smooth onboarding experience.

This verification ensures compliance with regulatory standards and reduces the risk of fraudulent activities.

Verification process

In the typical verification flow, the user submits all the required information through the hosted verification flow. Crezco then reviews this submitted information. The ideal outcome (happy path) is that Crezco complete the verification successfully without needing further contact with the organisation or end-user.

Cancelled verifications

If a user does not submit the required information within a reasonable timeframe, or is unresponsive to follow-up queries from Crezco, the verification process may be cancelled by Crezco. This will come through as a failed verification.

Hosted verification flow

To make integrating with Crezco’s API easier, we provide a hosted verification flow accessible via the POST organisations/{organisationId}/verify endpoint. This endpoint returns a URL which users can access in order to submit required information on behalf of an organisation.

The verification process is asynchronous and doesn't need to be completed in one session. We publish webhooks notifying your system of changes in verification status. See the Webhooks page for full details.

You must provide a returnUrl in the request body to redirect the user back to your system upon completion of the current process.

If the organisation has already completed verification, the endpoint returns a 204 No Content response. However, this is not necessarily a permanent state; a future verification requirement may result in a 200 OK response with a new verification URL.

We recommend calling this endpoint each time you initiate a verification flow for the user.

You may send a user into the verification flow whenever the Organisation’s verification property includes verifiable: true.

Within this flow, users can:

• Provide necessary KYC and compliance details about their organisation
• Edit existing compliance details if needed
• Trigger reminder notifications to persons of significant control (PSCs) required to provide personal information

Verify statuses and webhooks

Crezco uses webhooks to inform you about verification state changes. For details about the available verification statuses, webhook payloads, and handling failed verifications, please refer to our dedicated Verify Statuses and Webhooks page.