> For the complete documentation index, see [llms.txt](https://xarez.gitbook.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xarez.gitbook.io/guides/polygon-to-xrpl-bridge/polygon-to-xrpl-bridge-step-by-step-tutorial.md).
# Polygon to XRPL bridge: Step by Step Tutorial
Using [the Rezentix page](https://rezentix.com/) puts the Polygon to XRPL bridge on a single screen, with funds landing in 5 to 20 minutes once your wallet approves. Here is every detail needed to move value from Polygon's EVM side into an activated XRPL account without getting tripped up by reserve rules or missing tags.
### Polygon to XRPL bridge: Seven Steps for First-Time Senders
Step 1: Attach Your Polygon Wallet to the Session
Step 2: [Load the crossing screen](https://rezentix.com/) and Select Polygon and the XRP Ledger
Step 3: Fill the Destination Field With Your XRPL r-Address
Step 4: Add a Destination Tag If Sending to an Exchange
Step 5: Enter What Moves Across From Polygon
Step 6: Give the Wallet Its One Signature
Step 7: Search the XRP Ledger Side for Your Funds
### Readiness Checks for Your POL Balance and XRPL Reserve
* Native POL for Polygon gas: Keep at least $0.5 to $1 worth of POL in your sending wallet so the outgoing Polygon signature clears without an error.
* Activated XRPL r-address: Verify that a brand-new XRPL wallet receives enough XRP to satisfy the ledger's base reserve requirement on activation.
* Destination tag verified: Check whether your receiving platform requires a numeric destination tag alongside the r-address.
* Trust line enabled if needed: If you are receiving an issued token rather than native XRP on the ledger, confirm the trust line is already set on your XRPL account.
### Inside the Handshake From Polygon PoS to the XRP Ledger
When you bridge Polygon to XRPL, you are leaving an Ethereum-compatible proof-of-stake network and settling onto a specialized payment ledger with its own account rules. Different ledger, different rules. Your Polygon wallet signs the outgoing deposit with POL gas, and the relayer dispatches the payout directly to your XRP Ledger account.
Because the XRP Ledger uses r-addresses between 25 and 35 characters instead of Polygon's 0x format, you must pull a receiving string from a separate XRPL wallet — any EVM address pasted into the target box gets flagged as invalid. You won't be able to send funds to your Polygon 0x string on the destination side, so have an XRPL app like Xaman or a hardware ledger ready before you start.
Polygon and the XRP Ledger both clear local transactions in seconds, so any noticeable pause belongs to the bridge verification step between them. Your outgoing Polygon transaction locks in roughly two seconds, while the XRP Ledger closes its ledgers every three to five seconds once the relayer dispatches the payout.
### Total Charges Across POL Gas and XRPL Ledger Fees
Budget between $2 and $9 in total fees when moving Polygon to XRPL. Neither endpoint blockchain is expensive on its own: Polygon block gas paid in POL usually costs just a few cents, and the XRP Ledger burns a fraction of a cent per transaction.
The bulk of that $2 to $9 spread goes toward the cross-chain relayer liquidity and verification service that bridges the two separate ecosystems. Because your Polygon signature is paid in POL, don't empty your entire POL balance into the send box or you'll leave your wallet unable to pay the local gas fee.
Trust the final breakdown on the confirmation prompt over any historical range if the two numbers differ. Live liquidity depth determines the exact XRP arrival figure shown right before you sign.
### Important XRPL Rules on r-Addresses and Destination Tags
* You can review how POL powers transactions on the origin network through the official [Polygon](https://polygon.technology/) portal before funding your wallet.
* Forgetting the destination tag when sending directly to a centralized exchange XRPL address is a costly trip-up that can delay credit. Always check the tag field first.
* Every new personal account on the XRP Ledger requires a small base reserve of XRP locked in the address to activate it on the ledger, a rule documented on [XRPL.org](https://xrpl.org/).
* Entering your r-address into an XRPL explorer confirms whether the incoming payment has cleared the ledger.
### Core Takeaways for Sending Polygon Funds to XRPL
* Total fee window: $2 to $9 across Polygon gas and the relayer crossing spread.
* Expected arrival time: Five to twenty minutes from your Polygon wallet approval to XRPL ledger finality.
* Address requirement: A valid 25-to-35-character XRPL r-address (plus a numeric destination tag if sending to a shared custodial platform).
* Gas token needed: Native POL in your Polygon wallet to sign the outgoing transaction; it's a single-signature flow with nothing to claim on arrival.
### What People Run Into
#### Meeting the base reserve requirement on a new XRPL wallet
Unlike EVM chains where any empty address can hold a tiny fraction of a token, a brand-new XRPL address must receive enough XRP to meet the ledger's base reserve requirement to become active. If you are funding a fresh personal r-address for the first time, make sure your net arrival amount clears that reserve floor.
#### Including a destination tag for exchange deposits
Self-custody XRPL wallets rarely need a destination tag, because your r-address belongs solely to you. Custodial exchanges share one main r-address across thousands of customers and rely on the numeric destination tag to route the deposit to your specific sub-account.
#### Paying Polygon transaction gas with POL tokens
Polygon uses POL as its native gas token for all on-chain signatures. Even when you are sending another asset across the bridge, your Polygon wallet must hold a small balance of POL to broadcast the transaction.
[Visit the Rezentix gateway](https://rezentix.com/) whenever your Polygon wallet and XRPL r-address are set to move funds.
*Elena Brandt — Tests crypto transfers by hand and reports what each screen asks for.*
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://xarez.gitbook.io/guides/polygon-to-xrpl-bridge/polygon-to-xrpl-bridge-step-by-step-tutorial.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
