Swap SUI to XRP

FromSui
ToBase
ENTER AMOUNT
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.
XRP / USD
Price
24h
High
Low
Vol

What you need to know

SUI input identity and handling

Sui is classified as a native asset for this route. SUI uses a quote-selected representation. Native SUI exists on one recorded origin network; other network forms require representation checks. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model.

XRP output identity and receiving

XRP is classified as a native asset for this route. XRP uses a quote-selected representation. Native XRP exists on one recorded origin network; other network forms require representation checks. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.

Mistakes specific to SUI to XRP

Verify both asset identities, the selected network, current deposit instructions, and the receiving representation.

SUI source handling versus XRP receipt

Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.

Representation transition for this direction

SUI leaves as a quote-selected representation. XRP arrives as a quote-selected representation.

Private Route for SUI → XRP

Sui account, object, transaction-effect, and fee activity remain public, and XRP Ledger addresses, transfers, amounts, fees, and timing remain public. For this SUI on Sui to XRP on XRP Ledger path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Sui hexadecimal account address with an object-based asset model and destination-side Classic XRP Ledger r-address; some custodial destinations also require a destination tag; it does not hide either chain's public records.

  • Reduces the obvious link between the SUI deposit and XRP receipt
  • Compare standard and Private Route options for Sui → XRP Ledger
  • Shows what remains public on Sui and XRP Ledger before you deposit
Check Private Route availability →

Related routes

Swap SUI to XRP FAQs

Why does the SUI to XRP direction matter?

Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. On receipt, Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.

What changes between the source and destination asset roles?

SUI is the deposited native-asset input; XRP is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.

What should be matched before sending SUI?

Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. Match the source network shown by the quote. Confirm the destination network in the quote. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.

Can I swap SUI on Sui to XRP on XRP without KYC?

Requirements are checked for the live SUI Sui to XRP XRP quote. Verification requirements can depend on the provider, amount, jurisdiction, and current route. Sasquatch does not verify this route as universally no-KYC; check the live flow before continuing.

View all Help Center FAQs →