XDC Outpost XDC Proof

Payment receipts for XDC transactions

Turn any XDC payment into a PDF receipt with a QR code that links to the transaction on XDCScan, so anyone can check it. Make one at a time or a whole batch, for invoices, bookkeeping or trade finance.

  • Web app
  • PDF with QR verification
  • Batch to ZIP
  • Runs in your browser
Create a receipt Make a batch
Example receipt

Create a receipt

Paste a transaction hash to look it up, add what the payment was for, and download the PDF.

Seller (received the payment) · optional
Purchaser (sent the payment) · optional

A square PNG or JPG works best. Some image hosts block use on other sites; if so the receipt is made without the logo and you’ll be told.

Network settings

Use an Apothem testnet RPC for testnet transactions; the receipt’s QR code then points to the testnet explorer.

Address book

Save the names and details behind addresses you deal with often. Receipts then fill them in automatically. Saved only in this browser.

No address book saved yet.
CSV format 
"address","name","company","address_line","phone","email","logo_url"
"xdc1a2b…","Acme Corp","Acme Corporation","123 Main St, Suite 100, New York","555-1000","acme@corp.com","https://example.com/acme.png"
  • address is the wallet address (xdc… or 0x…). name is shown on receipts; company is used if name is empty.
  • Put every value in double quotes, so commas inside addresses don’t break the row.
  • Uploading a new file replaces the saved address book.

Batch receipts

Upload a list of transaction hashes and descriptions, and download every receipt in one ZIP. Names come from your address book.

CSV format 
"tx_hash","description"
"0x7f8c…a7b8c9","Invoice #501: 500 widgets"
"0x1a2b…e5f6a7","Consulting, Q3 2026"
  • Each hash is 0x followed by 64 characters. Rows with a missing hash or description are skipped and listed.
  • Failed or unconfirmed transactions are left out of the ZIP. A summary.csv inside the ZIP lists every row and what happened to it.

Things to know

What a receipt proves

The amount, date, addresses, block and status come straight from the blockchain, and the QR code lets anyone check them on XDCScan. Names, contact details and the description are what you enter, so they’re only as reliable as their source.

Only completed payments

Receipts are only made for transactions that are confirmed and succeeded. Failed or still-pending transactions are refused, so a receipt never shows a payment that didn’t happen.

XDC and token payments

Plain XDC transfers and XRC-20 token transfers are both supported. For tokens, the receipt shows the token amount and the real recipient, not the token contract.

Any language

Names, addresses and descriptions can be in any language. Chinese, Japanese, Korean, Cyrillic, Greek and accented Latin use embedded fonts, which load the first time they’re needed. Scripts like Arabic, Hebrew, Hindi and Thai are drawn by your browser so their letters join and read in the right direction.

Private by design

Receipts are created on your device. The only thing sent anywhere is the transaction lookup to the XDC RPC. Your address book stays in this browser until you clear it.

Need help?

Questions about XDC Proof, a receipt that looks wrong, or a feature you need for your accounts? Message me on whichever platform suits you.