The three artifacts and what each one proves
The transaction hash proves movement: a specific amount of a specific asset crossed from one address to another at a specific block, permanently and verifiably by anyone. It says nothing about intentions — only about what physically happened on the chain.
The accepted quote proves terms: the reference rate, the spread, the fee, the amounts on both legs, and the timestamp of acceptance. It is the difference between "I was promised a number" and a number with a timestamp and a breakdown. The chat record proves the agreements around the deal: confirmed requisites, answers from support, decisions taken mid-flight. Together the three cover past, terms and context — the anatomy of any disagreement.
- Hash — what moved, where, when. Public and self-verifying.
- Quote — at what terms, accepted when. The contractual spine.
- Chat — what was agreed and answered. The context.
Collecting them while it is still calm
The trick with evidence is that it is gathered during the deal, not during the fight. In GF-PAY the request itself accumulates the record: the hash appears in the request when the transfer matches, the quote and its timestamp live in the request header, and the coordination happens in the request chat. One screenshot habit at closing time — request screen, hash, final chat messages — covers everything.
For the fiat side, add the payout confirmation from your bank or wallet: the statement line with the amount, currency and date. This is the artifact that separates "the service never paid" from "the bank posted it late or net of its fee" — two situations that look identical from inside a messenger.
Presenting the case so it holds
A good dispute message is a timeline, not a mood. Structure it as: the request number, what was agreed and when, what happened on the chain (hash plus what the explorer shows), what the bank statement shows, and the specific gap you are asking to resolve. Support can act on a timeline in minutes; a mood takes rounds of clarifying questions.
One honest limitation: the hash proves the chain half, and the statement proves the fiat half, but neither proves what two people said in a call. Keep the substance in writing — if a conversation happens by voice, the summary sent into the chat afterwards ("as discussed: ...") converts it into evidence. This habit is worth more than any escalation.
The classic disputes, mapped to their evidence
"The payout is less than the quote": quote + bank statement. The statement shows whether the difference left at the service (recalculation, visible in the request) or at the bank (conversion, incoming fee) — the two require different conversations.
"I sent it but the request is not paid": hash + explorer output. If the chain shows the transfer confirmed on the right address in the right amount, the question narrows to the request's state; if the amount or the address differs, the hash is exactly what support needs to start the manual match. "My payment never arrived at all": bank statement plus chat — the confirmed requisites in the chat are the reference the bank trail is compared against.
Directions covered here
Receiving payments on a pool of addresses
When many people need to pay you in USDT, the fragile part is telling their transfers apart. The pool approach gives every request its own receiving address and its own exact amount, so each incoming transfer identifies itself by where it landed and for how much.
Learn moreOTC: large amounts, individual terms
Above a certain size, a deal stops being a retail exchange and becomes a small project: the price is negotiated, the execution is split into steps, and every agreement lives in the request chat in writing. This direction exists for that scale.
Learn moreFrequently asked questions
Can a transaction hash be faked?
A real hash refers to a real on-chain transaction that anyone can look up in a public explorer — a fabricated hash simply points to nothing or to someone else's transfer, which the first lookup exposes. Verification does not require trusting the person presenting it.
What if the chat was in Telegram and I deleted it?
The request record in the application retains the deal data — amounts, hash, status — regardless of your local chat. The chat messages around it, however, are your copy; this is a reason not to clean dialogs with services, or to export the important ones when closing a large deal.