---
title: "Resubmission and rejection"
description: "What to do when Nodu requests more information, issues a final rejection, or suspends or blocks a customer."
url: "/guides/customers/resubmission-and-rejection/"
index: "/llms.txt"
---

# Resubmission and rejection

Nodu can ask for more information about a customer, issue a final rejection, or suspend or block a customer. A final rejection ends onboarding for the customer. The steps cover hosted onboarding and API onboarding.

## When Nodu asks for more information

Nodu sends the `v1.customer.verification_resubmission_required` event. Check the customer and application statuses to see whether corrections are still required:

- The customer has `verificationStatus=resubmission_required`.
- The `status` of the customer's application is `resubmission_required`.
- [Retrieve an application](/api/tag/customers/get-v1-customers-customerid-applications-applicationid.md) returns `rejection.message`. This text explains what to correct and is written for the customer. Take the application's `id` from `activeApplication.id` on the customer.

Continue with the same customer. Do not create a new customer.

### Hosted onboarding

1. Tell the customer that Nodu needs more information. You can show `rejection.message`.
2. Call [Retrieve a link to verification page for a customer](/api/tag/customers/get-v1-customers-customerid-verification-link.md) with your `redirectUrl` to get a new link.
3. Redirect the customer to the link. Nodu's verification page shows the customer what information or documents to provide.
4. Track the review through customer webhook events. Nodu sends `v1.customer.verification_under_review` when the customer has submitted everything, and `v1.customer.verification_awaiting_associates` for a business whose associates still have to complete their verification. Nodu sends another event for the new outcome.

### API onboarding

1. Call [Retrieve an application](/api/tag/customers/get-v1-customers-customerid-applications-applicationid.md). Read `rejection.message`. In `documents`, find each document with `status=rejected`. Read each rejected document's own `rejection.message`.

   An excerpt of the response, with the applicant data left out. Here Nodu asks for a new proof of address:

   ```json
   {
     "id": "019f5c4f-d3e0-7043-931a-59c64d6c9ea9",
     "status": "resubmission_required",
     "rejection": {
       "message": "Provide a valid proof of address. Documents must:\nbe an accepted type and issued within the last 3 months."
     },
     "documents": [
       {
         "id": "019f5c4f-e100-7000-8000-000000000001",
         "kind": "identity",
         "subType": "passport",
         "satisfies": [],
         "status": "approved",
         "origin": "uploaded",
         "createdAt": "2026-07-14T10:00:00+00:00"
       },
       {
         "id": "019f5c4f-e100-7000-8000-000000000002",
         "kind": "proof_of_residence",
         "satisfies": [],
         "status": "rejected",
         "origin": "uploaded",
         "rejection": {
           "message": "Provide a valid proof of address. Documents must:\nbe an accepted type and issued within the last 3 months."
         },
         "createdAt": "2026-07-14T10:01:00+00:00"
       }
     ]
   }
   ```

2. Explain to the customer what to provide.
3. Correct the data with [Update application data](/api/tag/customers/patch-v1-customers-customerid-applications-applicationid.md). Replace each rejected document with [Upload an application document](/api/tag/customers/post-v1-customers-customerid-applications-applicationid-documents.md): see [Replace a document](/guides/customers/api-onboarding/adding-documents/index.md#replace-a-document).
4. Call [Submit an application for evaluation](/api/tag/customers/post-v1-customers-customerid-applications-applicationid-submit.md) again, for the same application.
5. Follow the outcome through the customer events, as after the first submission.

Three rules apply:

- You can update an application and upload documents only while it has `status=draft` or `status=resubmission_required`. In any other status, Nodu refuses the request with a business rule violation. For an update, `rule=application_not_editable`.
- Replace every rejected document before you submit again. If one is left, Nodu refuses the submission with `validation_failed`, and `errors` names the document as `documents.<kind>`.
- If you created the customer with a share token, correct the same application. You do not need a new token. See [onboarding with a share token](/guides/customers/api-onboarding/sumsub-sharing/index.md).

## Final rejection

Nodu sends the `v1.customer.verification_permanently_rejected` event. The customer has `verificationStatus=permanently_rejected`, and the application has `status=rejected`.

- Show the outcome to the customer. Stop onboarding this customer.
- You cannot correct the application or submit it again.
- Do not create another customer for the same person or company to start verification again.
- `activeApplication` on the customer becomes `null`. To read the application and its `rejection.message` afterward, use the application `id` that you stored.

## Suspended and blocked customers

A customer can become `suspended` or `blocked`. This can happen before or after the customer becomes `active`. Nodu sends the corresponding `v1.customer.suspended` or `v1.customer.blocked` event. The customer's `status` shows the new value.

For both statuses:

1. Stop offering new transfers to the customer. Nodu refuses new quotes, transfers and external accounts for the customer with `rule=customer_not_active`.
2. Call [Retrieve a customer](/api/tag/customers/get-v1-customers-customerid.md). Read the current statuses in the response.
3. Offer transfers again only when `status=active`. Nodu sends `v1.customer.activated` when a customer's `status` becomes `active`.

## Next steps

- [Upload and replace documents](/guides/customers/api-onboarding/adding-documents/index.md): upload and replace documents on an application.
- [How onboarding works, and customer statuses](/guides/customers/how-onboarding-works/index.md): the meaning of every status.
- [Errors and rule codes](/guides/api-basics/errors-and-rule-codes/index.md): the validation errors and rules that these requests return.
- [Test onboarding in the sandbox](/guides/sandbox/test-onboarding/index.md): produce a request for more information and a final rejection in the test environment.
