HPAY: read your inbox

This guide shows you how to read an address's QUAI or direct WQI activity in the HPAY inbox at hartiipay.app/hpay/inbox. QUAI candidates are discovered through Quaiscan and checked again against the Quai node. WQI candidates are scanned from the reviewed token's events on the node and checked against the transaction, receipt and canonical block.

Who it's for: anyone who wants to look back at what came in and went out, a shop or a person who wants a CSV for their books, or anyone checking an address. The inbox is Beta: it is tested by our own test suites.

There is nothing to sign up for. The address is the account.

#Invoice requests: first ten wallets

The sponsored campaign has ten places, one per unique proved wallet, for exactly 25 QUAI each. A proved wallet does not establish one unique person. Requests wait for sponsor approval; submitting one does not promise a payment.

#Request 25 QUAI

1. Open Request 25 QUAI and check the available places.
2. Enter your @username or public wallet. Connect the wallet that owns that address on Quai mainnet, Cyprus-1. A username must resolve to your connected wallet.
3. Press Sign free request for 25 QUAI and review the ownership message in your wallet. This signature sends no transaction, costs no gas and requires no transfer or deposit.
4. Keep the request ID shown on the page. Your request is pending sponsor approval. A repeated request from the same wallet returns its existing record, without taking another place.

#Review and pay as the sponsor

1. Open the existing HPAY inbox, expand Invoice requests, then press Open invoice requests. Connect the sponsor wallet and sign its free ownership message. Viewing another address's public payment history does not grant access to these records.
2. Choose pending rows individually, or Select all pending, then press Review selected requests. Review every full recipient address and its 25 QUAI amount.
3. Review the Live Airdrop fee, Estimated gas and Maximum total. Paying all ten requests means 250 QUAI for recipients, plus the existing Airdrop contract's fee and network gas. HPAY reads quoteFee for the selected recipient count and rechecks it before asking the wallet to pay. The fee can change; use the displayed live quote.
4. Press Accept and pay for that reviewed batch, then approve its one payout transaction in your wallet. This is a separate approval from the free session signature. The existing Airdrop contract pays every selected recipient together or reverts the whole batch; a revert can still cost gas.
5. Keep the original hash. The server marks the batch paid only after checking the exact payout, canonical receipt and block, a mined height after preparation, and 12 confirmations. Twelve is a policy threshold, not a measured guarantee of irreversibility.

#Resume or check an earlier batch

After a reload, reopen the sponsor session. A batch prepared before wallet invocation can be reviewed again with Review reserved batch, or released with Cancel review. A classified wallet rejection or explicit pre-broadcast node rejection can be reset only through the saved matching attempt's known-unsent report. The server authenticates that report; it cannot independently prove a wallet did not broadcast. A different tab cannot release another tab's attempt.

For a submitted, pending or unknown outcome, use Check payment status with the original transaction hash. Recovery reads the chain and never resends funds. An unknown wallet result remains held even if no hash was returned: check the original wallet activity. A delayed receipt, failed read, empty browser journal or changed domain does not authorize another payment. A verified canonical revert releases the batch only after the same confirmation threshold.

#Request records and privacy

The HPAY server stores the wallet address, exact amount and request status, along with authentication and batch records needed to enforce the campaign. Only the authenticated sponsor can read the invoice inbox. Its free-signature session lasts 15 minutes, with the access token held in browser memory. Reloading requires a new session; prepared or uncertain server reservations survive it.

The browser stores a payout recovery journal on the current origin/device. Preserve the original transaction hash before changing browsers, clearing storage or switching between HPAY and Biome. RPC and hosting services receive the requests needed for this feature; a payout's addresses, amounts and transaction are public on chain. These records are separate from the public payment-history reader described below.

#What you'll need

• A Quai address that starts with 0x00 (Cyprus-1). Your own wallet, or any address you want to look at.
• Optional: a Pelagus or Blip wallet, so the page can open your own inbox for you. Without a wallet you can still paste any address.

#Open it

Any of these gets you there:

• the first entry in the tools list on hartiipay.app/hpay;
• Your HPAY inbox in the Biome wallet panel, once your wallet is connected;
• See it in your inbox after a payment on a /pay page;
• a link with the address in it: https://hartiipay.app/hpay/inbox?address=0x... (add &tab=sent to start on a tab).

#Steps

