> For the complete documentation index, see [llms.txt](https://docs.doku.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.doku.com/changelog/may-2026/simpler-business-data-clarification.md). # Simpler Business Data Clarification Effective Date: May, 2026 DOKU has revamped the KYB (Know Your Business) Resubmission experience, giving merchants a clearer, faster, and more intuitive way to resubmit rejected or missing verification data directly from the DOKU Dashboard and no support ticket needed. The key insight behind this update: only 21 out of 5,239 merchants updated their data after being rejected once. The root cause wasn't unwillingness and it was a confusing experience that left merchants without clear guidance on what went wrong or how to fix it. *** ### πŸ” What’s New? The entire KYB Resubmission flow has been redesigned across five areas: Notifications, Dashboard, Approvals Settings, Business Information, and KYB Review Flow β€” making resubmission fully self-service and actionable. This update ensures: * Merchants understand exactly why their data was rejected * Resubmission is fully self-service and no support contact needed * Only data that requires action is shown, reducing cognitive overload * Merchants can upload additional documents directly from the Dashboard #### **πŸ“’ Notification**
DescriptionBeforeNew
Verification Rejected

Verification Succesfull

Under Review

Requesting Additional Datanot available

#### **πŸ–₯️ Dashboard**
DescriptionBeforeNew
Verification Banner

#### βš™οΈ Approvals Settings
DescriptionBeforeNew
Action Requirednot available

Data Details not available

#### **🏒 Business Information**
DescriptionBeforeNew
Action Required Component

Guidelinenot available

#### πŸ” KYB Review Flow
DescriptionBeforeNew
Data Rejection Specific Informationnot available

Request Additional Datanot available

*** ### How the KYB Resubmission is Changing #### πŸ”„ **Before This Update** Merchants who received a KYB rejection had no clear indication of what went wrong or how to fix it. Notification messages were vague, the resubmission flow was unintuitive, and merchants were left without a clear path forward and often having to contact the support team manually just to understand next steps. The result: only 0.4% of rejected merchants successfully updated their data that a clear signal that the experience was broken, not the merchants. Steps: 1. Merchant submits KYB verification 2. Verification is rejected or flagged 3. Merchant receives a vague rejection notification with no clear next step 4. Merchant contacts support team for guidance 5. Manual back-and-forth to collect missing documents or clarify rejection reasons 6. Merchant resubmits β€” if they haven't dropped off already {% hint style="warning" %} **Risk** High verification drop-off, increased support ticket volume, and delayed merchant activation. {% endhint %} #### πŸ†• **After This Update** With the revamped KYB experience, merchants can now see exactly what was rejected, what needs to be fixed, and take action with all from within the DOKU Dashboard. Steps: 1. Merchant submits KYB verification 2. If rejected or flagged, merchant receives a clear notification with specific rejection reasons and a direct CTA to update data 3. Verification banner and persistent Reminder Bar appear in Dashboard until all required data is updated 4. Merchant follows a structured checklist to resubmit the correct data and with guideline available for rejected brand data 5. Merchant views full approval/rejection history in the All Data tab under Approvals Settings 6. Resubmission completed independently with no support involvement needed {% hint style="success" %} **Benefit** Faster verification completion, lower support ticket volume, and a smoother path to full merchant activation. {% endhint %} *** ### πŸ“Œ Important Notes * This is a Dashboard UX improvement β€” no API changes or merchant integration required. * Merchants with outstanding KYB rejections can log in to their DOKU Dashboard and check their Approvals Settings for pending action items. * New merchants going through onboarding who encounter KYB issues will be covered under the upcoming Revamp Onboarding initiative. * For assistance, contact our Care Team at or (021) 1500963. *** Thank you and best regards,\ **DOKU Product Team** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.doku.com/changelog/may-2026/simpler-business-data-clarification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.