Is an escrowed payment sensible for an order shipping to Norway?

What I am working with: an escrowed payment · Norway.

The failure mode I am trying to avoid is making this decision emotionally.

I have twelve months in view and I would like the plan to survive that long.

What would you do, and what would make you change course?

Public blockchains are not private; they are pseudonymous ledgers that are permanent and searchable by anyone forever.

Bank transfers create a record with both banks, generally have no reversal mechanism once settled, and are the method with the least recourse for the most traceability — the worst of both.

Put another way, public blockchain transactions are permanent, globally readable and linkable. Chain analysis routinely deanonymises addresses through exchange on-ramps, and the record does not expire.

Keep your own records whatever you use. You will need them.

edited 28 Apr 2025 by w_okoye — fixed an arithmetic slip in the third paragraph

Answer first: the practical privacy question is what a payment record reveals and to whom, and the answer differs by method more than most people assume.

Using a dedicated email address per merchant makes any subsequent breach traceable to its source and costs nothing to set up.

Keep your own record of every transaction regardless of method: date, amount, reference, and what was ordered. This is the documentation you will need if anything requires resolving.

Merchant payment-data breaches are a well-documented and recurring exposure across e-commerce generally.

A dedicated email address per merchant is free and genuinely useful.

Whatever the method, keep your own records — they are what you will need if anything needs resolving.

Any method routed through a regulated exchange creates identity records at that exchange under standard customer-identification requirements, which is where most linkage actually happens.

Whatever a merchant says about not storing details, assume they do. Design around the assumption rather than the assurance.

Decide what you are protecting against first. Most of this question dissolves at that step.

The relevant point is that chargeback protection and privacy pull in opposite directions, and you cannot have both.

Card payments create a record with the issuer, the acquirer and the merchant, and they carry a chargeback mechanism. That mechanism is the only consumer recourse in this entire space and it is not nothing.

Public chains are permanent and searchable. Pseudonymous is not anonymous.

This is a question about record-keeping rather than about secrecy, and reframing it that way makes it tractable.

Merchant data breaches are the realistic exposure for most people, and the mitigation is minimising what the merchant holds rather than choosing an exotic payment rail.

Card scheme chargeback rules are published and provide a defined dispute mechanism with time limits, which no other common method offers.

No payment method makes an unlawful act lawful, and privacy is not a defence.

A chargeback is the only recourse mechanism in this space. Price that in.