Mistaken transfer to Aave pool contract instead of repay (Arbitrum)

Risk Smart Contract
1

Hi,
I attempted to repay my wstETH debt on Aave v3 (Arbitrum), but my Tangem wallet signed a simple ERC‑20 transfer instead of the actual repay() call. Because of this, the repayment did not reduce my debt and the tokens were sent directly to the pool contract.

Here are the details:

  • Wallet address: 0x072D7F991Cb577521c1d5576F6c87df43A14460D

  • Transaction hash: 0xa3302bb2c89d38a44959a588ab853dc6eea328380191d08c7566e90b3165ed55

  • Asset: wstETH

  • Amount: ~0.035 wstETH

  • Network: Arbitrum One

Please advise on whether the funds can be recovered or credited as a proper repayment.
This was not an intentional transfer — the wallet failed to sign the repay multicall.

Thank you for your help.

2

Hello there,
unfortunately tokens that have been sent to the pool cannot be recovered.
Please be careful in the future and always double check.

Sorry

3

This was not a mistaken transfer.

It was a failed repay due to a wallet signing issue.
The UI initiated a repay, but the wallet signed a transfer.
This is a UX failure, not user error.

čet, 16. tra 2026. 19:12 EzR3aL <notifications@aave.discoursemail.com> je napisao:

4

But still in the end the issue was either on the wallet or user side. If you think it was somehow the frontend then feel free to reach out to @AaveLabs

5

Thanks for the reply.
Just to clarify: this was not a user mistake and not a manual token transfer.

I initiated a repay from the Aave UI.
The UI generated a repay transaction, but the wallet (Tangem) incorrectly signed it as a simple ERC‑20 transfer instead of the required repay() multicall.

This is a frontend → wallet signing mismatch, not user error.

The transaction hash clearly shows:

  • no repay() call
  • no debt token burn
  • no multicall
  • only a raw transfer to the pool contract

This is a reproducible issue with Tangem + Aave v3 on Arbitrum for wstETH.
Please escalate this to the Aave frontend team, because this is not a user mistake — it is a UX failure that results in stranded funds.

I am requesting escalation to the Aave Guardian / Risk team for review.

čet, 16. tra 2026. 20:54 EzR3aL <notifications@aave.discoursemail.com> je napisao:

6

Hi,

We have reviewed the transaction you provided and can confirm that the repayment was executed correctly on-chain.

The transaction called the repay function on the Aave V3 Pool contract on Arbitrum One for 0.035 wstETH.

You can verify this directly on Arbiscan:

The repayment should also be reflected in your transaction history in the Aave interface.

Captura de pantalla 2026-04-16 a la(s) 5.14.30 p. m.
Captura de pantalla 2026-04-16 a la(s) 5.14.30 p. m.860×270 12.1 KB

Please note that this channel is not the right place for this type of support inquiry. If you have any further questions, please send us an email at wecare@aave.com and we will be happy to help.

Kind regards,
Cosme
Aave Labs

3 Likes