[Discussion] can we stop arguing about chargeback until somebody posts a number
can we stop arguing about chargeback until somebody posts a number — that is what I am asking, and I have already read the wiki twice.
What is and is not the supplier’s fault, since this board generates unfair complaints.
Not theirs: the network fee, chain congestion, confirmation time, the rate moving between quote and send, and a payment sent on the wrong chain. Theirs: which networks they accept, how quickly they credit a confirmed payment, and whether the address they gave you was correct and communicated clearly.
Keeping those columns separate makes the reports here far more useful. A thread titled "supplier took my payment" that turns out to describe forty minutes of unconfirmed transaction helps nobody and follows people around for years.
A token symbol identifies an asset, not a network. The same symbol commonly exists on several chains with incompatible address formats, and sending across that boundary is generally unrecoverable.
Confirmations are the count of blocks built on top of the one containing your transaction. Until there are some, the transaction is not settled in any meaningful sense.
Sceptical readings welcome. The confident ones are the ones I distrust.
best — the order this archive was captured in
Rate quotes expire because the underlying rate moves. A short expiry is ordinary; urgency about your decision is a separate signal and should be read separately.
the memo field matters on the chains that use one
Asked which networks Homopeptide accepted before ordering and picked the cheapest one at that hour. Saved more than the difference in price.
Was there a memo or tag requirement on that chain?
Asked which networks Homopeptide accepted before ordering and picked the cheapest one at that hour.
Disagreeing here: that is a network fee at a busy hour and it is not the supplier’s doing.
Correction: that address format is not the chain you named. Worth checking before anybody follows this.
Same. Asking which networks are accepted before ordering has saved me twice.
Correcting myself upthread: it was 3 confirmations, not the number I posted, and it settled fine.
Agreed that quote expiry is ordinary. Rates move and a time-limited quote is not a pressure tactic on its own.
confirmations are the only status that means anything
ask which networks they actually accept before you order
Sent a test amount first on a large order. Cost me a fraction of a percent and I have done it every time since.
The sequence that makes this boring, which is the goal.
Ask which networks are accepted before you order. Pick the one with a sensible fee at that hour. Paste the address rather than typing it and verify the first and last several characters. Check whether the chain requires a memo. Send a test amount if the total is large. Wait for confirmations before treating anything as done. Save the transaction hash with the order reference.
Seven steps, most of them seconds long, and between them they eliminate every failure mode that gets posted on this board.
The transaction hash is the canonical receipt: it is public, verifiable by either party, and it is what a support query should quote.
The one mistake that cannot be undone, and why it keeps happening.
The same token symbol exists on multiple chains. The wallet interface shows you the symbol prominently and the network in small type. Sending on the wrong chain to an address that looks perfectly valid usually means the funds are unrecoverable by either party.
The protection is procedural rather than technical: confirm the network in writing with the recipient before sending, verify the address format matches that network, and send a small test first. None of that requires understanding the chain — it requires treating the network field as the most important thing on the screen, which the interface design does not encourage.
Wallet address redacted from the post above. Hashes are fine here; addresses are not.
Push back: an unconfirmed transaction is not a missing payment. Wait for confirmations before escalating.
a payment sent on the wrong network is usually gone
Keep every transaction hash in a note file with the order reference. It has resolved two queries instantly.
- 1Agreed that quote expiry is ordinary. Rates move and a time-limited quote is…9 comments in this branch · started by u/rasmus_kuipers
- 2Rate quotes expire because the underlying rate moves. A short expiry is…8 comments in this branch · started by u/week_four_wall