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 and 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.