Skip to main content

Reuse verification with Sumsub sharing

Use Sumsub sharing when you have already verified a customer in your own Sumsub account. You share the applicant, which is the customer's record in your Sumsub account, with Nodu. Nodu reviews the shared information and makes its own decision.

Sumsub sharing is another way to start API onboarding. After the customer is created, the steps are those of Onboard a customer through the API.

Before you start​

  • Your integration agreement. Whether you can use Sumsub sharing and API onboarding depends on your integration agreement with Nodu. You need both.
  • Your Sumsub account. To share individuals, enable Reusable KYC. To share businesses, enable Copy KYB applicant and Reusable KYC. You also need an additional agreement with Sumsub to share applicants through the Reusable KYC and Copy Applicant features.
  • Nodu's Sumsub client ID. Nodu gives it to you during integration setup.
  • The requirements document. Nodu supplies a separate document listing the questionnaire answers and documents you need to provide. These requirements depend on the Nodu entity you integrate with and on your integration agreement with Nodu.

1. Obtain acceptance of the terms​

The example below assumes your agreement permits you to record acceptance in your interface. Obtain acceptance and send its time in tosAcceptance, as in API onboarding.

If you use hosted terms acceptance instead, omit tosAcceptance, create the customer in step 2, then redirect to the terms page before submitting the application.

2. Generate a share token and create the customer​

Generate the token​

From your backend, call Sumsub's Generate share token operation. Send the applicant's ID as applicantId, and Nodu's Sumsub client ID as forClientId.

A share token authorizes Nodu to copy one applicant. You can use the token once before it expires. Generate it when you are ready to create the customer. Send it to Nodu unchanged.

Create the customer​

Call Create a customer with the customer's details and an application.import object. In it, send provider=sumsub, and the share token as token.

  • For a business, send companyName.
  • The customer's email and phone number must match those of the shared applicant.
  • Nodu imports the applicant's information and documents. Send the questionnaire answers yourself. A suggestion: send the complete questionnaire in this same request, in application.individual.questionnaire or application.business.questionnaire. If the questionnaire that you send here is incomplete, Nodu refuses the request with validation_failed.
  • Other applicant fields that you send in application.individual or application.business replace the imported values.

This example creates the imported application and records terms acceptance. Add the questionnaire required by your separately supplied requirements, using the individual application example for its placement. You can also send it when completing the application in step 3.

curl https://api.sandbox.nodu.fi/v1/customers \
--header 'Authorization: Bearer <your-api-key>' \
--header 'Content-Type: application/json' \
--header 'Idempotency-Key: <new-uuid>' \
--data '{
"type": "individual",
"firstName": "John",
"lastName": "Smith",
"email": "john.smith@example.com",
"clientReferenceId": "client_reference_id_789",
"application": {
"import": {
"provider": "sumsub",
"token": "<share-token>"
}
},
"tosAcceptance": {
"acceptedAt": "2026-04-14T12:34:56+00:00"
}
}'

Nodu uses the token in this request, copies the applicant's information and documents, and creates a draft application. Store the customer id, and the application id from activeApplication.id. Nodu imports the applicant only in this request, when it creates the customer.

When Nodu refuses the token​

Nodu creates no customer. The rule in the response says why: import_token_expired, import_token_invalid, applicant_import_identity_mismatch, applicant_import_not_reusable or applicant_import_not_permitted. Errors and rule codes says what to do for each rule.

A request with a new token needs a new Idempotency-Key. If the original request timed out, first send it again with the same key and the same token, to get its result.

3. Complete what Nodu still needs​

Call Retrieve an application to see the application Nodu reviews. Fields you supplied replace the corresponding imported values. In documents, the origin of a document is imported or uploaded.

  • Data. Call Update application data and send only the fields that you add or change. The fields that you leave out keep their value. A null or empty value counts as not sent. A questionnaire that you send replaces the earlier questionnaire as a whole.
  • Documents. The imported documents often meet Nodu's requirements. Upload a missing or rejected document as Upload and replace documents describes.

This example adds an address and questionnaire to the imported individual application from step 2. Use the fields and answers supplied for your integration. Other imported profile fields remain unchanged.

curl --request PATCH 'https://api.sandbox.nodu.fi/v1/customers/<customer-id>/applications/<application-id>' \
--header 'Authorization: Bearer <your-api-key>' \
--header 'Content-Type: application/json' \
--data '{
"application": {
"individual": {
"address": {
"country": "PL",
"city": "Warszawa",
"state": "mazowieckie",
"addressLine1": "ul. Marszalkowska 10",
"addressLine2": "apt. 5",
"postalCode": "00-001"
},
"questionnaire": {
"services": "both",
"cryptoPurpose": "Personal investment and remittances to family abroad.",
"thirdPartyDeclaration": "Acting solely on own behalf.",
"incomeCountry": "PL",
"incomeType": "salary",
"monthlySalary": "1000-5000",
"plannedMonthlyTurnover": "500-1000",
"plannedMonthlyTxCount": "10-25",
"txValueRange": "50-2000",
"largestTxValue": "5000",
"sourceOfIncome": "salary",
"jobTitle": "Software Engineer",
"industry": "13.1",
"isPep": false,
"isSanctioned": false,
"financialCrime": false
}
}
}
}'

4. Submit and follow the outcome​

Call Submit an application for evaluation. Nodu reviews the imported profile together with what you added. Approval in your Sumsub account is not Nodu's approval.

Follow Submit for review, then the steps to track the outcome and confirm readiness. When Nodu asks for corrections, correct the same application. You do not need a new share token.

Next steps​