ONV Exchange Safety & Instructions
Goal: alert -> open exchange -> enter amount -> scan QR/open wallet link -> transaction status updates with tracking code.
Tracking code is shown immediately when an exchange intent is created. Final settlement still depends on chain/provider confirmations.
Interim settlement policy: until full ONV monetary rails are operational, selected routes may use established fiat-referenced stablecoins for execution and settlement continuity.
How It Works
- Open exchange from your alert link. Pair can be prefilled.
- Enter amount and destination XRPL wallet address.
- Review live quote, fees, and expiry timer.
- Create exchange intent and copy tracking code.
- Scan QR or open wallet deep link to sign the non-custodial route.
- Keep page open until status reaches Completed.
Safety Checks Before Paying
- Confirm destination address and XRPL network are correct.
- Confirm trustlines exist for required issued assets.
- Confirm issuer addresses match the approved instrument list.
- Confirm quote has not expired before signing.
- Sign only from the wallet that holds the source asset.
- Never send funds without a visible tracking code.
- For large amounts, test with a small amount first.
Fault Prevention (Automatic)
- Two-step flow only: quote first, then create exchange intent from that quote.
- Intent expiry lock: expired quotes cannot be paid against (fresh quote required).
- Strict route validation: source asset, destination asset, chain, and destination address must match intent.
- Idempotency key per request to prevent duplicate intent creation from double-clicks/retries.
- Duplicate-payment guard: if payment hash already linked to an intent, block second processing.
- Pending-intent protection: warn user and block creating a second intent while one is still pending.
Status Timeline
| Status | What It Means |
|---|---|
| Awaiting Payment | Quote/intent created. Tracking code is live. |
| Payment Detected | Submitted transaction hash detected for this intent. |
| Confirming | Ledger validation/confirmation checks are in progress. |
| Completed | Intent is marked complete after confirmed validation. |
| Expired/Failed | Intent expired, validation failed, or route requirements were not met. |
Wallet Requirements
Direction matters by pair, but the rule is simple: if two different chains are involved, users need one wallet per chain.
| Route Type | Wallet Requirement | Typical |
|---|---|---|
| XRP <-> PAXG / KAG / ONV | Xaman wallet with verified issuer trustlines configured | 1 wallet |
| XRP <-> RLUSD / EURCV | Xaman wallet with stable-rail trustlines configured | 1 wallet |
| Any issued-token pair (for example PAXG <-> KAG, ONV <-> EURCV) | Xaman wallet only; both issuer trustlines must exist | 1 wallet |
Wallet Setup (Official Links)
Use official wallet sources only. Avoid sponsored search ads and clone domains.
Version policy:
- Use the current official stable Xaman release.
- Verify issuer addresses before opening trustlines (do not trust ticker alone).
- Ensure trustlines are active for both sides of the selected issued-token route.
- Keep sufficient XRP reserve for account requirements and transaction fees.
-
Xaman (XRPL wallet)Use for XRP and all XRPL-issued token routes.
-
XRPL Trust Lines OverviewHow trustlines work and why issuer verification matters.
-
XRPL Currency CodesReference for token currency code formatting on XRPL.
Recovery: if a transaction appears delayed, keep your tracking code and payment hash, and use the Exchange status/lookup flow first.
Do not create a second request while the first intent is still pending.