Somehow show the decoded callata (maybe the dev should have the contract abi) so the end user know what the metatransaction is actually invoking.
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