Fix tecNO_LINE on XRPL
tecNO_LINE indicates the destination account has no trust line for the currency+issuer in the payment. Create TrustSet on the receiving account (or use a path that does not require that IOU). Native XRP payments use a different flow.
Key facts
- Result code: tecNO_LINE
- Fix: TrustSet on receiver
- Verify: Issuer address, not ticker
- Reserve: ~0.2 XRP incremental typical
Symptoms
tecNO_LINE indicates the destination account has no trust line for the currency+issuer in the payment. Create TrustSet on the receiving account (or use a path that does not require that IOU). Native XRP payments use a different flow.
Common scenarios
Exchange deposits, P2P IOU sends, and airdrops all fail with tecNO_LINE when the receiver never opened a line to that issuer. The sender cannot create a line on someone else’s account.
If both sides need IOUs, each account signs its own TrustSet.
Fix steps
- Identify currency code and issuer from the failed payment metadata.
- On the receiving wallet, Sign TrustSet with appropriate limit.
- Wait for validation; confirm line in account_lines.
- Retry the payment with the same issuer fields.
Verify on ledger
Paste your classic address into Manager or the TrustLine checker to compare currency, issuer, balance, limit, and freeze flags with what your wallet shows.
Cross-check issuer accounts on a public explorer before you Sign TrustSet for a new pair.
TrustSet, tecNO_LINE, and IOU receipts
This page (problems/tecno-line/) sits in the XRPline trust line cluster for xrpline.org. On ledger, issued assets are never identified by ticker alone: every IOU payment path resolves to a currency code plus issuer classic address. When a receiver lacks that RippleState, validated payments commonly end with result code tecNO_LINE rather than crediting balance.
Creating or updating a line is always a TrustSet transaction. LimitAmount.value sets the maximum IOU balance you accept from that issuer. Setting value to zero after clearing balance removes the object and typically lowers OwnerCount. Wallets may hide the JSON, which is why XRPline exposes a Sign TrustSet preview before you approve.
Native XRP transfers do not use this mechanism. If you only hold XRP, reserve math still applies (base plus owned objects), but you will not see tecNO_LINE for missing IOU lines.
OwnerCount, incremental reserve (~0.2 XRP), and Cleaner
Account reserve on XRPL is locked XRP, not a fee. Total reserve ≈ base reserve + (OwnerCount × incremental owner reserve). After network fee voting in late 2024, many operators cite ~1 XRP base and ~0.2 XRP per owned object — always verify live values in your wallet or in XRPline’s network strip.
Each new trust line usually increases OwnerCount by one unless an exemption applies (see first two trust lines). Closing an empty line with a zero balance and a cleared limit can reduce OwnerCount and return incremental reserve once the ledger accepts the transaction.
Users feel “missing XRP” when spendable balance is low even though total balance looks fine. That gap is often reserve, not theft. Each trust line you open for an airdrop or exchange token usually adds one owned object until you remove it.
XRPline Cleaner sorts zero-balance lines so you can reclaim multiple increments of incremental reserve after campaigns. You still sign one TrustSet per removal — we do not batch-sign and we never hold keys.
Issuer verification before you sign
Scammers exploit ticker collisions: two unrelated projects can both display similar three-letter codes with different issuers. Before any TrustSet, copy the issuer r-address from official documentation and match it character-for-character in the signing payload.
Use issuer lookup, issuer discovery guide, and explorer account flags (freeze, authorized trust lines, clawback) documented in Glossary. Risk tab heuristics prioritize review; they are not purchasable rankings and not financial advice — see Methodology.
Cross-links in this cluster
Guides walk step-by-step (set, remove, reserves). Problems decode errors (tecNO_LINE, cannot remove). Intents mirror search wording (check lines, reclaim XRP). Tools route into Manager, reserve calculator, and TrustLine checker.
Ledger checklist before you close this tab
For problems/tecno-line/, keep a personal checklist: (1) copy issuer r-address from official docs, (2) compare account_lines in XRPline Manager, (3) confirm OwnerCount and incremental reserve on live server_state, (4) read TrustSet LimitAmount in the wallet preview before sign, (5) retry IOU payments only after the receiver line exists to avoid tecNO_LINE.
If something still fails, match the transaction result code to a problem playbook, then cross-link to glossary entries for TrustSet, freeze, and trust line limits. XRPline publishes updates as an Organization — not individual author personas — and does not sell paid rankings inside product views.
When you finish maintenance, run Cleaner occasionally to remove zero-balance experiment lines so incremental reserve (~0.2 XRP per object typical) returns to spendable XRP. Native XRP balance is separate from IOU lines but shares the same reserve accounting for owned objects.
FAQ
Can the sender fix tecNO_LINE?
Only by changing payment asset/path. The receiver must add the line for that IOU.
Why did it work before?
You may have changed issuer, deleted the line, or sent a different currency code representation (hex vs ASCII). Confirm details on ledger explorers and in XRPline Manager before you Sign TrustSet.