> 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/july-2026/customer-static-va-enhancements.md). # Customer Static VA - Enhancements Effective Date: 16th July, 2026 Customer Static Virtual Account now comes with several **enhancements** to make it easier for merchants to view and track customer transactions. **With this enhancement, merchants can view the transaction list directly on the Customer Detail page, as well as access the Transaction Report to view transaction details associated with the customer.** Additionally, Static Virtual Account is now **compatible with BNI**, giving merchants more flexibility in managing customer payments. These enhancements make it easier for merchants to connect customers with their transactions and track transaction details through the Transaction Report.
*** ### πŸ” What’s New? #### **Customer-Level Transaction List** Each customer profile now includes a dedicated **Transaction List** showing the transactions associated with that customer. Merchants can view: * Inovice ID * Amount * Transaction Date This provides a more complete view of the customer's payment activity without requiring merchants to search for individual transactions separately. #### **Transaction Report** Merchants can also access the **Transaction Report** to view transaction details associated with a specific customer. This makes it easier to track customer transactions and review their payment activity in more detail. #### **BNI Compatibility** **Customer Static VA is now compatible with BNI**, expanding the available bank options for merchants using Customer Static VA. *** ### πŸ’‘ Why It Matters Previously, merchants could view customer information but had limited visibility into the customer's transaction history directly from the customer profile. CSVA V2 connects these two pieces of information, helping merchants understand **who the customer is and what transactions they have made** in one place. * **Better customer visibility:** understand transaction activity at an individual customer level. * **Faster transaction review:** check customer payment history directly from the profile. * **Easier monitoring:** quickly identify successful and failed transactions. * **Less manual searching:** no need to look for transactions separately. *** ### πŸš€ How It Works #### πŸ”„ Before Merchants could access customer information, but transaction activity was not directly available within the customer profile. To review a customer's transactions, merchants had to search for the relevant transactions separately. #### πŸ†• After Merchants can now: 1. Open the **DOKU Dashboard**. 2. Go to **Customers**. 3. Select the customer they want to review. 4. Open the **Transaction List**. 5. Review the customer's transaction amount and status. The customer's transaction activity is now available directly from their profile. *** ### πŸ’Ό **Key Features** * Transaction List within each customer profile * Customer-level transaction visibility * Transaction amount information * Transaction status information * Visibility into successful and failed transactions * Direct access through **Dashboard β†’ Customers** * No separate transaction search required for basic customer-level review *** ### **πŸ“Œ Key Details** * Transaction activity is displayed based on the selected customer. * Merchants can access the Transaction List from the customer's profile. * The feature is designed to provide **customer-level transaction visibility**, rather than replacing the main transaction monitoring experience. *** 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/july-2026/customer-static-va-enhancements.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.