All solutions

Specialized commerce

Use direct wallet payments without hiding the compliance rules

Lawful businesses can add direct XRPL payments that do not use card-network chargebacks. Provider-backed funding and payouts remain subject to eligibility, verification, monitoring, and provider terms.

Where the flow breaks

The operational problems behind the payment

  1. 01Card pricing can rise with a processor's risk classification
  2. 02Reserves and holds make available cash difficult to predict
  3. 03Dispute ratios can threaten a card-processing relationship
  4. 04Payment availability changes across industries and jurisdictions

How money moves

Three steps from request to recorded outcome

  1. 01

    Confirm the business is eligible

    Review applicable law, XRPay terms, and the requirements of any external provider before enabling a route.

  2. 02

    Offer a direct payment option

    Create a wallet payment request that settles to the configured merchant destination after confirmation.

  3. 03

    Keep other routes distinct

    Treat card, bank, conversion, and payout services under their own dispute and compliance rules.

Why it fits

Built around the work businesses with complex payment needs already do

  1. 01

    Direct settlement

    Supported direct XRPL payments settle to the configured merchant wallet rather than a card acquirer balance.

  2. 02

    No card-network dispute on direct payments

    A confirmed on-ledger payment is final, while merchant-initiated refunds remain separate transactions.

  3. 03

    Explicit provider boundaries

    Eligibility, holds, monitoring, and prohibited-use rules remain visible for regulated funding and payout routes.

Direct settlement

Know which route you are using

Direct XRP and RLUSD payments require a compatible wallet and typically confirm on the XRP Ledger in 3–5 seconds. They settle to the merchant destination configured for that payment.

Provider-backed routes

Availability and timing can change

Card, bank, mobile-money, conversion, and payout services depend on country, currency, verification, provider coverage, fees, limits, and processing time. XRPay shows the available route before confirmation.

Available tools

Use only what the workflow needs

Start with one payment surface and add adjacent commerce tools when the business process requires them.

  • Direct wallet settlement
  • Payment links
  • Transaction records
  • Merchant refunds
  • API and webhooks
  • Route-level status

Questions

Details that affect setup

Does XRPay make every industry eligible?

No. A payment method does not override applicable law, XRPay terms, sanctions rules, or an external provider's prohibited-use and eligibility requirements. The merchant is responsible for operating lawfully in every jurisdiction it serves.

Can a direct XRPL payment be charged back?

A confirmed XRPL payment does not use the card-network chargeback process. A merchant can issue a separate refund. Provider-backed card or bank payments retain the dispute rules of the selected provider.

Continue reading

Review direct payment options

Starter is $0 per month. The 0.5% platform transaction fee and any network, provider, conversion, FX, or payout costs depend on the route used.