Skip to main content

Payment proof and confirmations

Submit Proof is for the Buyer on chip Staked only. The screen shows the amount and payment address (copy/QR). You do not edit network or amount. The only input is TX Hash. Button: Submit Proof.

Confirm: “Only submit after you have sent the exact amount to the seller's payment address.”

Always: “Payment proof requires a public on-chain transaction hash. Off-chain, exchange-internal, or private transfers cannot be verified.”

Telegram Mini App Submit Payment Proof in light theme — Buyer, Staked, on-chain warnings; payment address and QR blurred.Telegram Mini App Submit Payment Proof in dark theme — Buyer, Staked; payment address and QR blurred.
Submit Proof. Buyer, Staked — paste the on-chain TX Hash after you send.

Confirmations by payment asset​

Payment verification is per asset — not one confirmation count for every payment asset. Watch Proof submit deadline: and Verification deadline: on the trade.

AssetConfirmations requiredApprox verify waitPayment/proof timeout
Bitcoin (BTC) BTC3~30 min3 hours
Litecoin (LTC) LTC12~30 min2 hours
Ethereum (ETH) ETH32~6.4 min1 hour
Tether (USDT) USDT20 (ERC-20 / Ethereum mainnet)~4 min1 hour
Solana (SOL) SOLfinalized (Solana finalized commitment; not a fixed confirm count)~13 sec30 min

XMR stake has no on-screen confirm count. Stake copy tells you to send with Automatic fee priority in your Monero wallet (avoid Slow).

Per-asset payment rules​

AssetQuoted warning
Bitcoin (BTC) BTCSend on-chain BTC only. Lightning payments are not supported.
Litecoin (LTC) LTCSend public on-chain LTC only. MWEB private transfers cannot be verified.
Ethereum (ETH) ETHSend on Ethereum mainnet only. L2 or sidechain transfers cannot be verified.
Solana (SOL) SOLSend native SOL on Solana mainnet only. SPL token transfers are not supported.
Tether (USDT) USDTSend USDT (ERC-20) on Ethereum mainnet only. TRC-20, BEP-20, Polygon, and other networks are not supported.

Profile for USDT: “USDT ERC-20 on Ethereum mainnet (0x…). Not TRC-20 or BEP-20.”

After proof, the chip moves toward Verifying. When payment is verified, the buyer enters their trade share and taps Receive XMR. Seller during Verifying/Sending sees “Your part is complete” — no Receive/Refund button there.

If proof is late or the hash is unusable, the trade can cancel (payment proof not submitted in time, invalid transaction hash, verification failed). Then the seller uses Request refund if stake remains. See Cancel Trade, Cancel Offer, and /support.

Last updated: 21 September 2026.