Pendle finance is a PT purchase, position check, and redemption workflow

Chain and asset mismatches stop the first transaction

A Pendle PT purchase succeeds only when the wallet network, market chain, and spendable token route align. The selected market controls where the swap executes, while the receiving-chain choice controls where a cross-chain PT arrives.

Pendle core deployment records distinguish Ethereum as chain ID 1, Optimism as 10, BNB Chain as 56, Monad as 143, Sonic as 146, HyperEVM as 999, Mantle as 5000, Base as 8453, Arbitrum as 42161, Ink as 57073, Berachain as 80094, and Katana as 747474. These numbers identify networks; they do not measure transaction size or value. A balance held on one chain cannot fund a conventional same-chain market on another. The market card, wallet network, and gas asset therefore need one consistent chain context before the first signature.

Cross-Chain PT changes the route rather than the market’s underlying contracts. The preview shows whether funds cross into the market chain, whether PT crosses out afterward, and which destination receives the position. Native gas remains necessary on the initiating chain even when the input is USDC or another ERC-20 token.

Once the market, wallet, and receiving chain align, the route is ready for review.

Wallet and token prerequisites

The PT workflow needs an EVM wallet, a supported input balance, and native gas on the initiating chain. PENDLE itself is not required for a standard PT purchase or redemption; the transaction uses the selected input asset and the chain’s gas token.

An EVM account address contains 20 bytes, normally shown as 40 hexadecimal characters after a 2-character 0x prefix, for 42 visible characters in total. Copying the right address matters when the receiver differs from the connected account. MetaMask and Rabby expose the active account and network, while WalletConnect carries that session context between the app and a compatible wallet. The address text alone does not identify a chain because the same address format appears across EVM networks.

The spendable balance must cover the entered amount without consuming the native gas reserve. An ERC-20 allowance is also required when PendleRouter lacks permission to move the chosen input. The app requests that approval before the swap, so each wallet prompt should name the expected token, account, chain, and contract action.

Market selection starts with the redemption asset

On those terms, Pendle market selection starts with the accounting asset and expiry because those fields define redemption. Fixed APY ranks opportunities, yet the asset unit and date determine what the wallet ultimately claims.

The accounting asset appears in parentheses beside the market name. PT-wstETH (stETH), for example, expresses its principal claim in stETH units even though wstETH from Lido supplies the yield-bearing wrapper. PT-sUSDe (USDe) measures its claim against USDe from Ethena. These labels prevent wrapper exchange rates from being mistaken for extra PT return. Read the asset description alongside the PT ticker before selecting the maturity.

Each market binds 1 PT contract and 1 YT contract to one expiry, making PT and YT the 2 expiry-bound claims. Standardized Yield (SY) has no maturity. A nearer expiry shortens the holding period, while a later expiry extends the term captured by the purchase. The final choice changes whenever either the accounting asset or expiry changes.

The purchase preview owns the executed position

The PT purchase preview decides the minimum output, maturity return, and wallet action before any signature. Select the PT fixed-yield side, remain on Swap, choose an input token, enter the amount, and inspect the complete route.

When the form presents approval and swap as separate on-chain actions, a zero-allowance path contains 2 confirmed transactions: 1 approval and 1 swap. An existing allowance large enough for the input reduces the sequence to 1 swap transaction. A wallet signature without an on-chain approval does not create a PT position.

Expected PT output states the projected balance, while minimum received sets the enforceable lower boundary. Maximum slippage defines how far execution may move before the swap reverts. Effective Fixed APY translates the acquisition price into an annualized term rate, but the redeemable amount gives the clearer unit-based check. Only the PT amount delivered by the confirmed transaction becomes the position.

A five-point check before signing

A useful PT decision check covers five conditions the transaction preview cannot decide for the wallet owner.

• Network: The market chain, connected wallet chain, and available native gas agree.
• Claim: The accounting asset shown beside the market is acceptable as the maturity unit.
• Term: The exact expiry matches the intended holding window and exit plan.
• Output: Expected PT, minimum received, and redeemable amount are visible before confirmation.
• Receiver: The destination account and receiving chain match where the position should appear.

