Accept XRP payments on your website
easyway accepts XRP on the XRP Ledger through the same API, hosted checkout and webhooks as every other coin. Payments go straight to your own XRP account and count as soon as their ledger is validated, usually within seconds.
Network, confirmations and limits
| Network | API id | Counted after | Smallest invoice | Fee taken from the payment |
|---|---|---|---|---|
| XRP Ledger | XRP | 1 validated ledger | 0.35 XRP | None |
No fee is taken from a payment: a customer paying 100 XRP puts 100 XRP in your account. easyway earns from subscription plans (Free: 30 live invoices a month; paid plans from $19/month). Other coins are on the pricing page.
One address, one destination tag per invoice
On the Wallets page of the dashboard you enter the address of your own XRP Ledger account. Every invoice is paid to that one account and gets its own numeric destination tag; the tag is what matches a payment to its invoice (destination tag per invoice). Only the public address is stored — no secret key or seed phrase is ever asked for, and easyway cannot move what arrives.
Two requirements for that account. It must be your own wallet, not an exchange deposit address: an exchange identifies its customers by a tag of its own, and a payment carrying the invoice's tag instead would not be attributed to you by the exchange. And it must already be activated, that is, hold the base reserve the XRP Ledger requires of every account.
The checkout shows the address and the tag side by side, each with a copy button, includes them in the QR code, and warns that the tag is required. When paying from an exchange, the tag goes into the field the exchange calls "Destination tag", "Tag" or "Memo" (more on paying from an exchange).
A payment that arrives without a tag, or with a tag that belongs to no open invoice, is not put on any order automatically: it is parked as an unmatched transaction that you assign to an invoice or ignore in the dashboard. The XRP is in your account either way.
How a payment is detected
Your account is followed by a watcher that holds no keys. Only validated ledgers are read. On the XRP Ledger a validated transaction is final, so the invoice turns paid after one validated ledger instead of waiting for a number of blocks. Before a payment 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; the checkout then asks for the remainder. More than asked is flagged as overpaid, and a payment that arrives within some hours after the invoice expired is still recorded and flagged as late. Very small transfers are ignored as spam.
Price and refunds
An invoice priced in USD is converted to an XRP amount when the customer picks it, at the rate locked for that invoice. The XRP you receive stays XRP, in your own account: there is no balance at easyway, nothing to withdraw and nothing is swapped. Refunds are sent by you from your own wallet; easyway holds no keys and cannot move or recover funds.
Three ways to accept XRP on your website
All three end on the same hosted checkout, which shows the receiving address and the invoice's destination tag, so you never handle tags yourself. Pick the one that matches how your site is built.
1. A payment link, no code. In Dashboard → Payment links, create a link with a fixed USD price, or let the customer type an amount within limits you set, and put /pay/link/pl_… behind a "Pay with crypto" button. Each visit creates its own invoice with its own destination tag, and the customer picks XRP on the checkout. Links can also deliver a licence key or other text after payment, or take donations.
2. A store plugin. For WooCommerce, PrestaShop, OpenCart, Magento 2, WHMCS, Blesta and Odoo there is a plugin that creates the invoice at checkout and marks the order paid from the signed webhook. They are in beta, so place a test-mode order before you switch to live.
3. The API, for a custom checkout: below.
Integrating XRP payments with the API
Set your XRP address in the dashboard first. Then create an invoice with currency set to "XRP", or price it in USD and let the customer choose, and 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.
Common questions
Can I accept XRP without writing code? Yes: a payment link behind a button, or one of the store plugins (currently in beta). The API is only needed for a custom checkout.
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.