# End-User Transaction Approval Process in Fireblocks NCW Implementation

**URL:** <https://community.fireblocks.com/t/end-user-transaction-approval-process-in-fireblocks-ncw-implementation/2268>\
**Category:** Developer Discussion\
**Tags:** docs, help-center\
**Created:** [March 2, 2025, 11:09am UTC](https://community.fireblocks.com/t/end-user-transaction-approval-process-in-fireblocks-ncw-implementation/2268 "2025-03-02T11:09:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![xls](https://avatars.discourse-cdn.com/v4/letter/x/51bf81/32.png) [@xls](https://community.fireblocks.com/u/xls)\
**Post date:** [March 2, 2025, 11:09am UTC](https://community.fireblocks.com/t/end-user-transaction-approval-process-in-fireblocks-ncw-implementation/2268/1 "2025-03-02T11:09:06Z")

</div>

Hi Fireblocks Team,

I am currently implementing Fireblocks’ Non-Custodial Wallet (NCW) solution for our application and have questions regarding the Transaction Authorization Policy (TAP) as it relates to end-user approval workflows.

After reviewing the documentation at [https://support.fireblocks.io/hc/en-us/articles/7354983580316-About-the-TAP](https://support.fireblocks.io/hc/en-us/articles/7354983580316-About-the-TAP) and [https://support.fireblocks.io/hc/en-us/articles/7361652234524-TAP-best-practices](https://support.fireblocks.io/hc/en-us/articles/7361652234524-TAP-best-practices), I couldn’t find specific information about how end-users approve their own transactions when a TAP rule requires their approval.

Specifically, I would like to understand:

- When a TAP rule requires end-user approval for a transaction, what is the user experience flow from the end-user’s perspective?

- How are end-users notified about pending transactions that require their approval?

- What interfaces or methods are available for end-users to review and approve transactions (mobile app, web interface, SDK integration, etc.)?

- Is there an API endpoint that our application should call to facilitate the end-user approval process?

Thank you for your assistance.

---

<div class="post-metadata">

**Author:** ![mnamakwala](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@mnamakwala](https://community.fireblocks.com/u/mnamakwala)\
**Post date:** [March 15, 2025, 12:52am UTC](https://community.fireblocks.com/t/end-user-transaction-approval-process-in-fireblocks-ncw-implementation/2268/2 "2025-03-15T00:52:01Z")

</div>

Hi, My name is Mohammed, and I am from Fireblocks.

1. The end users’ wallets cannot participate in the TAP flow, which includes approval. End-user devices are denoted by wallet ID. Only Fireblock users can participate in the TAP. Please refer to this [guide](https://ncw-developers.fireblocks.com/docs/implementation-steps#ew-tap-rules-for-production-workspaces:~:text=over%20their%20assets.-,EW%20TAP%20rules%20for%20Production%20workspaces,-If%20you%27re%20a) for TAP for NCW wallets. We do not have so much granular control in TAP for each end user device. Having said that you can build your access control on the backend server hosted by you.
2. The transactions will never require approval from end users it would only need signatures from end user wallet devices for transactions to be signed which initiated by those wallets
3. We have interfaces on the web, ios, and android for end-user devices. You can develop your app the way you would like using our SDK to show to your customers. Kindly check out our [demo apps](https://ncw-developers.fireblocks.com/docs/setup-5)
4. No there is no API endpoint. All user creation or transaction approvals go through the standard flow of the custodial wallet structure to fireblocks users mobile apps

Thanks