Together, these checks turn the Pendle finance preview into a term-specific instruction rather than a generic token swap. Save the market name, expiry, input amount, quoted PT output, and receiving chain with the transaction record. If all five conditions align, the signature matches the intended position.

How do you confirm the PT position?

Confirm a Pendle PT position by matching the receipt, token balance, market, expiry, and receiving address. A successful wallet notification is the first checkpoint, while the resulting ERC-20 balance proves delivery.

On EVM chains, receipt status 1 records successful execution, while status 0 records a reverted transaction. A transaction hash contains 32 bytes and renders as 64 hexadecimal characters, or 66 visible characters with its 0x prefix. Open the chain explorer from the Dashboard transaction record and match its chain, receiver, PT contract, and transferred amount. A successful receipt on the source chain is only partial evidence when a cross-chain route still has a destination stage.

Next, select the receiving chain in the Pendle Dashboard and open the relevant asset. The PT entry should carry the same market and maturity chosen in the purchase form. Its displayed amount should agree with the wallet balance after token decimals are applied.

The position is confirmed when the receipt, ERC-20 balance, and Dashboard entry describe the same claim.

Dashboard views and token records

The Pendle Dashboard should show the same PT amount and maturity the ERC-20 token record proves. Use the asset-level position view for the market label, position type, value, and transaction history.

The Dashboard provides 2 viewing modes: USD Mode and Underlying Mode. USD Mode converts the position through changing market data, so it is useful for valuation rather than exact unit reconciliation. Underlying Mode keeps the asset denomination visible. Asset details separate 3 position types: PT, YT, and LP. An ERC-20 balance uses a 256-bit unsigned integer, then applies the token’s decimal metadata for display. Although 18 decimal places form a common convention, ERC-20 does not require every token to use 18.

Compare displayed units rather than raw integers. If the wallet omits a custom token, importing the market’s PT contract changes only the display. The Dashboard and on-chain record remain decisive whenever wallet labels differ.

The route beneath a PT purchase

For that reason, Pendle routes the input through Standardized Yield before the PT/SY market delivers Principal Tokens to the receiver. SY wraps yield-bearing assets behind a common contract interface, and PendleRouter coordinates the necessary conversions. A Pendle V2 pool holds 2 asset types, PT and SY; a direct PT purchase exchanges routed SY for PT. YT uses a flash-swap path through the same pool. Auto-routing therefore lets USDC reach a PT position without requiring the wallet to handle SY separately.

An early exit is a new market trade

An early PT exit sells the position at the available quote before its fixed maturity redemption applies. Select the held PT as the input, choose the desired output token, enter the sale amount, and review the route.

The preview replaces the maturity claim with a market-priced output. That quote reflects the pool state, remaining term, implied yield, route depth, and selected slippage boundary at execution. It can differ from both the original purchase cost and the amount available at maturity. Confirm the minimum received, output chain, and receiving address before signing. A partial sale leaves the unsold PT under the original market and expiry.

In a conventional same-chain sale, an approval-plus-swap path contains 2 transactions when the router lacks PT allowance. A sufficient existing allowance leaves 1 sale transaction. After settlement, reconcile the lower PT balance and the received output token; holding the remainder preserves its maturity redemption path.

What changes when PT reaches maturity?

At maturity, Pendle PT reaches its redemption state and becomes claimable in the market’s accounting asset. The discounted purchase has completed its term, so redemption replaces the pre-expiry market sale as the direct exit.

At or after maturity, 1 PT redeems for 1 unit of its accounting asset through the applicable SY conversion. Open the matured asset from the Dashboard, where the position view exposes Roll Over and Redeem All. For a clean exit, choose Redeem All, select the supported output token, inspect the route, and confirm the required wallet action. The contract consumes the PT, redeems the principal through SY, and sends the routed output to the stated receiver, as covered in Pendle finance walkthrough.

Cross-chain PT follows the route displayed by the matured position, including any bridge stage needed to reach the redemption chain. Check the final destination rather than stopping at an intermediate receipt. The exit is complete when the PT balance falls by the redeemed amount and the chosen output arrives at the expected address and chain.