1. Open the inbox. If your wallet is already connected to the site, the page shows your own inbox. If not, press Connect wallet. This reads/shares your public address only: no signature or transaction is requested. The page then queries public chain sources for the address.
2. To look at another address, open Open any address (view only), paste a 0x00... address and press Open this inbox. An @name, a Qi address or an address outside Cyprus-1 is refused with a plain reason.
3. In Payment asset, choose QUAI or WQI. Wait while the page reads the public sources. The numbers at the top show the selected asset's activity and how many rows were checked.
4. Pick a tab: All, Received, Sent or Needs a look. Each row shows the direction, the other address, the amount, the dollar value when there is a price for that hour, and a check chip.
5. The first window is the last 30 days. Press Load older to read the 30 days before it.
6. Press Export CSV to download what is on screen.

#What the check chip means

Each QUAI payment is read again from the Quai node. A list of 60 payments or fewer checks itself; for a longer list, press Check all with the node. WQI rows are checked against the qualified token, exact transaction and canonical block as they are scanned.

• Checked: the node agrees and the payment has at least 12 confirmations.
• Confirming 3 of 12: the node agrees, but the payment is still young.
• Does not match: the node disagrees with Quaiscan. The node wins, the row appears under Needs a look, and it is left out of the totals. It stays in the CSV.
• Not checked or Could not check: the node was not asked yet, or did not answer.

#New since your last visit

The page counts the payments you received since you last pressed Mark all read. To do that, your browser keeps one time per address you open (at most 20), under a key of its own. Forget what this device has seen clears it. The inbox can also read same-device POS/activity records to show a Known on this device marker; it does not copy local note text into the inbox rows or CSV.

#The CSV

Export CSV downloads the windows on screen, in the order shown. Rows include direction (received, sent or self), transaction hash, addresses, amount, block, confirmations and checked_by_node. WQI exports add the asset, token contract and exact WQI base units; WQI has no historical dollar value. A payment the node disagrees with remains in the CSV with checked_by_node set to no. Unknown values are empty cells, never 0. The full column lists are in HPAY tools.

#What the inbox cannot do

• It cannot tell an HPAY payment from any other transfer. On the chain a QUAI payment looks the same whether it came from a pay link, a point of sale, a split, a button, Pelagus or Blip. WQI rows identify direct transfers from the reviewed token, not the bill or tool that prompted them. This is a payment history, not "all your HPAY receipts".
• Memos, order references and dollar prices from a link are not on the chain. If the same browser made or saw the payment (a point-of-sale sale, your HPAY activity), the row says Known on this device. Another browser or device will not show that.
• The newest plain transfers may lag. They come from Quaiscan's index, which can run behind the node, and the page says so when it is behind. QuaiRelay payments of the last 12 hours are read from the node itself.
• Some things are counted aside, not listed: failed transactions, transactions with no value, cross-zone transfers and other contract calls that carry QUAI. QUAI that other contracts send to the address (payouts, swaps) is not listed, because Quaiscan lists no internal transfers on Quai. WQI scans list direct holder transfers from the pinned token only and are bounded; older or unreadable candidates may be missing, with gaps shown.
• No alerts, no refunds, no disputes. The public payment-history reader sends nothing; it shows what the chain holds when you open it. The separate sponsor invoice panel above can request a reviewed payout from the sponsor's wallet. A refund is a new payment sent by the other person.
• A failed read is never an empty inbox. If a source does not answer, the page names it at the top and says the list may be incomplete.

#Who sees what

The public payment-history reader asks Quaiscan and the Quai node for public-chain data. Those services can see the addresses and requests sent to them, along with normal network metadata. WQI mode scans the public node and uses no price service; QUAI historical prices use a time range only. If you open or share an inbox URL with ?address=, the web host receives the address as part of the static page request. That history lookup does not send the address to a Hartii user or payment API. The separate invoice panel uses the HPAY request service as described above. Anyone can inspect an address's chain payments because they are public chain data.

Anyone can open an address's public payment history, because it is public chain data: it shows the same payments Quaiscan shows. The chain has no private mode. Invoice request records require the sponsor's authenticated session.

#Common mistakes

• "My payment is missing." If it is a plain transfer from the last few minutes, wait and press Read again: the index may be behind. Or the payment is older than the window: press Load older.
• "Nothing in this window." That means the sources answered and found none. If a source failed, the page says "Nothing found, but the chain was not fully read" instead.
• "This is not my receipt for an order." The inbox cannot match a payment to an order reference. Use the point of sale or the Pay with HPAY button, which check the exact tagged amount.
• Wrong network. The inbox reads Quai Mainnet, Cyprus-1 (chain 9).

#Next

The reference for every HPAY tool, including the CSV columns and limits, is HPAY tools. To read what an address received over a long period, see the Statement in the same page.