Accept XRP payments
easyway accepts XRP on the XRP Ledger through the same API, hosted checkout and webhooks as every other coin. Payments are credited as soon as their ledger is validated, usually within seconds.
Network, confirmations and limits
| Network | API id | Credited after | Min. withdrawal | Withdrawal fee |
|---|---|---|---|---|
| XRP Ledger | XRP | 1 validated ledger | 0.35 XRP | 0.02 XRP |
The platform fee is 0.5%: a customer paying 100 XRP leaves you 99.5 XRP. Other coins are on the pricing page.
One address, one destination tag per invoice
Every XRP account has to keep a base reserve locked on the ledger, so creating a new account for every invoice would tie up XRP for each one. Instead, like exchanges do, every invoice is paid to one receiving account and gets its own numeric destination tag. The tag is what matches a payment to its invoice.
The checkout shows the address and the tag side by side, each with a copy button, and warns that the tag is required. The QR code holds the address only, so the payer still types or pastes the tag in their wallet. When paying from an exchange, the tag goes into the field the exchange calls "Destination tag", "Tag" or "Memo".
A payment that arrives without a tag, or with a tag that belongs to no invoice, is not credited to anyone automatically: it is logged for a manual review instead of being guessed onto an order.
How a payment is detected
Only validated ledgers are read. On the XRP Ledger a validated transaction is final, so the invoice is credited after one validated ledger instead of waiting for a number of blocks. Before it is reported, a second, unrelated XRP Ledger server has to show the same payment.
The amount counted is the ledger's delivered_amount, not the transaction's Amountfield. A "partial payment" can name a large Amount while delivering only a fraction of it — reading the delivered amount means such a payment is counted for what really arrived, and the invoice turns underpaid instead of paid. Transfers under 0.01 XRP are ignored as spam.
Price and payouts
An invoice priced in USD is converted to XRP when the customer picks it, at the rate locked for that invoice. The XRP you receive stays XRP: easyway holds the balance until you withdraw it to an address you have whitelisted, and nothing is swapped. If you withdraw to an exchange, add the destination tag the exchange gave you when whitelisting the address — withdrawals carry it.
Integrating XRP payments
Create an invoice with currency set to "XRP", or price it in USD and let the customer choose, then redirect to the hosted checkout. The API invoice's pay_memo field holds the destination tag if you build your own payment screen. A signed webhook fires when it is paid; see the quickstart and the webhook guide.
Also accepted
USDT on TON uses the same one-address-plus-memo flow. Other options: Bitcoin, USDT on TRON, USDC and more on the pricing page.