Euler finance lets borrowers monitor position health and reduce outstanding debt

Euler finance lets you monitor a borrowing position's health and repay its outstanding debt. Track the selected position's collateral, debt and liquidation threshold, then review how repayment changes those balances. Completion requires a successful repayment transaction and an updated debt balance; a wallet approval alone doesn't repay the loan.

Sep 2026 - last updated

Position details connect monitoring with repayment

Portfolio separates borrowing positions from direct deposits, and each position's detail view provides its available debt and collateral actions. Health score describes collateral coverage, while the debt balance records what remains owed. The liquidation price, where shown, adds a price reference for monitoring. These fields answer different questions, so a better-looking balance alone doesn't establish that repayment succeeded.

Repay reduces debt. Adding eligible collateral increases the assets supporting that debt without paying it down. Withdrawal removes collateral and therefore needs its own review. The appropriate adjustment depends on whether the immediate task is reducing the liability, increasing collateral coverage or releasing assets. Available actions and funding sources depend on the selected position.

What does the health score measure?

The health score compares collateral value after liquidation risk adjustments with liability value, so it measures coverage rather than repayment progress.

Collateral value after risk adjustments

The calculation applies the relevant liquidation loan-to-value ratio, or LLTV, to each eligible collateral balance's value. It then compares the combined adjusted value with the debt's value. Prices come through the configured oracle, which supplies valuation data to the vault. A wallet's total holdings therefore aren't interchangeable with the collateral that supports this particular borrowing position.

View full-size image

The threshold and the displayed number

A standard Euler Vault Kit account with outstanding debt becomes eligible for liquidation when its liquidation-adjusted collateral value is no greater than its liability value. This corresponds to a health ratio of 1 or below. Display rounding can conceal which side of the boundary the raw values occupy. A displayed 1 is therefore insufficient evidence of a remaining margin.

Borrow LTV separately limits risk-increasing actions. A position can remain outside liquidation eligibility while failing the stricter check for another withdrawal or loan increase.

Repayment funding changes the effect on collateral

Repayment from wallet funds can reduce the liability without consuming the position's collateral, provided the wallet holds the required borrowed asset. With positive collateral value, unchanged asset prices and unchanged risk settings, reducing debt while some remains increases the health ratio. A later price move can still offset that improvement. The projected result describes the reviewed state, not a permanent level of protection.

Using deposits or collateral introduces different dependencies where those funding routes are supported. A collateral-funded repayment can reduce both collateral and debt, so the final relationship between them matters. A swap route also introduces execution price, price impact and slippage constraints. A transaction that exceeds its allowed slippage reverts rather than completing at the rejected price.

Why can debt remain after a repayment?

Debt can remain because the payment was partial, interest accrued before execution or the selected repayment source couldn't cover the full liability.

Interest changes the amount owed

Borrow interest accrues on outstanding debt under the vault's configured interest-rate model. Copying an earlier displayed balance can therefore leave a remainder when the transaction executes. Rates can change as the model's inputs change; utilization is a common input, although some models use time instead. A recorded payment and a continuing debt balance can both be correct.

A full-debt request still needs sufficient funds

The standard contract's full repayment option calculates the amount owed at execution and pulls that amount. The payer still needs enough of the borrowed asset and sufficient spending authorization. Repayment using shares of the same borrowing vault has a different limit: it can only cancel debt covered by the shares available. Selecting the largest available repayment doesn't establish that the whole loan has closed.

An allowance failure needs a changed authorization before retrying

Consider a hypothetical partial repayment from wallet funds. The wallet holds enough of the borrowed asset, but its spending allowance covers less than the requested repayment. The selected debt account and repayment amount are otherwise correct. The intended outcome is a lower recorded liability with the collateral balance unchanged.

Before submission, check whether the selected spending authorization covers the requested amount. If simulation reports insufficient allowance, the spender lacks permission to transfer the requested amount. Granting the required authorization changes permission to transfer tokens; it doesn't itself change the outstanding loan.

Before retrying, confirm that:

• The repayment targets the intended debt account and borrowing vault.
• The wallet holds enough of the exact borrowed asset for the partial payment.
• The required spender has sufficient allowance for that payment.
• The refreshed transaction simulation passes with the intended amount.
• Any earlier repayment transaction has failed or been confirmed dropped. If it succeeded, reassess the remaining debt and intended payment before submitting another repayment.

View full-size image

After the corrected repayment executes successfully, the updated debt should reflect the payment, allowing for accrued interest. If only the approval completed, the liability remains outstanding. If a transaction hash exists but its status remains unresolved, inspect that transaction before retrying.

How can you confirm that repayment finished?

A successful repayment receipt and a fresh debt reading for the intended account establish whether the requested reduction actually occurred.

A transaction hash identifies a submission; it doesn't establish successful execution. Likewise, an approval receipt establishes spending permission. The repayment transaction must succeed separately unless the flow combines the necessary operations atomically. When a required check fails within an atomic transaction, its operations revert together.

For a full repayment, the decisive remaining balance is zero. The borrowing vault's debtOf function exposes the selected account's debt in underlying asset units. An interface showing a rounded zero or an older indexed value may need a fresh reading. For partial repayment, the remaining balance and current health describe the continuing position; repayment success alone doesn't mean the account is outside liquidation eligibility.

Remaining debt determines the next decision

A position with outstanding debt remains exposed to collateral prices, debt prices, oracle updates and changing risk parameters. Interest can increase what remains owed even when no new borrowing occurs. Monitoring therefore continues after a partial payment. Available liquidity affects how easily a position can unwind, although liquidity alone doesn't determine liquidation eligibility.

After full repayment, collateral withdrawal remains a separate operation. Available vault cash, applicable account checks and configured restrictions can affect whether it succeeds. Zero debt confirms repayment closure; receiving withdrawn assets requires the withdrawal's own successful execution. The next decision is whether to retain the deposit or request the amount that the vault can release.

Euler finance: questions and answers