Payment mechanics and the recovery options that do not exist posts 61–90
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
The most useful reply I ever got about payment mechanics was a request to state my units. It sounds like pedantry and it has saved me twice.
Reporting rather than recommending, on payment mechanics. What happened is above. Whether it should have is a different question and not one I am qualified to answer.
Confirming the total before paying rather than after is obvious and is skipped constantly, particularly where shipping is added late.
Currency conversion: payment in your local currency often involves a conversion fee. Paying in the supplier's native currency sometimes saves money, sometimes costs more. Compare before committing.
Ask what happens if the material fails independent testing before you order, not afterwards. The answer is informative and costs one email.
Picking up post #65: that is the part I would want checked first.
What I can speak to on payment mechanics is narrow, so I will keep it narrow rather than generalising from it. Beyond that boundary I do not know.
Recurring billing: if a supplier sets up recurring billing by default, understanding the terms for cancellation is important before the first charge.
Building on post #69 rather than restating it.
Adding a reference point for payment mechanics. Mine is a single case, collected without controls, and I am posting the method alongside it so it can be discounted appropriately.
Fraud and scams: if a supplier demands payment upfront with no recourse if delivery fails, you are taking a risk. Reputation and history of other buyers matter.
That has held every time I have looked, which is not the same as always.
Post #70 put the caveat in the right place and I want to underline it.
Chargeback reality: if you pay by credit card and the supplier does not deliver, you can attempt a chargeback. Suppliers know this and many require non-chargeable payment (transfer, crypto) as protection against it.
Anyone who has looked at this more carefully, please correct the record.
The arithmetic in post #72 is right; the assumption feeding it is the part to check.
Payment mechanics was covered in the wiki last year and the page has a review date on it, which is a better starting point than my memory of a thread.
Documentation and tax implications: payments you make for compounds might have implications for tax reporting depending on your jurisdiction. Keeping clear records matters.
One caution on payment mechanics: everything above assumes the underlying documentation is what it claims to be. That assumption is doing real work and is rarely stated.
No payment facilitation: this site does not handle payments and does not connect buyers and sellers for the purpose of payment. We discuss logistics and documentation of the process but not the commerce itself.
I am not the right person to answer the follow-up to this.
This settles it for me, at least until somebody posts a reason it should not.
Post #74 describes the usual case. This is about the unusual one.
The version of payment mechanics that I was taught turned out to be a teaching simplification. Useful, and not true in the way I had assumed it was.
This follows post #76 rather than contradicting it.
Partial shipment with the balance to follow should be agreed in advance rather than discovered on arrival. Where it is agreed, it is unremarkable.
I have been on both sides of the payment mechanics argument in this category within eighteen months, which should tell you how strong the evidence for either side is.
Post #79 is right about the mechanism and I think understates the practical bit.
A first order deliberately smaller than you need is the standard risk-limiting approach here and it costs a little more per unit for a reason.
Collapsed as off-topic by two members at trust level 3 or above
Whatever the answer on payment mechanics turns out to be, the method for getting there is the same: state the assumption, do the arithmetic in public, invite the correction.
On payment mechanics, I would rather understate and be corrected upward than overstate and be quoted. That is a house style here and it is a good one.
I had written a reply contradicting post #84 and deleted it. Here is what survived.
Recording the time from payment to dispatch is worth doing, because it is the part of the process most within the supplier's control.
Useful. I had the fact and not the reason, which turns out to be the important half.
Payment mechanics is a good example of a question where the honest answer is boring and the interesting answers are unsupported. I would go with boring.
Adding a small correction to the payment mechanics summary above rather than a disagreement with it. The substance holds; one of the figures is out by a factor that matters.
Payment mechanics: I have looked for the primary source twice and failed twice. Either it does not exist or it is somewhere I do not know to look, and I would like to know which.
Suggested topics
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Currency conversion and the cost you did not see
Currency conversion and the cost you did not see — setting out what I have, and where I think it stops being reliable. Currency and fees, set out so that the comparison can be checked. Quoted amount,…
|
2 | 44k | 2mo | |
|
Coming back to: Payment method and the leverage it gives you, ranked
Payment method and the leverage it gives you, ranked — setting out what I have, and where I think it stops being reliable. A payments question, with the mechanics separated from the money. What I would like…
|
+21 | 26 | 43k | 2d |
|
[2026 update] Currency conversion and the cost you did not see
Posting this under the heading it deserves: Currency conversion and the cost you did not see Everything below is what sits behind that. Currency and fees, set out so that the comparison can be checked. Quoted…
|
+21 | 26 | 52k | 2d |
|
A payment that went through twice: how it was resolved
A payment that went through twice: how it was resolved Writing it up because I had to work it out twice and would rather nobody else did. A payments question, with the mechanics separated from the money. What…
|
+20 | 24 | 55k | 3mo |
|
Second pass at: Why chargeback is not the safety net people assume
Second pass at: Why chargeback is not the safety net people assume Writing it up because I had to work it out twice and would rather nobody else did. Asking about the record rather than the transfer. Every…
|
2 | 25k | 3mo |
Related topics — sharing the tags documentation quality, research use only, payments
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Second pass at: Import rules for personal quantities, by jurisdiction, dated
Second pass at: Import rules for personal quantities, by jurisdiction, dated Writing it up because I had to work it out twice and would rather nobody else did. Asking what a regulator's document actually…
|
2 | 5k | 11mo | |
|
Coming back to: Payment mechanics and the recovery options that do not exist
On the subject in the title: Payment mechanics and the recovery options that do not exist Working notes rather than a conclusion. A payments question, with the mechanics separated from the money. What I would…
|
+7 | 11 | 2.6k | 7mo |
|
Reading a regulatory notice rather than an article about it — what changed since
Reading a regulatory notice rather than an article about it — what changed since — setting out what I have, and where I think it stops being reliable. Asking what a regulator's document actually says, since…
|
+28 | 32 | 640 | 13mo |
|
Coming back to: When "no data" is the complete and final answer
When "no data" is the complete and final answer I have a specific reason for asking rather than idle curiosity, and the context is below. Asking about the compound itself rather than about a trial of it. I…
|
+77 | 82 | 12k | 11mo |
|
Second pass at: Cost versus information: making the trade-off explicitly
Posting this under the heading it deserves: Second pass at: Cost versus information: making the trade-off explicitly Everything below is what sits behind that. Posting a small dataset on Cost versus…
|
+23 | 27 | 6.1k | 22h |