All solutions

In-person commerce

Run counter payments from the hardware you already have

Use XRPay POS in a browser, present a scannable payment request, and record the sale against the register and employee who created it.

Where the flow breaks

The operational problems behind the payment

  1. 01Dedicated terminals add hardware and maintenance costs
  2. 02Card fees put pressure on already narrow margins
  3. 03Busy counters need an unmistakable payment status
  4. 04Unattributed sales make shift reconciliation harder

How money moves

Three steps from request to recorded outcome

  1. 01

    Enter the order

    Build the sale from the shared product catalog and add any configured tip.

  2. 02

    Present the payment

    Show the customer a QR code or supported checkout option on a tablet, phone, or computer.

  3. 03

    Confirm the register

    XRPay records the result with the location, terminal, and signed-in employee.

Why it fits

Built around the work restaurants & cafés already do

  1. 01

    Hardware-light setup

    The register runs in a modern browser, so teams can begin with an existing tablet or computer.

  2. 02

    Clear counter status

    Pending, confirmed, expired, and failed states help staff decide what to do next.

  3. 03

    Shift accountability

    Employee PINs and register attribution keep sales connected to the person and location that accepted them.

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.

  • Browser POS
  • Kiosk mode
  • Tip presets
  • Employee PINs
  • QR payments
  • Daily sales reporting

Questions

Details that affect setup

Do I need special POS hardware?

No dedicated XRPay terminal is required. XRPay POS runs in a modern browser on a tablet, phone, or computer. The device still needs a reliable internet connection and a screen the customer can scan.

How does tipping work?

The merchant can configure tip presets or allow a custom tip. The tip becomes part of the payment request and is recorded with the sale.

How quickly does the register confirm payment?

Direct XRPL payments typically confirm in 3–5 seconds. Card, bank, mobile-money, or conversion routes use the timing and status model of the selected provider.

Set up a browser register

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.