Simulate business eKYC approvals
Learn how to trigger specific eKYC statuses by submitting predetermined test data during the verification process. This guide helps you understand the end-to-end user journey for business eKYC approvals and rejections in the staging environment.
Note that these procedures are unsupported in Production and should only be performed in UAT or Staging.
Use Cases:
- You need to simulate an business eKYC approval to test the success scenarios of your onboarding process.
- You need to simulate an business eKYC rejection to test the negative scenarios of your onboarding process.
Prerequisites:
- You must already have an
activeregistered business user that is ready to perform eKYC. Refer to the Perform business eKYC section to learn about the specific required KYC criteria.
Approval Workflow
1
Generate a KYC capture link for the business user
Simulating a KYC approval requires you to undergo the eKYC process. Render the eKYC capture link in any web/mobile browser that you want to conduct your test on.
Initiate KYC Capture (Business User)
Call Initiate KYC Capture (Business User) (POST /businesses/authentications/documents/verifications) to get the href or the redirect link to the eKYC web app. To redirect users back to your application after they complete or exit the eKYC flow, include the following callback parameters in your request.
Callback Parameters (eKYC capture screen back to your app)
redirect_url: The fully qualified callback URL to which the user is redirected upon exiting or completing the eKYC flow.redirect_mode: The method of redirection. Accepted values are auto (immediate redirection upon completion) or button (requires explicit user interaction to trigger the redirect).redirect_text: The custom label displayed on the redirection button (e.g., "Exit" or "Return"). Applicable only when redirect_mode is set to button.
Initiate KYC Capture (Business User) request
curl --location --request POST 'https://{{identity_base_url}}/{{program_code}}/v2/businesses/authentications/documents/verifications' \
--header 'X-Auth-User-ID: {{business_id}}' \
--header 'Authorization: ••••••'
--header 'Content-Type: application/json' \
--data '{
"verification_mode":"document_based",
"redirect_url":"www.partner-callback.com",
"redirect_mode": "button",
"redirect_text": "Exit"
}'
Initiate KYC Capture (Business User) response
{
"id": "caa61227979e43fea38d2730c11e8667",
"links": [
{
"href": "https://api-sg-sdk.matchmove-beta.com/v2/web/sdk?id=459b1daa8fd49e7071daa9bd429dc30432dc4039e7fd067669330db4f6e89320d65554474c2b4fdace25920a30599578fcf519de4e74d2db7167e3187c83eeeb8141916b5c800b9eb2ef7485182ef21046a8f71a045c8cf8839988519bd6bddacf06eb3dd0ad5f837d40b40fd5c6cbba246ae60d74b1925f913c4ac339cc6f095244c807189ab3bfaa61e55de1da2d029abe9ffd352c7727f8205e0b0bc7f5d75f9fe85ab14b568512e2dc2e7a1d403e52f0026e93d063b8e26f73985e5b3bd968a590d54f3b08be8a3f09744206a7916ea2aee896864871bdfc41ad223efe14b2e7b77b59ef8f0f7268f32e0b5e3b1d0de123fedf957d0353de5168c9ac9c17603b44358cda2cb7a43317sd9dd844de4de81ff951&user_id=&auth_token=",
"method": "GET",
"rel": "capture.sdk"
}
],
"sub_type": "business",
"type": "users",
"verification_id": "vfc_29baeb0da5144c678c1adf7eic61381e",
"verification_mode": "document_based"
}
2
Perform the eKYC process and submit pre-approved values
The following procedure below is the only way to simulate an approval in the staging environment.
Submitting any other values aside from the pre-approved values will result in rejection.
You can subscribe to the KYC verification webhooks to be notified of the KYC approval of the business user.
![]() | In the Company Information screen, enter and change the following fields: Pre-approved values:
|
|---|---|
![]() | Associated party definition: In the Edit associated party screen, you will need to define an associated party. For the sake of efficiency, we recommend that you define an associated party that is an Individual User. Since associated parties are required to have their own KYC approved, defining an individual will be easier since it has fewer requirements than defining a business user. Role selection: In the live environment, it is required to define an associated party for all the roles available in the associated party form. For staging or UAT, if you just want to simulate the KYC approval process, you won't need to define an associated party for every role. Instead, you can define at least one associated party (Assoc Party A) and assign all the roles to this party (Assoc Party A). Associated party submission: Complete the user details of the associated party and proceed to submit. |
![]() | After submission, the business verification will be put on hold, awaiting the successful verification of all of its defined associated parties. Associated party KYC submission and approval (individual): On the Verification not yet complete (eKYC Submitted) screen, click the Verify Now button or render the KYC capture link in a web browser to proceed with the associated party's verification. Follow the Simulate individual eKYC approvals section to learn about how to simulate the verification of an individual user. |
3
[Additional] For onboarding business from high-risk regions and industries
If a business user is flagged as "high-risk" (due to business foundation location* or profile), the system automatically triggers Enhanced Due Diligence (EDD). This adds extra screens and document requirements to their eKYC journey.
Note on Testing: You can use dummy data and documents for EDD requirements during simulation.
Please keep in mind that EDD flips the process from automated to manual review. Since MatchMove Compliance must personally vet these submissions in both staging and live environments, approval won't be immediate. In staging and for the purpose of simulation, we have established a 1-day SLA for these specific cases.
*Refer to Standard Operating Procedure for Compliance Management document for the list of high-risk and sanctions regions.
4
Request to trigger the simulation of the business KYC approval process from the backend:
After the individual associated party KYC has been completed and passed its own verification, you will then need to submit a Freshdesk ticket requesting the KYC approval of the business user.
On this ticket, please include details of the business, such as the business user ID, business name, and email.
This additional step is needed to sync all the KYC states between MatchMove and the KYC provider in the simulation environment.
When the states are all synced, that is when the update webhooks will be triggered.
On this page
- Simulate business eKYC approvals


