XRP invoices & payment records
Create saved payment requests, share them safely and verify settlement.
Browse all 38 guides
Create an invoice
Verify the receiving Mainnet wallet in Profile using Xaman, Ledger or CROSSMARK. This proves ownership for database access; it does not send a ledger transaction.
Connect or view the same receiving wallet in Receive, select the invoice network and enter the XRP amount. Title, due date, tag and public note are optional.
Create the invoice. The service saves the recipient, exact XRP amount, network, tag, memo and unique InvoiceID.
Share the generated link. Confirm the full payment details with the payer through another trusted channel.
Treat links as untrusted requests
The link identifies a stored request, not a verified business or proof that goods were supplied. A copied link can be substituted. Review the full recipient, network, amount, tag, memo and InvoiceID before signing. A due date is request metadata, not a ledger restriction.
Old links containing editable invoice JSON are rejected. Import your older browser records into the verified receiving wallet, then issue new database links.
Saved records and recovery
Invoice records are held in the service database and accessible from the same verified wallet on another device. Clearing browser data signs you out but does not erase server invoices. Keep independent accounting records; database storage is not a promise of a particular backup or recovery SLA.
Older browser invoices can be imported from Receive. Imported payment status is not trusted; settlement must be verified again. The import preserves records belonging to other receiving accounts.
Verify an invoice payment
A Paid status requires a successful validated payment matching the network, recipient, exact delivered XRP, destination tag, InvoiceID and memo. Recent account history can find candidates; the Verify payment hash action can check an older transaction.
An Awaiting payment label does not prove no payment happened. A payment with a missing reference may need manual reconciliation outside this invoice match. Never pay twice simply because a label has not updated.
PDFs, QR codes and privacy
Print / Save PDF creates a snapshot. The printed receiving-address QR does not carry all payment details; enter and compare them separately. The on-screen invoice-link QR opens the request.
Anyone with a share link can read the invoice. Public memos become permanent ledger data once paid. Keep confidential customer information, tax IDs and secrets out of titles and notes.