[Vendor] FGP order #23 — Germany, 12 days, no drama, receipts inside
FGP order #23 — Germany, 12 days, no drama, receipts inside. Order-by-order, with dates, because vibes are not data.
Numbers, in the order they matter: 12 days.
Sent a test amount first on a large order. Cost me a fraction of a percent and I have done it every time since.
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.
Screenshot none of this. Read the whole thread, including the parts where I am told I am wrong.
- FGFGP source pageFlourishglobal Peptide Biotech (Chengdu) Co., Ltd. · Chengdu · 89% here, rank 20 · shop at flourishglobalpeptide.net →
nofollow and sponsored; nobody here is paid for it.best — the order this archive was captured in
Network fees are set by chain congestion at the time of sending. They are paid to the network, not to the recipient, and they vary by hour as well as by chain.
network and address, checked twice, before anything else
[removed by moderator]
Memo requirements are chain-specific. The chain you are describing does not use one.
the memo field matters on the chains that use one
Correcting myself upthread: it was 18 confirmations, not the number I posted, and it settled fine.
fees vary by chain and by hour, not by supplier
fees vary by chain and by hour, not by supplier
zaid_dahlberg is right about confirmations. "Sent" is not a status.
How many confirmations does it show?
Yes — the same token symbol on two chains catches people constantly and it is unrecoverable.
Correction: that address format is not the chain you named. Worth checking before anybody follows this.
Was there a memo or tag requirement on that chain?
A test transaction costs one extra network fee and verifies the address, the network and the recipient’s crediting process before the main amount moves.
Left up. It has a hash, a chain and a timeline, which is what a payment report needs.
Small fix — that is the network fee, not a supplier charge. The distinction matters for the complaint you are making.
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.
ask which networks they actually accept before you order
The transaction hash is the canonical receipt: it is public, verifiable by either party, and it is what a support query should quote.
Cosigning on keeping the hash. It is the only receipt in existence and people screenshot their balance instead.
Some chains require a memo or destination tag to route funds to the right account. Omitting it on those chains is one of the more common ways payments go astray.
nobody legitimate needs the payment in the next ten minutes
Push back: an unconfirmed transaction is not a missing payment. Wait for confirmations before escalating.
screenshot the transaction hash, not the wallet balance
nobody legitimate needs the payment in the next ten minutes
Agreed — and the hash is the receipt. Nothing else is.
I would not treat a delayed confirmation as evidence of anything at all. Chains have busy hours.
- 1Network fees are set by chain congestion at the time of sending. They are…9 comments in this branch · started by u/saskia_wojcik