> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/data-protection-and-privacy/view-payment-instruction-mask-account-number-and-ifsc.md). # View Payment Instruction - Mask Account Number & IFSC ## Scope View Payment Instruction - Account Number and IFSC to be masked. ## **Actor** Employee ## **Details** 1. Change in View Payment Instruction is required to implement data privacy. 2. PII and sensitive information are masked so the users do not have a role to view it. 3. The format of masking is given below. 1. Account number - Only the last 4 digits are displayed, the rest are masked with asterisk. e.g. 321004567621 to \*\*\*\*\*\*\*\*7621. 2. IFSC - The first 4 letters and last 2 digits are displayed. e.g. ICIC0000047 to ICIC\*\*\*\*\*47. 4. The details shown are masked for the role other than **View\_WS\_Unmasked, View\_ORG\_Unmasked, and View\_DED\_Unmasked.** 5. For the user having roles **View\_WS\_Unmasked, View\_ORG\_Unmasked, and View\_DED\_Unmasked** information displayed is unmasked. ## User Interface {% embed url="" %} ## Acceptance Criteria 1. Beneficiaries' PII and sensitive data are to be masked while displayed based on role. 2. A user having roles **View\_WS\_Unmasked, View\_ORG\_Unmasked, and View\_DED\_Unmasked** can see the details unmasked. 3. A user having roles other than **View\_WS\_Unmasked, View\_ORG\_Unmasked, and View\_DED\_Unmasked** views the details masked. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/data-protection-and-privacy/view-payment-instruction-mask-account-number-and-ifsc.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.