# Better UX for metatransactions

**URL:** <https://community.metamask.com/t/better-ux-for-metatransactions/28143>\
**Category:** Feature Requests\
**Created:** [February 7, 2024, 1:11pm UTC](https://community.metamask.com/t/better-ux-for-metatransactions/28143 "2024-02-07T13:11:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rafagl.dev](https://avatars.discourse-cdn.com/v4/letter/r/c6cbf5/32.png) [@rafagl.dev](https://community.metamask.com/u/rafagl.dev)\
**Post date:** [February 7, 2024, 1:11pm UTC](https://community.metamask.com/t/better-ux-for-metatransactions/28143/1 "2024-02-07T13:11:34Z")

</div>

**Description:**  
Somehow show the decoded callata (maybe the dev should have the contract abi) so the end user know what the metatransaction is actually invoking.

**Purpose:**  
When signing a metatransaction all the user can see is mostly noise. What method is the metatransaction calling? which arguments is it using?

Metamsk docs on sign-data highlights the following : “Ensure your contract is as readable as possible to the user”. This is not possible right now using metatxs